Stop Error: PFN_LIST_CORRUPT

[Thresher]

I just bought and installed an Asus A7V266-E. I bought new Corsair PC2400 RAM (256MB) to go with it. I moved all of my old hardware over to the new mobo (inc. a T-Bird 1.4Ghz). I installed WinXP Pro on the machine and it worked fine for 5 days, now I get all sorts of problems on boot. I can't run for more than a few seconds before I get a buttload of errors, all of which result in a dump. Unfortunately, it goes by so fast, I can't read it and I can't get to the minidump (frigging NTFS).

I've caught the following ones as it goes by:

Stop : 0x0000007E

Stop: 0x0000008e

and a few others. I've looked them up on MS Knowledgebase and can't find an exact match, but the all seem to point to a hardware problem.

On occasion, I've run into PFN_LIST_CORRUPT with a stop error of 0x0000004E.

The knowledgebase seems to indicate a bad memory chip, but it could also be bad internal cache. I doubt that is the problem because I've been running this CPU for about 4 months with no problems. The Vidcard has been running for about a year with no problems either, so I'm leaning towards the mobo or the RAM.

Anyone seen this error or have any clues? Is it a memory problem? I don't understand why it would run fine for several days, at least 2 of those days for 20 hours or so straight, and then go bad. Prior to the problems, it was running fine temperature wise. I booted it this morning with no trouble, then this evening, it went to hell. I backed off of the memory settings (had them at 2-2-2) and went with the defaults, but still BSOD. This box is not overclocked at all.

I'd REALLY rather not have to buy more memory now, right before Xmas, so any help or guidance would be appreciated. I bought the RAM over a month ago, so I can't RMA it and I'd hate to have throw it out.

 

[Thresher]

bump

 

[Thresher]

Bump
------------------------


Anyone got a clue on this thing?

 

[BlueTDimly]

<< I bought the RAM over a month ago, so I can't RMA it >>



You can't???! I just RMAed a stick of Crucial that I bought 8 months ago and (finally) figured out that it was what was causing my system to be unstable. I would really suggest that you try plugging in a new stick of RAM. Even just borrow a friend's or something.

You mention that it just started happening. Did you do anything to instigate the problems?

BlueT.

 

[Thresher]

Not a thing. I fired it up in the morning, it worked fine. Turned it on last night, BSOD all over the place. I broke down and bought some more RAM today, we'll see if that helps.

I've never seen RAM go bad AFTER it has been installed and running unless it was overclocked. Mine wasn't and it may have died. Wierd.

 

[Thresher]

I put the new RAM in and the computer is running. Cross your fingers.

I just hope there isn't some defect in the motherboard or the powersupply that is going to keep screwing up my RAM.

 

[yazz]

this happens every now and then. dont be too surprised. sometimes this error can be a combination of problems ranging from the motherboard or CPU, cache or ram. i have seen this error occur in some servers and workstations before. they would run great and fast ranging from 1 week to 2 months without a reboot and then BSOD. it can take a while to repeat those errors but you have to keep track of those BSODs and these BSODs you are getting are typical of something failing on the CPU, motherboard, cache RAM or RAM. try replacing one at a time and see if that clears up the problem. you may have to replace the motherboard, cpu and ram. good luck
have fun

 

[Thresher]

Well, it seems to be working now.

If it dies again under the same circumstances, chances are something is burning out my RAM, either a faulty voltage regulator on the mobo or a bad power supply.

Keep your fingers crossed.

One thing I noticed after running some tests is that my memory bandwidth is now half of what it should be. I'm going to tweak a bit this weekend, possibly move my timings up.

Anyone know of a good memory testing program? SiSoft Sandra used to have a part in it that would tell you what timings your memory would support, now I don't see it in there.