From: soinie on
I'm running a Core 2 Quad 6600 2.4 ghz and the temp when idle is about
25C according to Asus PC Probe II, although I've seen it up to 34C
with tasking. I want to moderately over clock this (P5E WS Pro) setup
and would like to know what to look for in terms of temp increases and
what might be considered a threshold temp. I'm using a Scythe Mini
Ninja and Arctic Silver 5, and thanks to those who recommended an
after-market heat sink.
From: GSV Three Minds in a Can on
Bitstring <6ghnp3p7pup116oks9os30jn19s8nnvpph(a)4ax.com>, from the
wonderful person soinie(a)hhotmail.com said
>I'm running a Core 2 Quad 6600 2.4 ghz and the temp when idle is about
>25C according to Asus PC Probe II, although I've seen it up to 34C
>with tasking. I want to moderately over clock this (P5E WS Pro) setup
>and would like to know what to look for in terms of temp increases and
>what might be considered a threshold temp. I'm using a Scythe Mini
>Ninja and Arctic Silver 5, and thanks to those who recommended an
>after-market heat sink.

Heat is not going to be the problem - there is a thermal protection
mechanism on the die, iirc, and probably another on the motherboard, and
you are ~30 degrees the right side of a problem anyway. If the CPU gets
too hot it will throttle the clock back.

If you (have to, or choose to) ramp the VCore up too far in pursuit of
extra GhZ then you may fry something .. but It'll be volts and not
degrees C that does the damage.

Before you go overclocking though, try a PROPER stress test at your
current clock rate - Prime95 torture test (maybe 4 copies, one pointed
at each core - I don't think the current one knows about loading more
than one core at once).

34c is 'loafing' IMO, but then it's hard to really work 4 cores in
everyday use. This assumes it's being measured right - not always the
case with Asus Mobos (what's the case temperature registering at? Heck,
how cold is the room it is in??)

--
GSV Three Minds in a Can
10,414 Km walked. 2,032 Km PROWs surveyed. 36.9% complete.
From: Paul on
GSV Three Minds in a Can wrote:
> Bitstring <6ghnp3p7pup116oks9os30jn19s8nnvpph(a)4ax.com>, from the
> wonderful person soinie(a)hhotmail.com said
>> I'm running a Core 2 Quad 6600 2.4 ghz and the temp when idle is about
>> 25C according to Asus PC Probe II, although I've seen it up to 34C
>> with tasking. I want to moderately over clock this (P5E WS Pro) setup
>> and would like to know what to look for in terms of temp increases and
>> what might be considered a threshold temp. I'm using a Scythe Mini
>> Ninja and Arctic Silver 5, and thanks to those who recommended an
>> after-market heat sink.
>
> Heat is not going to be the problem - there is a thermal protection
> mechanism on the die, iirc, and probably another on the motherboard, and
> you are ~30 degrees the right side of a problem anyway. If the CPU gets
> too hot it will throttle the clock back.
>
> If you (have to, or choose to) ramp the VCore up too far in pursuit of
> extra GhZ then you may fry something .. but It'll be volts and not
> degrees C that does the damage.
>
> Before you go overclocking though, try a PROPER stress test at your
> current clock rate - Prime95 torture test (maybe 4 copies, one pointed
> at each core - I don't think the current one knows about loading more
> than one core at once).
>
> 34c is 'loafing' IMO, but then it's hard to really work 4 cores in
> everyday use. This assumes it's being measured right - not always the
> case with Asus Mobos (what's the case temperature registering at? Heck,
> how cold is the room it is in??)
>

I would find a utility that uses the internal CPU temp sensor. I haven't
tested these. They read out the digital temp sensor. Programs like
Asus Probe would likely be reading the analog sensor (CPU diode + hardware
monitor chip).

Intel Thermal Analysis Tool (TAT) - this was not intended for public
distribution, but is used by overclockers. There may be a later version,
but I'm not going to search all over for it. This is just the first
copy I found.

http://www.techpowerup.com/downloads/392/.html

This one does a similar measurement, and was not written by Intel.

CoreTemp
http://www.alcpu.com/CoreTemp/

Both of those programs rely on knowledge of Tj_max. That is the maximum
junction temperature before the processor starts to throttle. The reason
the measurement programs need to know that constant, is the measurement
mechanism has a "relative" and not an "absolute" temperature readout.
In other words, if Tj_max is 85C and the measurement returns a value
of zero, then the calculated temperature is 85C. If the value returned
is two, then the calculated temperature is 83C. Something like that.
So it is important to know the Tj_max of the processor types. A 65nm
processor could have a different Tj_max than a 45nm processor. The
various families, because they have different die sizes and quantities
of cache, and different power dissipation numbers, will also have a
different Tj_max. So the measurement tool needs a table of values, to
compute an absolute value from the relative readout. When those
two measurement programs give a wrong result, the theory is that
the Tj_max value is wrong.

Maybe Speedfan (almico.com) can read the digital temp sensor.
The release notes here, says the capability to read it was
added in version 4.32. Current release is 4.33.

http://www.almico.com/speedfan.php

So the issue with programs like that, is that they've been updated
with the latest values of Tj_max.

To load the CPU to 100%, this version of Prime95 will run on all
four cores at once. To use this program, when it asks to "Join
GIMPS ?" say No. Next, a custom dialog will appear. The maximum
memory to be tested will be shown in the lower right hand
corner. On my 1GB machine, it shows 767MB as the amount of memory
to test. I edit this value, and select something smaller, like
200MB. By doing that, enough memory is left on the computer, so
I can do other things while Prime95 runs. You can leave the other
settings as is. When you are finished with that dialog, the program
will launch a number of threads. For a Q6600, you should see four
threads launched. And your processor should start to heat up. The
program has a "stop" and "exit" option in the left-most menu,
so when you're finished, you can use that menu to get rid of the
program.

http://www.mersenne.org/gimps/p95v255a.zip
http://www.majorgeeks.com/Prime95_d4363.html (if mersenne is down, use this one)

When I want to do an actual integrity test, and not just heat up
the CPU, then I might set the memory to test back to the 767MB
value, as then as much of the available memory is tested as
is possible.

Those are the tools I know about. Have fun :-)

Paul
From: GMAN on
In article <ECJxinBLA9mHFA2+(a)from.is.invalid>, GSV Three Minds in a Can <GSV(a)quik.clara.co.uk> wrote:
>Bitstring <6ghnp3p7pup116oks9os30jn19s8nnvpph(a)4ax.com>, from the
>wonderful person soinie(a)hhotmail.com said
>>I'm running a Core 2 Quad 6600 2.4 ghz and the temp when idle is about
>>25C according to Asus PC Probe II, although I've seen it up to 34C
>>with tasking. I want to moderately over clock this (P5E WS Pro) setup
>>and would like to know what to look for in terms of temp increases and
>>what might be considered a threshold temp. I'm using a Scythe Mini
>>Ninja and Arctic Silver 5, and thanks to those who recommended an
>>after-market heat sink.
>
>Heat is not going to be the problem - there is a thermal protection
>mechanism on the die, iirc, and probably another on the motherboard, and
>you are ~30 degrees the right side of a problem anyway. If the CPU gets
>too hot it will throttle the clock back.
>
>If you (have to, or choose to) ramp the VCore up too far in pursuit of
>extra GhZ then you may fry something .. but It'll be volts and not
>degrees C that does the damage.
>
>Before you go overclocking though, try a PROPER stress test at your
>current clock rate - Prime95 torture test (maybe 4 copies, one pointed
>at each core - I don't think the current one knows about loading more
>than one core at once).
>
>34c is 'loafing' IMO, but then it's hard to really work 4 cores in
>everyday use. This assumes it's being measured right - not always the
>case with Asus Mobos (what's the case temperature registering at? Heck,
>how cold is the room it is in??)
>
Well in my case, mighty chilly with the 3 120mm fans and the 200mm blowhole in
my Antec Nine Hundred case!
From: soinie on
On Sun, 27 Jan 2008 00:27:55 +0000, GSV Three Minds in a Can
<GSV(a)quik.clara.co.uk> wrote:

>Bitstring <6ghnp3p7pup116oks9os30jn19s8nnvpph(a)4ax.com>, from the
>wonderful person soinie(a)hhotmail.com said
>>I'm running a Core 2 Quad 6600 2.4 ghz and the temp when idle is about
>>25C according to Asus PC Probe II, although I've seen it up to 34C
>>with tasking. I want to moderately over clock this (P5E WS Pro) setup
>>and would like to know what to look for in terms of temp increases and
>>what might be considered a threshold temp. I'm using a Scythe Mini
>>Ninja and Arctic Silver 5, and thanks to those who recommended an
>>after-market heat sink.
>
>Heat is not going to be the problem - there is a thermal protection
>mechanism on the die, iirc, and probably another on the motherboard, and
>you are ~30 degrees the right side of a problem anyway. If the CPU gets
>too hot it will throttle the clock back.
>
>If you (have to, or choose to) ramp the VCore up too far in pursuit of
>extra GhZ then you may fry something .. but It'll be volts and not
>degrees C that does the damage.
>
>Before you go overclocking though, try a PROPER stress test at your
>current clock rate - Prime95 torture test (maybe 4 copies, one pointed
>at each core - I don't think the current one knows about loading more
>than one core at once).
>
>34c is 'loafing' IMO, but then it's hard to really work 4 cores in
>everyday use. This assumes it's being measured right - not always the
>case with Asus Mobos (what's the case temperature registering at? Heck,
>how cold is the room it is in??)

The motherboard temp is 32C idle the CPU temp currently is 28C, the
room is about 76F. I'm using a Seasonic S12 Energy 550 watt power
supply which runs generally very stable. I'll download Prime95 and
run a few tests. Thanks for that.