So while you say "AT THE SAME TIME", it most likely is a couple seconds apart. Some programs may sample the sensor every 2 seconds, others every 5 seconds, others every 1.5million CPU clock cycles. This is because, once again, there are no standards for sampling rates or sampling times. Note there will almost always be small differences. If there is a consistent and large discrepancy between monitoring programs, then probably the sensor is faulty. That means if a hex number of 1ef8c7b4 = 60☌, then every monitoring program should represent that 1ef8c7b4 as 60☌.
#Amd system monitor won showing gpu software#
The sensor makers publish this information and make it available to all the hardware makers and monitoring software developers. There is nothing proprietary or magical or secret about that hexadecimal number. And the monitoring programs then take that hexadecimal number and convert it into an understandable Celsius or Fahrenheit value. The only consistent part is what they do - they sense a temperature and represent that value with a hexadecimal number. They are not precision, medical-grade quality by any means.
That is, they are very low-tech, cheap devices. And then every motherboard/BIOS/Chipset maker have their own way of monitoring temps.Īnother problem is these sensor devices are a dime a dozen. Even between AMD and Intel, there are no standards.
That is, there is no standard for which type sensor, where they are placed, or how they are monitored.
Click to expand.There is no good reason but I note part of the problem is there is no industry standard for sensors.
0 kommentar(er)
