Quote Originally Posted by SLi_dog
Does anyone know what the Tjunction value should be for E4300s?
no, nobody does! the only way to find out is to push this cpu to its limits and see what temps are reported by coretemp when throttling starts...

Quote Originally Posted by GGuyZ View Post

Originally Posted by SLi_dog
Technically it's not a "fix" just an adjustment of the Tjunction value from 85C to 100c for E4300s which will mean CoreTemp will read 15C hotter now.

This does not make sense at all. Since Tjunction temperature does not exist in desktop processors, why would a fix be required? If you are already assuming that a Tjunction temperature exists(which is fault assumption too, as we all agreed), why not use the same Tjunction for E4xxx as well as E6xxx. I can understand why reporting C2Qs as 100c Tjunction makes sense, but I don't understand this logic with the E4300.
most of the time PROCHOT# (TCC activation) temperature erroneous gets referenced as tjunction! coretemp uses this TCC activation temperature as a reference point to calculate temperatures from. TCC activation temperature can't be read by software, BUT there is a bit in a register (we discussed this a few posts earlier) which was implemented by intel. this bit is valid on mobile processors and defines if TCC activation temperature is near 85c or near 100c! i use the term "near" because in reality, this temperature is calibrated on a processor basis and differs from die to die. on one processor die it might be 87c while on an other processor die it might be 83c! coretemp, as i assume all other programs using DTS, uses this bit to decide if for a certain processor 85c or 100c has to be used in the calculations. although this is valid only for mobile processors, this seems to work also for most current BUT not all desktop processors too. we have seen more and more new processors coming out where this assumption is not correct anymore. thats the situations, where coretemp reads temps about 15c off!
so, to get coretemp back to more valid readings, the only thing to to is to change the reference temp from 85c to 100c instead on relying on the obviously wrong set bit in the register. that was done in coretemp 0.95 for e4300 and may be some other processors too.

This would confuse many users that will now believe their E4300 operates at a much higher temperature. If any fix was to be applied, then it should be on TAT itself. Or instead, reporting only the DTS value(as fgw suggested) might be a better solution.
well, in fact the new 15c higher readings might be the correct readings. i have a second rig with one of this e4300. unfortunately i have not yet pushed it into throttling. this is the only way to figure out which temp is right. for now i would assume the "new" 15c higher reading is correct. i can hardly believe, that my e4300 running on air keeps temps at 55c under full load! its far more realistic, that it should read 70c instead. will verify this as soon as i get my hands on this rig ...

Originally Posted by cadaveca
In RD600 cpu throtlles @ 85c via smartguardian. Shutdown temp set in bios also reads same temp. this is not the same temp that Coretemp displays(61c).

So, unless it's the bios @ fault on RD600, Coretemp is not reading correctly. I have same issue too, reading 19c idle in 25c ambient, using AIRCOOLING.

this being said, coretemp reports same temp across many different boards for same cpu, when voltages/cooling are the same. Although the temp may not be perfectly accurate, it's the best we got ATM.

This is very fishy and may damage the integrity of the conclusions which we all now believe in. While the absolute temp reading CT gives may be incorrect in many cases, it should always start throttling at 85C with C2D cpus, and 100C on C2Q cpus and some E4xxx. Obviously this is not real temperature, but it does indicate the throttling point. If this is indeed so, how is it possible that this guy encountered throttling at 61c in Coretemp?
unfortunately i don't have any information on smartguardian and so cant say anything here. you are right, this does not fit very well into this picture. different polling intervals might play a role here.

cadaveca, did the cpu throttle at 85c or did the bios shutdown the system as the bios is set to 85c too? may be smartguardian did not signal throttling correctly? there is a tool called rmclock, which i use to check throttling. may be you can give it a try http://cpu.rightmark.org/products/rmclock.shtml