Fiery

Thank you. Please keep on using Build 1462 until the next beta is released. We're in the middle of revamping the Logitech LCD module, to implement SensorPanel-like features and multiple devices support. The next beta with those improvements should be out early next week. It will hopefully fix the mentioned bug as well. If the bug persists, then please let us know about it.

On your system it's best to watch the "CPU" temperature, since the core temperatures may be off by 10-15 degrees Celsius due to incorrect TJMax value. If you intend to test the stability and thermal status of your overclocked system, then start AIDA64, go to main menu / Tools / System Stability Test, uncheck all tests except for FPU, and press the Start button. Then watch the bottom graph that shows the throttling status of your CPU. The throttling should stay at 0% all the time, even after several hours of stress testing. In case your CPU shows any throttling activity, then your CPU is overheating and throttles itself down to protect itself from physical damage. In case the System Stability Test displays an error message, or your computer turns off, or your computer restarts, or Windows throws a BSoD (Blue Screen of Death), then your system is not stable.

The issue is caused by the infamous ULPS feature of AMD Catalyst driver that switches off the secondary GPU in CrossFire systems. Please try to disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability. In case it doesn't help, then you need to disable ULPS completely by scanning the Registry for EnableUlps entries and setting them all such entries to zero.

Please try to downgrade to AIDA64 Beta Build 1462, and let me know if it works flawlessly or has the same issue. Thanks, Fiery

Please let us know more about your system. Do you have a RAID array? What video card (or video cards) do you have? Thanks, Fiery

Please note that the core temperatures are measured by a different method than the "CPU" temperature, hence you're not supposed to compare them to each other. Core i3/i5/i7 processors have an internal register to indicate the correct TJMax. AIDA64 reads that register to detect the TJMax value. Hence adjusting the TJMax is not advised, since it makes core temperature measurement out of Intel's DTS specifications. Thank you for the feedback

Even if you have a clean CPU cooler, a clean CPU heatsink and a clean rear exhaust fan, they may still be too weak for the excessive heat dissipation of your CPU and video card(s). You may need to install a more powerful cooling solution, or move the complete system to a new system case that has more room and a better component arrangement.

We've changed the minimum bar width to 3 pixels in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1469s2elk8yzgnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented sensor tweakings for Gigabyte Z68XP boards in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1469s2elk8yzgnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented the T-Balancer stability option in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1469s2elk8yzgnzip 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. We've added that monitor in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1471w6elkn1gczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

During the AIDA64 System Stability Test your processor was heating up too much. You need to improve the CPU cooling by cleaning and re-seating the CPU heatsink, getting a bigger (more efficient) CPU cooler, or by installing the rear exhaust case fan. In many cases the system chassis is too crowded (too many devices, too many cables), too small, or the rear exhaust cooling is missing.

I'm afraid we can't help from our end. But if you contact Franck (the author of CPU-Z), he should be able to fix this bug in CPU-Z. We'd be happy to work with him on this matter, if he contacts us about this.

It depends on how many items do you put on the SensorPanel. But on modern multicore processors the CPU% hit of the SensorPanel rendering module is negligible.

I think it may be a fan divisor reconfiguration bug in CPU-Z. Please try to switch off the relevant option in AIDA64 / main menu / File / Preferences / Stability, and restart your computer. Then start AIDA64, go to the Computer / Sensor page, and then launch CPU-Z. Let me know how it works.

No, it's not possible with the OSD Panel. If you need more flexible items configuration, you may want to check the new SensorPanel feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel).

Thank you. On your video card "GPU Temp. #2" reports the same temperature as "GPU Temperature". If you try to put some stress (load) on your video card, you'll see that those 2 temperatures will rise and fall together. The only difference between the 2 temperature readings is the resolution: in GPU-Z the "GPU Temperature" readout has a 1 Celsius resolution, while the other 3 temperatures have a 0.5 Celsius resolution.

In the next AIDA64 beta we'll implement a new option on the Stability page of the Preferences to let you disable the T-Balancer detection. I'll drop a message in this topic once the new AIDA64 beta is available for download.

Does the Arduino's FTDI driver put a FTD2XX.DLL file into the \Windows\System32 folder? AIDA64 uses that DLL module to issue commands to T-Balancer sensor devices.

We've done a test run on a HD5770 card, and on our HD5770 card GPU-Z didn't measure a "GPU Temperature", but only the 3 other GPU temperatures. Please do the following: 1) Post a screen shot that shows the AIDA64 Computer / Sensor page right next to the GPU-Z v0.5.4 Sensors tab. Using that screen shot we can directly compare the measured values. 2) Right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic. 3) Right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump. Copy-paste the full results into this topic. Make sure to use the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1462zqf1bnw9axzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Thanks, Fiery

AIDA64 measures the same temperatures as GPU-Z. AIDA64 temperatures on HD5770 have the following relation to GPU-Z temperatures: AIDA64 "GPU Diode (DispIO)" = GPU-Z "GPU Temp. #1" AIDA64 "GPU Diode (MemIO)" = GPU-Z "GPU Temp. #2" AIDA64 "GPU Diode (Shader)" = GPU-Z "GPU Temp. #3" Regards, Fiery

Please try to enable SMBus operations again, but disable Koolance TMS-200 support. Then restart AIDA64 to apply the changes. Let me know if it helps. BTW, do you have a T-Balancer device connected to your computer? Or the T-Balancer driver installed? Thanks, Fiery

Correct. Although, keep in mind that we never include .INI files in our beta or stable AIDA64 packages. So if you download the latest AIDA64 ZIP package, and extract all files from it into your existing AIDA64 installation folder, all your previous settings will be retained.

Do you have sensor readings in the BIOS Setup? If yes, then you can verify the CPU temperature there. I suspect the "CPU" temperature is an invalid reading on your motherboard, and either the "Motherboard" or "Aux" temperature may be the actual CPU temperature reading.

In your submitted report there's no full video BIOS dump. And since apparently you had both the Intel integrated GPU and the GeForce GTX 580 video card enabled, AIDA64 may just read the video BIOS date of the primary video adapter (the one used to boot the system), which is the Intel GPU.