A sudden blue screen crash displaying the stop code: ‘PFN_LIST_CORRUPT’ or bug check code 0x0000004E forces Windows 11 to restart abruptly during active workloads. In Windows memory architecture, the Page Frame Number (PFN) list is a vital kernel database that indexes and tracks every physical page of RAM in your system (marking pages as active, standby, modified, or free). When a device driver passes an invalid memory descriptor or physical memory hardware corrupts PFN list pointers, the Windows kernel halts immediately to prevent widespread data corruption.
What Causes PFN_LIST_CORRUPT in Windows 11?
Bug check 0x0000004E indicates corruption within the core memory page frame database. Common causes include:
- Defective Hardware RAM Modules: Physical memory bit-flips or bad capacitors corrupting PFN pointers in physical RAM.
- Unstable Memory Overclocking Profiles: Aggressive XMP, EXPO, or manual memory timings failing under thermal load.
- Faulty Storage & Chipset Drivers: Corrupted SATA, NVMe, or chipset drivers improperly freeing memory page references.
- Corrupted Windows Virtual Memory Paging File: Bad sectors or corruption within
pagefile.sys. - Antivirus Kernel Hook Collisions: Low-level third-party security filters corrupting page state transitions.
Step 1: Check Parameter 1 in Event Viewer
The first bugcheck parameter reveals the exact nature of the PFN database violation.
- Press Win + X and open Event Viewer.
- Navigate to Windows Logs > System and locate the latest BugCheck (Event ID 1001) event.
- Check Parameter 1:
0x00000001/0x00000002: Corrupted list header detected (indicates physical RAM defects or driver corruption).0x00000099: Page frame was freed while still in use.0x00000007: Memory page share count became corrupted.
- Parameter 2 contains the Page Frame Number that was corrupted.
Step 2: Test RAM with Windows Memory Diagnostic
Physical memory defects account for the majority of PFN_LIST_CORRUPT errors.
- Press Win + R, type
mdsched.exe, and press Enter. - Click Restart now and check for problems (recommended).
- Allow the extended memory test to complete both passes.
- If errors are reported, shut down your PC, remove one RAM module, and test each stick independently to identify the failing hardware.
Step 3: Disable XMP / EXPO Memory Overclocking
Aggressive factory overclocking profiles frequently cause memory timing desynchronisation.
- Reboot your computer and enter UEFI BIOS (press Del or F2).
- Navigate to the Overclocking / Memory menu.
- Set XMP, DOCP, or EXPO to Disabled / Auto.
- Run memory at standard JEDEC frequencies (e.g. 2133/2400/4800 MHz depending on DDR4/DDR5 standard).
- Save changes and reboot into Windows.
Step 4: Recreate the Windows Paging File
Purging corrupted pagefile blocks resolves virtual memory page indexing errors.
- Press Win + R, type
sysdm.cpl, and press Enter. - Go to Advanced > Performance > Settings > Advanced tab.
- Under Virtual memory, click Change.
- Uncheck Automatically manage paging file size for all drives.
- Select your C: drive, choose No paging file, click Set, and restart Windows.
- After rebooting, return to the menu and check Automatically manage paging file size for all drives to build a fresh, uncorrupted pagefile.
Step 5: Run DISM and SFC Kernel Integrity Scans
Restoring corrupted Windows system files ensures core kernel memory management binaries are intact.
- Open Command Prompt (Admin).
- Execute:
DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow - Restart your computer.
Testing physical RAM, disabling unstable memory overclocks, rebuilding the paging file, and running DISM repairs permanently resolves PFN_LIST_CORRUPT in Windows 11.