Originally Posted by azanimefan
Several half turths in this.
most FX (piledriver) cpus stop measuring temps accurately under 35C. once the cpu falls bellow that temp threshold the most common piledriver behavior is for the temps to get too low for reality. As 35C is plenty cool enough it doesn't really matter in the end.
Next, even when a piledriver is reporting its temps accurately, accurate is a "relative" term. You see, piledriver cpus, like all amd cpus since the phenom II don't actually have a "real" thermometer on the cpu. It uses some mathematical algorithm to estimate the chip temp. furthermore, on piledriver that correctly reported temp is pretty reliably -10C cooler then the reported socket temp on a motherboard.
now this is where it gets confusing because you'll see things about safe cpu temps. Typically those temps are given as core temps (65C) and socket temps (73C), generally at 65C reported core temps your cpu will start to throttle itself IF you left that option turned on in the bios. Meanwhile your motherboard typically will start to throttle your cpu when the socket temp hits around 73C (regardless what the bios is set to do).
since the socket temp often lags behind the "cpu" temps, usually taking 30-60 seconds to catch up and stabilize, there still is plenty of value in keeping an eye on core temps. Assuming your piledriver reports it's core temps accurately anyway. not all of them do. If your chip doesn't then you'll have to rely on the socket temps to guide you.
EXTRANEOUS AND UNIMPORTANT INFORMATION:
To further complicate things, people like to analyze what the piledriver package/core temp is really reporting. Because of the higher socket temps it's assumed that the core temp doesn't really refer to core temp but rather the SURFACE temp of the cpu heat spreader.