pfn list corrupt // page fault in nonpaged area

Hi Team,

Last week i brought to your attention i was having dxdiag and atikmpag errors. I have resolved that by purchasing and using a Nvdia gtx560ti and the tech support people i bought the previous 6950 from advised me that they have come across a lot of problems with the Asus version of the card.

With the new Gtx560ti, i purchased another 4GB of the Kingston HyperX pnp Ram. Since, i was getting random BSODs relating to "page fault in non pages area". I resolved this by removing the ram stick in Slot 4 of my Motherboard. After a few successful attempts, i reconnected the "suspected" Ram stick in Slot 3 and put another stick in Slot 4. Since, i have not had a problem with page fault in nonpages area BSODs.

However, i am now beginning to get PFN_LIST_CORRUPT. What i would like to know is if this is related to the "bad" ram stick or a driver problem. I use the Uniblue Driver Scanner which is unable to find any outdated drivers. Can you look at my minidump please? :)

Note that i used the Windows 7 memory diagnostic test and a pfn list corrupt BSOD occurred at 99% completed. At 98% it still showed "no errors have been found".

chimpindistress said:

Hi Team,

Last week i brought to your attention i was having dxdiag and atikmpag errors. I have resolved that by purchasing and using a Nvdia gtx560ti and the tech support people i bought the previous 6950 from advised me that they have come across a lot of problems with the Asus version of the card.

With the new Gtx560ti, i purchased another 4GB of the Kingston HyperX pnp Ram. Since, i was getting random BSODs relating to "page fault in non pages area". I resolved this by removing the ram stick in Slot 4 of my Motherboard. After a few successful attempts, i reconnected the "suspected" Ram stick in Slot 3 and put another stick in Slot 4. Since, i have not had a problem with page fault in nonpages area BSODs.

However, i am now beginning to get PFN_LIST_CORRUPT. What i would like to know is if this is related to the "bad" ram stick or a driver problem. I use the Uniblue Driver Scanner which is unable to find any outdated drivers. Can you look at my minidump please? :)

Note that i used the Windows 7 memory diagnostic test and a pfn list corrupt BSOD occurred at 99% completed. At 98% it still showed "no errors have been found".

This error is typically caused by a driver passing a bad memory descriptor list.


Windows memory diagnostic doesnt stress the memory enough. I would run these two.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

Hi ZigZag,

Thanks. Will give them a shot. About 30 minutes ago i started getting that PFN LIST CORRUPT BSOD everytime windows was beginning to load up. (The screen where it shows windows and the flag is forming from 4 different colored orbs merging together). The moment the blue screens merged i was getting the BSOD. This occured 5 times in a row. I have gone and removed the RAM i believe is at fault and have logged back in successfully.

I will however give them ideas a shot since i won't know if the BSODs will occur again at a later stage.