1.    09 Aug 2016 #1
    Join Date : Aug 2016
    Posts : 4

    Just got this BSOD awhile ago PFN_LIST_CORRUPT

    So upon getting this I ran Who crashed and got this

    On Tue 8/9/2016 9:24:57 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\080916-18015-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x4E (0x99, 0x2B83F3, 0x0, 0xA00000000302773)
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Can someone help?
      My System SpecsSystem Spec

  2.    09 Aug 2016 #2
    Join Date : Aug 2016
    Posts : 4

    BTW if anyone wants the Windbg Analaysis

      My System SpecsSystem Spec

  3.    09 Aug 2016 #3
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 3,806
    Windows 10 Pro X64 14393.105

    Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    You windbg trace does show memory_corruption so I would start by testing your PC memory:

    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums


    is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My System SpecsSystem Spec


Similar Threads
Thread Forum
Today my pc randomly crashed with a BSOD what could be causing it?
BSOD Crashes and Debugging
Just experienced PFN_LIST_CORRUPT - See attached DM Log Report
My computer has been crashing very frequently lately. This was the BSOD that I just saw before posting with the DM log report. I'm really struggling to complete work these days, so any help would be amazing!
BSOD Crashes and Debugging
So awhile back...
This is just a general question, but awhile back I heard that the taskbar isn't skinned in custom windows 10 themes because it "doesn't support visual styles anymore". Is this true? And if so, how is it known? (General curiosity)
Lose desktop once in awhile
Every once in awhile I lose my desktop which turns black and have no taskbar or icons. When this happens windows explorer appears and my gadgets are still showing and my mouse pointer shows and works. Outlook 2007 is still running ok as I hear...
General Support
Solved BSOD PFN_List_Corrupt error shortly after free upgrade from Win 7
Hi, I have partially solved this issue and I am still working it. I get a BSOD PFN_List_Corrupt error about 3-5 minutes into working. I used MSConfig to go into safe mode and disabled all. No more BSOD. Off safe mode with normal startup and...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:16.
Find Us
Twitter Facebook Google+

Windows 10 Forums