On 12/02/07, Alan McKinnon <[EMAIL PROTECTED]> wrote:
On Monday 12 February 2007, Matt Richards wrote:
> I wouldn't of thought it would be the RAM not from behavior like that
> but it does sound like a overheating issue, I have had computers just
> power off because they get too hot.
The thing with memtest is that it does (mostly) predictable tests, which
can detect consistent errors with memory chips, or somewhat random
errors with memory.
BUT, it doesn't help at all with detecting didgy hardware in other
areas. It doesn't give you any valid tests for what happens when the
machine gets hot for example. Compiling a kernel (or openoffice.org) 10
times in a loop does do that.
It does look like it's a problem with the PSU or (God forbid) the cpu. ("God
forbid" because new CPU means new motherboard also).
So, I would say that you have shown that your memory chips are not
likely to be faulty, but you have not yet proven that the cpu (or the
rest of the machine) isn't getting hot and overloading.
Jeff, if you were paying me to diagnose your problem, I'd be telling you
to swap out the psu and test some more, then disassemble the
cpu/heatsink combination and replace the thermal grease and test some
more. If it then fails, the tests are still not conclusive so I would
want to forcefully cool the machine (with an external fan etc) while
putting it through some stress tests (like a looooooong compile).
Well at the moment it doesn't even survive the early stages of a short
compile (the ./configure stage) so hopefully if any progress at all is made
at diagnosing the problem, it'll be quick. Unfortunately if I were paying
you to diagnose the problem I'd also have enough money to buy spare PSU's -
but I'm not!
Jeff
--
Now, did you hear the news today?
They say the danger's gone away
But I can hear the marching feet
Moving into the street
Adapted from Genesis, "Land of Confusion"
http://latedeveloper.org.uk
