Fiery

@Charlie Chou @Nephrite 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 how it works.

Thank you! Somehow the standard AMD graphics API (ADL) is either missing or fails to work on your system. Can you please try to reinstall the video drivers, and maybe upgrade to the latest beta version of 22.10.1 as well?

Can you please check what AIDA64 reports as Manufacturer and Product on the Computer / DMI page, inside both the System and Motherboard subpages? I hope those values will help us identify your motherboard properly.

Do you mean GHz or GB?

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 how it works

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. 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 --> Video Debug --> ATI SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

We've contacted Asus to seek a resolution to this issue.

We can disable PCH Diode temperature measurement specifically for your motherboards if you could kindly let us know what motherboards do you have, as it is shown by AIDA64 on the Motherboard / Motherboard page. Please post that for both motherboards.

1) Individual core temperatures are only supported by Intel processors. 2) DIMM thermal sensor support has to be enabled in AIDA64 / main menu / File / Preferences / Stability in order to have DIMM temperatures measured. 3) On top of that, you need to enable the following 2 options (in AIDA64 / main menu / File / Preferences / Stability) as well to have all sensor readings unlocked for Crosshair VIII Extreme: - Embedded Controller (EC) support - Embedded Controller (EC) bank switching

It's already supported, but only if you enabled DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability.

Thank you! We've fixed 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.

We've added a new option to the Preferences / Stability page to let you disable the Kraken X-2/X-3 sensor module in order to avoid those slowdowns. 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.

Those licenses aren't genuine ones and soon AIDA64 will refuse to work when you try to use any of them. Try to ask for a refund at CJS.

After a few unsuccessful attempts, our app is now in the Jolla/Harbour Store again, now with 64-bit binary too. I’d appreciate it if you can check how it works on a native 64-bit device. Make sure to check the Sensors page as well as try to save a report to file if possible.

Please avoid posting a single issue into multiple topics. I've replied you in your other topic. This topic closed.

You can enable SensorPanel in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel, or by right-clicking on the System Tray icon of AIDA64 --> Show SensorPanel.

Do you have the same multi-monitor configuration in both scenarios?

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

Virtualization is active on your system. I'm not sure what causes it, since you said you already disabled the usual suspects of Hyper-V and memory integrity...

I think some files that are part of the AIDA64 distribution package is not present in the same folder as AIDA64.EXE (main binary). Try to reinstall the latest version, and restart Windows to apply the changes.

Can you please check if it works the same with the latest AIDA64 beta update? https://www.aida64.com/downloads/latesta64xebeta

If this is the device with USB VID 0x2A55 and PID 0x9990, then you've sent me an email about it in early August. Please give us a bit more time to work on the protocol. Thanks, Fiery

AIDA64 cannot use its kernel driver to talk to the sensor chip on your motherboard. Either the kernel driver files are missing, Windows is acting up, or your Windows user has no administrator privileges. Try to restart Windows to rule out the Windows mixup issue, and make sure to have all AIDA64 files copied into the folder where you start AIDA64.EXE from.

It depends on how your Android platform behaves about data connections.

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. Thanks, Fiery