Fiery

I'm not sure if your device supports streaming custom information or bitmaps through USB. Can you please check in the Vision user's manual whether such a trick is supported?

We've checked this on multiple Windows 10 based system (latest patches applied), and couldn't reproduce the issue. Do you happen to have a special desktop or window management software installed? Or maybe there's a non-standard entry in the right-click context menu of your Windows Desktop? BTW, what video card do you have in your PC?

Thank you for your suggestion.

The Cache subtest of the AIDA64 System Stability Test stresses all cache levels.

On most Android devices it's not possible to downgrade. I'm not 100% sure if that's the case for your particular device though.

Yes, we're certain that both thermal readings are valid for your PSU. You can try to put some load on the system to heat the PSU up, and check whether both thermal readings react to the PSU heat-up.

Yes, we're already working on it. AMD has changed a lot in Radeon VII about thermal monitoring, so we need to update AIDA64 quite a bit to make it work with your video card. I will let you know in this topic once a new AIDA64 update is available for download.

What motherboard do you have, and what version of AIDA64 are you using?

Is your video card active cooled? In other words, does it have a cooling fan installed?

Can you please check the Event Logs? Maybe it shows why your Windows installation fails (or refuses) to load the new AIDA64 kernel driver that was introduced in AIDA64 Beta Build 4944.

1) The SSD temperature most likely disappears and resappears again because one of the hard disks or SSDs you've got in your system goes to sleep (and wakes up after a while), which may cause AIDA64 to re-enumerate your storage devices. In which case the SSD may get a different drive index than in the previous state. Do you think you've got a storage device that goes to sleep sometimes? 2) As for Aquaero, please let me know what Aquaero model you've got. 3) Also let me know what version of AIDA64 are you using.

I'm glad the advice helped

Thank you for your feedback. It means the RAID driver that's currently installed for your SATA controller gets confused about one of the RAID enumeration methods that AIDA64 issues at startup. If your system doesn't have a RAID array defined, you can leave the RAID enumeration module disabled.

Thank you! I've sent you a private message about this issue.

Notebooks can be hard nuts to crack about fan RPM monitoring. Let's try this first: 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

I'm not sure if I understand the current state of the issue, so please clarify: after enabling the GPU waking option, all your GPUs are picked up by the PCI device enumerator of AIDA64, but you still don't have all 3 GPUs listed properly on the Display / GPU page of AIDA64?

Try to navigate to the installation folder of AIDA64. If you can already find a file called AIDA64.INI there, open it using Notepad, find the following 2 lines in there: LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 And change those lines to: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 ------------------ If you don't yet have that file there, create a new, empty text file called AIDA64.INI there, and add the following lines to the file using Notepad: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0

Go to AIDA64 / main menu / Help / Command-line Options to see the list of command-line arguments AIDA64 supports. Please note that only AIDA64 Business, AIDA64 Engineer and AIDA64 Network Audit support command-line driven automation.

Try to post that question to StackOverflow. This forum is dedicated to supporting our software AIDA64.

The new kernel driver of AIDA64 v5.99.4960 Beta is not working on your system. It's most likely because the old kernel driver got stuck in the driver cache of your Windows installation. Try to remove all AIDA64 versions from your system, restart Windows and download + extract the latest AIDA64 beta build.

Thank you for your feedback!

On some motherboards the Vcore rail indicates the CPU VID voltage, that's normal.

I can't see any critical or too high values there. But please avoid posting a single issue into multiple topics. I've removed your other 2 topics with the same question.

There's no need to update AIDA64. If your computer cannot stand the very demanding task of the AIDA64 FPU stress test, it's not because there's anything wrong with AIDA64

If you're afraid of the system burning up or catching fire, then no, you shouldn't leave it unattended when a demanding task is running.