On 12/14/2011 01:01 AM, Colin B. wrote:
wrote:
Colin B. wrote:


So this is my plan for the next round of "homework" (Bah, I'm too old to
be troubleshooting junk like this!):

1) Reset the CMOS and retry
2) Boot from a Linux LiveCD and test the CPU. I'm thinking of using
stresslinux - any thoughts?
3) Try to do a fresh XP install to a spare HDD I have.
4) ???

Oh, just in passing I should also mention temperatu At first it was
floating aroung 51C in the BIOS, but I decided to reseat the cooling
fan (used the original fan from the E2200--both CPUs are 65W, so it
should be sufficient), and now the BIOS is reporting about 41-43C; even
immediately after Windows crashes. If I can get the livecd to run, then
I should be able to monitor this closer.

Thanks,
Colin


Any kind of stress test will do.

The nice thing about Prime95, is that the program computes maths
with a known answer, allowing it to check that any computations
done are correct. It was originally intended, to help users contributing
to the Mersenne prime number project, to be able to weed out bad hardware.
The Mersenne prime project will fork out the same work, to more than one
machine, to seek confirmation, so even if machines aren't error free, they
can look at the response of multiple machines for better quality results.

If you only have one computer, you have the option of returning to running
the E2200, until you have all your tools in hand, and are ready to start
testing. I recommend two computers minimum, for home builders/hackers. I've
actually managed to break two machines while working on them, and needed a
third to make CDs, download stuff, and allow me to web surf for an answer, so
that's my current record for busting things :-) But normally, if something
breaks here, a second machine is enough.

You can always go to a computer recycler, and find some old Pentium III
box, which would be good enough for emergency downloads. Throw in a
$20 DVD burner, and your "liferaft" computer is ready. It might not be
fast enough for anything else, but for bailing out your main machine,
it would be enough.

So I hereby declare the CPU to be bad.



snip

It's essentially impossible for a CPU to be bad if the machine boots.

Try clocking it down to see if you can get the machine to boot