Q6600 Danger temps?

[JC316]

I picked up a Q6600 G0 today and I had a question about the temperatures. What is the danger zone for one of these processors?

 

[technicks]

I would not let it get higher then 60/65.

They can take more though.

 

[Richieb0y]

72c is the limet but just like tech said let it not go high then 65c

 

[JC316]

Ok, I will stick to my normal 60*C max. Quick question though, is that 65*C in TAT, or 65*C in Bios?

 

[Richieb0y]

Ok, I will stick to my normal 60*C max. Quick question though, is that 65*C in TAT, or 65*C in Bios?

i dont use TAT i use speedfan

but still i look in tat & coretemp for load temps then when i know its safe i del tat

 

[hat]

Screw what the BIOS says. If my BIOS was right, my CPU would never survive.

 

[Mussels]

70C load is fine. use coretemp (latest version) to read the temps.

TAT and speedfan cant read G0 cores right, they're 15C too low.

 

[Wile E]

Thanks Mussels. Good to know. My new mobo (Maximus Formula) comes on Friday, and I'll be getting my Q6600 up and running this weekend.

 

[vega22]

if you want to be on the safe side use rightmark cpu clock utility and watch for your cpu to start throttling itself, if it does start to do this it means it is getting too hot.

dif chips do it at dif temps and it is a sure fire way to make sure your getting the full performance out of your overclock, as there is no point having it setup if you are only ever running at 50% of your accutual speed because its slowing itself down when you put it under full load.

 

[trog100]

70C load is fine. use coretemp (latest version) to read the temps.

TAT and speedfan cant read G0 cores right, they're 15C too low.

tat and core temp cant read my E6750 cpu temps at all.. tat errors and coretemp produces an instant reset (system crash) when the executable is clicked..

soo to be honest i wouldnt take any of em as gospel.. my abit guru says a nice reassuring 22 C in the bios and 40 C going balls out at 3.8 gig.. not as i trust that either but it looks good..

trog

 

[PaulieG]

Ok, just to make things clear with temps on the Q6600. Their tjunction temp is 100c. Best way to monitor these chips is to use coretemp, and set the option to "degrees to tjunction". Keep in mind that the cores run about 15c hotter than the cpu temp. General rule is to try and keep temps 20-25c below tjunction.

 

[Mussels]

Ok, just to make things clear with temps on the Q6600. Their tjunction temp is 100c. Best way to monitor these chips is to use coretemp, and set the option to "degrees to tjunction". Keep in mind that the cores run about 15c hotter than the cpu temp. General rule is to try and keep temps 20-25c below tjunction.

which would be 75-80C

Therefore, keeping it under 70 is a good idea, in case a fan fails or you have unusually hot weather (Someone turns the air con off, forgets to open a door/window, etc)

 

[PaulieG]

which would be 75-80C

Therefore, keeping it under 70 is a good idea, in case a fan fails or you have unusually hot weather (Someone turns the air con off, forgets to open a door/window, etc)

LOL. I guess my point is that people should be aware of core temperatures, not cpu temps when looking at limitations.

 

[Mussels]

LOL. I guess my point is that people should be aware of core temperatures, not cpu temps when looking at limitations.

more emphasis here: on G0 quads, i find two cores are always hotter than the other two. For example

cores 0+1 - 55C
cores 2+3 - 70C

Thats quite possible on say, a cooler in bad need of lapping. CPU software that gives a SINGLE result, would average that out and give you something like the low 60's - which is off by enough to be concerning.

(speedfan etc, sometimes only show ONE core (the first they detect) which is just as misleading)

 

[technicks]

So this is ok?

 

[largon]

technicks,
"66ºC to Tjunction remaining" means your temp is 34ºC (100ºC - 66ºC).
Go to Options - Settings in Coretemp window and untick "Show Delta to Tjunction temp.".

 

[JC316]

Core temp don't work for me. When I try to start it, I get "Driver Failed to Load" over and over till I stop the program in task manager. In fact, Everest is the only thing that does work to read the temps.

 

[Mussels]

Core temp don't work for me. When I try to start it, I get "Driver Failed to Load" over and over till I stop the program in task manager. In fact, Everest is the only thing that does work to read the temps.

press F8 as your 64 bit OS is loading, and choose 'disable driver signing'

It only works for that one boot, but it lets coretemp be happy.

 

[JC316]

I will give it a shot

 

[PaulieG]

more emphasis here: on G0 quads, i find two cores are always hotter than the other two. For example

cores 0+1 - 55C
cores 2+3 - 70C

Thats quite possible on say, a cooler in bad need of lapping. CPU software that gives a SINGLE result, would average that out and give you something like the low 60's - which is off by enough to be concerning.

(speedfan etc, sometimes only show ONE core (the first they detect) which is just as misleading)

Exactly. That average cpu temperature does not tell you that you have 2 cores hot as hell, and two nice and cool. Always monitor cores.
Note: I've always had 2 cores 5-6c hotter than the other 2

 

[JC316]

Ok, got a nice program from CPUID that works nicely. Highest core is 40*C idle, the coolest is 31*C.

Also, here is a hack that makes it so you don't have to disable driver signing to make core temp work. http://forums.erodov.com/showthread.php?p=15559

Here is the program from CPUID, it's the exact same as Core temp. http://www.cpuid.com/hwmonitor.php