- Joined
- Sep 22, 2004
Ok, I'm chillin' surfing the web last night and my machine completely locks up for the first time since I built it a few months ago. This is bothersome. So I reboot and get into windows(XP Pro SP2) and find that a Norton process is pegging my cpu out at 100%- again, strange and bothersome. So I reboot again. I get to the XP login screen, enter my password and the desktop begins to load... then, da dadada ta da....!!!!! BSOD!!!#$!@ What the heck?!? The main error I get is PFN_LIST_CORRUPT. Googling this will bring up a document from Microsoft explaining what to go check.
http://support.microsoft.com/?kbid=291806
I had not added any hardware before this happened, so it's not a driver issue. The only thing I have changed in the last month was switching to my new Mushkin BH-5 and the Microsoft site does say that bad ram can cause this behavior. I have only had the ram for about a month. So I run memtest86+, Test #5, and get almost instant errors or a total lockup before completing the first pass of Test #5 at either 200FSB or 220FSB, so I believe a stick or both sticks of ram have crapped out. Haven't had a chance to try each stick individually.
By my memtest results I am willing to bet that the ram is the culprit. Actually I hope it is the problem... then I can just get Mushkin to send me a new one. Anyone else ever experienced this problem? If so, was it your ram or something else?
http://support.microsoft.com/?kbid=291806
I had not added any hardware before this happened, so it's not a driver issue. The only thing I have changed in the last month was switching to my new Mushkin BH-5 and the Microsoft site does say that bad ram can cause this behavior. I have only had the ram for about a month. So I run memtest86+, Test #5, and get almost instant errors or a total lockup before completing the first pass of Test #5 at either 200FSB or 220FSB, so I believe a stick or both sticks of ram have crapped out. Haven't had a chance to try each stick individually.
By my memtest results I am willing to bet that the ram is the culprit. Actually I hope it is the problem... then I can just get Mushkin to send me a new one. Anyone else ever experienced this problem? If so, was it your ram or something else?