Fiery

It's quite odd. AIDA64 uses the standard method for Asus boards with Intel processors, to read CPU temperature. If it gets stuck, while it works on other systems, then I suppose it is either a BIOS issue or some hardware malfunction related to the CPU diode temperature readout logic of your motherboard.

If your CPU is throttling, then it is overheating.

Please note that not all video controllers support reporting GPU utilization value,

Make sure to disable any other methods of auto-launching AIDA64 at Windows startup. AIDA64 itself supports that (in main menu / File / Preferences / General / Load AIDA64 at Windows startup); and then there's Windows Task Scheduler. Maybe multiple methods are active, and they interfere with each other.

Are you sure you use AIDA64 Business Edition? Please note that AIDA64 Extreme Edition doesn't support command-line based automation, hence it ignores any command-line arguments. Regards, Fiery

We've asked Intel to get the necessary programming details, but they didn't provide anything useful I'm afraid

In that case I'd bring the computer back to the shop for diagnosis. While playing a game the system should definitely not overheat.

I'm not sure why you want to buy new memory modules. If your memory is running at 667 MHz, then it is running at factory default (normal) settings for a DDR3-1333 module. As for the overheating, some of the mobile computers may be designed in a sub-par way that even when everything is clean and brand new, the system can still not stand a heavy stress test without overheating. Usually your system is not under such heavy demand workloads, so the overheating most likely wouldn't come up while running regular everyday tasks. AIDA64 System Stability Test puts the "absolutely worst case scenario" on the computer.

1) It means your CPU is overheating. You should stop the test and check the exhaust ports of your notebook -- maybe they're clogged up with dust that prevents hot air from escaping from your notebook's inside. 2) DDR3-1333 memory is running at 667 MHz real clock. Regards, Fiery

Thank you, we'll work on those. However, please note that some SSD drives may be reported as unknown HDDs, that's normal. And with those cases when the model ID is not fully available ("SSDSC2CW18" instead of "SSDSC2CW180A3"), AIDA64 hardware database may not be able to provide a record. BTW, do you have official specifications on the Velociraptor drive? (WD1600HLFS) Regards, Fiery

As far as we know, CPU package power can only be measured on Sandy Bridge and newer Intel Core processors. On your Nehalem-class CPU the reading is not available. Regards, Fiery

As I've stated above: "We don't yet have an online database for benchmark results." It's still the case

Have you tried the latest beta version of AIDA64 Extreme Edition? It's available for download at: http://www.aida64.com/downloads/aida64extremebuild2256z8l9qktcjyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it's still stuck, then your motherboard may not be able to measure PCH temperature.

Yes, overvoltage (or unstable voltage delivery) and fan issues can also trigger the BIOS to shut the machine down.

Core temperatures are zero when the ACC (Advanced Clock Calibration) feature of AMD processors is activated. ACC is used to unlock disabled CPU cores. This is a hardware limitation that cannot be fixed from software. Regards, Fiery

Is it only missing from the SensorPanel? Is it still there on the Computer / Sensor page? BTW, what video card(s) do you have? Thanks, Fiery

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. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

Graphical artifacts and sudden power-off are both critical issues that reflect the instability of your system at the settings you used. A sudden power-off is usually due to overheating: the BIOS senses one of the components (usually either the motherboard or the CPU) is too hot, and it powers the system off to prevent fatal hardware damages.

Thank you, got the email. Please provide us a few days to diagnose this issue. I'll post updates about this matter in this topic

It is the file called AIDA_VSB.VSB that you can find in AIDA64 installation folder. Try to rename it to AIDA64.gadget and copy it to your gadgets folder, and see if it works that way. However, please note that AIDA64 itself will try to install the gadget as soon as you enable Desktop Gadget support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Desktop Gadget. Regards, Fiery

If you get an error message in the AIDA64 System Stability Test, then your system is not stable We usually recommend to run the test for at least a few hours to make sure all your system components are heated up to their maximum temperature. Regards, Fiery

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. BTW, does the CPU temperature reading look alright in the BIOS Setup? Thanks, Fiery

That's normal. Intel wrote to us: To make things more consistent across different GPU vendors, we've decided to go for the number of shaders instead of the number of EUs. Regards, Fiery

I'm afraid we currently have no plans to extend SensorPanel in that way.

1) Do you mean the temperature reading labelled as "CPU" is always 40 Celsius, no matter if the system is under load or at idle? 2) Do you have Asus AI Suite installed? 3) Do you have any other hardware monitoring, tweaking or overclocking application running in the background? Thanks, Fiery