CPU temp readings seem a little whack

leftisthominid

Distinguished
Jan 7, 2014
342
0
18,790
I just upgraded my stock cooler on my FX 6300 to a Hyper 212 EVO last night. I have noticed that when gaming my temp (tried both HWMonitor and Core Temp) are in the low/mid 30s. They start in the low, get to the mid over time. Oddly Prime95 running for 59 minutes only got me around 28-32 in HWMonitor.

As this is a new cooler, I am a bit confused. Are these readings normal, or is something screwed up somewhere?
 

leftisthominid

Distinguished
Jan 7, 2014
342
0
18,790


Definitely looking at the right numbers. Here is a cropped screengrab of my second monitor (while playing Assassin's Creed Unity on the first monitor)
Yj9zUrn.png


Update:
I tried running its predecessor Asssasin's Creed IV, and the temp stayed around 30-31
 

mdocod

Distinguished
I know this is going to be hard to believe.... but it's actually pretty normal to see higher temps while gaming than while running P95 on an FX-6300 with turbo core and APM active. The reason for this has to do with the way the chip's clocks and voltage scale with different workloads in order to maintain operation with the specified TDP envelope.

When you run P95, all the cores get hammered, and APM pulls back the voltage and clocks (to as low as 3.2ghz depending on the specific chip and your implementation of APM, which could theoretically vary a bit from board to board), and pulls back the voltage (to as low as ~1.15V). When running like this, the ~95W being dissipated by the chip is very spread out, evenly across the chip, the "peak" temp anywhere in the chip is low.

When gaming, the workload really only hammers on 1-3 cores hard at a time, so the chip ramps up to ~1.425V and pushes for 4.1ghz turbo speeds. This causes much higher localized temperatures even though the overall dissipation is likely no higher than it was running P95... This is why you're seeing 45C peak temps in gaming, and only ~30C peak temps in P95. This is normal...

Turn off APM/Turbo, and the phenomenon will "go away" because the chip will run at a more "fixed" voltage under a load at 3.5ghz all the time regardless.

-----------

Now.... it's important to understand that there is actually no such thing as a core temp reading from a piledriver chip. Try not to fuss too much over whether the numbers seem too high or too low in a particular piece of software because they are all WRONG. However, WRONG is fine, as long as you understand the way in which it is wrong.

On a properly calibrated scale, idle temps can read as low as 0C on piledriver, and the maximum supported continuous operating temp should read as 70C. This "range" is roughly the inverted output from AMD thermal margin, which is a very precise, but very inaccurate "calculated" temperature monitoring system. I do not know what "scale" HWMonitor is calibrated to, so I can't tell you where you are really at... but you can find out...

Use AMD Overdrive to observe thermal margin. This is the most precise way to observe your CPU temps.

------

Oh.. and on a final note... It would not surprise me at all for a properly mounted 212 EVO to give a stock 6300 some pretty HUGE thermal margin readings (very low temps). The 212 EVO's heatpipes are "tuned" to produce chart topping heat flux characteristics at loads in the ~100W range. It's not a great cooler for overclocking at 200W+, but down under 150W is probably the best heat-pipe unit out there.
 

leftisthominid

Distinguished
Jan 7, 2014
342
0
18,790

My cpu is not overclocked (yet). I think I am going to hold off on that for a little while. Also, the game play peaks may be around 45, but the norm is generally 33-35.

I had tried installing AMD Overdrive. I put AMD Overdrive and HWMonitor on my second screen and started up ACU. My CPU went up to 129C then fell to 79C on HWMonitor. I freaked out, turned off the game and uninstalled AMD Overdrive. Any idea what caused that?

I am thinking about leaving things as is for a while and just ignoring temperatures altogether (until I get around to overclocking). Good idea or bad idea?
 

mdocod

Distinguished
AMD overdrive will basically "override" the CPU thermal margin information coming from the CPU and screw up the reading in other software. This is totally normal, it happens all the time. If you want to see your thermal margin, re-install AMD Overdrive. Ignore the false data that other software spits out when overdrive is running.

HWMonitor is just software spitting out numbers, many of which are not even "real"

You'd probably be SHOCKED to find out how many of those "numbers" are actually generated or scaled from very different looking data...

For example, your voltage readings. The super IO Chip can't handle more than ~3V, so your 5V and 12V readings, are scaled back up from a scaled down reading. That "scale up" process is handled by an algorithm in the software.

How do you know they applied the right algorithm to the right input?

---------

The problem is, HWMonitor creates the "impression" that it is just giving you the numbers that are already going on somewhere else.. It isn't. The numbers are going through all sorts of adjustments and calibrations to be in "human readable" format.
 

mdocod

Distinguished
Well... I suspect it wasn't really idling totally then. You should see 60C+ thermal margins when truly idling, UNLESS you have modified settings in BIOS or in power management at the OS level.

When Cool-n-Quiet is enabled, C1E enabled, C6 enabled, with "auto" voltage controls, and the OS doesn't have any "performance mode" overrides in place, the CPU will idle down to 1.4ghz at 0.9V and gate off most of it's circuitry. This will result in a "temp reading" as low as ~0C or a thermal margin reading as high as ~70C.
 

leftisthominid

Distinguished
Jan 7, 2014
342
0
18,790


As I post this, with avast and Steam etc. running in the background, I am around 45-55 in thermal margin (it is generally around 52-55, but it occasionally spikes to 45). During gameplay it is around 35-40.

Also, one quick question, does running Overdrive (and not changing any settings in it) overclock by default?