Quote Originally Posted by jaredpace View Post
well if you know for sure, you should probably tell unclewebb. duh
The post above yours read:
Quote Originally Posted by KTE
I'll post as soon as I can get on the drive with data saved on it. Not been back to flat in 9 days yet all my gear is there and this is someone elses.


So communication with our contact went as following. It's non-verbatim, I have to protect confidentiality but it's very close to the exact words said. Hope I don't get in trouble for this.

KTE: I need a favor from you. Have you seen this thread? Common users don't have enough information on temps. and so we're guessing based on some unprofessional and limited testing and docs. You confirmed E8400 temps at 51C load earlier when you came in January but what about how we can work out temps? I know the 0x19C MSR but word has it that no one knows the correct TjMax and we're all guessing... why won't you release these details?

Contact: Hmm.. were'd you hear that? AFAIK all developers who inquired know.

KTE: I talk to most oc software developers regular, which ones are you talking about so I can confirm?

Contact: We released this info back in 2006 and since then at every stepping update but you know it's only allowed under NDA in the BIOS writers guide. Ask Rudolf who made the Lm-sensors driver for Linux, or Matthias who develops CPUTempWatch or Fiery at EVEREST, Franck at HWMonitor, or Arthur who makes CoreTemp just to name a few, they all should know the details as they use them in their software calcs.

KTE: I'll definitely ask them but why was this info never public?

Contact: Check.. or if that's not enough, then

KTE: Hmm.. damn I searched everywhere but you knew what to search for and I didn't. These guys knew it all along
So.. let me get this straight: retrieve MSR 0xEE, bit:30 0=100 1=85 on earliest, for my Q6600 G0 its 0=100 1=85 and thats factory set TjMax?

Contact: Spot on Tye

============2 days ago again============

KTE: Just seen you're on, quickly, some more temp. qs for you.
So you're saying devs know the info you gave me about MSR 0xEE to get TjMax for a Core 2 CPU plus even the latest TjMax updates for Penryn?

Contact: Yep just check their software and they'll have all the updates to them from official authorised documentation for our Penryn 45nm lineup.

Contact: Oh look

KTE: 0=105 1=95 Penryn.. hmm, that makes sense, that's why most of them were in sync I guess. Thanks [names contact], you've been big help many times now!
BTW what's the temperature Abit EQ/Gigabyte EasyTune and EVEREST "CPU" reports then? Sorry had to ask that its confusing me, it's lower than DTS...

Contact: Probably Tcase, there's an analogue Tcase sensor there as well as the DTS sensors in each core, which motherboards can read and EVEREST probably reads that temperature. There is nothing else that will give a CPU temperature value but you're best off asking Fiery at their forum

KTE: Ah ok. That sorta brushes things up.
Can I get quick peak access to the guide?

Contact: [names my uncle] can, just need to sign the NDA that's all

KTE: No thanks

KTE: Just reading link you gave... Fiery mentions any problems with the TjM/Temps and it's your fault

Contact: Hehe, well someones got to take the blame. Temperatures shouldn't matter too much under normal warrantied conditions though
Kinda makes things clear as crystal there. So, if you want to follow Intel like you do for MSR 0x19C, then check MSR 0xEE and you can go on from there combining the two.

7 software temp. values compared on my Q6600 G0:



Hope it helps, sorry for delay but I'm heavily backlogged on more than 180 PMs at just XS, many emails and many threads.