Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASUS Prime X470-Pro - Fan headers shutting down after a while when running HWiNFO
This probably sounds crazy as hell, and HWiNFO may not be even be the culprit here, but please hear me out first.

End of April I built a new PC around the Ryzen 7 2700X, and everything was fine (and still is, mostly). On the first weekend, after playing some games for a while, I noticed temps were getting a bit hot. Shortly after, I realized all the case fans had shut down. The following day (probably Sunday or so) and the following weekends, it also happened. Always after I had the PC running for at least around 8 hours, sometimes after longer times, all the case fans would shut down.

Overall, this seriously weirded me out and made zero sense. Weird sensor readings (37000 RPM on some case fans, or stuck case fan readings) didn't help the situation either. ASUS support suggested a potential power issue, and asked me to test a more minimal setup (fewer fans, only one RAM module), but that didn't help either. I then also tried fiddling with fan tuning in ASUS BIOS. First I modified the curves to something else, then I set the fans to full power. Neither helped. I then googled again (last weekend or so) like I have before, but this time I found this reddit post:

A fellow user with the same problems I had! They claim the problem is ASUS' implementation of PBO doing something it shouldn't or some such. I hadn't even realized it's turned on, so I looked for the setting in the BIOS and set it to "Disabled" from "Auto". But again, it didn't help. I then found the post in the same reddit thread I didn't want to find:

Somebody claiming to have had the same problem, and it stopped once they uninstalled HWiNFO. And that's why I'm here. After disabling PBO didn't help, the first thing I did was disable monitoring for any sensor in HWiNFO I didn't need. This left me with the sensors for CPU usage and temperature, GPU usage and temperature and fan speed sensors. But again, same problem. I then tried once more with the fan speed sensors disabled as well. But again, after 8 hours, my fans turned off... so today, for the first time, I didn't have HWiNFO running at all. So far, my PC has been running for about 13 hours with no issues. And so, it really does seem like HWiNFO is the culprit. But why? I'd really like to have it running again, for monitoring temperatures and such...

Tomorrow's a holiday here in Germany, so I'll have enough free time to run the PC long enough for the problem to occur again. I will generate a report and debug file for this report tomorrow. Until then, maybe somebody has an idea what may be causing this.
No, that doesn't sound crazy at all Wink
Some ASUS X370/X470 boards are known to have problems when other monitoring applications access their sensors, which can use the symptoms you describe (invalid readouts, malfunction of the SIO).
Initially these issues were quite heavy, but we found a solution with ASUS that significantly reduces the probability of occurring, so on some systems this should not be happening. But still there's a small chance, especially when running for prolonged time.
ASUS continued investigation and developed an alternate solution that should completely fix this problem. We spent a lot of time with them working on this, I was directly involved in this process. We came with a solution, which however wasn't yet released by ASUS as part of an official BIOS. So HWiNFO has support for this already, but you will need to wait for ASUS to release the fixed BIOS.
For the time being, you might try to run HWiNFO, but with the ITE sensor (and most probably the ASUS EC sensor too) disabled - you will need to disable monitoring of the entire sensor (it's heading included). This should workaround the problem, but you won't be able to see any values from the mainboard sensor.
Man, it's such a relief to read that. Seriously! I disabled monitoring of the ITE sensor. I don't have an EC sensor, however. Should I see that anywhere, or do some boards not have one?
If you're not sunning the latest Beta version (v5.83) then the EC sensor won't be shown.
Does that mean I don't have to worry about that sensor, then, or should I get the beta so I can disable monitoring for it?
You don't need to worry about it as the version you're using doesn't access that sensor at all.
Alright, sweet! Thanks for all the info, and especially the quick responses Smile I'll keep watching out for BIOS updates that may address this.

Forum Jump:

Users browsing this thread: 1 Guest(s)