1 |
Hi Alex, |
2 |
|
3 |
...shot in the dark: |
4 |
Remove as much as possible of the cards, addons, connections etc |
5 |
from the PC ... make in as much "bare bone" as possible. |
6 |
|
7 |
Check All coolers (the little ones also) for dust. Remove all |
8 |
dust even if it is not completly covered with it. |
9 |
|
10 |
Dont forget the internals of the power supply. Detach all cables. |
11 |
Remove the power supply. Go outside ;) and blow the dust inside away. |
12 |
|
13 |
Put the power supply back into the PC again an attach the cables. |
14 |
|
15 |
Remove all RAM, carefully clean the contacts, insert as less RAM as |
16 |
possible. |
17 |
|
18 |
Remove even the HD if it is possible to get into the BIOS |
19 |
without any HD attached. |
20 |
|
21 |
Remove the BIOS battery, wait at least a day and insert it again. |
22 |
|
23 |
Start the PC and go directly into the BIOS. Check the date/time. |
24 |
If it shows the current date/time, the battery wasn't removed |
25 |
long enough. Check the battery voltage. Reinsert the battery. |
26 |
If your board has a BIOS reset: Reset the BIOS. |
27 |
|
28 |
Then: In the BIOS enter a page which "does something" |
29 |
(reports continously temperatures for example). |
30 |
|
31 |
If this is possible, let the PC run for a |
32 |
while that BIOS page and see, whether it |
33 |
hangs again or not. |
34 |
|
35 |
If all went fine, add ONE component and try it again. |
36 |
Add the HD at last to sort out hardware from software bugs... |
37 |
|
38 |
May be one of the components and not the CPU or motherboard |
39 |
causes the problem and you will be able to identify it by |
40 |
this procedure... |
41 |
|
42 |
HTH! |
43 |
|
44 |
GOOD LUCK! |
45 |
|
46 |
Best regard, |
47 |
mcc |
48 |
|
49 |
Alex Schuster <wonko@×××××××××.org> [12-08-17 09:56]: |
50 |
> Hi there! |
51 |
> |
52 |
> Two days ago, my PC suddenly died, after working fine for half a year. |
53 |
> I used myrtcwake as usual to suspend to RAM, and it woke up in the |
54 |
> morning. But after two minutes, the screen went blank and nothing, even |
55 |
> SysRq, gave a reaction. I tried booting a couple of times again, and |
56 |
> sometimes it did not even reach KDM. Now, I cannot even run Grub (from |
57 |
> my USB stick) any more, I only see a "GRUB" string at the top right, |
58 |
> then nothing happens. |
59 |
> |
60 |
> Booting with SystemRescueCD also freezes sometimes. If not, I can make |
61 |
> it freeze after seconds by running 'memtester'. |
62 |
> |
63 |
> Booting good old memtest86 ran for an hour and only found one error, |
64 |
> then I aborted, removed three of my four memory modules (4GB each), and |
65 |
> tried different ones in the first bank. Memtest86 again did not find |
66 |
> much errors, but froze once. Running memtester after booting from |
67 |
> SystemrescueCD again makes the thing freeze in seconds. It once also |
68 |
> froze while being in the BIOs setup. |
69 |
> |
70 |
> What could be the problem? CPU, board, or even the PSU? I do not think |
71 |
> it has to do with bad memory. I removed most of the other stuff (hard |
72 |
> drives, PCI cards). I have no similar hardware so I cannot simply |
73 |
> exchange things, the question is what to buy and try. How would you |
74 |
> proceed? |
75 |
> |
76 |
> The fan is still working, the cooler does not become hot, and in the |
77 |
> BIOS there are not high temperatures begin reported. But one thing was |
78 |
> strange: I updated Calligra from 2.4 to 2.5 (I think), and it took |
79 |
> ages, at least 8 hours. I thought there may b something strange with |
80 |
> the build process of this new version, forcing MAKEOPTS=-j1 and such, |
81 |
> but still this is very long. But when working with it, I did not notice |
82 |
> anything strange like sluggish reactions, and videos played fine. But I |
83 |
> did not use it as much as I normally do, and maybe even when overheated |
84 |
> and throttled down it would have been fast enough for me to not notice |
85 |
> this. I watch the syslog normally, but maybe I just did not look |
86 |
> closely that day, I was busy doing other stuff. |
87 |
> |
88 |
> CPUs don't just die, do they? Even when overheating, I think these days |
89 |
> throttle down, so no permanent harm should be done? So maybe it's the |
90 |
> board? It looks okay, no bent or leaking capacitors. |
91 |
> |
92 |
> This is really annoying. Of course most of my passwords are in my KDE |
93 |
> wallet I cannot access. There's also Wiki, CVS and Git repositories, |
94 |
> not needed every day, but still important. And the timinig is very bad, |
95 |
> I just started my new job the day the problem happened, and I do not |
96 |
> have much time for this now. Before, I was working at home, so I would |
97 |
> have had all day to diagnose and try things. |
98 |
> |
99 |
> It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. |
100 |
> |
101 |
> Wonko |
102 |
> |