Fiery

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

Thank you! A virtualization or sandboxing environment is affecting benchmark results on your system. Please disable Hyper-V and Memory Integrity as well, and check the benchmark scores again.

I'm afraid we still haven't been able to figure out why polling the GPU causes issues in the video driver. We now avoid using any low-level GPU calls on AMD GPUs, but apparently the driver still cannot handle the calls we issue to it and sometimes goes nuts. We believe this issue is a bug in AMD's video driver rather than AIDA64, and so make sure to report it to AMD too.

I'm afraid we still haven't been able to figure out why polling the GPU causes issues in the video driver. We now avoid using any low-level GPU calls on AMD GPUs, but apparently the driver still cannot handle the calls we issue to it and sometimes goes nuts. We believe this issue is a bug in AMD's video driver rather than AIDA64, and so make sure to report it to AMD too.

Using the latest BIOS version and the latest AIDA64 beta build, please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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

Yes, that's the default battery capacity for your device.

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.

Make sure to check if you're using the right version of the LUIse library. AFAIK there are 3 generations of it, and your DLL has to match the display hardware.

Please note that AIDA64 shows the current CPU instruction set, as it is utilized by the Android platform. So when your Android platform is 32-bit, AIDA64 will show 32-bit CPU instruction set. It's normal that many 64-bit capable Android devices have a 32-bit Android platform installed. You can only convert an Android platform to 64-bit by installing a new Android firmware update that is 64-bit. You need to consult with the manufacturer of your device and inquire them whether they have such an update for your device.

Are you using AIDA64 v6.60 (latest version) ? If yes, then 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

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'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.

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 if it helps.

We currently have no plans about such a new feature for our app.

Make sure to upgrade to the latest version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If you're running Windows 11, it's best to disable Memory Integrity using Windows Settings as well, since it may affect benchmark results.

It depends on your requirements. 5-inch screens are offered by Matrix Orbital (check EVE3 and EVE4) as well as BeadaPanel.

Yes, it would work with either RemoteSensor or Odospace.

Maybe something altered the power profile. Try to do the following: press Windows key + R, enter: control panel In there open Power Options. Click on Change plan settings for the currently selected plan. Click on Change advanced power settings, scroll down and expand Processor power management. Check if both On battery and Plugged in setting for Minimum processor state are set to 5%, and that they're both set to 100% for Maximum processor state.