Fiery

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!".

Here's the new AIDA64 Engineer beta build: https://www.aida64.com/downloads/latesta64eebeta

Thank you. 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. Let me know how it works.

Overheating protection has multiple layers, and one of those is to lower the clocks when throttling is not enough to protect the CPU from overheating.

It's normal. You cannot enable them both because that would mean that you cannot restore AIDA64 when it's minimized to the System Tray.

I don't think Hardware Info implements the sensor mutexes that are necessary to synchronize that software with ours. Try to inquire Hardware Info technical support about the industry standard mutexes like: Access_ISABUS.HTP.Method Access_SMBUS.HTP.Method Access_EC etc.

Try to go to AIDA64 installation folder, and find the settings file called AIDA64.INI. If you have the file there, try to edit it using Notepad, and replace the following lines: LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 ... with the followings: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 If you don't have the file there yet, create it, and enter the following lines into the new text file: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0

You can build a beautiful layout that fits all your needs using the AIDA64 SensorPanel module

Thank you for your feedback!

We can try the following three dumps: 1) 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. 2) Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. 3) Finally, 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. Thanks, Fiery

That is a high-end Haswell core based mobile CPU. Haswell chips tend to run at high temperatures and tend to throttle even when the cooling of the system is in fine conditions. So on such systems a constant throttling (due to frequent overheating) is sadly normal.

That was a promotion we ran 8 years ago.

Thank you. In NZXT CAM can you see the firmware version listed for GRID+ V3? Also, does GRID+ V3 work in NZXT CAM?

Thank you, we will fix the issue in the next AIDA64 beta update.

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. Also 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. Thanks, Fiery

The primary IP address is provided by Winsock, and may or may not be the primary network adapter. In rare cases Windows treats one of the least used network adapters as primary. We haven't found a way to fix it from our end.

I guess you would have mentioned this, but I gotta make sure: did you have GPU stress test enabled for any of your test runs?

Does it show that if you restart your system and check it out right after Windows bootup? What CPU and motherboard do you have?