Random BSOD PFN_LIST_CORRUPT Win 7 64

[marek4ern7]

Hello, i need help with random BSOD on Windows 7 64 bit. System is updated including all patches and drivers, but i'm getting BSOD PFN_LIST_CORRUPT once per day. Based on my findigs this BSOD is pointing to buggy driver, but i can't identify which one.
I executed memtest86 for 12 hours run, without any issues, as well ase hard disk check.
Could someone please have look on memory dumps and help identify root cause of the problems?

Perfmonitor and dump files attached.

Thanks,
Marek.

 

[zigzag3143]

Hello, i need help with random BSOD on Windows 7 64 bit. System is updated including all patches and drivers, but i'm getting BSOD PFN_LIST_CORRUPT once per day. Based on my findigs this BSOD is pointing to buggy driver, but i can't identify which one.
I executed memtest86 for 12 hours run, without any issues, as well ase hard disk check.
Could someone please have look on memory dumps and help identify root cause of the problems?

Perfmonitor and dump files attached.

Thanks,
Marek.

Since you have appeared to pass memtest please run driver verifier.

I'd suggest that you first backup your stuff 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.

 

[marek4ern7]

Hi zigzag, i did steps you recommended and i got another three BSOD but with different bug check code now it is Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL instead of PFN_LIST_CORRUPT. Memory dumps attached can you please have a look. I installed WinDbg but i'm not expert for these kind of issues it's saying something like VISTA_DRIVER_FAULT but don't know which one.
Thanks,
Marek.

 

[zigzag3143]

Hi zigzag, i did steps you recommended and i got another three BSOD but with different bug check code now it is Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL instead of PFN_LIST_CORRUPT. Memory dumps attached can you please have a look. I installed WinDbg but i'm not expert for these kind of issues it's saying something like VISTA_DRIVER_FAULT but don't know which one.
Thanks,
Marek.

Marek

Your most recent is driver verifier enabled and blamed on pool corruption. The specific driver is still unknown.

Something changed after the 9:11pm crash. Is that when you enabled verifier?

One thing of note:

VB Box often causes bsods.