So it's probably either a sensor which doesn't actually exist, one not calibrated right or one which shouldn't be exposed. It's not locked at a maximum, normally 125C, or a minimum, so it's not a short. The board is recent, so it's not an aged thermistor (recent boards use diodes). That your temperature being read changes, I've seen you post 114C and 117C, means it likely is not a faulty sensor. These chips, and those settings, can be altered freely at runtime (SpeedFan does this). Sensor chips also have offsets (which can be wrong), calibration curves (can be wrong) and a selection of whether their pin is reading a thermistor or a diode (can be wrong).
Some sensor chips support dozens of sensors, a simply typo error in UEFI code can change sensor #07h to being sensor #17h. Thermistors age (faster when hot) while diodes can undergo an avalanche effect and lock at a particular reading. The diode or thermistor itself can be faulty. that's why you don't use speccy to monitor temps. I've put in the comments other results from other softwares. There are many ways a temperature sensor can give a silly number. Speccy says my cpu temp is around 100 degrees While AMD master and CoreTemp are saying it is about 49 degrees Should I be worried, should I do something about it I now have nzxt s340 with stock fans and a Ryzen 2600X with stock fan. Speccy is known for sometimes being a little funky with temps, try using something else and seeing if that reports the same results.
0 kommentar(er)
