Fiery

What motherboard and CPU do you have?

Of course, it will!

We've fixed the device icons in the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta

Sadly, via WMI the same incorrect information is returned, e.g. last AV signature update in 2016, etc. Anyway, here's a new AIDA64 beta where we've fixed what we could: https://www.aida64.com/downloads/latesta64xebeta

We've fixed the sensor readings for your motherboard in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've implemented the requested feature in the latest AIDA64 beta: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

I'm afraid we don't maintain such a list of devices.

Thank you for the bug report. I'm not sure if it's possible to detect Windows Defender on recent Win10 builds, but we'll improve on it in the next AIDA64 beta in order to show some details on the Windows Defender installation. The virus database date seems to be off though, so we need to do more research on that matter.

I've asked our worldwide distributor Abseria Ltd to contact you directly about this matter. They will let you know what options you've got. I'm 100% sure you can find a way to acquire the licenses with the advertised discount of -50% for educational organizations and students.

Not all GPUs can provide a GPU power reading value in Watts.

The Statistics tab is designed to measure sensor readings while the AIDA64 System Stability Test is running. And while a stress test session is running, the average CPU usage is usually exactly 100% You can use the Logging facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) to measure sensor values as well as CPU utilization while gaming.

It is sadly normal, but somehow doesn't happen on all Windows installations. It happens because sometimes the Windows driver cache gets invalidated when a software tries to load a dynamic kernel driver. When that happens, Windows gets extremely sluggish for a few minutes, exactly what you experience on your system. AIDA64 uses a dynamic kernel driver (and not a fixed, installed kernel driver) to provide the maximum flexibility and make sure that what we call portable version is really portable. I know it's not a real solution and probably not even a consolation for you, but the issue doesn't seem to happen under Windows 10, so by the time you upgrade to that OS, it will most likely be resolved.

32-bit architecture means that even though you have a 64-bit CPU, the Android platform installed on your device is the 32-bit flavour.

If I were you, I would try to warm up for SensorPanel instead of waiting for an improvement that may never come

There's a sticky bit in one of the architectural registers (MSR) that reflects whether since bootup there ever was an overheating condition as monitored and detected by the CPU itself. When that bit equals 1, AIDA64 will show "Overheating Detected!".