Motherboard Temps reading from the wrong sensor

[Gh0stw0lf]

Hello all, I'm hoping someone here can shed some light on what's happening here.

I have the latest experimental BIOS 1403 (I already upgraded from 1401 to see if it would solve this temp issue, it hasn't)

HARDWARE:

• Ryzen 1700 with Stock Cooler
  

So across all programs, my temps are reading extraordinarily low 19C - 21C under load, they read this in HWMonitor, UEFI Bios, and Ryzen Master. Sometimes If I'm manually overclocking through Ryzen Master or Bios, the temps will show the right temperature but it isn't usually consistent.

As of late, though, I had been having alot of issues like the computer crashing and saying the reason for the error was that the CPU got too hot. I was dumbfounded; at first I thought that my CPU Wraith Cooler had stopped working but that wasn't the case. As I tried 2 other air cooler to have the same crashes occurring.

It wasn't until I was monitoring temps in CPU HWMonitor that I noticed that TMPIN0 matched my ambient temps and TMPIN2 was matching typical CPU temps 30 idle and up to 49c and 50 underload. However, since the motherboard is reading from the wrong sensors, my fans would never kick on to keep my CPU cool which would lead to 95c temps and consequently the compouter would shut down or I'd have system crashes.

I managed to compensate for this by adjusting my fan curve to account for this but is there anyway to get this solved so that I can have the most efficient cooling? I'm not really sure what to do here.

[MrAgapiGC]

try HWiNFO64 or Aida64 and Coretemp 1.9 i just download it and fix some sensor readings. I did get a good use o nthe hwinfo64. Most problems are to many readings programs. try the ones i add. has work fantastic.

[LIONDOG]

I have same ploblem.
My room already 32C, but AIDA64 and AMD Ryzen Master still show 24c...

[Gh0stw0lf]

LIONDOG wrote:
I have same ploblem.
My room already 32C, but AIDA64 and AMD Ryzen Master still show 24c...

Good to know I'm not the only one. What BIOS are you running?

[LIONDOG]

Gh0stw0lf wrote:
Good to know I'm not the only one. What BIOS are you running?

BIOS is 1403

HWMonitor same 😞

[Sjf2k17]

Gh0stw0lf wrote:
Hello all, I'm hoping someone here can shed some light on what's happening here.

I have the latest experimental BIOS 1403 (I already upgraded from 1401 to see if it would solve this temp issue, it hasn't)

HARDWARE:

• Ryzen 1700 with Stock Cooler
  

So across all programs, my temps are reading extraordinarily low 19C - 21C under load, they read this in HWMonitor, UEFI Bios, and Ryzen Master. Sometimes If I'm manually overclocking through Ryzen Master or Bios, the temps will show the right temperature but it isn't usually consistent.

As of late, though, I had been having alot of issues like the computer crashing and saying the reason for the error was that the CPU got too hot. I was dumbfounded; at first I thought that my CPU Wraith Cooler had stopped working but that wasn't the case. As I tried 2 other air cooler to have the same crashes occurring.

It wasn't until I was monitoring temps in CPU HWMonitor that I noticed that TMPIN0 matched my ambient temps and TMPIN2 was matching typical CPU temps 30 idle and up to 49c and 50 underload. However, since the motherboard is reading from the wrong sensors, my fans would never kick on to keep my CPU cool which would lead to 95c temps and consequently the compouter would shut down or I'd have system crashes.

I managed to compensate for this by adjusting my fan curve to account for this but is there anyway to get this solved so that I can have the most efficient cooling? I'm not really sure what to do here.

Don't know if this will ease your worries but the Ryzen 1700x and 1800x read incorrectly anyway -*https://www.techporn.ph/amd-clarifies-ryzen-7-1800x-1700x-temperature-readings/ also the factory sensors aren't always precisely accurate I prefer using my corsair link utility for my temps.

[gupsterg]

I would advise members to use HWINFO, as this post is based on sensors as labelled in that program.

On UEFI 1403, for non X CPU set Sense MI Skew: Disabled. tCTL/CPU Sensor will be realistic and correct.

On UEFI 1403, for X CPU, also set Sense MI Skew: Disabled.

tCTL has had the 20°C offset removed but CPU Sensor under "Asus Crosshair VI Hero" section of HWiNFO, has not been set to match tCTL in the case of X CPU. CPU Sensor is Super IO Chip reading of tCTL and removing a further 20°C.

So with Sense MI Skew: Disabled, tCTL has the 20°C offset present that AMD state X CPU has. CPU sensor has the 20°C offset removed, that AMD state X CPU has. As the CPU sensor reading is used by UEFI for fan profiling cooling/fan profiles will behave correctly. Then also CPU sensor / tDIE is realistic temperature. tDIE in HWiNFO is not a real sensor, but author of SW has set this "sensor" to show tCTL with 20°C offset removed. This was due to early UEFI (plus some other vendors currently) did not have offset for X CPU removed from tCTL.

Below is a screenshot a member sent me on OCN when asking for help on how to set Sense MI Skew, it is an X CPU, UEFI 1403 used.

[Gh0stw0lf]

gupsterg wrote:
I would advise members to use HWINFO, as this post is based on sensors as labelled in that program.

On UEFI 1403, for non X CPU set Sense MI Skew: Disabled. tCTL/CPU Sensor will be realistic and correct.

On UEFI 1403, for X CPU, also set Sense MI Skew: Disabled.

tCTL has had the 20°C offset removed but CPU Sensor under "Asus Crosshair VI Hero" section of HWiNFO, has not been set to match tCTL in the case of X CPU. CPU Sensor is Super IO Chip reading of tCTL and removing a further 20°C.

So with Sense MI Skew: Disabled, tCTL has the 20°C offset present that AMD state X CPU has. CPU sensor has the 20°C offset removed, that AMD state X CPU has. As the CPU sensor reading is used by UEFI for fan profiling cooling/fan profiles will behave correctly. Then also CPU sensor / tDIE is realistic temperature. tDIE in HWiNFO is not a real sensor, but author of SW has set this "sensor" to show tCTL with 20°C offset removed. This was due to early UEFI (plus some other vendors currently) did not have offset for X CPU removed from tCTL.

Below is a screenshot a member sent me on OCN when asking for help on how to set Sense MI Skew, it is an X CPU, UEFI 1403 used.

Wow, I feel like a dolt. This worked!

[LIONDOG]

gupsterg wrote:
I would advise members to use HWINFO, as this post is based on sensors as labelled in that program.

On UEFI 1403, for non X CPU set Sense MI Skew: Disabled. tCTL/CPU Sensor will be realistic and correct.

On UEFI 1403, for X CPU, also set Sense MI Skew: Disabled.

tCTL has had the 20°C offset removed but CPU Sensor under "Asus Crosshair VI Hero" section of HWiNFO, has not been set to match tCTL in the case of X CPU. CPU Sensor is Super IO Chip reading of tCTL and removing a further 20°C.

So with Sense MI Skew: Disabled, tCTL has the 20°C offset present that AMD state X CPU has. CPU sensor has the 20°C offset removed, that AMD state X CPU has. As the CPU sensor reading is used by UEFI for fan profiling cooling/fan profiles will behave correctly. Then also CPU sensor / tDIE is realistic temperature. tDIE in HWiNFO is not a real sensor, but author of SW has set this "sensor" to show tCTL with 20°C offset removed. This was due to early UEFI (plus some other vendors currently) did not have offset for X CPU removed from tCTL.

Below is a screenshot a member sent me on OCN when asking for help on how to set Sense MI Skew, it is an X CPU, UEFI 1403 used.

Thank you so much!!:o