Blue screen: PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)
The kernel or a driver accessed memory that wasn’t there — faulty drivers, antivirus, RAM or disk issues.
Seen on:
Windows
Meaning
Stop 0x50 usually names the faulting driver in the minidump (e.g. ntfs.sys, a GPU driver, an antivirus .sys). Recent driver updates, overclocking or failing RAM are common.
Common causes
- Faulty or incompatible driver (often recently updated)
- Antivirus/filter drivers
- Defective RAM or unstable overclock
- Disk/file system corruption
⚡ Quick fix
- Boot to Safe Mode and roll back the recent driver
- Analyse the minidump with WinDbg (!analyze -v)
- Run Memory Diagnostic and chkdsk
Detailed fix by platform
Windows
- powershell
# minidumps: C:\Windows\Minidump mdsched.exe chkdsk C: /scan
How to diagnose
- Dump — Faulting module in the dump
- Changes — New drivers/software?
- Hardware — RAM test, XMP/overclock off
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Windows
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026