Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Wrong CPU Socket Temperature on Asus Crosshair VII Hero
#1
Hi all,

I am facing an issue with HWInfo reporting wrong CPU Socket temperatures on a Asus Crosshair VII Hero (AMD X470) motherboard. The CPU Socket temperatures seem to be an exact copy of the PCH Temperatures, and are very high compared to the CPU Temperatures being reported. This happens even when the system is idling.

I have tried Reinstalling HWInfo, a clean install of windows and even rolled back to a previous bios version with no change.

This wasn't the case until about a week ago, and is a recent issue. Will appreciate any help on the matter.


Attached Files
.dbg   HWiNFO64.DBG (Size: 947.38 KB / Downloads: 3)
Reply
#2
CPU (Socket) temperature on these series of mainboards is an 'unofficial' value, it's possible that ASUS changed something in recent BIOSes and this value now reflects the chipset value.
I propose to ignore this.
Reply
#3
(01-13-2019, 03:37 PM)Martin Wrote: CPU (Socket) temperature on these series of mainboards is an 'unofficial' value, it's possible that ASUS changed something in recent BIOSes and this value now reflects the chipset value.
I propose to ignore this.

Thanks for the response, but a BIOS reset seems to fix the issue, and the problem pops up only when I configure a few OC parameters. Will investigate further and narrow it down to the specific setting.

Edit: I have attached the latest debug file, could you please check it and let me know what has changed to fix the issue?


Attached Files
.dbg   HWiNFO64.DBG (Size: 911.62 KB / Downloads: 1)
Reply
#4
Hi Martin,

Not noted an issue same as fullterms on C7H WIFI, used all UEFIs since launch of mobo with HWINFO. If you can take the time to check debug file it would aid us to perhaps get an inclining on what is going on.

Cheers
Gup
Reply
#5
Sorry guys, but in this case all sensor values are provided by the BIOS via WMI and HWiNFO doesn't touch the SIO nor EC anymore (to avoid issues).
It's completely in the hands of the BIOS and I assume they changed something here (either the SIO temperature source, or report this value from EC).
ASUS should be able to provide more details.
If you'd like to switch back to the original method (with the risk of issues when accessing the SIO), put the following line at the end of HWiNFO64.INI file:
AsusWMI=0
Reply
#6
(01-14-2019, 10:32 AM)Martin Wrote: Sorry guys, but in this case all sensor values are provided by the BIOS via WMI and HWiNFO doesn't touch the SIO nor EC anymore (to avoid issues).
It's completely in the hands of the BIOS and I assume they changed something here (either the SIO temperature source, or report this value from EC).
ASUS should be able to provide more details.
If you'd like to switch back to the original method (with the risk of issues when accessing the SIO), put the following line at the end of HWiNFO64.INI file:
AsusWMI=0

Ok thanks for thisĀ  Wink .

I'll get fullterms to compare EC FW with me. Perhaps then roll back a UEFI so SIO FW is downgraded, then reflash newer (which has SIO FW update) to see it resolves the issue for him Smile .
Reply
#7
Thanks for the input guys, I think I have traced the issue.

The error occurs when I configure Chassis Fan 1 to use PCH as the temperature source in BIOS.

I tested various combinations and have attached the logs for your review.

Fans headers used for testing -ChFan1, ChFan2, HAMP Fan
Temperature Sources - CPU, PCH, T Sensor
BIOS Version - 1201.


Attached Files
.dbg   Error - ChFan1-PCH--Chfan2-PCH.DBG (Size: 863.66 KB / Downloads: 0)
.dbg   Error - ChFan1-PCH--HampFan-CPU.DBG (Size: 713.24 KB / Downloads: 0)
.dbg   Error - ChFan1-PCH--HampFan-PCH.DBG (Size: 646.13 KB / Downloads: 0)
.dbg   Works - ChFan1-CPU--HampFan-CPU.DBG (Size: 713.19 KB / Downloads: 0)
.dbg   Works - ChFan1-CPU--HampFan-PCH.DBG (Size: 1.08 MB / Downloads: 0)
Reply
#8
Attaching the last test result to this post.


Attached Files
.dbg   Works - ChFan1-TSensor-ChFan2-PCH-HampFan-PCH.DBG (Size: 681.77 KB / Downloads: 0)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)