Fiery

Thank you for your feedback!

The above mentioned new AIDA64 beta update can now be downloaded from: https://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update can now be downloaded from: https://www.aida64.com/downloads/latesta64xebeta

@Amit Paz The above mentioned new AIDA64 beta update can now be downloaded from: https://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update can now be downloaded from: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works.

The latest AIDA64 beta update implements support for up to three AX206 LCD devices: https://www.aida64.com/downloads/latesta64xebeta Let us know if you need more devices

I don't think your video card supports measuring VRAM temperature. Can you please shot a screenshot of HWiNFO64 where it can indeed measure that thermal spot?

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.

Thank you, we'll fix the 950p --> 905p issue. As for PCIe ports capabilities, that information is enumerated and put into the relevant PCIe root port device registers by the BIOS. When the information is incorrect, it's due to a BIOS bug.

Thank you, we will fix the issue in the next AIDA64 beta update.

@mfung1985 We will fix the GPU diode temperature measurement issue in the next AIDA64 beta update. As for the CPU utilization issue, please refer to this forum topic:

Then there's this: https://aaron-margosis.medium.com/task-managers-cpu-numbers-are-all-but-meaningless-2d165b421e43 https://illuminati.services/2021/03/17/windows-10-task-manager-cpu-inaccurate-a-tale-of-two-metrics/

Somehow we're unable to reproduce the issue. Maybe Microsoft has already fixed the issue in one of the KB's applied on 22H2?

We've done thorough test runs with various Win10 and Win11 builds and so far our conclusion is that the discrepancies between the CPU usage % reported by Task Manager and AIDA64 are due to the updated formula Microsoft uses to calculate CPU usage that also takes Turbo Boost into account. For example, when you open AIDA64 System Stability Test, go to Preferences / General, and set CPU mask to utilize 50% of the logical processors available in the system, and you start CPU stress test, Task Manager clearly shows the first half of the logical processors are stressed to 100% and the rest are idling. Yet if you have Turbo Boost enabled and your processor is capable of utilizing Turbo in that scenario, CPU usage % in Task Manager will show a value higher than 50%. And if you deactivate Turbo Boost, Task Manager will show exactly 50%. However, in both scenarios AIDA64 will show 50% CPU utilization.

Is there always the same 4 degrees difference between the GPU diode temperature reported by AIDA64 and HWiNFO? We're working on the CPU utilization measurement issue under Win11.

Windows can go to sleep regardless of the displays connected. IMHO those displays that are handled as regular monitors under Windows offer more flexibility. So if it's the same display panel, I'd opt for it to have a monitor feature via USB, DSub, DVI, HDMI or DisplayPort. And of course several monitors can connect via USB nowadays too and doesn't require special software support.

Make sure to disable (uncheck) the option called SMBus access through ACPI (Asus motherboards) in AIDA64 / main menu / File / Preferences / Stability, and on the same page enable (check) the option called DIMM thermal sensor support. Let me know if it helps.

Please avoid opening multiple topics for the same issue. This topic closed.

The issue is most likely due to the bunch of detection AIDA64 performs when it collects all the sensor readings. That could affect the CPU utilizing its power saving features and eventually would make it run at a different core clock frequency than when the CPU is truly idle.

We are aware of the issue and working on the fix.

We're aware of the issue and working on the resolution.

We're aware of the issue and working on the resolution.

10+ inch screens typically have a HDMI or USB connection and appear under Windows as a secondary monitor. In which case you don't need any special tricks, you can simply use AIDA64 SensorPanel.

At this time, no. Do you have multiple devices?

Can you please do the following? 1) Upgrade to the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta 2) 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. 3) Wait for readings to become erratic in AIDA64. 4) Create an updated ISA Sensor Dump. 5) Start HWiNFO to get the readings back to normal. 6) Create an updated ISA Sensor Dump. Hopefully those three ISA Sensor Dumps will help us to understand the nature of the issue. Thanks, Fiery