BSOD in Windows 7 - PFN_LIST_CORRUPT
By admin on Dec 15, 2009 in PC Crash, Windows 7
Few days ago I experienced my first Windows 7 problem. My dad’s Toshiba L300 laptop, which was upgraded from Windows Vista to Windows 7 recently, suddenly started showing the Blue Screen Of Death. It appeared randomly and all I could see before the laptop restarted was the PFN_LIST_CORRUPT message. The error code that followed was 0×0000004E.
I could see no reason for it, since the laptop was new, no new software or hardware was installed and the only change was the Windows system upgrade.
This error message means that the Page Frame Number is corrupt, and it usually has to do with bad memory or bad drivers. It comes up in Windows 2000, XP, Vista and 7.
In my case the memory was brand new, but I still ran the Windows 7 memory diagnostic tool, just to be safe. To access this program, you’ll need the Windows 7 installation DVD. Boot from this DVD and follow the instructions on the screen to ‘Repair you computer’. At the next screen, you’ll see some new options on the menu, one of which is the Windows Memory Diagnostic Tool. For detailed instructions on how to get there, please go here.
Next, I suspected that one of the drivers didn’t agree with Windows 7. Even though all drivers installed correctly when the laptop was upgraded, a ‘bad’ driver could still have caused this error, especially a graphic driver. I went to the Toshiba Support site and downloaded their most recent Windows 7 graphic card driver. After this installation, the error hasn’t come back. I’m still testing the laptop, but more than a week later, the BSOD hasn’t reappeared.
Most Web sites I visited recommend that you check your memory and drivers. Test your RAM with memory diagnostic tools (memtest86 and memtest86+) and update all your drivers. If that doesn’t solve your problem, uninstall all programs and/or hardware you added recently and see if that helps. Another thing you could do is update your BIOS (and disable RAID controllers in BIOS).
UPDATE: If you are not sure which driver you need, download Everest Home Edition, a free driver identification tool.
Hi! I already upgraded to Win7 for two weeks now and so far no problem.
Thanks for this post, might come handy, in case..
jeist | Dec 16, 2009 | Reply
I’m currently trying to troubleshoot this exact same issue. Thanks for the article (keeping my fingers crossed).
DeLorean Time Machine Rental Guy | Dec 26, 2009 | Reply
You’re welcome. Good luck!
admin | Dec 26, 2009 | Reply
I had a very similar problem on my Toshiba Satellite A300. For me the most suspicious driver was the Synaptics Pointing Device. I tried to run verifier.exe to observe this driver, but it crashed my whole system. So I upgraded it from version 10.xx.xx to 14.xx.xx and BSOD disappeared (for now).
Sadly on Toshiba website there was no info and no drivers for Synaptics - I had to identify the problem on my own.
Maciej | Mar 2, 2010 | Reply
Hi, i´ve the same problem, few weeks ago i reinstalled windows 7 to the final version (i had a rtm), and started to have that blue screen. I just had been installed only 2 new elements, a game with nvidia physx optimization(and i have a Radeon), and a webcam. so i proceed to unistall those software and drivers, but the problem stills. i dont know what more can i do. and my BIOS is updated
Any Ideas?? (doing test memory)
Gelipe | Mar 13, 2010 | Reply
Sometimes there are still files in the registry after you uninstall a program or drivers. Use a registryu cleaning program to clean your registry. you can also try system restore. Finally, I’ve read somewhere that a bad touch pad (in laptops) can cause this error. How often do you get the blue screen?
admin | Mar 14, 2010 | Reply
I cleaned the registry with differents tools (ccleaner, tuneup, comodo) but the bluescreen stills appearing only when tun on the PC, it happens maybe 2 times before keeps stable. and display different trouble, pfn_corrupt_list, irql_not_less_or_equal, or memory_management
Gelipe | Mar 15, 2010 | Reply
pfn_corrupt is often caused by memory problems. Plus, you have memory management errors. Try to take out the RAM and test with new modules, if you can find some spare ones. I would also see if the error appears in safe mode.
admin | Mar 16, 2010 | Reply