HWINFO keeps resetting ARGB and dynamic dashboard 3 of MSI x870e godlike

L

lambej

Member
Did a recent build which included the MSI x870e godlike, which has a few extras. It gets detected fine, but two aspects tend to get reset / interfered with:

1. There three ARGB headers, which get reset to default colors. If you re-set them using MSI center, it stays for a little bit but gets reset again eventually.
2. The "Dynamic Dashboard 3" which is an LCD screen. This doesn't _seem_ to get reset periodically, but on initial startup (?).

Can gather any debug data needed.
 
I suspect there's one or more SMBus devices on that board that don't like it when scanned by HWiNFO.
This will require ticking some boxes in the SMBus exclusion list in main settings of HWiNFO.
Would you be able to figure out which of them need to be ticked? I suspect it's in the 20-2F range but will require running several tests to find those causing it.
 
Martin said:
I suspect there's one or more SMBus devices on that board that don't like it when scanned by HWiNFO.
This will require ticking some boxes in the SMBus exclusion list in main settings of HWiNFO.
Would you be able to figure out which of them need to be ticked? I suspect it's in the 20-2F range but will require running several tests to find those causing it.
Click to expand...

Thanks, happy to do the testing, thanks for the quick response! Question, when do the settings get applied? I went through most of the exclusions (and even turned off SMBus entirely) and it still kept reverting, but if I fully close out HWINFO it doesn't happen. So it does seem like HWINFO is resetting it, but unless the SMBus settings only take effect on full restart it may be some other kind of monitoring?

Is there a tool to debug what an app like MSI Center is doing?
 
OK - if I disable SMBus and fully restart HWInfo that seems to fix it... so will try the testing above with restarting the service/app in between.
 
You need to first tick the SMBus exclusion boxes and then start HWiNFO scan.
I'd suggest to start with the entire 2x row and if that fixes it, continue unticking the boxes until you find all those that need to be ticked.
 
I just got feedback from MSI. Try to tick the box belonging to address 2F and let me know if that solved the issue.
1742206260979.png
 
> You need to first tick the SMBus exclusion boxes and then start HWiNFO scan.

Thank you. How do you start the HWiNFO scan? Is that by re-opening the Sensors screen after fully closing out of the settings? I only ask as I am seeing some non-deterministic behavior here, with the only consistent thing being that it only happens when HWiNFO is running.

I also hear the device disconnect/reconnect Windows sound when this happens, but only on when it's reset back to defaults not when Mystic Light resets it.
 
Not sure how exactly you start HWiNFO, so the best practice would be to apply the exclusion in settings, click OK and then restart HWiNFO.
 
Thanks. So it doesn't happen immediately on re-launch of HWiNFO. It happens some period of time later, from a few seconds to a few minutes. It also happens even when I have SMBus Support disabled as well as enabled but 20-2F excluded (along with other ranges). Are there HWiNFO logs I could pull which I could use timestamps to try to determine what may be the cause?
 

Attachments

  • sensors.png
    sensors.png
    42.8 KB · Views: 2
I'm afraid the HWiNFO logs probably won't tell in this case.
Maybe try to disable monitoring of the NUC126 sensor - hit Del over the sensor heading.
 
Thanks for the support. That seems to have stopped it, at least for the last few hours which is much longer than what the past. I'll purchase a Pro subscription for your help! Also want it for the integration with Aquasuite =)
 
Thank you :)
If this fixes it, then it could mean it's because of a conflict between HWiNFO and some other monitoring or RGB control app. What other apps are you running?
 
If you wish to figure out, you can try to run with NUC126 enabled in HWiNFO and stop either of those apps to see if they are causing the problem.
 
I've re-enabled NUC126 and haven't seen it again, with 2F disabled. My guess is that it was perhaps MSI Afterburner causing the conflict, as I have stopped running that.

I can try to re-enable 2F and see if I get it again in isolation without Afterburner, if that would help. My gut feel is it was probably both of these.
 
You must log in or register to reply here.
Back
Top