PAGE_FAULT_IN_NONPAGED_AREA — BSOD Memory and Driver Crash on Windows
Criticalbsod
Overview
Fix Windows BSOD PAGE_FAULT_IN_NONPAGED_AREA caused by faulty RAM, driver bugs, corrupted page files, or incompatible hardware accessing invalid memory.
Key Details
- PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) occurs when Windows references invalid memory that should always be in RAM
- The nonpaged pool is memory that cannot be swapped to disk — it must always be available
- A driver or system service is attempting to access memory at an address that does not exist or is corrupted
- The BSOD typically shows the faulting driver name (e.g., ntfs.sys, win32k.sys, or a third-party driver)
- This error can be caused by both software (drivers) and hardware (RAM) issues
Common Causes
- Faulty RAM module causing random memory corruption
- Buggy driver accessing deallocated or invalid memory addresses
- Corrupted page file (pagefile.sys) on disk
- Recently installed hardware or driver incompatible with the system
Steps
- 1Note the driver name shown on the BSOD (e.g., xxx.sys) — this identifies the faulting component
- 2Run Windows Memory Diagnostic: search 'Windows Memory Diagnostic' > Restart now and check for problems
- 3If a specific driver is named: update or roll back that driver via Device Manager
- 4Delete and recreate the page file: System Properties > Advanced > Performance Settings > Advanced > Virtual Memory > No paging file > restart > re-enable
- 5Run memtest86+ from a USB boot drive for thorough RAM testing (minimum 2 passes, ideally overnight)
Tags
bsodpage-faultnonpaged-areamemorydriver
Related Items
More in Bsod
windows-0000000A-irql-not-less-or-equalWindows Error 0x0000000A — IRQL NOT LESS OR EQUAL
Criticalwindows-00000050-page-fault-in-nonpaged-areaWindows Error 0x00000050 — PAGE FAULT IN NONPAGED AREA
Criticalwindows-0000007E-system-thread-exception-not-handledWindows Error 0x0000007E — SYSTEM THREAD EXCEPTION NOT HANDLED
Criticalwindows-0000007A-kernel-data-inpage-errorWindows Error 0x0000007A — KERNEL DATA INPAGE ERROR
Criticalwindows-000000EF-critical-process-diedWindows Error 0x000000EF — CRITICAL PROCESS DIED
Criticalwindows-00000133-dpc-watchdog-violationWindows Error 0x00000133 — DPC WATCHDOG VIOLATION
CriticalFrequently Asked Questions
Run memtest86+ from a bootable USB overnight. Any errors indicate faulty RAM. Also try removing one RAM stick at a time and running the system to identify the failing module.