PAGE_FAULT_IN_NONPAGED_AREA — BSOD Memory and Driver Crash on Windows
About PAGE_FAULT_IN_NONPAGED_AREA
Fix Windows BSOD PAGE_FAULT_IN_NONPAGED_AREA caused by faulty RAM, driver bugs, corrupted page files, or incompatible hardware accessing invalid memory. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: 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. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Note the driver name shown on the BSOD (e.g., xxx.sys) — this identifies the faulting component. Run Windows Memory Diagnostic: search 'Windows Memory Diagnostic' > Restart now and check for problems. If a specific driver is named: update or roll back that driver via Device Manager. Delete and recreate the page file: System Properties > Advanced > Performance Settings > Advanced > Virtual Memory > No paging file > restart > re-enable. Run memtest86+ from a USB boot drive for thorough RAM testing (minimum 2 passes, ideally overnight). If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
How do I know if my RAM is faulty?
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.
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)