A good example of why you follow procedure when troubleshooting

Discussions about anything Computer Hardware Related. Overclocking, underclocking and talk about the latest or even the oldest technology. PCA Reviews feedback
Post Reply
User avatar
FlyingPenguin
Flightless Bird
Posts: 33161
Joined: Wed Nov 22, 2000 11:13 am
Location: Central Florida
Contact:

A good example of why you follow procedure when troubleshooting

Post by FlyingPenguin »

My file server has been a little buggy. It tends to crash with a vague page fault BSOD for no apparent reason. Usually under strain though (copying lots of files, burning DVDs).

Ran MEMTEST on it and I immediately got a memory error (AHA!). I then tried several different DDR memory sticks I have lying around here and they all failed MEMTEST so I knew it wasn't actually bad memory.

- Tried resetting CMOS. Nada.
- Pulled all PCI cards in case one was interfering with the memory bus. Nada.
- Swapped the PSU and that fixed it much to my surprise!

I had little expectation it would work since all voltages looked good on the meter - but the meter doesn't tell you anything about spikes and fluctuations. Still, it was the next thing on the list before swapping the CPU and then just writing it off as a bad mobo.
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

Image
User avatar
normalicy
Posts: 9514
Joined: Sat Nov 25, 2000 4:04 am
Location: St. Louis, MO USA
Contact:

Post by normalicy »

Yup, I've had that happen a bunch of times (even on good PSUs).
Post Reply