Fix PAGE_FAULT_IN_NONPAGED_AREA on Windows 11
Short answer: PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) means Windows needed data from memory that should always be resident and it was not there — a bad RAM cell, a driver writing garbage, or a corrupted page file. If the blue screen names a .sys file, update or roll back that driver; if it only says ntoskrnl.exe, test your RAM with MemTest86 and reset the page file to system-managed.
The system needed data from a chunk of memory that’s supposed to always be resident — nonpaged pool, the stuff Windows never swaps to disk because it needs instant access — and the data wasn’t there. Either the RAM cell holding it went bad, or a driver wrote garbage over it, or the page file on disk is corrupted. Stop code 0x00000050. The blue screen sometimes names a .sys file, sometimes just says ntoskrnl.exe which isn’t helpful by itself.
Check Event Viewer first. Win+X, Event Viewer, Windows Logs, System. Look for the BugCheck entry — the second parameter tells you the memory address that faulted, the fourth tells you whether it was a read (0) or write (1) operation. A write fault usually points at a driver actively corrupting memory. A read fault could be bad RAM, bad page file, or a driver trying to read from memory it already freed.
When It Names a Driver
If the blue screen or Event Viewer shows a specific .sys file, that’s your starting point. The ones I see most often with this particular stop code: win32kfull.sys (display subsystem, usually an outdated GPU driver), ntfs.sys (filesystem driver — usually means a failing drive rather than a driver bug), and ndis.sys or various network adapter .sys files.
A customer’s Surface Pro 9 was crashing every couple hours with PAGE_FAULT naming win32kfull.sys. She was on the November 2025 Intel Iris Xe driver that Windows Update had pushed. Rolled back to the October version through Device Manager and it stopped. Microsoft pushed that same bad driver to thousands of Surface devices before pulling it three weeks later.
For any driver-specific crash, the sequence is the same: Safe Mode, roll back or uninstall the driver, restart, install a known-good version from the manufacturer’s website. If it’s the GPU driver, DDU clean install is the proper method — just updating on top of a corrupted driver installation doesn’t always clear the problem.
When It Doesn’t Name Anything
No .sys file, or just ntoskrnl.exe — suspect RAM or page file. If your blue screen says MEMORY_MANAGEMENT instead of PAGE_FAULT, same diagnostic — different stop code, overlapping causes.
The page file is the easy one to rule out. This is the file Windows uses as overflow when physical RAM fills up. If it’s on a dying sector of the drive, any attempt to swap data in or out of it hits a read error and you get PAGE_FAULT. Open System Properties (Win+R, sysdm.cpl), Advanced tab, Performance Settings, Advanced tab, Virtual Memory Change. Uncheck “Automatically manage,” set it to System managed for your C: drive specifically, click Set, restart. This forces Windows to rebuild the page file from scratch. If the crash was a corrupted page file, this fixes it.
If that doesn’t help, or if the crashes happen when you’re not even close to using all your RAM, suspect the physical memory. Same story as every other memory-related blue screen — MemTest86 from a USB boot, overnight, minimum four passes. Windows Memory Diagnostic catches maybe 30% of what MemTest86 finds. Had a machine that only crashed when ambient temperature was high — summer afternoons specifically. One RAM stick had a marginal cell that worked fine cool but failed when the inside of the case warmed up. MemTest86 didn’t catch it until I ran it with the case side panel on and the room at 28°C. Weird, but memory faults don’t always show up under ideal test conditions.
If MemTest86 comes back clean and the page file rebuild didn’t help, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin Command Prompt. Corrupted system files in the nonpaged pool area cause the same crash pattern. Our SFC guide covers what to do when those commands find but can’t fix problems.
This stop code is one of the harder ones to nail down because it sits at the intersection of RAM, storage, and drivers. If you’ve been chasing it for more than a couple hours, send us your crash dump files — they’re in C:\Windows\Minidump and they contain the exact faulting address and call stack that pinpoints the cause.
Frequently Asked Questions
What causes PAGE_FAULT_IN_NONPAGED_AREA?
Windows tried to read data from memory that's supposed to always be resident — the nonpaged pool — and the data wasn't there. Three possible causes: a RAM cell went bad and lost the data, a driver overwrote that memory area with garbage, or the page file on your drive is corrupted. The stop code is 0x00000050.
The crash names ntfs.sys — is my hard drive dying?
Possibly. When ntfs.sys shows up in a PAGE_FAULT crash, it usually means the filesystem driver hit a bad sector while trying to read data it expected to find. Run CrystalDiskInfo to check your drive's SMART status. If it shows Caution or Bad, back up everything immediately. The drive is failing and no software fix will save it.
Can a corrupted page file cause this blue screen?
Yes. The page file is where Windows stores overflow data when physical RAM fills up. If the page file sits on a bad sector or gets corrupted, any swap operation can trigger a PAGE_FAULT. Fix: open System Properties, Advanced tab, Performance Settings, Advanced, Virtual Memory, uncheck Automatically manage, set to System managed, restart. This forces Windows to rebuild it from scratch.
My RAM passed Windows Memory Diagnostic — could it still be bad?
Absolutely. Windows Memory Diagnostic runs two quick passes with basic test patterns and catches maybe 30% of actual faults. MemTest86 from a USB boot runs dozens of pattern types across multiple passes and catches failures that only show up under extended testing, especially on DDR5 modules.