Fiery

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

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

We'll extend the number of AX206 LCD pages from 4 to 6. It will be available in the next AIDA64 stable update due on 12-April

In order to have a proper driver installed for an AX206 device, what you need to do is the following: 1) Download the Samsung SPF LCD driver digitally signed by us (FinalWire) from: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip 2) Extract the ZIP package into a folder on your PC, e.g. C:\1 3) Right-click on the Windows button on the Taskbar --> Device Manager 4) In the Device Manager look for the device entry for the AX206. It should be inside the group called Other devices 5) Right-click on the AX206 device --> Update driver --> Browse my computer for drivers 6) Click on the bottom button: Let me pick from a list of available drivers on my computer 7) Select Show All Devices --> click on the bottom Next button --> click on the Have Disk button 8) Navigate to the folder where you've extracted the ZIP package into and select the .INF file there 9) In the Select the device driver you want to install for this hardware window feel free to choose any of the devices, e.g. the first one called Samsung 1000P Digital Photo Frame 10) Click on the Yes button in the Update Driver Warning message box 11) You're done with driver installation and can start using the AIDA64 AX206 module Please note that this process of driver installation applies to both Windows 10 and Windows 11.

Quite frankly, I have no idea about that You can try to switch the mentioned features off one at a time and see how it affects the way AIDA64 behaves.

Make sure to disable all virtualization and sandboxing features of Windows, including Hyper-V and Memory Integrity. That should solve both the DRAM frequency measurement issue as well as the high latency issue.

How many pages would you need?

There's no such facility in AIDA64.

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.

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.

I'm not sure if you're at the latest stable version or the latest beta build. If yours is the stable (v6.60.5900), then make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.

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

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

It sounds like the another software is colliding with the EC (Embedded Controller) register access module of AIDA64. Do you have any other monitoring software running in the background?

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.

Please check it with the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta In case the issue persists, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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

Could be due to a few reasons: another software running in the background is interfering with the AIDA64 System Stability Test. Or the CPU is under heavy stress and it tries to prevent overheating by lowering its core clock frequency. Try to use only the FPU subtest of the System Stability Test to see how the clocks and thermals turn out that way. With the FPU subtest alone your processor will get under the most demanding circumstance in terms of power draw and thermal stress.

Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.

In the video they were using an old version of AIDA64 that didn't yet include full support for Alder Lake. We recommend you to use the latest AIDA64 beta on Alder Lake: https://www.aida64.com/downloads/latesta64xebeta Also, it's not clear whether any sandboxing was used in the video. We recommend disabling both Hyper-V and Memory Integrity to get accurate benchmark results.

Thank you for your feedback!

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. In case it still doesn't work properly, then disable Hyper-V and Memory Integrity in Windows Settings to remove the sandboxing of AIDA64.

You need to add the font to Windows, not AIDA64.

It's already in our PCI device database, that's why it could be detected as "PCI Device" (last line on your screenshot)

Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.

Can you please disable the PCH HWMon module and then 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