Rockstonicko

Sorry I didn't see your response until now. Unfortunately I abandoned AIDA64 with ASUS. I haven't tried testing again with the newest versions of both AIDA and the recent AGESA BIOS update on my board, but I will probably give it a go at some point. I don't have a ton of confidence in ASUS, so I suspect the situation will be the same indefinitely. I was never able to find a solution to the problem, and had to move on to using HWiNFO64. Nothing I did in the BIOS changed the behavior. I tried all manner of combinations including completely disabling the fan sensors, disabling the temp sensors, tried combinations of PWM/DC, changing the temperature the sensor was referencing, and I had no results. I'd list all the things I tried, but it would be a huge list, so let's just say "everything." Been building PC's for 18 years and have fair bit of experience, and I've rarely had a problem with a build defeat me, so it's very annoying to say the least.

Okay, so for anyone else experiencing issues using AIDA64 to monitor Asus X470 boards, I asked Asus if I could post their reply, and received no response to the request. So I'm going to assume that means it's fine: "Our Engineers provided a response on the issue as per our Engineering Team, Please tinker with AI suite 3 FanXpert to avoid re occurrence, The best way is to adjust the fan curve manually to prevent over fan speeds. and kindly confirm if by doing that it prevented any occurrence of the issue." The engineers response was to "tinker" with AI Suite. I think I will "tinker" with an MSI board from now on. I will be contacting GamersNexus, Der8auer, and Buildzoid, and seeing if we can round up anyone else experiencing a similar issue to try and give Asus more of a prerogative to further address this. Thanks again Fiery for the great support and all the wonderful work you do! I will edit this post if I hear anything else back from them, but I don't think Asus is currently too concerned about fixing this.

Thanks so much for the great support. I will also try and get permission from Asus to post their response to the situation in this thread if that's alright with you.

Thank you for the fast reply. I've not seen that anyone else has discovered that the fan logic is reversing when it's being monitored, so perhaps if we're lucky, maybe this will be new information for Asus's software engineers and this will move them towards a solution. I will re-enable WMI sensor support. Do you mind if I send your response, or a link to this thread to Asus support? I refuse to use my PC without AIDA's monitoring features. It's the best, and there is simply nothing else even close to the AMAZING built in customization for the Logitech LCD.

So I'm about at my wits end with this, this is such a bizarre issue. I've already submitted a ticket to Asus about this and they are "researching" why this is happening for the last 2 days but I've heard nothing back yet, so I figured I'd do the same for AIDA64 and see if there are any answers/suggestions/solutions or jokes to ease my insanity. AIDA64 Extreme ver. 6.10.5200 is the only hardware monitoring application I'm using as I've read multiple monitoring apps can cause the ITE IT8665E Super IO chip to bug out. (Among 1000 other things, is this thing just garbage or what?) I'm also using the Logitech LCD configuration in AIDA64 to display temperatures/clockspeeds/VRM current/power/etc. basically all the important information I can fit spread between 4 pages on my Logitech LCD. However, I'm not monitoring fan speeds on my LCD just in case that's causing an issue. After anywhere from 15 minutes to 2 hours, the fans I have connected to motherboard headers will stop spinning. After doing some experimentation and attempting to control the fans after they have stopped, I've figured out that the fan logic is randomly inverting. That is, 100% fan speed becomes 0%, and 0% becomes 100%, 66% fan speed becomes 34% fan speed etc. So after it happens, I can set the fans to 0% and they will spin back up to 100%, or to 34% and they will spin back up to 66%. So I have some form of solution, albeit not an ideal one. I've also noticed that once the logic reverse happens, the fan sensor values in AIDA64 either freeze at their reported value, or they just show 0 RPM depending on how it's feeling at that particular instance. If I'm not running AIDA64 this will not happen, but it's an inevitability whenever AIDA64 is running. Rebooting the PC or sleep/resume will correct the issue for another 15 minutes to 2 hours. Here are the only options I have enabled in the stability section of AIDA64: Load Kernel driver Low-Level MSR Low-Level PCI Low-Level SMBus Low-Level sensor Low-Level SMART SMBus access through ACPI GPU Sensor Support I have disabled Asus WMI sensor support because I read that can solve the issue, but it hasn't helped. This is also the second fresh install of Windows 10 on this machine, and it has happened during both installs. I'm on the latest 5220 BIOS, and changing all of the parameters of Q-Fan in the BIOS doesn't seem to have any effect. Specs: MB: Asus Prime X470-Pro CPU: AMD Ryzen 5 3600X RAM: 16GB G.Skill Ripjaws V 3600MHz GPU: AMD Radeon RX 5700 XT SSD's: Samsung 860 EVO 256GB + Samsung 840 Pro 128GB HDD's: Seagate Barracuda 2TB + Western Digital Blue 1TB PSU: Enermax Triathlor Eco 1000W