How to Fix PFN_LIST_CORRUPT in Windows 11

•
Ankit Kumar
Windows 11BSODTroubleshootingFixHardware

The Problem

PFN_LIST_CORRUPT (stop code 0x0000004E) means the Page Frame Number list was found in an invalid state. That list is Windows' master index of every page of physical memory — which pages are in use, which are free, and who owns them. If the index is wrong, Windows cannot safely allocate or free another byte, so it stops instantly.

Two things damage it: failing memory hardware, or a driver writing outside the memory it was given. Of the two, memory is the more common answer for this particular code, which is why the order below starts with RAM instead of drivers. That is the opposite of most blue screen guides, and it is deliberate.

Getting BAD_POOL_HEADER or MEMORY_MANAGEMENT as well? Same family of causes — see fix BAD_POOL_HEADER and fix MEMORY_MANAGEMENT BSOD.

Symptoms

  • Blue screen reading PFN_LIST_CORRUPT, with no consistent trigger.
  • Crashes increase when memory pressure is high — many browser tabs, a large game, a video export, a big file copy.
  • Started after adding RAM, enabling XMP/EXPO, or moving the PC.
  • Occasional file corruption or apps closing without warning between crashes.

Step 1: Test the RAM Before Anything Else

  1. Windows + R → mdsched.exe → Restart now and check for problems.
  2. Press F1 during the test, set Test Mix to Extended, and let it run to completion.
  3. Then run the real test: create a MemTest86 USB stick and run at least four full passes. The built-in Windows tool routinely misses faults MemTest86 catches within one pass.
  4. A single error is enough — marginal RAM does not get better.
  5. Background: check and upgrade your RAM and how much RAM do I need.

Step 2: Reseat and Isolate the Memory

  1. Shut down, unplug the PC, and hold the power button for five seconds to discharge.
  2. Remove each stick, check the contacts are clean, and reseat until both clips click.
  3. If you have two or more sticks, run with one stick at a time in the slot nearest the CPU, and test each for a day.
  4. Consult the motherboard manual for the correct slots — populating the wrong pair is a common cause of instability in a two-stick kit.
  5. Mixed kits bought at different times often will not run together at rated speed even when each is individually fine.

Step 3: Turn Off XMP / EXPO and Test at Stock

An enabled memory profile is an overclock, whatever the box calls it — and an unstable one corrupts memory structures exactly like a failing stick.

  1. Enter firmware setup: how to enter BIOS or UEFI.
  2. Choose Load Optimized Defaults, then confirm XMP / EXPO is Disabled.
  3. Save, exit, and use the PC hard for a day or two.
  4. Stable at stock? The profile or the memory controller is the problem. Re-enable XMP but drop the frequency one step, or raise the memory controller voltage slightly per your board's guidance.
  5. Update the motherboard BIOS while you are here — memory compatibility fixes ship in firmware updates.

Step 4: Update Storage and Graphics Drivers

The PFN list is heavily exercised by paging, so storage drivers are the most likely software cause.

  1. Right-click Start → Device Manager → expand Disk drives and Storage controllers.
  2. Install the chipset and storage (RST / NVMe) drivers from your motherboard or laptop vendor's support page — not from Windows Update, which often has a generic version.
  3. Update the SSD firmware from the manufacturer's toolbox (Samsung Magician, Crucial Storage Executive, WD Dashboard, etc.).
  4. Do graphics separately and cleanly: clean install GPU drivers with DDU.
  5. General method: how to update outdated drivers.

Step 5: Check the Drive and the Page File

  1. Right-click Start → Terminal (Admin) and run: 
    chkdsk C: /f /r
  2. Press Y to schedule at next boot, then restart and let it finish.
  3. Check drive health readings: check SSD and hard drive health.
  4. Rebuild the page file: Windows + R → sysdm.cpl → Advanced → Performance → Settings → Advanced → Change. Untick Automatically manage, select No paging file, reboot, then set it back to System managed size and reboot again.
  5. Never place the page file on a failing drive — if the disk is the suspect, fix that first.

Step 6: Repair Windows System Files

  1. In Terminal (Admin): 
    sfc /scannow
  2. Then: 
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Reboot and repeat sfc /scannow.
  4. Full guide: how to run SFC and DISM.

Step 7: Name the Driver With Driver Verifier

Only once memory has tested clean. This deliberately makes the PC crash more while it runs, so have backups and know how to reach Safe Mode first.

  1. Windows + R → verifier → Create custom settings (for code developers).
  2. Tick Standard settings plus Special pool, then choose Select driver names from a list and select only non-Microsoft drivers.
  3. Reboot and use the PC. The next crash should name a .sys file — that is your target.
  4. Turn it off immediately afterwards: 
    verifier /reset

Step 8: Remove Kernel-Level Third-Party Software

  1. Uninstall any third-party antivirus, then run the vendor's official removal tool to clear its filter drivers. Defender takes over on its own: fix Windows Defender not working.
  2. Remove disk-imaging, virtual-drive, RGB, and fan-control utilities that install kernel drivers.
  3. Turn off fast startup so each boot initialises memory cleanly: Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → untick Turn on fast startup.
  4. If crashes began after an update, roll it back: fix Windows 11 after a bad update.

What Not to Do

  • Don't skip straight to reinstalling Windows. If a RAM stick is failing, the clean install itself will often crash partway through.
  • Don't assume "the PC posts, so the RAM is fine". POST tests almost nothing.
  • Don't leave XMP enabled while troubleshooting. Testing at stock is how you separate hardware fault from unstable profile.
  • Don't ignore file corruption between crashes — that is the same memory damage reaching your data. Back up now.

Still Not Working?

If memory tests clean across four MemTest86 passes, the drive is healthy, drivers are current, and Driver Verifier names nothing, the memory controller inside the CPU or the motherboard slots are the remaining suspects. Test the sticks in another machine to separate the two. Protect your data first: set up automatic backups.

Related: fix IRQL_NOT_LESS_OR_EQUAL, fix WHEA_UNCORRECTABLE_ERROR, and how to fix a blue screen.

Related guides