CPU or m/b?

[Kenny]

Have been given a Philips Iqon PC and told if I can fix it I can keep it.
It has an ECS m/b and Celeron D 3.06 CPU.
Boots past the POST but shuts down before Windows starts. Watching the
hardware monitor in the BIOS CPU temp creeps up till it reaches the 85C
threshold then shuts down.
Fan's OK, have cleaned off old thermal compound and renewed it but no
difference.
Found out that someone had previously opened it and hoovered the dust out
but whether that was before or after the fault I don't know, also it was
obvious that the CPU had been removed because the h/s was not properly
fitted and an attempt had been made to replace thermal compound without
removing the old.
Question is is it a faulty m/b or CPU?
Should I play safe and replace both?
Replies appreciated.

 

[Paul]

Have been given a Philips Iqon PC and told if I can fix it I can keep it.
It has an ECS m/b and Celeron D 3.06 CPU.
Boots past the POST but shuts down before Windows starts. Watching the
hardware monitor in the BIOS CPU temp creeps up till it reaches the 85C
threshold then shuts down.
Fan's OK, have cleaned off old thermal compound and renewed it but no
difference.
Found out that someone had previously opened it and hoovered the dust out
but whether that was before or after the fault I don't know, also it was
obvious that the CPU had been removed because the h/s was not properly
fitted and an attempt had been made to replace thermal compound without
removing the old.
Question is is it a faulty m/b or CPU?
Should I play safe and replace both?
Replies appreciated.

Clean *all* the thermal waste products off the top of the CPU, and
from the base of the heatsink. There are actually cleaning compounds
you can get, which are a bit more effective. I use whatever rubbing
alcohol I have around, but it is not a proper solvent. It sounds
like there is no reason to panic, and perhaps a bit more work
on the cooling will fix it.

http://www.newegg.com/Product/Product.aspx?Item=N82E16835100010&Tpk=arcticlean

The other possibility, is the cooling is wonderful, but Vcore is
way too high and is cooking the thing.

The thing is, there are two thermal protection mechanisms. The
first, throttling, reduces the clock rate for short intervals, in
the hopes of keeping the CPU below the throttle temperature. The
second level of protection is THERMTRIP, set perhaps 20C above
the throttle temperature. Since THERMTRIP is turning off the computer,
the processor has already tried to remedy the situation by reducing
the compute rate. Usually, when this is happening, the heatsink has
fallen off.

So I'd check that a *thin* layer of a single thermal interface
material is applied (to displace the air gap between processor
and heatsink). And that the heatsink is actually flush with the
processor and under compression. A thin layer is better than
a thick layer, as too much paste or pads, acts as a thermal
insulator.

Paul

 

[Edric]

Have been given a Philips Iqon PC and told if I can fix it I can keep it.
It has an ECS m/b and Celeron D 3.06 CPU.
Boots past the POST but shuts down before Windows starts. Watching the
hardware monitor in the BIOS CPU temp creeps up till it reaches the 85C
threshold then shuts down.
Fan's OK, have cleaned off old thermal compound and renewed it but no
difference.
Found out that someone had previously opened it and hoovered the dust out
but whether that was before or after the fault I don't know, also it was
obvious that the CPU had been removed because the h/s was not properly
fitted and an attempt had been made to replace thermal compound without
removing the old.
Question is is it a faulty m/b or CPU?
Should I play safe and replace both?
Replies appreciated.

And this purely hardware fault has WHAT to do with XP? Oh, right,
NOTHING.

Ask elsewhere

 

[Kenny]

Edric, here's what I think:
http://www.amishrakefight.org/gfy/

 

[JohnO]

ROFL, that's beautiful.

Edric, here's what I think:
http://www.amishrakefight.org/gfy/

 

[Michael W. Ryder]

And this purely hardware fault has WHAT to do with XP? Oh, right,
NOTHING.

Ask elsewhere

And this purely wetware fault has WHAT to do with XP? Oh, right, NOTHING.

Reply elsewhere

 

[Edric]

And this purely wetware fault has WHAT to do with XP? Oh, right, NOTHING.

Reply elsewhere

It's easy to get me off the group - get your fellow dumbasses to stop
posting off topic CRAP.