PFN List corrupt Blue Screen

So I've been getting this blue screen for a while now, and I have no idea what's causing it.
It gives me the "PFN_LIST_CORRUPT" message. This happens every few hours or so of use on my computer.
Here's a picture of the screen: [Link]
I also have the msinfo32 and minidump files, if it helps.

Eagerly awaiting a helpful response.
KH

Up until April these were related to memory corruption.  In June they change to a hardware error (BCC124)

I suggest you run these two test

These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

Dont forget to upload any further DMP files (especially those when verifier is running)

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!   If you dont know what this means you probably arent

1-Memtest.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
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.

Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.


2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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).

Here is 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" (or  Type "verifier /standard /all"  (no quotes) if you want to verify all of them (this will slow your computer down))
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking 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.
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.

Further Reading
http://support.microsoft.com/kb/244617

About Driver Verifier
Driver Verifer information  driver verifier Windows Vista - Microsoft Search
Driver Verifier issues within Vista/ Windows 7  http://support.microsoft.com..default.aspx?+verifier1&res=20
Driver Verifier Special Pool Feature  http://support.microsoft.com/kb/188831

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I've used memtest for 6 passes, and no errors, so I know my RAM and motherboard slots are fine.
I'm currently using verifier to stress the drivers, like you suggested, but I genuinely have no idea which driver might be causing this problem. How will I be able to find out which driver it is, and what do you recommend doing after finding out?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

KH

When verifier finds a mis behaving driver it will crash the system.  Upload the DMP files when it does so we can investigate them.  It may take as long as 72 continuous hours to stress the system into crashing.

If it does not crash say within 24-48 hours we can reset verifier to "verify" all drivers which will slow the computer a bit.  To do that simply go into verifier and select "all" drivers.


Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

So, after 48 hours of sustained use on both settings, my computer decided to crash a total of 0 times. Both tests have come back inconclusive for results. What else could this possibly be?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

KH

Sometimes verifier acts like a buffer between the mis-behaving drivers.  I would run it for another 24 continuous hours and if it still doesnt crash turn it off by typing verifier /reset
Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated May 7, 2021 Views 46,810 Applies to: