I have reported these issues several times to ASUS, but it seems that with every new update they fix some but create other bugs...
Hi. I also have the same problem, using aida64 monitoring utility. It probably functions the same way as hwinfo. Would you suggest downgrading the firmware to the one before the Abba update? So, I am about to try the 9-9-2019 bios, one before the 5220 of the same month. But I see only you had success with this? Previous posts are made before 5220, so...Also, can I downgrade from windows?I am also having this problem with the chasis fans randomly switching off when HWiNFO is running on the ASUS Prime X470-Pro.
It didn't happen before the September BIOS 5220 update (220.127.116.11ABBA) which also broke the temperature reporting for the chipset, temp sensor and CPU OPT speed, and neither issue was fixed by the most recent BIOS 5406 (Update AM4 combo PI 18.104.22.168 patch B).
I'm expecting this to be another BIOS bug (thanks ASUS), however it also only ever occurs for me when HWiNFO is running.
Before the ABBA update I was doing extensive fan and temp testing and had HWiNFO running all day every day for several weeks and never had this problem.
After the BIOS update broke the temp reporting there wasn't much point in me continuing my tests, so since then I have had HWiNFO running only occasionally. However, on maybe 30-50% of these occasions of running HWiNFO the fans stop after an undetermined period of time.
If I restart HWiNFO the chasis fans vanish completely from the report. First screenshot shows stopped fans. Second shows missing readings on restarting HWiNFO.
Hi. I also have the same problem, using aida64 monitoring utility. It probably functions the same way as hwinfo. Would you suggest downgrading the firmware to the one before the Abba update? So, I am about to try the 9-9-2019 bios, one before the 5220 of the same month. But I see only you had success with this? Previous posts are made before 5220, so...Also, can I downgrade from windows?
Thanks for you reply.There have been new bios since these--see: https://www.hwinfo.com/forum/threads/anomalous-sensor-readings-in-hwinfo64.5906/post-26121
Upgrading to 5603 fixed the fan speed and temperature reporting errors also discussed in that linked thread.
And personally I have not had the fan shutdown issue since updating either.
Hope this is of some help
A couple of days and no problem so far, I think the new bios works well with hwinfo. However, aida64 kills the fans and does really bad things to the motherboard. Switching to hwinfo. Do you have sensors only mode or full settings enabled? Because I really customized and removed a lot of stuff and don't dare enable them.
If you would read this thread and several others hear you would know that the issue is not in HWiNFO, but in the BIOS.
ASUS has tried several times to fix this - one BIOS worked perfectly, another one broke things. This all just because of the faulty SIO chip used on those series and we lost track of all those BIOS combinations and which ones worked or not. ASUS doesn't seem to have much interest in providing support for those series anymore.
I've read through several threads here, and I understand that this is some sort of BIOS bug with ASUS motherboards.
As a consumer, I don't really care if the root cause is a BIOS bug. If the problem only started when using your software, the easiest solution is to just stop using it.
The issue that I have is that your monitoring software did not warn me in any way that all of my fans had all stopped and that the temperature of my components was skyrocketing.
Also, your software is able to detect the components on my machine, so why not add some sort of alert to inform users of this issue that you've know about for years now?
I'm not trying to give you a hard time and be a jerk, but please understand my frustration here. The components in my machine aren't exactly cheap, and I don't want them to break or have reduced lifespans. I didn't even consider the possibility that monitoring software could somehow cause my fans to intermittently stop working. I spent weeks troubleshooting this issue, trying to find a common denominator on what was causing it. Only after I exhausted several other potential causes did I even consider looking at the forums for HWiNFO to see if anyone else has seen this before.