Fiery

Please try to create a Sensor Profiling Dump right after you start AIDA64. Hopefully it won't freeze then.

Thank you, we've added this display to AIDA64.

Please show me the code you're using to open the shared memory incl. the mapping and unmapping sections. If you prefer to keep your code from the public, you can send it to me in private message as well.

As I've explained it in your other topic, please contact me in private message and describe what you have configured as e-mail settings in AIDA64 / main menu / File / Preferences / E-mail.

Try to disable RAID features as I've explained above.

You're right, our implementation of the VRM temperature turned out to be inadequate. We'll fix it up in the next AIDA64 beta update.

Do you have any special images placed on your SensorPanel layout, or any custom gauges?

1) It would be best to first check what might cause the high CPU usage. Try to 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Generally speaking, certain Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM. 2) It's not really a huge issue, especially if you almost never max out the CPU usage across all cores. If you only load the first 2 or 3 CPU cores using Photoshop, Windows will automatically switch AIDA64 to use one of the other cores to update the sensor readings and the SensorPanel.

Thank you for the info, it's very useful! We'll fix the fan labels in the next AIDA64 beta update. I'll post a message into this topic once the new beta becomes available for download.

I'm afraid that anomaly is due to the way the standard Windows UI element ListView works. We have no control over that behavior.

You can check the list of available network adapters in both cases on the Network / Windows Network page of AIDA64. I think the issue may be because one of the network adapters gets removed by Windows for some reason. Maybe a WiFi adapter that gets disabled and enabled sometimes?

No restrictions on the shared memory access in the trial version. Have you tried to perform the shared memory reading operation by using elevation?

Please contact me in private message and describe what you have configured as e-mail settings in AIDA64 / main menu / File / Preferences / E-mail.

It is most likely because your notebook has an old Intel RST RAID drivers installed, and the driver gets confused by the RAID enumeration commands that AIDA64 issues. You can however disable the RAID enumeration if you don't have any RAID arrays defined in your system by going to the AIDA64 installation folder and editing the file called AIDA64.INI. Try to find the following 2 lines in it (by using e.g. Notepad): LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 And modify those lines to make them look like this: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 If you don't have an AIDA64.INI in there, then create a new one (a text file) and put the following lines in the file: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0

Happy New Year! Yes, already working on it. It's quite a head-scratcher though...

Thank you for the dumps! We've implemented support for EVGA iCX2 for your video card in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that it will only measure temperatures. In case iCX2 is capable of measuring fan speed RPM on your video card as well, then please create 2 new nVIDIA SMBus Dumps, one with the fans stopped and another with the fans spinning. Please also let me know approx. what RPM are the fans spinning that time. Thank you!

Thank you for the dump! Please 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 Let me know how it works.

Thank you for the data. I think the issue is because of AMD SATA/NVMe/RAID chipset drivers causing the classic NVMe SMART functions stop working. We'll work on it, although I'm not entirely sure if there's a proper way to get around this issue

Thank you for your testing. I agree, it seems to be quite difficult to get a proper CPU temperature measurement from your system.

I don't think the sensors are assigned incorrectly across the cards. What may be the problem is if AIDA64 uses a different indexing order for your 3 GPUs than other software or the physical order of your video cards. AIDA64 uses the order that is dictated by the PCI device ordering on the PCI bus.

It still happens in rare cases. We haven't yet found a reliable method to fix it up 100%.

1) Are you running Windows 10 64-bit with all the latest updates installed? 2) Do you use AIDA64 v5.99? (latest version) 3) Is your CPU overclocked?

If you start the System Stability Test, the CPU usage is supposed to stay at 100%, constantly, as long as you don't stop the test. Do you mean that while the test is running, after a few minutes the CPU usage drops down to cca. 9%, without you interfering with the test?

First you say no errors, then you say the app didn't open. Which one is the case? If AIDA64 doesn't open, then you cannot verify if there are any incorrect information displayed