ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

PFN_LIST_CORRUPT

Windows PFN_LIST_CORRUPT: corrupted memory page frame list

Verified with sources5 sourcesReviewed Oct 4, 2026
Technician coming? See the 2 steps they must show you

Risk level

Medium

Proceed carefully and stop if the check is unclear.

Urgency

High

Quick answer

Windows stopped because the list it uses to track physical memory pages (PFN) is corrupt. First check Device Manager for any driver showing an error, install pending updates and test the RAM with the Windows tool.

Safety first

Stop and check this first

  • If the service centre will update the BIOS or replace the motherboard, save your BitLocker recovery key first: Windows may ask for it after a hardware change.
  • Do not open the PC to move memory modules yourself; at most unplug external peripherals and leave the rest to the maker or a technician.

Safe checks you can perform

  • Devices with errors in Device Manager
  • Pending updates and disk space
  • RAM and maker diagnostics
  • Safe Mode use as a test

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Hardware diagnosis at a service centre
  • Do not attempt this professional task: Dump analysis with the call stack

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Hardware diagnosis at a service centre

    What they doIf the dump shows a hardware subcode or memory tests fail, the maker's service centre checks memory, motherboard and firmware.

    They must show youthe diagnostic report with the tests run and their result.

    In writingthe part repaired or replaced, the final BIOS version and whether warranty covers it.

  2. Dump analysis with the call stack

    What they doA technician loads the memory dump in WinDbg, runs !analyze and reviews the call stack with the k commands to see which driver was handling the pages.

    They must show youthe !analyze -v output, the parameter 1 value and the module that appears in the stack.

    In writingthe driver or component identified, whether the subcode points to hardware and what was changed.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Devices with errors in Device Manager

    No special tools

    Who:
    you, from your Windows account.
    How:
    right-click Start, open Device Manager and expand the categories looking for an exclamation mark; on any flagged device try Update driver and, if that fails, disable or uninstall it.
    Result that matters:
    finding a device whose driver is not loading properly and could be damaging the page list.
    If one was flagged and after fixing it the blue screen does not return, that driver was it.
    If nothing is flagged, carry on with updates and disk space.
    Evidence to keep:
    screenshot of the flagged device and driver version before and after.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors

  2. Pending updates and disk space

    No special tools

    Who:
    you, with the laptop on mains power.
    How:
    in Settings, Windows Update, install everything pending and restart; then check in File Explorer how much free space drive C: has and clear files until 10 to 15 percent is free.
    Result that matters:
    Windows having its fixes current and room for the paging file.
    If updates or space were missing and after fixing them the PC stays stable, treat it as solved while watching a few days.
    If everything was already in order, move on to checking memory.
    Evidence to keep:
    free space percentage and the list of updates installed that day.

    Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors

  3. RAM and maker diagnostics

    No special tools

    Who:
    you, without opening the case.
    How:
    start Diagnose your computer's memory problems by searching Memory in Control Panel and, if your PC maker offers a hardware diagnostic tool, run it too following its instructions.
    Result that matters:
    a report saying whether RAM or another component fails an objective test.
    If a test fails, keep the report and ask for a warranty or technician check.
    If everything passes, a driver becomes the main suspect again.
    Evidence to keep:
    the MemoryDiagnostics-Results entry in Event Viewer and the maker's report.

    Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors

  4. Safe Mode use as a test

    No special tools

    Who:
    you, following Microsoft's guide for your Windows version.
    How:
    boot into Safe Mode, where only basic drivers load, and use the PC for a while with simple tasks such as browsing or opening documents.
    Result that matters:
    seeing whether the stop disappears without third-party drivers.
    If it never crashes in Safe Mode, the problem is almost certainly a driver or service that does not load there.
    If it crashes in Safe Mode too, hardware gains weight and a professional test makes sense.
    Evidence to keep:
    how long it ran in Safe Mode and whether any stop occurred.

    Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x0000004E
  • 0x4E
  • PFN LIST CORRUPT
  • STOP 0x0000004E
  • stop code PFN_LIST_CORRUPT

What it means

Microsoft defines bug check 0x0000004E as a corrupted page frame number (PFN) list; it is the table Windows uses to know which RAM pages are free, in use or locked. The typical cause is a driver passing a bad memory descriptor list, for instance unlocking the same pages twice. Some parameter 1 values, such as 0x8D, point more towards hardware, and 0x06 can come from single bit errors or broken DMA transfers. On its own this code does not confirm that memory or any other part is faulty.

Warnings and stop conditions

  • Highsource verified

    If the service centre will update the BIOS or replace the motherboard, save your BitLocker recovery key first: Windows may ask for it after a hardware change.

    Evidence: Find your BitLocker recovery key

  • Mediumsource verified

    Do not open the PC to move memory modules yourself; at most unplug external peripherals and leave the rest to the maker or a technician.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors

Symptoms and causes

Probable causes · in order

  • A driver locking and releasing pages badlyCommon

    Microsoft says the usual cause is a driver passing a bad memory descriptor list, such as calling MmUnlockPages twice with the same list.

    Evidence: Bug Check 0x4E PFN_LIST_CORRUPT

  • Memory fault or broken DMA transfersPossible

    The parameter table links some subcodes to hardware single bit errors, broken DMA transfers or a page-free list damaged by hardware.

    Evidence: Bug Check 0x4E PFN_LIST_CORRUPT

  • Outdated system or little free spacePossible

    The support guide asks you to install the latest updates and keep 10 to 15 percent of the drive free for swap files and system functions.

    Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors

Virtual technician

Does PFN_LIST_CORRUPT still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Stop code error or bug check troubleshooting (IT professionals)

    Microsoft · 2026 · official_doc

  2. 2

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

  3. 3

    Solución de problemas de reinicios inesperados y errores de código de detención de Windows

    Microsoft · 2026 · official_doc

  4. 4

    Find your BitLocker recovery key

    Microsoft · 2026 · official_doc

  5. 5

    Bug Check 0x4E PFN_LIST_CORRUPT

    Microsoft · 2026 · official_doc

Sources: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors · Solución de problemas de reinicios inesperados y errores de código de detención de Windows · Find your BitLocker recovery key · Bug Check 0x4E PFN_LIST_CORRUPTreviewed 2026-10-04 · verified

Was this entry useful?