| 1 |
On Sun, Feb 15, 2009 at 4:26 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 2 |
> Mark Knecht <markknecht@×××××.com> writes: |
| 3 |
> |
| 4 |
>> Reseat memory and PCI cards, etc. Consider removing for a period of |
| 5 |
>> time any hardware not absolutely necessary to debug the problem. (I.e. |
| 6 |
>> - second video card, extra disk drives, extra network adapters, etc.) |
| 7 |
>> Run memtest86 for a few days if you can spare the machine. Run |
| 8 |
>> spinrite, etc., to look for drive problems. Open the box up and place |
| 9 |
>> a fan blowing extra air for additional cooling. |
| 10 |
> |
| 11 |
> That all sound fairly drastic... wouldn't any or all of those problems |
| 12 |
> leave some kind of track? Something I can look for short of tearing |
| 13 |
> up the whole machine? |
| 14 |
> |
| 15 |
|
| 16 |
If it's contact oxidation then no, you won't be able to see it |
| 17 |
visually. If you're nervous about this then save it for later. |
| 18 |
|
| 19 |
Do as Volker and Neil say. (PSU, smartmon) Run tests for a while. |
| 20 |
memtest is a must. |
| 21 |
|
| 22 |
Always pays to go slow but you might want to make sure you're backups |
| 23 |
are VERY good right now. |
| 24 |
|
| 25 |
Good luck, |
| 26 |
Mark |
Archives