Questionable cpu and gpu heat HELP

Arfast

Prominent
Jun 10, 2017
3
0
510
So I recently upgraded my case to the Phanteks p400s TG and I've noticed quite a bit of heat from the exhaust fan (notably it's just getting into summer so it's considerably warmer as well).

Anyways, I have an amd fx-8320 cpu and windforce nvidia gtx-960, and have been monitoring both with HWMonitor and AMD overdrive.

in HWMonitor it's recorded the cpu as reaching up to 63 degrees, while AMD overdrive hasn't had it reach higher than 40 degrees. I can feel the top of my case getting warm and the exhaust air is pretty warm also, but I don't think it's hot enough to match what HWMonitor says (60 degrees)

So my question is, should I be worried? or just trust that amd overdrive is accurate and not worry about it, I don't want to be frying my hardware :/

Any advice would be much appreciated, thanks :)
 
Solution
First of all, get rid of HWmonitor, it's NOTORIOUSLY inaccurate and has very poor support for AMD chipsets in general and is spotty on Intel chipsets. Also, Overdrive generally does not show CPU temperatures. It shows "distance to Tjmax" which is a calculated distance to max temp before throttling begins. Use HWinfo, the picture will be much clearer.

HWinfo has MUCH better accuracy and much broader chipset support. I can't point you to about nine hundred threads, just here at Tom's, where incorrect sensor info was being reported by HWmonitor and switching to HWinfo clarified or eliminated the "problem" they were seeing.

In order to help you, it's often necessary to SEE what's going on, in the event one of us can pick something out...
First of all, get rid of HWmonitor, it's NOTORIOUSLY inaccurate and has very poor support for AMD chipsets in general and is spotty on Intel chipsets. Also, Overdrive generally does not show CPU temperatures. It shows "distance to Tjmax" which is a calculated distance to max temp before throttling begins. Use HWinfo, the picture will be much clearer.

HWinfo has MUCH better accuracy and much broader chipset support. I can't point you to about nine hundred threads, just here at Tom's, where incorrect sensor info was being reported by HWmonitor and switching to HWinfo clarified or eliminated the "problem" they were seeing.

In order to help you, it's often necessary to SEE what's going on, in the event one of us can pick something out that seems out of place, or other indicators that just can't be communicated via a text only post. In these cases, posting an image of the HWinfo sensors or something else can be extremely helpful. Here's how:

*How to post images in Tom's hardware forums



Run HWinfo and look at system voltages and other sensor readings.

Monitoring temperatures, core speeds, voltages, clock ratios and other reported sensor data can often help to pick out an issue right off the bat. HWinfo is a good way to get that data and in my experience tends to be more accurate than some of the other utilities available. CPU-Z, GPU-Z and Core Temp all have their uses but HWinfo tends to have it all laid out in a more convenient fashion so you can usually see what one sensor is reporting while looking at another instead of having to flip through various tabs that have specific groupings.

After installation, run the utility and when asked, choose "sensors only". The other window options have some use but in most cases everything you need will be located in the sensors window. If you're taking screenshots to post for troubleshooting, it will most likely require taking three screenshots and scrolling down the sensors window between screenshots in order to capture them all.

*Download HWinfo
 
Solution