Jump to content

Fiery

Administrators
  • Posts

    11186
  • Joined

  • Last visited

  • Days Won

    475

Posts posted by Fiery

  1. 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

  2. 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

  3. 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

  4. "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

  5. 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

  6. 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

  7. 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.

  8. 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

  9. 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 :)

×
×
  • Create New...