Windows 10: Random PFN_LIST_CORRUPT BSODS?

Hi all - a friend asked me to look at their laptop which is having random PFN_LIST_CORRUPT Bluescreens. These seem to happen at random. I had it playing a HD video on Youtube for 3 hours this morning and it was fine, but I tried to open the Event Log to look at the data, and it crashed again (as well as crashing once just sitting on the desktop....and another time opening the browser....no idea what's causing it).

It's a Lenovo Y50-70 running Win10 Home (v. 2004). I know this can be a driver issue, so I updated all the drivers as much as I could....no dice, still does it.

SFC comes back clean, DISM comes back clean.

Link to the Windows MEMORY.DMP from the BSOD is here (for the last BSOD, anyway):
MEMORY.DMP - Google Drive

I haven't been able to keep it working long enough to see if the BSOD codes match from BSOD to BSOD, but I do know they are all consistently a 'PFN_LIST_CORRUPT" error.

Any thoughts or ideas I could try?

:)

 

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:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

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.

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

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.