Fiery

I'm afraid it's not AIDA64. FX processors feature a temperature diode that measures wrong temperatures in basically all conditions. Usually that temperature is unrealistically low, well below ambient temperature. So far noone seems to have an idea on how to implement a workaround. It already happened before, with some AM2 processors, and there a simple offset helped to get proper temperatures. Maybe this time it's the same, but AMD didn't provide any useful information on the issue. Regards, Fiery

NetUpdate is not meant to be translatable, so we wouldn't need to fix that We'll check the "OK" issue. Thanks, Fiery

AIDA64 reads BIOS Settings (as listed on the Motherboard / BIOS page) using Asus ATK BIOS calls. Hence those values reflect the values Asus BIOS provides to Windows applications. In your case I'm afraid there's a BIOS bug that results in improper DRAM voltage calculation by the BIOS. It doesn't mean the BIOS uses the wrong DRAM voltage, so you don't have to worry about that. It's a minor glitch that only affects software that read out the BIOS Settings via Asus ATK BIOS calls. Regards, Fiery

Thank you for the data. It looks like a tough one though (to figure out the voltage registers and voltage ratios), so if it's possible, please provide us with more data. Please go the BIOS Setup and note down all values you can see on the M.I.T.\PC Health Status page, all temperatures, voltages and fan speeds measured there. Or, alternatively, you can also make a photo of that page, if it's easier for you. In case your voltage settings have changed since you made the dumps above, then please create a new ISA Sensor Dump to make sure the BIOS Setup PC Health Status values match the dump. Thank you for your time. Regards, Fiery

"CPU" temperature reflects the surface temperature of your processor, measured by the onboard sensor chip built onto your motherboard. Your processor itself has quite a few temperature diodes integrated onto certain parts of the CPU die. "CPU Package" reflects the average inside temperature of your processor, "CPU IA Cores" is the average temperature of the processing cores (classic CPU cores) part, "CPU GT Cores" is the temperature of the HD Graphics IGP (integrated GPU of your processor), while the "CPU #1 / Core #n" temperatures are the per-core temperatures. I hope this helps Regards, Fiery

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 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 results into this topic. Based on those data we can investigate this issue and implement the missing sensor values Thanks, Fiery

Thank you for the feedback

That is due to the infamous ULPS feature of AMD Catalyst drivers. You need to disable ULPS to make AIDA64 work 100% reliably. You can disable ULPS by setting all occurences of EnableUlps to 0 (zero) in the Registry, using Registry Editor (REGEDIT.EXE). Regards, Fiery

Please contact ABSEIRA Ltd. (info AT abseira.com), our distributor about this matter. I'm sure they will be able to figure out something for such a special purpose Regards, Fiery

The MemBW dump is an experimental hidden feature It's not a problem if it doesn't work "nicely", since it's not intended for general use.

Thank you

Thank you for the feedback

Thank you for the feedback

We've implemented a new option in AIDA64 / main menu / File / Preferences / Stability to let you disable GPU sensor support. So far we haven't found a better way to prevent nVIDIA drivers from "waking up" the sleeping GPU while reading GPU sensor values in AIDA64 Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...40jw8gb7pkfzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

I'm sorry for the delays. It took quite a while to reproduce the issue and fix it up. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...40jw8gb7pkfzzip 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. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...40jw8gb7pkfzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Display / GPU page in AIDA64 You can navigate there using the left page menu in AIDA64.

Then please try to go to the Display / GPU page, and select all video adapters you have, one by one. Let me know if it triggers the same desktop refresh or not. We need to narrow this down to a specific part of the hardware monitoring module of AIDA64 BTW, what kind of Windows do you have installed? Win7? 32-bit or 64-bit?

I'm pretty sure the HFM issue is not related to AIDA64 at all, so I'm afraid I can't help you about that. AIDA64 does change power management settings before running benchmarks, but it changes them in a way to squeeze out the most performance from the CPU. It definitely doesn't alter power settings in a way to make the CPU run at LFM. As for the 50C vs. 60C issue, you can lower TJMax temperature (in AIDA64 / main menu / File / Preferences / Hardware Monitoring) if you're adament that Everest was more accurate on core temperature measurement.

1) The access violation error may be a bug in AIDA64, a bug in Intel RAID drivers, or an issue where AIDA64 communicates with the Intel RAID drivers. We'll try to reproduce this issue in our labs, and then fix it up if possible. I'll drop a message in this topic once we have an update to this matter. Until then, you can simply ignore the access violation issues, since I'm confident it doesn't mean there's a stability issue with your system. However, in case while running the Stability Test a BSoD occurs, or the system locks up, then there's a stability issue 2) The warning about EC is simply due to AIDA64 communicating with the EC chip (Embedded Controller) of your motherboard. We've done some improvements in the past few months to try eliminating those warnings by rewriting the EC communication layer of AIDA64. The new layer works much better, but in rare cases it may still trigger something in Windows kernel that causes the kernel to place such warnings in the Event Logs. It's not a problem at all, it doesn't affect system stability or system performance at all, so you can simply ignore those warnings. The MSI motherboards don't have an EC chip, hence AIDA64 doesn't use EC communications on them. Regards, Fiery

Please try to disable Low-level SMART operations in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. Let me know if it makes the issue go away, or it still persists. Thanks, Fiery

Intel core temperature diodes are well known to have accuracy issues. Accuracy is only guaranteed close to TJMax. You don't need to worry too much about temperatures as long as your processor is not throttling under heavy load.

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 --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. Thanks, Fiery

On most motherboards (including most Asus boards) the motherboard temperature equals to the internal temperature reading of the sensor chip that is integrated on the motherboard PCB. On your motherboard however the sensor chip reads the motherboard temperature from a special register that is only used on a handful of Asus motherboards to measure temperature. So we simply had to modify the motherboard-specific sensor code for your motherboard to switch from the usual register to the special register

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1734k9g4vtlhfszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery