Fiery

Thank you for the screen shot. We've implemented support for the new temperatures. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the data. We've fixed the sensor readings for your motherboard. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

You can use the Sensor Icons feature (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Sensor Icons) to display sensor values on System Tray icons. Regards, Fiery

Yes, AIDA64 configuration settings are completely OS independent. Regards, Fiery

Nothing changed about startup configuration between AIDA64 v1.50 and v1.60. I think the problem is that you try to hide the main window, and also you want to hide the AIDA64 System Tray icon. You can only do one of them, but not both combined. That limitation is because if you could hide both the main window and the System Tray icon, then you may end up "losing" AIDA64 -- not being able to restore the application in any ways.

Please post a screen shot of the Cache & Memory Benchmark Panel at both settings. If it's possible, please run the Cache & Memory Benchmark 3 times, to see how stable the results are. BTW, Sandra only measures memory copy bandwidth, so the value you could compare in AIDA64 is the Memory Copy benchmark. And the Memory Copy seems to be the least affected by the C-State setting.

Please send a screen shot that shows the measured voltages in E-LEET next to AIDA64 Sensor page. And please also copy-paste an ISA Sensor Dump Thanks, Fiery

No need to do that. Just download the latest beta ZIP package, and extract the ZIP contents straight into the installation folder of AIDA64. Let it overwrite any existing files. Your old configuration settings will be retained. Latest AIDA64 beta is available at: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip

Thanks for the feedback I've put a sticky on this

Please try to disable the option "nVIDIA GPU SMBus access through nVIDIA ForceWare" in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. Let me know if it helps.

1) Do you have any RAID arrays defined? 2) Do you have any external (USB, FireWire or eSATA) drives connected? 3) Do you have a GeForce 4xx or 5xx card? 4) What motherboard and CPU do you have? Thanks, Fiery

I think those spikes are most likely because of the sensor chip providing instable values. In case your PSU would provide such unstable values at cases, your system should sometimes lock up. BTW, 5.6V for the +5V rail seems a bit high. Do you use an old AIDA64 version that does not fully support your motherboard? Or your PSU really puts out 5.6V?

Thank you for the feedback

Thank you, the next beta release of AIDA64 will fix that issue. The actual thing changed between those Everest builds were the ForceWare interface support for GF100 based cards. Hence with Everest v5.50.2100 the SMBus access was always done directly. --- We've done some more test runs on our Gigabyte GTX470 test card, and it seems the issue is related to the ForceWare driver calls, and so it is not a bug related to AIDA64 I'm afraid That effectively means performing direct SMBus access, to avoid ForceWare interface performance issues. Further improvement can be achieved by disabling the option "GPU fan speed measurement" in AIDA64 / Preferences / Stability, when GPU fan monitoring is not required.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) 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. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

Thank you. So it seems AIDA64 measures the same weirdly low CPU temperature as Asus' software It may be a hardware implementation issue.

We've implemented GPT support in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

In case you mean the core temperatures, then maybe you need to adjust the TJMax temperature to a higher value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery

Thank you, we've implemented the temperature readouts in the following beta release of AIDA64: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that there's a slim chance the measured CPU temperature is lower by a fixed value (e.g. by 10 Celsius) than the actual one. In such case, both at idle and under load a certain offset will be shown compared to the actual CPU temperature. In case you have an Asus temperature monitoring software on hand, you can verify the CPU temperature using that. Thanks, Fiery

Thank you, we've fixed the +12V reading in the following beta release of AIDA64: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

If you want to override the automatic settings used to calculate core temperatures, go to AIDA64 / main menu / File / Preferences / Hardware Monitoring, and adjust TJMax temperature to 100 Celsius. Regards, Fiery

1) Close AIDA64 2) Start REGEDIT.EXE (Registry Editor) 3) In the left panel navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 4) In the main panel search for OSDPosX and OSDPosY, and modify their values both to 0 5) Then try to move the OSD Panel to the right side of the desktop. Regards, Fiery

Even though AIDA64.EXE is a 32-bit application, the benchmarks and the System Stability Test are fully ported to 64-bit, and they are in the AIDA_BENCH64.DLL module. Legacy 32-bit benchmarks and the 32-bit version of the System Stability Test are held in the AIDA_BENCH32.DLL module.

Debug information is there to help us diagnose various issues, and to implement support for new hardware. You can turn off debug info in AIDA64 / main menu / File / Preferences / Report. Regards, Fiery

Are you sure the issue is with AIDA64? Maybe TMS-200 software fails to update the shared memory content after waking up from sleep. BTW, we've tested it with an Asus P8P67 motherboard and a TMS-200, under Win7 64-bit SP1, and this system doesn't seem to be affected by this issue.