Fiery

Thanks for the feedback. The explained issue was in fact fixed right before the release of AIDA64 v1.50 Happy New Year!

A computer restart while running the System Stability Test could happen due to overheating, or because of motherboard failure, system memory failure or power supply failure.

Thank you for performing the test. I suppose Intel Rapid Storage drivers will need to get a few iterations to mature, since other users also reported issues like you did, and it also seems to be a fault of the Intel RAID drivers We've been told that Intel is already working on RST v11, so let's hope they can finish it up in a few weeks.

In case the latency spikes are approx. 20 seconds away from each other -- as it seems --, then I suppose it's caused by the SMART detection layer of AIDA64, which is used to measure HDD/SSD temperature. AIDA64 now uses a special driver call to pass through the Intel Rapid Storage RAID drivers, in order to reach the RAID member drives. I guess Intel drivers will need some more iterations to mature

Yes, I know But it would be necessary to verify if the SMART module of AIDA64 is really the cause of the CPU hogging.

It's rather weird, since nothing has been changed about the Intel RAID handling between AIDA64 v1.20 and AIDA64 v1.50. Please try to disable SMART handling in AIDA64 v1.50 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps to avoid the CPU hogging issue. BTW, what motherboard do you have, and what Windows version are you running? Thanks, Fiery

You can verify the video driver status on the Display / Windows Video page in AIDA64. You may need to revert back to the previous Catalyst driver in case that proved to work better with your video adapter. Regards, Fiery

Please let us know more about your system configuration: 1) Motherboard model 2) CPU type 3) Video card (or cards) model 4) Number of internal or external hard disk drives or SSD 5) Any special sensor devices connected 6) Windows variant, kernel type (32-bit or 64-bit) Thanks, Fiery

The idea of the System Stability Test is that any stable systems should be able to run it for days or weeks, non-stop, without errors. So you start the test, and you should have it running for at least 12 hours. If the computer does not fail (does not freeze, does not restart), and the test keeps running without displaying any error messages, then the computer shall be considered fairly stable. If you specifically looking for any overheating issues, then only have the "FPU" test enabled, and the rest of the tests disabled. Otherwise, enable everything, and see if your computer can stand the stress Regards, Fiery

Thank you. We haven't found programming documentation or guidelines on the shared memory feature, so we have to ask Koolance to provide the necessary details so we can implement that in AIDA64. I'll let you know (in this topic) once we got the programming information from them.

RealTemp uses a special formula to calculate core temperatures from raw DTS register readings. We advise against using RealTemp as a reference software to measure core temperatures, since every other software (e.g. AIDA64, CoreTemp, HWMonitor, HWiNFO32, SIV, etc) use the formula specified and published by Intel. So, if it's possible, please use either CoreTemp or HWMonitor to compare their measured values against AIDA64 values. Thanks, Fiery

AIDA64 has built-in support for the LCD screen of Logitech G13, G15 and G19 keyboards.

1) Do you have any external (USB or FireWire or eSATA) drives connected? 2) Do you have any special sensor devices connected? E.g. T-Balancer, Koolance, DIMM Thermal Sensor. 3) Do you have any other hardware monitoring software running in the background? E.g. HWMonitor, CPU-Z, Rivatuner, GPU-Z, Supermicro SuperO Doctor? Thanks, Fiery

I think it's because your second GPU is put to sleep by the infamous ULPS feature of the Catalyst driver. Once the secondary GPU is put to sleep (deactivated), AIDA64 will keep showing the last clock that was read from the chip. It could either be the idle (2D) clock, or the high (3D) clock. I'm not sure why is there a difference with GPU-Z, maybe it reads clocks using driver calls (ADL), and not direct GPU I/O like AIDA64.

Exactly what information would you like to see about the page file? Current Page File Usage in MegaBytes?

The IDs are SUSEDSWAP and SFREESWAP. We've added to the manual now, thank you for bringing our attention to that issue.

Do you have the RAID array connected to the on-board Intel ICH10R RAID controller? If yes, then what version of Intel Rapid Storage Drivers do you have installed? Thanks, Fiery

1) Do you mean CPU temp = Mobo temp? Or that the CPU temp is stuck at a fixed value, and the mobo temp is also stuck at a different but fixed value? 2) Does Asus PC Probe II report the same temperatures as AIDA64? Thanks, Fiery

I think it's already implemented AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting

Benchmark Results Manager was implemented on June 21, 2005

Yes, we've implemented that feature as per your request

I think it is possible Please do the following: 1) Run AIDA64 Extreme Edition 2) Navigate to the Benchmark / CPU Queen page 3) Click on the Results button on the tool bar 4) Select "Show Reference Results". That should remove all reference results from the list. If you haven't yet saved any of your own results, then the benchmark results list will be emptied. 5) Then run one of the benchmarks as usual 6) When the benchmark is finished, click on the Results button on the tool bar 7) Select "Add Result to User List". Then you will start building your own results. 8) Later on, if you want to manage your saved results (e.g. delete one or more results), you can click on the Results button, and select "Manage User Results". Regards, Fiery

No other tricks or software is needed. Make sure to enable the AIDA64 plugin in Rivatuner as well.

Such mixups can occur when a hot-pluggable (usually USB) device is connected while running AIDA64. We tweaked a lot about hot-plug support in AIDA64 v1.50, so hopefully it will work better than previous versions As for "ATA Device", that text is put there by Windows, and we have no control over that naming scheme. Windows uses "ATA Device" for both PATA and SATA drives. The "IDE" tag is detected by AIDA64, and it means the drive is either PATA or SATA, but a more precise identification is not possible.

I think both "CPU" and "Aux" temperature readings are invalid, and should be ignored. You can verify how many temperatures your motherboard can actually monitor, if you check the PC Health Status (or HW Monitor) page in the BIOS Setup. Regards, Fiery