Fiery

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.

It is missing usually because the user who's launched AIDA64 has no administrator privileges.

If your CPU or RAM is overclocked, then I'd try to use their factory default setting and see if it helps. If not, then try to lower the memory clock frequency and ease up on the memory timings (use higher timings). Most importantly, set the RAM to Command Rate (tCR or tCMD) 2T instead of 1T.

Does this issue have any relation to our AIDA64 for Android app?

Sadly, it's correct and it's still valid with the latest iCUE version. All you Corsair hardware owners out there: you need to put more pressure on Corsair to get their act together and make it possible for other applications to access Corsair hardware while iCUE is also running in the background. It was possible with an older version of Corsair Link Software, but Corsair decided to discontinue supporting 3rd party application developers

The issue will be fixed in the next AIDA64 beta build

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

What motherboard do you have? Do you have the onboard SATA controller configured as IDE, AHCI or RAID? If RAID, then do you have any RAID arrays defined?

We've done further test runs, but it still works properly for us. The issue is still due to the kernel driver mixup: try to backup your settings (AIDA64.INI file in AIDA64 installation folder), remove AIDA64 from your system, restart Windows, download the latest AIDA64 beta build, and check it again.

Thank you for your feedback. In order to have the DIMM thermal readings in AIDA64, make sure to enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes.

Please post your questions and issues in English if possible.

Please check how this issue works with the new AIDA64 Business beta build that I've sent you in both email and private message.

I've just sent you a private message about this.

I'm not sure what you're trying to achieve. Can you please tell us more about your project? Consider opening a separate topic for your issue.

Thank you for your feedback

The new AIDA64 beta update is available at: https://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta build is available at: https://www.aida64.com/downloads/latesta64xebeta

Here's the fix: https://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update is now available for download: https://www.aida64.com/downloads/latesta64xebeta

Yes, it is very difficult to develop a fully transparent SensorPanel.

I'm not sure how to talk to our server via both path (VPN and non-VPN). The external IP address as provided by AIDA64 is basically the same as if you manually visited one of the IP address providing sites, e.g. https://whatsmyip.com/