HW Monitor is reporting every core of my CPU as 287 degrees C. Obviously this is incorrect and there would clear signs of an issue. Flames being the most tell tale sign.
It’s an old AMD FX-6100 that’s driving a Plex Server. The machine is working absolutely fine, feeding up to 4 1080p streams at once with seemingly no issues. The server is, and has been on 24/7 for almost 6 years except for the usual maintenance.
The question is does the CPU need replacing?
Also as the CPU temps are wrong and if the CPU fan fails would the wrong temp readings prevent the machine from automatically shutting down due to overheating? Now that would be a major fire hazard.
Thanks in advance for any advice.
I overclocked my AMD 8320 to 4.00 ghz and ran prime 95 for 2 hours with a maximum temp of 73 degrees on load. Later on I played planetside 2 for 40 mins & I was getting ready to hit the bed. I logged out of the game and saw something really alarming!! Current CPU temp was at 55. Which was fine becasue I just got out of the game but the max temp was reading at 161 Degrees!!
Which is impossible because the Cpu should throttle itself down and turn the PC off before anything like that would ever happen. Hell my cpu & board should be fried if it went over like that.
My questing is it normal for HWmonitor give false reading? or am I missing something!!
Just wondering, because I've run Cyperpunk on UltraRT and thermals sit anywhere between high 70s and mid 80s, and I can clearly feel the heat above my case if I touch it.
However, sometimes (randomly) when running not nearly as intensive games it will sit around high 80s and 90s on HWMonitor, and it is clearly not hot at whatsoever. I ran Diablo 2 resurrected and my GPU (RTX 3080) was at a comfortable 45-50, but the CPU was at high 80s, even 90 (again, not warm at all) .
I know most recommend using HWinfo, so I'm wondering if this is a common thing for HWMonitor. Thanks!
The max temperature for many CPUs is listed in the 105-110°C range. But for long-term use, you’re much better off keeping things below 80°C in general and only pushing up to 85°C at the most
To make sure your software is giving you an accurate reading you could compare the results with those of another temperature monitoring application. There are several free lightweight tools to monitor your CPU temperature, one of which is Core Temp.
It would be advisable to check your heat sink to see if it has been dislodged, or that the thermal paste is still connecting the heat sink to the CPU, as running your CPU at that temp is sure to cause damage in the long run.
The GPU temperatures that are shown in your question are not in the danger zone.
You're well into the range that can cause permanent damage to the CPU. Most consumer electronics (including CPUs) are not designed to operate above 85 °C for any extended period of time, and most will actually shut down when they get over about 100-105 °C. Provided you have a working (and properly sized) cooling system and are not somewhere with unusually high temperatures to begin with (40 °C or higher), you should not be seeing temperatures that high no matter how hard you push the CPU.
However, I'm inclined to believe something is wrong with your system due to that insane discrepancy between reported package and core temperatures. In particular, the possibilities that come to mind are:
- The sensor isn't being read correctly and the core temperature is actually much lower. This is the best possible case, and it's easy to check (try a handful of other tools for reading these sensors. Everything else reporting similar temperatures does not rule this out though, because the drivers being used to make the reading may be bad (you can check that case by booting into a live Linux environment and seeing what it says the temperatures are. I know 100% for certain that Linux reports the temperature correctly on that model of CPU because the sensor interface the CPU provides has been around since the AMD K10 days and is very well supported by Linux).
- The sensor isn't being read correctly, and the package temperature is actually much higher. This is extremely unlikely, because for it to be the case you have to have somehow managed to run a CPU with a 20 W TDP so hard that it got that hot. The only possibilities I can think of that would allow for that are running with no cooling system at all or running in an environment that was already unlivably hot for humans.
- Something is wrong with one of the temperature sensors. It is not very likely, but it is still possible. If you've eliminated the two above possibilities, then this one can be checked by using a (good) infrared thermometer or (real) thermal camera to get an estimate of the temperature of the junction between the heat-sink and the IHS. If that reads back at close to 115 °C, then the package temperature sensor is bad (and something else is probably wrong with your CPU). If it reads back at close to the 66 °C being reported by the package temperature sensor, then either something is wrong with the core temperature sensor or the next (worst case) possibility is the case.
- Something is physically wrong with the thermal junction inside the package between the IHS and the CPU die. This is the absolute worst case scenario, as it means your chip is essentially useless (because you quite simply cannot cool it well enough for it to be practically usable. This is also astronomically unlikely (actually, it's beyond astronomically unlikely, it's even beyond the unlikelihood of a SHA-256 hash collision with two randomly chosen files), but it's still technically possible. There's unfortunately no practical way to check this one if you've eliminated all the other possibilities, because delidding the CPU to manually check will make it irrelevant (and also require use of a completely different cooling system).
!SOLVED!
Hi I just upgraded from my i5 8400 to a i5 12400f and when I open hw monitor I don't see any temperatures , I only see the utilization tab under "Intel processor". Can someone explain what's happening here? I didn't have this issue with my i5 8400
Edit:I'm leaving this embarrassing post online so that anyone else with the same issue can see it
What you need to do is update HWmonitor