Fiery

The French language module will be updated in the next AIDA64 beta build. As far as I can tell, you cannot avoid putting more and more pressure on us about implementing the feature of renaming labels on the Computer / Sensor page That would solve many of your existing issues about sensor labels I guess. We'll jump on it now, it's already too much pressure

Thank you for your feedback. No, ATKEX is a different interface, so that setting does not have any affect on Asus WMI.

Here's the first AIDA64 beta that supports the new Asus WMI sensor interface: https://www.aida64.com/downloads/latesta64xebeta You can enable/disable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability. It is enabled by default. It requires a BIOS interface, so it will only work in case the motherboard BIOS supports Asus WMI. If it doesn't, and you flash a new BIOS that does support it, AIDA64 will automatically switch to using the WMI interface right away. The current implementation supports Asus Crosshair VI Hero, Crosshair VII Hero and Zenith Extreme motherboards. Other motherboards are partly or fully supported by the current implementation. When a certain motherboard is not fully supported, make sure to 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. That dump will enable us to fine-tune the Asus WMI implementation and adjust it to support new motherboards. We've tested the current implementation with the following motherboard + BIOS combinations with success: - Crosshair VI Hero / 6201 - Crosshair VII Hero / 0702 Everyone: please let us know how it works on your motherboards

Most non-ATA-compliant storage devices do not feature a proper model ID that would let us add them to our storage device databases. And it's already very difficult and time consuming to maintain the HDD and SSD databases, so we're not really keen on piling up even more tasks over that already huge pile of things to do every day...

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.

Just a sidenote: a process can load a DLL (in this particular case the one for NVAPI) which can issue kernel driver calls (exactly what happens in this case) which can then cause a BSoD. Sometime it's difficult to go through that chain of calls to find the culprit

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery 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

Since the issue affects any software that uses NVAPI (nVIDIA's own API), it should be pretty easy to reproduce it in nVIDIA's own labs. We can however be of assistance if asked. We're always open to work with hardware manufacturers, but nVIDIA is not famous for being open to such cooperations I'm afraid.

It's best if you leave the main window open and the Computer / Sensor page showing to make sure the readings are constantly updated/polled. If hiding the main window is a key requirement, then it's best to enable one of the External Applications modules to make sure the sensor readings are polled in the background.

Thank you for your feedback

We're already working on it The new WMI interface will be implemented in other AM4 and TR4 Asus motherboards as well, so hopefully soon all such motherboard owners will have a stable monitoring solution.

That happens when the report creation process was interrupted, or when AIDA64 is not able to modify the previous SQL record in the Report table. Make sure to provide both write and modify (update) privileges to the SQL user that you use for report insertion.

AIDA64 doesn't calculate or average the clocks over a period of time, but instead it detects the current CPU ratio (multiplier) at any given time point, and multiplies it with the current BCLK to get the CPU core clock. You can monitor the CPU clock for all CPU cores individually if you right-click on the bottom status bar of AIDA64 main window --> CPU Clock Monitor. You may need to enable status bar in AIDA64 / main menu / View first.

We've done extensive test runs with Ryzen 1000 and Ryzen 2000 Series processors, and couldn't reproduce the issue Have you tried to use the latest AIDA64 beta build? https://www.aida64.com/downloads/latesta64xebeta Also, do you still have the MSI B350 Tomahawk motherboard and AMD Ryzen 5 1600 CPU? Do you have any nVIDIA video cards in your system?

I just did. I apologize for the delays.

Do you use DPI scaling (DPI zoom) for your monitor?

I'm sorry for the late reply. We've already got a few topics about the same bug of the recent ForceWare drivers. The issue is not related to AIDA64 at all -- which can be considered a problem since we cannot fix it in our end. Downgrading ForceWare to 388.31 solved the issue:

The issue seems like a collision between the manufacturer's own monitoring software and AIDA64. Have you tried to uninstall ASRock's own monitoring utility?

We still believe the issue is with the video driver (ForceWare) and not AIDA64. Try to downgrade to an older ForceWare release, and check if it helps. I know you've mentioned that you've tried that path with no success, but maybe you've downgraded to a too recent version that already has the bug? For others 388.31 solved the issues:

Thanks for the feedback

Please let me know what motherboard, CPU and video card(s) do you have, and whether you're using the latest Windows 10 build (17134).

Thank you for your feedback. The test is the same as before, it's only the amount of memory to be stressed that you can now adjust.

We've implemented the requested Memory allocation % option in the Preferences of the AIDA64 System Stability Test. https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

Thank you, that's a very useful breakdown of the labelling issues. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.