Fiery

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.

Logitech Gaming Software and Ghub are known to be behind such anomalies

Do you experience the issue with Odospace disabled, and SensorPanel or OSD Panel enabled?

As I've requested above, please post an Embedded Controller Dump.

Yes, there is. You basically need as many licenses (nodes/seats) for AIDA64 Business as many licenses you'd wish to use at any given client's. So if you have 3 clients: a small client with a network of 50 computers, a mid-size client with 500 computers and a large client with 5000 computers, you need an AIDA64 Business license with 5000 nodes or the size of your largest client's network basically. If you're looking for a more affordable solution, please contact our distributor ABSEIRA at: https://www.aida64.co.uk/contact They will be able to propose alternative ways of making the envisioned project possible.

It's not possible for the SensorPanel, but you can have that data either logged into a HTML or CSV log file (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging), or track it using the Statistics tab of the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test).

Thank you for your help! The fix will be added to the next AIDA64 beta update. As it turns out, a similar bug plagued the Elgato and EVGA LCD modules as well, so we've fixed all three at once

Thank you! In order to accelerate fixing this bug, I've sent you an email about this.

We'll try to replicate the same environment where you experience this issue. Do you have RTSS installed as part of Afterburner, or did you use a RTSS standalone installer? Do you experience the issue with other 3D games as well? Or the issue only comes up with Minecraft?

Try to toggle the option AIDA64 / main menu / File / Preferences / Stability / Asus WMI sensor support.

It's in AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup.

Thank you, we'll fix the issue in the next AIDA64 beta update due next week. I will post a message into this topic once the new beta becomes available for download.

Thank you, we'll fix the issue in the next AIDA64 beta update due next week. I will post a message into this topic once the new beta becomes available for download.

Thank you for your feedback

I'm afraid that's not that useful since it refers to a module (PSHED.DLL) that is not used by AIDA64 at all. I have no idea how that module can be related to this issue or AIDA64.

It's not supported by AIDA64 yet. In order to let us have a better understanding on the USB layer of it, please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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

The issue is about loading certain PNG images when the PNG decoder module of AIDA64 goes crazy and starts leaking memory We've added a new PNG decoder module, but it seems it fails to work in some cases too. Our best guess is that there's a certain property of the PNG images you use and that by converting the images or exporting them using a different image editor could help -- but so far we haven't found a single reason that could be blamed for the PNG module to go south. Check the following post for a potential workaround, although it requires you to convert your images using Gimp:

Are you sure the GPU is not activated when you start a 3D game? What AIDA64 notified about was simply a Registry setting that needs to be altered to put a constant stress on the GPU using OpenCL. It will not alter any hardware settings or remove any hardware.