Fiery

You can always copy-paste the AIDA64 icon from the Start Menu onto your Desktop Regards, Fiery

1) Have you enabled both RAID options in AIDA64 / main menu / File / Preferences / Stability? Please note that you need to restart AIDA64 after altering any options on the Stability page. 2) What version of Intel RSTe (RST Enterprise) RAID drivers do you have installed? 3) Do you have Windows 7 64-bit SP1 installed? Thanks, Fiery

I'm glad you managed to fix it up Regards, Fiery

1) Are you running AIDA64 v2.70 stable release, or the latest beta release available at: http://www.aida64.com/downloads/aida64extremebuild2260kdjhw1xz8bzip 2) Have you tried what happens without EVGA Precision X and RealTemp? 3) Have you tried to switch the Asus ATKEX option in AIDA64 / main menu / File / Preferences / Stability? Please note that you need to restart AIDA64 after altering any option on the Stability page. Thanks, Fiery

We do have plans about multiple SensorPanels, and also about a vastly improved Alerting facility to fulfill all those needs listed above. Stay tuned Regards, Fiery

As you discovered, the Alerting facility is there already Also, the min/max/average values can be checked using the Statistics tab of AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test) -- or using the Logging facility of AIDA64 that you can activate in main menu / File / Preferences / Hardware Monitoring / Logging. Regards, Fiery

That logic is embedded in your processor (CPU).

AFAIK RSoD (Red Screen of Death) is a ForceWare-related issue, and has nothing to do with gadgets. You should see the same issue with e.g. the OSD Panel or SensorPanel of AIDA64. Do you use the latest ForceWare WHQL release of 310.90? Do you have the option nVIDIA GPU SMBus access through nVIDIA ForceWare option enabled? Disabling that option is quite risky, especially on GeForce 500 and later cards.

That command-line looks slightly incorrect. You need to specify the filename right after /R, with only a space character between them. Also, you cannot mix /AUDIT and /HW, you need to use only one of them. So your fixed command-line would look like this: /R \\FS01\Aidareports\$HOSTNAME /CSV /AUDIT /SAFE /SILENT /DELAY 60

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