CPU Temp: 13C

  • Thread starter Thread starter Jack
  • Start date Start date
J

Jack

I have just updated the drivers for my MSI K8T Neo mobo, updated my BIOS and
updated the MSI "CoreCenter" monitoring software.

CoreCenter and the BIOS both give me temperature readings for my CPU. Before
the updates the BIOS and CoreCenter reported my CPU as having temperatures
of between 39C and 51C depending on the room temp and what I was doing. This
seemed a fairly normal temperature and I was satisfied with it.

However since the updates my CPU temperature has went way down according to
this software. When I go into the BIOS it's reporting the temp as 19C. When
I'm sitting idle in Windows XP - as I am now - it's sitting at 13C! I tested
it by encoding a large MP3 and it went up to 27C after 5 mins of encoding.

I have CoolNQuiet (http://www.amdboard.com/coolnquiet.html) switched on and
an Athlon-64 3400 Clawhammer (2.2GHz) with a Arctic Cooling Silencer 64 fan.
Can this be real? I'm concerned that the temps are being misreported...
 
Jack said:
I have just updated the drivers for my MSI K8T Neo mobo, updated my BIOS and
updated the MSI "CoreCenter" monitoring software.

CoreCenter and the BIOS both give me temperature readings for my CPU. Before
the updates the BIOS and CoreCenter reported my CPU as having temperatures
of between 39C and 51C depending on the room temp and what I was doing. This
seemed a fairly normal temperature and I was satisfied with it.

However since the updates my CPU temperature has went way down according to
this software. When I go into the BIOS it's reporting the temp as 19C. When
I'm sitting idle in Windows XP - as I am now - it's sitting at 13C! I tested
it by encoding a large MP3 and it went up to 27C after 5 mins of encoding.

I have CoolNQuiet (http://www.amdboard.com/coolnquiet.html) switched on and
an Athlon-64 3400 Clawhammer (2.2GHz) with a Arctic Cooling Silencer 64 fan.
Can this be real? I'm concerned that the temps are being misreported...
Click to expand...

Have you checked the release notes for the BIOS and CoreCenter updates
that you installed? It could be that the old versions were misreporting
the temps.

Parish
 
Parish said:
Have you checked the release notes for the BIOS and CoreCenter updates
that you installed? It could be that the old versions were misreporting
the temps.
Click to expand...

I just did and one of the fixes was a misreported CPU temperature. :)
 
Jack said:
I just did and one of the fixes was a misreported CPU temperature. :)
Click to expand...

Well AMD must have done some good design work with the 64 then if it
only hots 27C after 5 mins of MP3 encoding. Athlon XPs were very hot
chips - my dual MP2800s idle at 45-50 depending on room temp, although
they don't get much hotter when worked hard, thankfully :-)

Parish
 
Parish said:
Well AMD must have done some good design work with the 64 then if it only
hots 27C after 5 mins of MP3 encoding. Athlon XPs were very hot chips - my
dual MP2800s idle at 45-50 depending on room temp, although they don't get
much hotter when worked hard, thankfully :-)
Click to expand...

Hence the reason for my concern. I previously had an Athlon XP 2000 and it
ran anywhere between 40C and 60C - therefore my new chip running at 13C is
worryingly low for me... I find it hard to believe it's correct. :)
 
Jack said:
I just did and one of the fixes was a misreported CPU temperature. :)
Click to expand...
Of all the PC's I've built, the only ones to consistently misreport temps
are the ones based on MSI boards!

SteveH
 
Hence the reason for my concern. I previously had an Athlon XP 2000 and it
ran anywhere between 40C and 60C - therefore my new chip running at 13C is
worryingly low for me... I find it hard to believe it's correct. :)
Click to expand...

What's your ambient temperature? If it's above 13°C (very likely) and you are
not using Peltier or phase change cooling then a false temperature reading is
the only possibility left I would say.

David
 
Jack said:
updates >>> that you installed? It could be that the old versions
were misreporting >>> the temps.

Hence the reason for my concern. I previously had an Athlon XP 2000
and it ran anywhere between 40C and 60C - therefore my new chip
running at 13C is worryingly low for me... I find it hard to believe
it's correct. :)
Click to expand...

You're not the only one! I've got a 64 3500 on an Abit AV8 which idles
at 36C with Cool'n'Quiet clocking the multiplier at 5. Under load it
goes up to 68C. That's with a fairly mild overclock of 216FSB & all
voltages at their standard settings. Abit & MSI must read the temps in
very different ways...

One thing that threw me when I first started using Cool'n'Quiet was how
some apps didn't make the temps go up despite causing 100% CPU usage.
Then I discovered that the multiplier stays at 5 if the app uses a task
priority of 'Low'.
 
David Johnstone said:
What's your ambient temperature?
Click to expand...

Above 13C. ;)
If it's above 13°C (very likely) and you are
not using Peltier or phase change cooling then a false temperature reading
is
the only possibility left I would say.
Click to expand...

Yeah. I'll look out for another BIOS update then...
 
Jack said:
Hence the reason for my concern. I previously had an Athlon XP 2000
and it ran anywhere between 40C and 60C - therefore my new chip
running at 13C is worryingly low for me... I find it hard to
believe it's correct. :)
Click to expand...

Considering that room temperature is about 20 C, and that very few
CPUs function as refrigerators, the possibility of your system
being correct becomes vanishingly small.
 
Considering that room temperature is about 20 C, and that very few
CPUs function as refrigerators, the possibility of your system
being correct becomes vanishingly small.
Click to expand...
He could be an Inuit. Brings a whole new meaning to Artic Silver!
 
| | > Jack wrote:
| >> | >>>
| >>> Have you checked the release notes for the BIOS and CoreCenter updates
| >>> that you installed? It could be that the old versions were misreporting
| >>> the temps.
| >>
| >> I just did and one of the fixes was a misreported CPU temperature. :)
| >
| > Well AMD must have done some good design work with the 64 then if it only
| > hots 27C after 5 mins of MP3 encoding. Athlon XPs were very hot chips - my
| > dual MP2800s idle at 45-50 depending on room temp, although they don't get
| > much hotter when worked hard, thankfully :-)
|
| Hence the reason for my concern. I previously had an Athlon XP 2000 and it
| ran anywhere between 40C and 60C - therefore my new chip running at 13C is
| worryingly low for me... I find it hard to believe it's correct. :)

It's not correct unless your system is in a very cold room! 13C
(55.4F) probably wouldn't even occur in an operating computer in an
igloo!

Larc



§§§ - Change planet to earth to reply by email - §§§
 
Hi Jack, why dont you check the temperatures with a Digital thermometer
also some Digital Multi Meters have a thermometer function too.

Yes 13%C does seem a bit too low for my liking too, likewise i have a ASUS
A7V600-X with and overheating Via KT600 chipset, the bios and Everest
reports about 30%C, rarly changes (sometimes it jumps 20-30%C in a single
step), but my DMM reports between 28 from cold rising 1%C every 3 seconds
to 55%C just sitting idle, under load it rises to 65%C, the DMM sensor is
placed in bottom of HS on the top side opposite the core.

Cpu: XP3200+ 26 - 35 idle, 36 - 55%C under load
chipset: 28 - 55 idle, 56 - 65%C, (highest recorded so far)
HDD: 18 - 25%C
Room: 18 - 22%C
 
Jack said:
I have CoolNQuiet (http://www.amdboard.com/coolnquiet.html) switched on and
an Athlon-64 3400 Clawhammer (2.2GHz) with a Arctic Cooling Silencer 64 fan.
Can this be real? I'm concerned that the temps are being misreported...
Click to expand...

Unless you are using active cooling (like a refrigeration system), the
CPU temperature cannot be less than that of the ambient air; and usually
it will be well above it.

My poorly-designed desktop runs with its Athlon processor between 53°
and 64° C. It used to be even worse, until I added a case fan (which
the manufacturer was too cheap to install).

In my old server, which was exactly the same kind of box, the BIOS
couldn't display more than two digits for temperatures in Celsius. When
the OS got stuck in a loop after the CPU fan failed, the temperature
reached at least 114° C (240° F), but the BIOS displayed only two digits
(fortunately, it also gave the temperature in Fahrenheit with three
digits, which is how I knew what was happening--although the smell gave
it away, too).
 
Jack said:
Above 13C. ;)


Yeah. I'll look out for another BIOS update then...
Click to expand...

Make sure you don't have any other monitoring software installed
too (eg the old version, or MBM5 etc) as they usually (always?)
interfere with each other - a problem with the design of the SMbus,
I think.
HTH
 
Hi Jack, why dont you check the temperatures with a Digital thermometer
also some Digital Multi Meters have a thermometer function too.

Yes 13%C does seem a bit too low for my liking too, likewise i have a ASUS
A7V600-X with and overheating Via KT600 chipset, the bios and Everest
reports about 30%C, rarly changes (sometimes it jumps 20-30%C in a single
step), but my DMM reports between 28 from cold rising 1%C every 3 seconds
to 55%C just sitting idle, under load it rises to 65%C, the DMM sensor is
placed in bottom of HS on the top side opposite the core.

Cpu: XP3200+ 26 - 35 idle, 36 - 55%C under load
chipset: 28 - 55 idle, 56 - 65%C, (highest recorded so far)
HDD: 18 - 25%C
Room: 18 - 22%C
Click to expand...

65C is not "overheating", it is within the specs for the
chip. It's actually a good compromise to have a stable chip
with passive cooling, rather than one cooler than it needs
be, with the added noise and maintenance of a fan.

Even so, sometimes the 'sink interface isn't too good.
Sadly it's even common for boards to have a thermal
interface material that doesn't even touch the center
heat-spreader of (chips incorporating such a spreader) due
to it being sunk below the plane of the outer epoxy
(carrier) border.

If it's really bothering you, taking off the 'sink and
checking the interface is one option, perhaps it can be
improved. I have an A7V600 and note no overheating
problems. The 'sink is fairly warm but so are most chipsets
@ 200MHz/DDR400 FSB and higher.
 
kony said:
65C is not "overheating", it is within the specs for the
chip. It's actually a good compromise to have a stable chip
with passive cooling, rather than one cooler than it needs
be, with the added noise and maintenance of a fan.
Click to expand...

Cooler components last longer, although most PCs are probably dumped
before added heat damages the components. A processor that runs hot
will very gradually deteriorate over the years as dopants tend to drift
more quickly in the chip. However, except in the case of processors
that truly overheated, I've not seen processors fail. If they run for
48 hours, they'll run forever. But why take chances by running them any
hotter than necessary?
 
Cooler components last longer, although most PCs are probably dumped
before added heat damages the components. A processor that runs hot
will very gradually deteriorate over the years as dopants tend to drift
more quickly in the chip. However, except in the case of processors
that truly overheated, I've not seen processors fail. If they run for
48 hours, they'll run forever. But why take chances by running them any
hotter than necessary?
Click to expand...

Then what solution to you propose? Fans have far shorter
lifespan than the ICs.

There may indeed be a chance it won't then last 30 years,
but IMO, the principle focus should always be the earlier
failure points rather than the latter... fans, caps,
mechanical switchs and contacts are more likely to cause
failure at which point the systems aren't worth the time or
expense to fix (if it's even reasonable to track down some
of the older parts beyond proprietary industrial
applications).
 
Back
Top