Gentoo Archives: gentoo-user

From: Alex Schuster <wonko@×××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] My PC died. What should I try?
Date: Fri, 17 Aug 2012 17:30:03
Message-Id: 502E7E9F.8060206@wonkology.org
In Reply to: Re: [gentoo-user] My PC died. What should I try? by v_2e@ukr.net
1 v_2e@×××.net writes:
2
3 > If the system behaves in such an unpredictable way (freezing at a
4 > random point), I usually check the following things:
5 > - RAM;
6 > - bloated capacitors on the Motherboard;
7 > - bloated or dried capacitors in the power supply unit;
8 >
9 > If your PC is only half a year old, it is unlikely that the
10 > capacitors dried. But they could easily bloat, especially if they were
11 > of bad quality or situated near some hot surface like heat sinks.
12 > Testing the power supply needs not only visual analysis. It would be
13 > good to attach the oscilloscope to the output and see the voltage
14 > level. It should not have large peaks (voltage jumps). But this is
15 > usually true for the old units with dried capacitors, as I said.
16
17 The power supply is older, I re-used it from the PC I had before this
18 one. I hope it causes the trouble, and will try another one this
19 evening. Thanks for this information, this strengthens my confidence
20 that I do not have to buy a new board or CPU. Now I am driving home with
21 a bag of three PSUs I had lent to a friend (and already forgotten).
22
23 > If I were you, I'd tried to temporarily replace the memory with a 100%
24 > working module, and if it does not help - replace the power supply
25 > unit (if you do not have the necessary equipment to test it thoroughly).
26
27 I wish I had :) The RAM is okay, I think, I cannot imagine different
28 memory modules to suddenly go bad all at once. And memtest86 found one
29 error only after an hour, while the crashes happen after a few minutes
30 already.
31
32 > And one more simple test: turn on the PC, enter the BIOS setup
33 > utility and keep it running in this state. If it runs ok for some time
34 > (like a couple of hours), I'd say the problem is in RAM.
35
36 It once crashed after ten minutes. That was not reproducable, but I did
37 not try that often.
38
39 Wonko