Windows stopped with a PFN_LIST_CORRUPT bug check because the page frame number list became corrupted. This usually points to memory-management corruption caused by a buggy driver, repeated page-lock misuse, DMA-related corruption, or failing RAM.
A driver corrupted the PFN list or unlocked pages incorrectly, damaging Windows memory-management structures.
Faulty RAM or unstable memory settings caused memory corruption in kernel-managed page structures.
A DMA-capable device or controller wrote invalid data into memory.
A broader low-level memory corruption issue exists in the system, often tied to drivers, firmware, or hardware instability.
How to fix it
Test memory stability first, including disabling memory overclocks or XMP/EXPO profiles and running an extended memory test.
Roll back or update recently installed drivers, especially storage, GPU, antivirus, virtualization, and device-management drivers that interact heavily with kernel memory.
If the issue started after adding hardware, remove or isolate that device and retest. DMA-capable devices and their drivers are common suspects.
Check for BIOS or chipset firmware updates if the problem appears after a platform change or new CPU/RAM combination.
Use crash dumps and driver analysis if available to identify repeated driver involvement around the PFN corruption path.
If crashes persist across clean driver states, suspect defective RAM or motherboard-level memory instability.
