Fiery

Thank you! Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Yes, thank you. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Feel free to share this topic with anyone. I'm glad you like using AIDA64. I wish we could do more to fix this issue and issues about monitoring Asus AM4 motherboards internally. But with the whole thing riding on how Asus implements the WMI ACPI interface, we need to work with Asus and expect them to deliver the fix soon.

Battery Capacity is shown on the Battery page in our AIDA64 for Android app. In the Windows PC version of AIDA64 you can find the information on the Computer / Power Management page.

Thank you for the photos. I suppose the issue is because of the problem with Asus AM4 motherboards where concurrent access by a 3rd party monitoring tool (like AIDA64) and the motherboard BIOS can cause collisions which could make the fans to act up. In case your motherboard supports Asus WMI ACPI interface, you can try switching to that to avoid the collisions: go to AIDA64 / main menu / File / Preferences / Stability / tick the option called: Asus WMI sensor support and restart AIDA64 to apply the changes. If you cannot see the 2nd line on the Computer / Sensor page to change to "Asus WMI", then your motherboard doesn't support the new Asus monitoring interface and so we cannot fix the problem from our end. BTW, you've got a nice AX206 there

If you have no RAID arrays defined, you can try disabling the two RAID related options in AIDA64 / main menu / File / Preferences / Stability. It accelerates AIDA64 startup and you can also avoid BSoD in certain circumstances.

On Asus AM4 systems it's safer with the Asus WMI sensor support enabled. Without it concurrent access by AIDA64 and the motherboard BIOS can cause collisions that may just end up in fan duty cycles messing up. Please note that even though the new Asus WMI ACPI interface was invented and designed to avoid those collisions that plagued the Asus AM4 platform since the very beginning, the interface is poorly implemented in multiple Asus motherboards. It is also not implemented all across the board. So while it's a great thing in theory, in practice it causes a lot of headaches. All you can do is put more pressure on Asus to fix this issue in a future BIOS update.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

I don't think Asus' own monitoring tool uses their own ACPI WMI interface simply because it's still not mature. Your case is just one example where it has a glitch. A future BIOS update is the only way to fix this up.

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. BTW, do you have NZXT CAM running in the background? Thanks, Fiery

Please post a screenshot of the Computer / Sensor page of AIDA64.

1) It depends on the actual DRAM frequency your memory modules are running at. Make sure to have XMP enabled in the BIOS Setup, and then check the DRAM frequency in AIDA64 again. If you still have doubts about its accuracy, compare the clock readings against CPU-Z or HWiNFO64. 2) It's difficult to tell, but most likely it is. You can enable Extended Labels to clarify the generic sensor readings in the right-click context menu on the Computer / Sensor page. 3) Chassis #3 is one of the fan headers located on your motherboard. Fan RPM is always for a single fan. No averaging or other combination of multiple fans is done by AIDA64. 4) Same as 2)

We've checked, and the LSI libraries aren't seem to be able to provide thermal readings for the controller, so we cannot measure it from AIDA64

1) What is the difference between the CPU utilization value AIDA64 measures and other tools measure? 2% vs 3% or something more dramatic? 2) Do you mean that AIDA64 shows a constant 99% of GPU utilization even at idle?

Awesome

Sounds great

Thank you. It means your motherboard BIOS fails to provide the T_Sensor thermal reading (as well as the Chipset temperature reading for that matter) due to a BIOS bug.

Thank you for helping us implement support for Z10 RGB.

Please try to perform the dumps that I asked for in my first post in this topic. You can have the debug popup menu pop up if you use the Ctrl + Alt + D key combination. When that menu pops up, select System Debug, then USB Dump to make the USB dump. Then also select Sensor Debug --> Aqua Computer Dump in order to have the other dump.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aqua Computer Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I think we've managed to fix the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

No problem. I think we've managed to fix the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you for testing the first beta with Z10 RGB support. I'm glad at least on the USB communication level it worked out okay. We've fixed the LCD preview issue in the following new beta build: https://www.aida64.com/downloads/latesta64xebeta Note that you cannot re-use the old profile for Z10 simply because Z10 and Z10 RGB are way more different about their LCD displays than what at first glance you would think. The old (the original) Z10 has a graphical display with a resolution of 160 x 32 pixels, while the new Z10 RGB steps back quite a lot by having only an alphanumeric display that supports 20 x 4 characters. That's why you cannot change the font on Z10 RGB at all.

Stability issues are not black and white. There are a lot of grey area in there where even the same software could pass 9 out of 10 times. But when only a single software fails only once, it means the system is almost stable. I'm sure what you experience is not due to a bug in AIDA64. But, if you conclude that your system is 100% stable, then you don't need to use AIDA64 System Stability Test actually.

We will fix the issues coming up about Aqua Computer devices due to the latest firmware upgrade in the next AIDA64 beta update. As for power consumption, it is a calculated value (based on the TDP of the video card) and not a measured value as it is displayed in other tools like GPU-Z. If you know the TDP of your video card, you can use the Correction facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction) to apply the TDP as the Ratio to end up having the same calculated value as in other monitoring software.