
PAGE_FAULT_IN_NONPAGED_AREA means Windows tried to read memory that should always be available but could not access it. The usual causes are a bad driver, faulty RAM, or drive corruption affecting the data Windows reads.
This guide applies to Windows 10 and Windows 11 PCs showing the PAGE_FAULT_IN_NONPAGED_AREA stop code.
Does This Affect You?
Start with the driver if the blue screen names a .sys file. If it does not, test RAM and storage next. This stop code is specific enough that targeted checks usually beat reinstalling Windows immediately.
Update or Roll Back the Named Driver
- Write down any
.sysfile shown on the blue screen. For example, NVIDIA graphics and Qualcomm/Atheros Wi-Fi drivers often show recognizable file names. - Right-click Start and open Device Manager.
- Find the matching hardware category, such as Display adapters, Network adapters, or Sound devices.
- Right-click the device, choose Properties, and open the Driver tab.
- Click Roll Back Driver if it is available and the crash began after an update.
- If rollback is not available, choose Update driver or install the newest driver from the device maker.
- Restart and see whether the blue screen returns.
If no driver name appeared, check Windows Update history for driver updates installed near the time crashes began.
Test RAM for Errors
- Search for Windows Memory Diagnostic and open it.
- Choose Restart now and check for problems. Save your work first.
- Let the test run during startup.
- After Windows starts again, check the notification or Event Viewer under Windows Logs > System for MemoryDiagnostics-Results.
If errors appear, reseat or replace RAM. If new RAM was recently installed, remove it temporarily and test with the original memory.
Check the Drive and Repair Windows Files
- Open Command Prompt as administrator.
- Run
chkdsk C: /f /r. When Windows asks to schedule the scan, type Y and restart. - After the disk check finishes and Windows loads, open administrator Command Prompt again.
- Run
sfc /scannow. - If SFC cannot fix everything, run
DISM /Online /Cleanup-Image /RestoreHealth, then run SFC again.
If It Still Crashes
Inspect Minidumps
Crash dumps under C:WindowsMinidump can reveal the responsible driver even when the blue screen does not. Tools such as WhoCrashed or BlueScreenView can summarize them.
Check Temperatures
If crashes happen during gaming or heavy workloads, check CPU and GPU temperatures and clean blocked vents or fans. Heat can trigger memory-looking failures under load.
Reset Windows Last
When drivers, RAM, disk checks, and system-file repairs do not solve it, back up your files and use Reset this PC with Keep my files to clear deeper software conflicts.
Sources
- Microsoft Learn: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA
- Microsoft Support: Troubleshoot blue screen errors
- Microsoft Support: Windows Memory Diagnostic
