Good old BSOD

[morkus64]

Alrighty, gt a BSOD with:

STOP: 0x0000008e (0xc0000005, 0x805f10e2, 0xf88c565c, 0x00000000

Running WinXP on an Athlon XP 1800+... haven't changed any hardware in ages...

So, from looking around so far, it seems like a ram error? would this mean that one of the physical modules is bad? is there a program to test them, or would i have to try one at a time? Anything else to try? I'd love to get this fixed before i leave home tomorrow, so i don't need to take another trip back here too soon. thanks for any help everyone

 

[mountcarlmore]

download memtest86, load on floppy, and boot with floppy in drive, run tests.

 

[Smilin]

Could be memory modules, sure. Don't confuse the 0xC0000005: STATUS_ACCESS_VIOLATION (A memory access violation occurred) with a hardware error though. It is more likely a driver issue.

If a driver was mentioned during the crash, update or disable it.
If win32k.sys was mentioned, disable any 3rd party remote control software.
Be sure your BIOS is up to date.

 

[FlyingPenguin]

9 times out of 10 it's a bit of corrosion on one of the memory stick edge connectors. Remove your memory sticks and look at the edge connectors (both sides). They should be bright and shiny. If not use a NEW clean pencil eraser to lightly rub the connectors. This gets the thin patina of corrosion off them. Make sure to take static discharge precautions since it's dry this time of year.

Blow any eraser residue off with a can of dust off.

Usually just removing and re-installing the sticks will clean the contacts but in extreme cases, or humid environments, you might have a lot of crud on the contacts.

I would then MEMTEST86+ all night (at least 12 hours). If it passes then the memory is fine.

 

[morkus64]

well i tried memtest86, and it only made it to 3% pass before the system rebooted itself...

 

[Smilin]

Originally posted by: morkus64
well i tried memtest86, and it only made it to 3% pass before the system rebooted itself...

Ouch, hardware error. Items in use and under heavy load were CPU, Motherboard (memory controller & bus), and your memory. A few more controlled runs should help you isolate.

go to a single stick of memory in the first slot.
Run your test again.

If it completes, move the same stick to a different slot and try again. If it then starts rebooting, then you have a memory controller or bus problem. Replace the motherboard.

If it does not complete, move the same stick to a different slot and try again. If this new run fails, try a different stick of memory. If this still fails you have a bad cpu or mobo. If a new run works, then your first stick of memory was bad.

If you have another set of memory sticks from a known-good machine, swapping the two would also help isolate.