Different CPU temperature readings

[Qu9ke]

For what it's worth I have the AMD FX-6300 cpu.
I have two different questions.

1. Why is the cpu temp reading in ASRock eXtreme Tuner different than the readings I get on Cam and HWiNFO?

2. What is the difference between these two cpu readings in HWiNFO? The second cpu reading must be the same reading that ASRock eXtreme Tuner is getting, whatever it is.

 

[atljsf]

no sensor is perfect, each tool reads based on their own drivers and parameters

keep this in mind, mainboard says my cpu is runnign hot, hw info seems to point to the same

amd overdrive says it is running at -270°c

my hand touching the heatsink says it is at 50 something

you can't believe anything the sensor says

try with hwmonitor, it will tell you differnet values, openhardwaremonitor might don't even tell you any value, such is life

theoretically, if the sensor is ok, believe the source, here would be asrock, followed by your hand telling you if it is running hot or cold

 

[Qu9ke]

no sensor is perfect, each tool reads based on their own drivers and parameters

keep this in mind, mainboard says my cpu is runnign hot, hw info seems to point to the same

amd overdrive says it is running at -270°c

my hand touching the heatsink says it is at 50 something

you can't believe anything the sensor says

try with hwmonitor, it will tell you differnet values, openhardwaremonitor might don't even tell you any value, such is life

theoretically, if the sensor is ok, believe the source, here would be asrock, followed by your hand telling you if it is running hot or cold

I can understand that no sensor is perfect, but hwinfo and cam both line up perfectly telling me the same readings as does hwmonitor, so I feel I can trust them. What I still don't understand is why there are two cpu readings in hwinfo. I don't know which one to rely on when using an overlay when playing games and what not.

Update: I have come to the conclusion however wrong it may be that the first cpu reading in HWiNFO is the core temp and the second reading is the socket temp.

 

[atljsf]

socket theoretically would be tmpin0 or 1, in this case is systin0

but it doesn't come from the cpu, it comes from the mainboard

it could be the app reading the same sensor twice, with different readings, as i mentioned, the driver on the app could b wrong, or the sensor not be a great one, doing weird readings

form the two you point, one if cpu reading, the other is mainboard, not sure the rest, some readings as you see are just the same reading repeated