Quote Originally Posted by gtj View Post
IDCC and IDU are lousy for reading temps because they don't measure the cores. I've found absolutely no use for either program.

Coretemp, RMClock and TAT are all getting their temps from the Digital Thermal Sensor located on each core. Those sensors are VERY sensitive and can update as fast as 30 times a second so unless the programs are all reading at EXACTLY the same instant, they'll probably not agree. They should be close though. RMClock averages the core temps over 5 seconds by default so it's going to be even more slightly off. Pick one and stick with it.

Speedfan and Everest report both the DTS core temps and the standard cpu and motherboard temps from the onboard sensor chip. You HAVE to use the latest versions of each program though. Everest versions before 3.80.880 or so can cause the board to lock up and prior to Speedfan 4.32, our board wasn't supported.

Tjunction is the reference temp for the processor. If the temp goes above that point, throttling should occur to prevent damage. It can be either 85 or 100 depending on the processor you're using. It's important to report because the processor reports the core temps as a number relative to tjunction. If the display program is using the wrong tjunction as a base, the temps will be 15c off.
Quote Originally Posted by gtj View Post
I believe the e4300 has a 100c tjunction. There are a few threads in the info and support sub-forum that talk about this. You might take a look.
New 0.95 version of coretemp appears to have addressed the e4300 temp reporting issue. Anyone verify? I would but my bx2 box is STILL down waiting for parts...