Fiery

Thank you for the data. Can you please check what values does BIOS Setup report for +5V and +12V rails? That info will help us to calibrate voltage readings. Thanks, Fiery

I'm sorry, but we haven't yet installed any Windows using a USB drive, so I cannot help you about that. Maybe other users will chime in and give you guidelines.

Thank you, that's a great info! We'll try to get a DeLock hw soon. At least they're distributed around here, although that particular model is not available right now

I'm afraid there's no such debugging feature in AIDA64 that could "catch" such a weird issue However, can you please try the following: 1) Leave the new BIOS in the board (do not downgrade to 0704) 2) Install AI Suite II (latest release) 3) Restart the system 4) Start AIDA64, make sure to have the Asus ATKEX option enabled in main menu / File / Preferences / Stability. If you alter that option, then you need to restart AIDA64. 5) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. That way we could check what happens with AI Suite installed. That seems to be the only way on this board (with the new BIOS) to make AIDA64 stable, since when AI Suite is installed, AIDA64 skips its low-level EC (Embedded Controller) communications and instead call an AI Suite component (ATKEX) to gather sensor readings. However, there's a slim chance with the new BIOS our ATKEX code fails to work for some reason. Having the ISA Sensor Dump on hand may enable us to verify that theory. Thanks, Fiery

The values exported by AIDA64 have no specific ordering applied. So the external (3rd party) application is the one responsible for ordering the values AIDA64 exports. Regards, Fiery

Maybe MSI Afterburner uses an offset of +10 Celsius on the GPU1 temperature reading. You can apply such offset on AIDA64 temperature readings in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. Regards, Fiery

AIDA64 shows physical information for both HDDs and SSDs on the Storage / ATA page. Basically any SATA SSD drives are compatible with your system, as long as your system has a SATA controller.

Maybe it's because you accidently uninstalled AIDA64?

Yes, you need the latest AIDA64 beta to have that option.

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.