From: Bob Tennent on
When I try to do something computationally intensive (such as lame
encoding), my system shuts down. I think it's because a bad thermistor
is producing high readings. Even when the system is 100% idle, the CPU
temperature is 61�C according to lm_sensors. The "high" value is 80�C,
and I believe the system shuts down if the CPU utilization goes too
high, even if the real temperature is much lower.

Can this be fixed by editing a configuration file or turning off the
broken thermistor?

Bob T.
From: General Schvantzkopf on
On Fri, 28 Dec 2007 22:51:04 +0000, Bob Tennent wrote:

> When I try to do something computationally intensive (such as lame
> encoding), my system shuts down. I think it's because a bad thermistor
> is producing high readings. Even when the system is 100% idle, the CPU
> temperature is 61°C according to lm_sensors. The "high" value is 80°C,
> and I believe the system shuts down if the CPU utilization goes too
> high, even if the real temperature is much lower.
>
> Can this be fixed by editing a configuration file or turning off the
> broken thermistor?
>
> Bob T.

You might be able to disable shutdown in the BIOS but I wouldn't do that
if I were you. It's entirely possible that the temps are real.

The first think you should do is see if your heatsink is covered with
dust, if it is you should clean it off. The second thing you should try
is to replace the thermal compound with something like Artic Silver or
Zalman. Remove the heatsink, clean off the bottom of the heat sink and
the top of the chip with a solvent (alcohol works fine for this) and then
put on a small amount of a good thermal paste on the CPU and replace the
heatsink. Chances are you will see a 5-10 degree drop in temperatures
which might be enough to fix your problem. If that doesn't do it then you
might want to invest in a better cooler.

From: Rikishi 42 on
On 2007-12-28, Bob Tennent <BobT(a)cs.queensu.ca> wrote:

> When I try to do something computationally intensive (such as lame
> encoding), my system shuts down. I think it's because a bad thermistor
> is producing high readings. Even when the system is 100% idle, the CPU
> temperature is 61�C according to lm_sensors. The "high" value is 80�C,
> and I believe the system shuts down if the CPU utilization goes too
> high, even if the real temperature is much lower.
>
> Can this be fixed by editing a configuration file or turning off the
> broken thermistor?
Is the shutdown an orderly one, performed by Linux?
Or is it the BIOS, plainly shutting down the power?

In the latter case, there's not much you can do in Linux. If your BIOS
'high' is set to 80, and an faulty measure from the thermistor says your cpu
is hotter, it's going to be shut down.


--
There is an art, it says, or rather, a knack to flying.
The knack lies in learning how to throw yourself at the ground and miss.
Douglas Adams
From: Calab on

"Stefan Patric" <tootek2(a)yahoo.com> wrote in message
news:d%gdj.24897$Wt7.19881(a)newsfe14.phx...
> On Fri, 28 Dec 2007 22:51:04 +0000, Bob Tennent wrote:
>
>> When I try to do something computationally intensive (such as lame
>> encoding), my system shuts down. I think it's because a bad thermistor
>> is producing high readings. Even when the system is 100% idle, the CPU
>> temperature is 61�C according to lm_sensors. The "high" value is 80�C,
>> and I believe the system shuts down if the CPU utilization goes too
>> high, even if the real temperature is much lower.

- Bad PSU
- Bad mainboard (check capacitors)


From: Bob Tennent on
On Fri, 28 Dec 2007 17:29:34 -0600, General Schvantzkopf wrote:
> On Fri, 28 Dec 2007 22:51:04 +0000, Bob Tennent wrote:
>
>> When I try to do something computationally intensive (such as lame
>> encoding), my system shuts down. I think it's because a bad thermistor
>> is producing high readings. Even when the system is 100% idle, the CPU
>> temperature is 61�C according to lm_sensors. The "high" value is 80�C,
>> and I believe the system shuts down if the CPU utilization goes too
>> high, even if the real temperature is much lower.
>>
>> Can this be fixed by editing a configuration file or turning off the
>> broken thermistor?
>
> You might be able to disable shutdown in the BIOS but I wouldn't do that
> if I were you. It's entirely possible that the temps are real.

No way. On a "cold" start, the CPU temperature is over 50, even when
the motherboard is at 22.