Windows 10: BSOD right after Windows loading screen (PFN_LIST_CORRUPT)

Since 2PM today I have had to deal with my system having a random BSOD with the PFN_LIST_CORRUPT error code and every attempt at booting the system normally has resulted in the same error being presented right after the Windows 10 loading screen went away.

I have tried the following:

• chkdsk /f /r - no issues found, but: "Failed to transfer logged messages to the event log Status 50"
• sfc /scannow - no issues found
• mdsched.exe - no issues found
• booting in safe mode to update any driver that was out of date - I could do it, but the issue persists

At the end of the day I still have the same issue. I'm typing from that computer while booted in safe mode, which I suppose is somewhat of a silver lining, and I'd rather get useful advice from far more expert users in here than proceed with a more drastic approach.

Attached below you'll find logs retrieved by the beta log collector. I hope the information I've provided proves helpful and I'm ready to provide further data wherever possible, if necessary.

:)

 

PFN_LIST_CORRUPT Windows 10

Hi,

The issue you're experiencing with having a blue screen with an error code PFN_LIST_CORRUPT might be due to a variety of reasons, and that is what we are going to find out. To help us identify the cause of this issue, we would need to know the following
information:

• Which build and edition of Windows is installed on your computer?
• What particular activity are you doing on your device before this issue happened?
• What troubleshooting steps have you done so far?

In the meantime, we suggest performing a clean boot on your device. Check if the same issue persists even after booting the device into a clean boot. This
link provides further information about how clean boot works and the steps on how to perform clean boot. Make sure to follow the steps under Windows
10.

We are looking forward to your response.

 

pfn_list_corrupt BSOD

I was having an issue with BSOD'. I was getting the pfn_list_corrupt, kmode_exception_not_handled, memory_management error and a couple others I didn't write down. I am using win10 and after the 1/8/16 update, I was having a boot issue. after all my t/s
steps, I discovered it was the data port on my optical drive that caused the problem, not the updates. while I had the tower open I decided to boost my RAM to max out @ 16GB. all seemed well ar first, then I started getting the bsod's and error msgs. the memory
error msg seemed to come up the most.

after going through the steps in the posts here nothing seemed to work. I decided to put my original memory back in the computer and waited, but did not get anymore bsod's. tried the new memory, which aht flunkie at best try assured me would be compatible
based on the exact specs I brought to their store. yeah right. so I have had my old memory in the system now and still have not gotten the bsod's.

sad to think that some of the components out there aren't usable w/ win10, but some of these issues others are having may be related to their RAM.

Thought I'd share this with you all. Just food for thought.

 

PFN_List_Corrupt

Hi there,

I have been trying to fix a BSOD error of PFN_List_Corrupt for a few weeks now with my Windows 10 install. It's very random, but annoying. I've run memtest a few times with no findings. I've reinstalled various drivers and no luck. I just recently did a
fresh Win 8.1 install to the SSD and then upgraded to Win 10. I am assuming I need to do another fresh install of 10, but before going through that, I thought I would ask the community if there was an easy PFN_List_Corrupt fix. I've searched around a fair
bit and tried some of the suggested fixes, but so far, nothing has worked.

Verifier.exe puts me in a BSOD loop. Luckily, I had a system restore point and used that.

Here is a link to my three most recent Minidump files:

Minidump.zip

Three different driver crashes here

- First one, the PFN_List_Corrupt (0x0000004e) caused by ntoskrnl.exe

- Second one, Nvlddmkm.sys

- Third one, Driver Verifier BSOD loop caused by aswsnx.sys (my Avast antivirus) as well as ntoskrnl.exe

Anyway, would love any suggestions as to best go about repairing this. Thanks in advance for any help.