Skip to content
PCDecoder
0x0000004EPFN_LIST_CORRUPTStop codeWidely reported

PFN_LIST_CORRUPT (0x4E): what it means and how to fix it

Updated Oct 16, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

The PFN_LIST_CORRUPT stop code occurs when the internal database Windows uses to track physical RAM pages becomes damaged. It is typically caused by a malfunctioning device driver or faulty physical RAM. Checking your memory for hardware errors and updating misbehaving drivers are the best first steps.

What it means

Windows organizes physical RAM into fixed blocks called page frames. To track where these frames are located, whether they are in use, and which process owns them, the Windows kernel maintains an internal database known as the Page Frame Number (PFN) list.

When bug check 0x0000004E appears, Windows has detected that this tracking list has become corrupted. The operating system halts immediately to prevent data corruption from spreading across your system files or storage drives.

Why the list gets corrupted

The corruption usually happens in one of two ways: software driver errors or physical memory defects.

A device driver might pass an invalid memory descriptor list to the kernel. For example, a driver might attempt to unlock a page of memory more times than it locked it (such as calling MmUnlockPages repeatedly), or it might try to free a page that is still actively locked for input/output operations. When a driver mishandles memory pointers like this, it writes invalid values into the kernel's memory tracking structures.

Alternatively, physical hardware faults can cause this crash. If a memory module has a single-bit error, or if Direct Memory Access (DMA) transfers fail, the underlying page table entries and PFN structures get altered outside the control of the operating system. In these cases, Windows attempts to read or write to a tracked page, finds inconsistent state data, and triggers the blue screen.

Common causes

  • A faulty device driver passing an invalid memory descriptor list or mismanaging page locks.
  • Physical RAM errors, including single-bit hardware memory failures.
  • Hardware Direct Memory Access (DMA) transfer failures corrupting page structures.
  • A driver attempting to free a memory page that remains locked for I/O operations.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run the Windows Memory Diagnostic tool

    Use this first to check if physical RAM defects are causing the corrupted page structures.

    1. Press the Windows Key and type Windows Memory Diagnostic.
    2. Select Restart now and check for problems.
    3. Wait for your PC to reboot into the diagnostic environment.
    4. Allow the scan to finish; Windows will restart and display test results after login.
    Did this fix it?

  2. Update or roll back recently installed drivers

    Use when the crash started after a recent hardware addition, driver update, or system change.

    1. Right-click the Start button and select Device Manager.
    2. Expand the categories to locate devices that were recently updated, such as display adapters or storage controllers.
    3. Right-click the device and choose Properties.
    4. Select the Driver tab and click Roll Back Driver if the option is available, or choose Update driver to search for newer software.
    Did this fix it?

  3. Analyze crash dump files with a debugger

    Use if driver issues persist and you need to identify the exact driver file causing the error.

    1. Open a kernel debugging tool capable of reading Windows minidump files.
    2. Load the crash dump located in the Windows Minidump directory.
    3. Run the !analyze debug extension command to view the failure analysis.
    4. Execute a stack backtrace command, such as k, to display the call stack and identify the faulty driver.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 14, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does PFN stand for in Windows?

PFN stands for Page Frame Number. It is the numbering system Windows uses to index and track blocks of physical RAM.

Does PFN_LIST_CORRUPT mean my RAM is broken?

Not necessarily. While faulty memory hardware can trigger it, the crash is frequently caused by buggy device drivers that write invalid data into the kernel's memory tracking lists.

Why does this error sometimes mention ntoskrnl.exe?

ntoskrnl.exe is the Windows operating system kernel that manages system memory. When a faulty driver corrupts memory structures, the kernel detects the failure and halts the system, making it appear in crash reports as the affected component.

More stop codes decoded