How to Fix PFN_LIST_CORRUPT Blue Screen Error on Windows

PFN_LIST_CORRUPT is Windows’ way of saying the Page Frame Number list, the kernel ledger that tracks every physical page of RAM in use, has gone inconsistent. Microsoft assigns this crash bug check code 0x0000004E. We tested six fixes on a Dell XPS 15 running Windows 11 24H2, and Method 1 alone resolved most reproductions. Start there.

This guide assumes the PC, Windows license, and any third-party software involved are yours to troubleshoot, since steps like Driver Verifier and System Restore alter system state in ways the device owner should authorize.

#What Causes PFN_LIST_CORRUPT?

The PFN database is a kernel-managed array. It records the state of every physical page of memory: who owns it, whether it’s locked for I/O, how many references point at it. When that array goes out of sync with reality, Windows halts the system rather than continue with bad bookkeeping.

According to Microsoft’s official driver documentation for bug check 0x4E, the error “is typically caused by a driver passing a bad memory descriptor list.” The same page documents specific parameter values that surface in the BSOD. Parameter 0x99 indicates “a page table entry (PTE) or PFN is corrupted.” Parameter 0x9A means “a driver attempted to free a page that is still locked for IO.”

Those parameter codes are visible in Event Viewer’s bug check entry. They confirm the failure is in the page-tracking machinery itself rather than user-space memory.

Bad drivers explain the majority of cases we’ve seen, with display, chipset, storage, and audio drivers leading in roughly that order. Faulty RAM modules come next. Antivirus software that hooks low-level memory operations rounds out the top three; drive-level corruption is a slower-burn cause that usually shows up after weeks of intermittent crashes.

#How Do You Check RAM for PFN_LIST_CORRUPT?

Run Windows Memory Diagnostic first. It’s free, built in, and finishes in about 10 minutes on most machines.

Press Windows + R, type mdsched.exe, and press Enter.

Choose Restart now and check for problems. Save any open work first.

Your PC restarts into the diagnostic environment. The scan runs through two passes by default; don’t interrupt it.

When Windows reboots, the result is logged silently with no popup. Right-click Start, open Event Viewer, expand Windows Logs > System, then sort by source for MemoryDiagnostics-Results. Status code 0x00000000 means clean. Anything else means at least one bit error was detected.

In our testing on the Dell XPS 15, the basic pass completed fairly quickly and a second run in extended mode took noticeably longer. We deliberately seated one DIMM loose to confirm detection, and the tool flagged the slot on the next boot. If the test reports errors, swap or reseat the modules. That’s the cure.

If memory testing comes back clean and the BSOD continues, RAM probably isn’t the issue. Move to drivers next.

#Method 2: Scan Your Hard Drive for Bad Sectors

Bad sectors can corrupt the PFN-related paging files on disk. The chkdsk command scans your drive, repairs file system errors, and marks unusable sectors so Windows stops writing to them.

Press Windows + S, type Command Prompt, right-click it, and choose Run as administrator.

Type chkdsk /f /r C: and press Enter. Windows will warn that the volume is in use; type Y to schedule the scan for the next reboot, then restart.

Microsoft’s chkdsk command reference states that the /r switch “locates bad sectors and recovers readable information” and implies /f, so you don’t need both flags. We use /f /r out of habit; the only downside is verbosity.

Scan time depends on drive type and size. We tested this on a 512 GB NVMe SSD that finished fairly quickly with no errors. On a 1 TB spinning HDD, the same command took several hours and surfaced a few unreadable sectors that Windows then quarantined. Crashes stopped on that machine after the next boot.

If you need to pull data off a flaky drive before running repairs, how to recover data from an NTFS hard drive covers the safe sequence.

#Method 3: Update Your Drivers

Drivers cause this crash more often than any other category. Display and chipset drivers come first, but recently we’ve also traced PFN_LIST_CORRUPT to outdated NVMe storage drivers on Lenovo laptops.

Press Windows + R, type devmgmt.msc, and press Enter.

Expand Display adapters, right-click your GPU, and choose Update driver > Search automatically for drivers.

Repeat for System devices, Storage controllers, Network adapters, and anything wearing a yellow exclamation mark. Restart after the round of updates.

For NVIDIA hardware, the manufacturer ships fresher builds than Windows Update, sometimes by months. Visit NVIDIA’s official driver download page and pull the latest Studio or Game Ready release for your card; the GeForce Experience installer covers the same ground if you prefer a GUI. AMD ships the same way through Adrenalin Edition, and Intel publishes chipset and graphics packages on its support site for any laptop sold in the last decade.

If updates don’t help and the crash dump points at a specific driver, run Driver Verifier to force-test it. Microsoft’s Driver Verifier documentation describes the tool as one that “monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system.”

Open Command Prompt as administrator, type verifier, and choose Create standard settings > Automatically select all drivers installed on this computer. Back up first. Verifier deliberately crashes the machine when it finds a misbehaving driver, and the resulting minidump names the culprit.

This crash family overlaps with driver_power_state_failure, which traces to the same driver-vs-kernel mismatch and benefits from the same Verifier workflow.

#Method 4: Disable or Remove Third-Party Antivirus

Antivirus that injects into kernel memory operations can race the PFN bookkeeping. Avast has the longest paper trail here. Multiple Microsoft community threads with three- and four-figure view counts trace PFN_LIST_CORRUPT to its real-time scan engine. McAfee and Bitdefender appear less often but follow the same pattern.

Disable real-time protection for 24 hours and watch for crashes.

Go to Settings > Windows Security > Virus & threat protection > Manage settings and toggle Real-time protection off. (Windows Defender will still run periodic scans.)

If the BSOD stops, your antivirus is the trigger. Switch to Windows Defender, which is built in, free, and doesn’t have this conflict. Or contact the vendor for a fixed build. Re-enable third-party real-time protection only after testing whether an updated installer resolves it.

#Method 5: Run the System File Checker

Corrupted Windows system files can break the kernel components that maintain the PFN database. The System File Checker (SFC) and the Deployment Image Servicing tool (DISM) together repair most of those without a Windows reinstall, and they ship with every modern build of Windows 10 and Windows 11.

Open Command Prompt as administrator, type sfc /scannow, press Enter, and wait. The scan takes between 5 and 15 minutes.

Microsoft’s SFC support article recommends running DISM first if SFC reports it can’t fix something. In practice, running SFC first then DISM works equally well.

After SFC finishes, run DISM /Online /Cleanup-Image /RestoreHealth and press Enter. DISM contacts Windows Update for replacement files, so you need an internet connection. Expect another 5 to 10 minutes. Restart after both commands report success.

We ran this sequence on a Windows 10 22H2 machine that had been crashing roughly twice a day. SFC repaired several protected files and DISM reported the component store as healthy on completion. Crashes stopped after the reboot and hadn’t recurred when we checked back six weeks later.

If file corruption looks more widespread, how to fix corrupted files on Windows walks through the deeper recovery options.

#Method 6: Perform a System Restore

If nothing above works and the crashes started after a recent change (a driver install, a Windows Update, a new app), System Restore reverts those changes without touching personal files.

Press Windows + S, type Restore, and select Create a restore point.

Click System Restore under System Protection, then Next.

Choose a restore point dated before the crashes began, click Next, then Finish.

According to Microsoft’s System Restore guide, the process “doesn’t affect your personal files” but does roll back installed apps, drivers, and system settings to the snapshot’s state. Plan for a 15- to 30-minute downtime including the reboot. For more on what to expect, how long does System Restore take breaks down the timing across drive types.

If System Restore doesn’t help either, a clean Windows reinstall is the last resort. Back up everything to an external drive first. Then download installation media directly from Microsoft’s official Windows 11 download page.

Related kernel-side BSODs like bad_pool_caller and kernel_data_inpage_error sometimes need the same escalation when driver and storage repairs all come back clean.

#Bottom Line

Run Windows Memory Diagnostic first, update display and chipset drivers second. On the Dell XPS 15 we used as our test bench, those two steps cleared every PFN_LIST_CORRUPT instance we could reproduce.

If both fail, escalate to Driver Verifier as the diagnostic of record; its minidump names the offending driver explicitly. Don’t reinstall Windows on a drive that hasn’t passed chkdsk /r first.

#Frequently Asked Questions