Stop error question!

[gymscat]

Recently one of my pcs has been giving me fits with various stop errors, the latest of which is
pfn_list_corrupt. I have tried new ram, new hd, etc. but to no avail. I've run Memtest and it has come up with no errors. I"ve tried to reinstall Win XP Pro more times than I can count!
Is it possible that one of the RAM slots has gone bad but Memtest doesn't pick it up?
The only other thing I can think of replacing is the motherboard and/or CPU.
Any suggestions?
Thanks
Gary

 

[Rugger]

What are your system specs? OS? Here is a list of <A HREF="http://kadaitcha.cx/stop_err.html" target="_new">Windows XP Stop Errors</A>.

Have you tried a <A HREF="http://www.google.com/search?hl=en&q=pfn_list_corrupt" target="_new">Google search?</A>
Here's what MS has to say on <A HREF="http://support.microsoft.com/?kbid=291806&sd=RMVP" target="_new">PFN_list_corrupt</A> on Win 2000.

Looks like this is memory or drivers. Create a boot disk and run <A HREF="http://www.majorgeeks.com/download4226.html" target="_new">Memtest86+</A> if you haven't already. If you have more than 1 stick of RAM, then remove one stick and test one of the sticks at a time. Let us know what you find....

__________________________________________________
<font color=red>You're a boil on the arse of progress - don't make me squeeze you!</font color=red>

 

[gymscat]

Thanks for replying. I have already read that article and run Memtest for approx. 12 hour with no errors.
I'm beginning to think it's gotta be the ps or the mobo.
G.

 

[Rugger]

Have you run Sandra memory burn (looping) in windows? What are your system stats?

__________________________________________________
<font color=red>You're a boil on the arse of progress - don't make me squeeze you!</font color=red>

 

[gymscat]

Thanks for replying Rugger. No I ran Memtest only for about 10 tests. Turned up everything ok. However the box runs fine with only one RAM module in the first slot. Must be the slot?

Gary

 

[beetlebz]

Ive seen ram do some weird things, I would be willing to bet that its just bad ram. The only time Ive seen memory-esque BSOD's when memory was NOT the cuplrit was when the customer was running a PS that was too small. The one that came with the case was a POS. threw in a thermaltake purepower and never looked back. Same thing with my own PC.

You should be able to check the rail voltages in your bios, and theres a handful of free downloads on the net to monitor voltages and sound an alarm if it fluxuates too low.

my money is still on bad ram though