Q6600 temperatures :(

cmsbfent · 12 Aug 2007 at 13:26

basically, i've read that the tjunction as shown in TAT is 100 degrees.

The chip is designed to run within this temperature, after which the heat produced will cause errors. Not sure if its true or not, its just something i spotted on a forum.

Either way though, my chip is still running prime after a night out so its a good 16 hours or so.. so looks like 80+ degrees is fine. Think I'll knock the volts down a notch though and go for 3ghz.. should be able to run it silently then.

I think though that if I brought a bigger radiator I could get 3.4'ish with around 1.47 volts.. but think i'll cope with 'just' 3 gig and silence

Cotti · 12 Aug 2007 at 19:25

cmsbfent said:
basically, i've read that the tjunction as shown in TAT is 100 degrees.

The chip is designed to run within this temperature, after which the heat produced will cause errors. Not sure if its true or not, its just something i spotted on a forum.

Either way though, my chip is still running prime after a night out so its a good 16 hours or so.. so looks like 80+ degrees is fine. Think I'll knock the volts down a notch though and go for 3ghz.. should be able to run it silently then.

I think though that if I brought a bigger radiator I could get 3.4'ish with around 1.47 volts.. but think i'll cope with 'just' 3 gig and silence

Ive just done that and imho it wasnt worth it for the performance increase/hassle save your money m8 its the right decision!

TONY · 13 Aug 2007 at 14:54

After lapping my cpu I am running it at 3 ghz and it's idling now at 29/27/24/24 and reaches 52/51/45/45 when the four cores are running sp2004 (before lapping they were around 30 degrees higher (I think due to the heatsink only making contact with the very edges of the heatspreader on the cpu), I am using speed fan to measure temps so the actual temps may be slightly higher but I tried to use TAT and it would not work I think maybe due to Vista 64.

Tooks · 13 Aug 2007 at 15:05

Try coretemp, those temps seem suspicously low!

PantsUK · 13 Aug 2007 at 15:40

speed fan on my q6600 is out by a good 10-15 degrees ... still makes me feel better looking at that

TONY · 13 Aug 2007 at 16:50

Tooks said:
Try coretemp, those temps seem suspicously low!

For some reason pressing F8 does nothing on my system (to allow coretemp to run due to unsigned drivers), I have tried pressing it continuosly from power on until Vista 64 loads and I get nothing :confused:

Tooks · 13 Aug 2007 at 17:14

I don't know what you mean about F8, is that a Vista thing?

I meant have you tried this temp monitoring program?

http://www.thecoolest.zerobrains.com/CoreTemp/

It reads the internal cpu temp. I think you may need to disable driver signing or similar to get it working on Vista?

TONY · 13 Aug 2007 at 17:17

That program won't work in Vista 64 until you have enabled unsigned drivers by pressing F8 when booting your system.

Tooks · 13 Aug 2007 at 17:19

Ah, I see! I thought it was something to do with that, as my post alluded to really!! Just wanted to check we weren't confused!

TONY · 13 Aug 2007 at 17:32

Thanks anyway mate, I just need to figure out why F8 don't work. Maybe someone with the same mobo as me has the answer

GeForce · 13 Aug 2007 at 17:33

cmsbfent said:
basically, i've read that the tjunction as shown in TAT is 100 degrees.

The chip is designed to run within this temperature, after which the heat produced will cause errors. Not sure if its true or not, its just something i spotted on a forum.

Pretty much

In short, Tjunction is the maximum allowable temperature at the junction between the core and the die it sits on.

Most (if not all) Allendales and Kentsfields have a Tjunction of 100C, whereas Conroes have a Tjunction of 85C.

Jon

TONY · 13 Aug 2007 at 17:40

Would they not throtle before then and so never reach that temp? or is it not effected by core temp readings?

GeForce · 13 Aug 2007 at 17:46

Yeh they do. The real use of Tjunction is for reading the temperatures. The DTS in the core reports a temperature that is the difference between Tjunction and the real temperature (delta)

So CoreTemp (and similar) programs work out the real core temperature as follows:

Core Temp = Tjunction - delta.

Tjunction is a set value that is not stored in the CPU. CoreTemp works it out by reading it off a database built into the program.

Jon

PantsUK · 13 Aug 2007 at 18:17

everest works fine in 64 bit and reads the same temps as core temp and TAT.

(for some reason it wont remember the fact you've assigned it admin rights though) gotta love Vista :rolleyes:

fornowagain · 13 Aug 2007 at 18:34

GeForce said:
Tjunction is a set value that is not stored in the CPU. CoreTemp works it out by reading it off a database built into the program.

The Tjmax is a generic value for the range of chips. The DTS delta is a -ve towards the TCC throttling point. TCC cannot be read from the chip. Programs like coretemp have to assume a value to subtract the DTS. Usually from an MSR, its supposedly near to the Tjmax.

GeForce · 13 Aug 2007 at 18:51

fornowagain said:
The Tjmax is a generic value for the range of chips. The DTS delta is a -ve towards the TCC throttling point. TCC cannot be read from the chip. Programs like coretemp have to assume a value to subtract the DTS. Usually from an MSR, its supposedly near to the Tjmax.

Yep, but CoreTemp labels the value taken from the MSR as "Tjunction".

And yes, sorry, when I said "database" I was referring to the MSR, but couldn't remember the name at the time

Jon

fornowagain · 14 Aug 2007 at 11:18

I think its important to realise that when you say

"Core Temp = Tjunction - delta"

Its actually the DTS subtracted from an assumed value. There's couple of issues with that. The program writer 'The coolest' used to use Tcasemax, its just a label. Coretemp reads hex from the MSR and decides from the value it sees, if its 85C or 100C. Firstly it can get this wrong and assume the wrong one, secondly the Tjmax value isn't what the delta DTS is heading towards anyway. It approaches a zero state, at which point the chips throttling point activates. This TCC value is factory set and completely unknown for each chip and cant be read externally.

The point is, we have to assume a value to subtract from if we want an approximation of the absolute value. The generic Tjmax is the same for each chip type. So we use that, assuming it gets assigned correctly. Its still not the correct value and could be several degrees from the actual value. The DTS sensor is only accurate near the upper range and values can get very weird near idle.

There is some more detail here if you're interested.

GeForce · 14 Aug 2007 at 11:41

fornowagain said:
There is some more detail here if you're interested.

Very interesting read, thanks a lot!

Jon

ele7en · 15 Aug 2007 at 14:59

TONY said:
Thanks anyway mate, I just need to figure out why F8 don't work. Maybe someone with the same mobo as me has the answer

go to start menu under windows and type CMD, when it shows in the list, right click it and go to run as administrator.

when you are in the command prompt type this:

bcdedit /set advancedoptions Yes

this will force the f8 option to start everytime you start windows. this is useful if you want to always set disable driver signing.

it seems you have f8 turned off, if you wish to manually press f8 when windows startsup or dont just want windows to start normal without pressing anything type this (default value):

bcdedit /deletevalue advancedoptions

this is the option you probably have right now which is why you cannot press f8 at startup:

bcdedit /set advancedoptions NO (this is the command thats causing the problems, avoid using this and delete it or change it via the /deletevalue or use the YES option.

I had similar problems as you and this took me quite a while to find out. google didn't help and i had to figure it out on my own. hope this helps.