Fiery

Thank you for your feedback! The indicated readings come from your smart PSU (I suppose it's a Corsair PSU), so they're not related to the motherboard sensor readings.

Thank you. We'll try to find out what's going on. There must be an issue with AMD's own video drivers that causes these headaches.

Thank you, that looks correct so far. Is there a software like Corsair's own iCUE that can report all 3 fans individually for your AIO device?

Please be more specific about what exact sensor readings do you miss from AIDA64.

Awesome

In order to have SMART information and thermal readout for Samsung 980 Pro, 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.

That's the utilization of memory. So in your case (based on your screenshot) 4758 MB out of total 6144 MB (= 6 GB) is utilized at the time you made the screenshot. Auto-starting is only initiated by the built-in facility of AIDA64 at Windows startup (AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup). Any other case is managed by another software. Logitech Gaming Software and Logitech Ghub are known to have a facility to start AIDA64 on their demand, but I'm not sure about MSI Afterburner...

Thank you for your feedback! AIDA64 should measure the same CPU temperature as Asus' own monitoring software. If you have doubts about the CPU temperature reading, just focus on the other ones (CPU Diode, CPU Package). All three of those thermal readings are measured using different methods, so they most likely will never end up showing the same reading.

Please contact the author of Odospace and request a bug fix in their DLL.

Then it must be an issue about AMD Adrenalin video drivers We've already discussed this with AMD, but they seem to have no more ideas on what to do about this matter. A part of AIDA64 sensor code triggers the BSOD in AMD video drivers. We've eliminated direct register access as requested by AMD, but it doesn't seem to be 100% suitable as a fix

We can compile a beta build for you. Please send me your email address and AIDA64 Business product key in private message.

The latter image looks interesting. Can you please expand the Path column to let us see the filename part of the path? It would be useful to see the 5th column expanded on the first image too. The one with values starting with HKCU.

The sensor profiling dump indicates that the whole update process takes less than a second. If you have a low SensorPanel update rate (could be down to 100 millisec) configured in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency, then the update rate shouldn't be 2-3 seconds. Currently it's not possible to decouple any part of the sensor update process from the others. We'll need to work on that.

1) Computer / Sensor page can be found in the left page menu of AIDA64. First you need to expand Computer to find the Sensor page. 2) Beta builds are only available as portable ZIP packages. You can download the ZIP file and extract it to the existing installation folder of AIDA64. Let it overwrite any existing files. It will retain your settings as well as your license. 3) It's very odd to be honest. 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. 4) Fan Extension Card is already supported for your motherboard.

It depends on a lot of factors, mostly the type of display you want to use. Is it a graphical display? If yes, what resolution and bit depth? Also, through the USB connection what protocol can you use? HID? LibUsb?

Please 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. You may need to enable status bar in AIDA64 / main menu / View first.

Yes, you need to have AIDA64 running. You can have AIDA64 automatically launched at Window startup by enabling (checking) the opion AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup.

It could be due to a various potential issues, like motherboard, RAM or power supply unit failure; driver issues; misconfiguration; too much overclocking; too agressive memory timings set, etc.

Thank you! I'm afraid our RAID methods cannot access or identify your WD drives at all Can you please post a screenshot of HD Sentinel, showing the Information tab of one of the WD drives?

You may find a suitable one among these ones:

First of all, please make sure to backup your SensorPanel layout. The issue is most likely caused by DPI scaling discrepancy (difference) between your various monitors. We're already working on a solution for that exact issue. However, in case your existing SensorPanel layout was already designed with a non-100% DPI scaling setting in mind, it would still require adjustments after us implementing the DPI scaling option for the SensorPanel. I will drop a message into this topic once we have an update to this. It shouldn't take more than a week.

1) What motherboard, CPU and video card(s) do you have? 2) Are you using the latest AIDA64 version of 6.32?

Try to check if it's caused by the SMART HDD monitoring module of AIDA64 by disabling it by unchecking the option AIDA64 / main menu / File / Preferences / Hardware Monitoring / Enable disk temperature measurement.

Maybe getting a second monitor (2nd-hand 15" and 17" LCD monitors are quite affordable) and using AIDA64 SensorPanel with it would fit the bill? You can find ideas on SensorPanel layouts at:

Yes, you can disable auto-starting programs individually in LGS or Ghub.