EpicEric6
-
Posts
5 -
Joined
-
Last visited
EpicEric6's Achievements
Newbie (1/14)
0
Reputation
-
Hope it helps. It's not your fault, but this is what I'm talking about. That polling current ASUS WMI interface will still cause problems. On my system I've described the behavior in my previous posts. Please see the bold line below: HWiNFO v5.87-3490 Beta available.Changes: Enhanced sensor monitoring on MSI MS-7B10. Fixed NXZT Kraken X52/X62 support on some systems. Disabled ASUS WMI support on current BIOSes due to a faulty BIOS implementation. Added NVIDIA GV102 and GV104.
-
I can assure you that the CPU（TDie) on HWInfo and CPU on AIDA64 is the same reading. They can be perfectly synced for a few hours until the AIDA64 reading stopped changing. That's also when the fan start to play up (Similar to original method that cause IT8665E to hang) If I have to guess, HWInfo is reading directly from CPU while the AIDA value still queue the motherboard? Although this reading ultimately come from the CPU.
-
It happened again. It seems that only CPU temp is affacted. CPU Diode and other sensors are working fine. However, all fan speeds seems to depend on CPU temp, so that in the image below, fan won't spin up. To me it seems like prolonged pooling to fan speed can still cause the issue, no matter accessing via EC or WMI.
-
Hi Fiery, I was trialing the C6H new BIOS 6201 and latest AIDA 64 Beta version. The fan issue seems to be better, but I got some weird issue. After some CPU-heavy tasks, the CPU temperature reading is off, it now drops very slowly from 65 to 59 in about 5 minutes. On the other hand, HWInfo64 actually have a correct reading, please see attachment. I can't explain it, as HWInfo and AIDA64 should both be reading off the ASUS WMI sensor by now.
-
Did the BIOS update and latest AIDA64 beta fix your problem completely? I'm asking because I still get fan issue even with latest BIOS on C6H and latest AIDA64. I turned off EC support and is using WMI to read sensor data. Does this mean that I may have other programs that is causing the trouble?
