HWINFO shows higher GPU temperature than MSI Center and Afterburner

Chip_Iron

New Member
Hello everyone,


I have an RTX 5080 MSI GAMING TRIO OC GPU. I’ve been trying to monitor its temperature using HWINFO, but the temperature it shows (43ºC) is very different from what MSI Center (27ºC), MSI Afterburner (27ºC), and even the Windows Task Manager performance tab (27ºC) are reporting.


Is there a known issue with HWINFO that could cause it to show a higher temperature? Or am I possibly doing something wrong?


Thanks in advance for your help!
 

Attachments

  • hwinfo.png
    hwinfo.png
    551.9 KB · Views: 4
I see the GPU load fluctuates a lot, so the temperature should be as well. In such case when each app measures the value at a different time point, it could be different. Can you compare the values at constant GPU load?
Also, another reason could be a bug in NVIDIA drivers when temperature reporting might become stuck. It will freeze in most tools but not in HWiNFO.
 
Last edited:
Also, another reason could be a bug in NVIDIA drivers when temperature reporting might become stuck. It will freeze in most tools but not in HWiNFO.
Most likely the case, the reading stuck on the lower temp value (see 27C as min on HWiNFO64)

Hello everyone,


I have an RTX 5080 MSI GAMING TRIO OC GPU. I’ve been trying to monitor its temperature using HWINFO, but the temperature it shows (43ºC) is very different from what MSI Center (27ºC), MSI Afterburner (27ºC), and even the Windows Task Manager performance tab (27ºC) are reporting.


Is there a known issue with HWINFO that could cause it to show a higher temperature? Or am I possibly doing something wrong?


Thanks in advance for your help!
On the good side if the fans are on the driver control it continues to read the temp correctly (internally) and adjust rpm as it should.
The real problem is when someone uses a third-party software fan controller like afterburner for example. Then fans will stuck at minimum too like the temp reading, causing thermal throttle.
I think it was fixed with v576.15 (hotfix)


 
Back
Top