Fiery

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?

It's hard to tell, since Nuvoton makes all sorts of chips. What markings can you see on those chips?

Thank you for your feedback!

I'm afraid we have no information on how to talk to the special embedded controllers of modern HP systems

Thank you for your feedback

Thank you. We've added MOS and Chipset temperature reading for your motherboard: 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 After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

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 if it helps.

Thank you. Please check the latest AIDA64 beta: https://www.aida64.com/downloads/latesta64xebeta Please note that it may not work with a different driver. If you change the driver and it stops working, please submit a new trio of the requested dumps so we can check what the new driver is and how to implement support for that as well.

Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA 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 --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Great Does it mean you have all video card related readings available in AIDA64?

At this point I gotta go back to my original stance of recommending you to switch to the SensorPanel module which is more capable than the Sensor page. I know you favour the Sensor page over the SensorPanel, but we can find very little development time to improve an inferior module (Sensor page) when we already have a much more powerful module (SensorPanel) ready.

Thank you. The sensor code itself takes cca. half a second to complete, so the slowdown of 3-4 seconds is mostly caused by the LCD API (Odospace).

It seems the driver of those keyboards have difficulties handling a power-loss while AIDA64 is talking to the keyboard. We're not sure what can be done at our end. We follow the protocols of those keyboards, and we try to disconnect from them gracefully when a suspend/restart/sleep event is triggered.