Fixes / Windows · Checked September 30, 2026

Windows PAGE_FAULT_IN_NONPAGED_AREA: what it means and how to fix it

Short answer

PAGE_FAULT_IN_NONPAGED_AREA (bug check 0x50) means Windows or a driver tried to read memory that doesn't exist or was already freed, so Windows stopped to protect your data. The most likely cause is a faulty or recently updated driver, or antivirus. Check the "What failed" file name on the crash screen, then roll back or update that driver. If that doesn't help, test your RAM.

What this message means

Windows keeps some of its most important data in "nonpaged" memory, which has to stay in physical RAM at all times. This stop code (bug check 0x00000050) appears when code running at the core of Windows, usually a driver, reads or writes a memory address that is invalid or has already been freed. Windows can't safely recover from that, so it stops, saves a crash dump and restarts. Microsoft lists four main causes: a faulty driver or system service, antivirus software, a corrupted NTFS disk volume, and failing hardware (most often RAM). On Windows 11 version 24H2 and later the same error appears on a black screen instead of a blue one.

Common causes

Cause	How to tell
A faulty, outdated or recently updated driver	The crash screen shows a "What failed:" line with a .sys file (for example nvlddmkm.sys for NVIDIA graphics, or a network, storage or webcam driver). The crashes started after a driver update, a Windows update or new software.
Third-party antivirus or other security software with kernel drivers	The "What failed" file belongs to your antivirus, VPN or anti-cheat software, or the crashes started right after you installed or updated one of them.
Defective or unstable RAM, including memory overclocking (XMP/EXPO)	The crashes happen at random times under different workloads, the "What failed" file changes from crash to crash (or is ntoskrnl.exe), or you recently added RAM or turned on XMP/EXPO in the BIOS. Windows Memory Diagnostic reports errors.
Corrupted NTFS volume or a failing drive	The "What failed" file is ntfs.sys, chkdsk finds and fixes errors, the PC is slow to open files, or the drive's manufacturer tool reports health warnings.
Corrupted Windows system files	sfc /scannow reports that it found corrupt files, or the crashes began after an interrupted update or an unexpected shutdown.
Recently added or failing hardware	The error began right after you installed a new component (RAM, SSD, graphics card, USB device), or Device Manager shows a device with a yellow exclamation mark.

How to fix it

1. Undo the most recent change and deal with the file named on the crash screen

Write down the file shown next to "What failed:" on the crash screen. If you missed it, open Reliability Monitor (press Windows key + R, type perfmon /rel, press Enter) and click the red "Windows was not properly shut down" or hardware error entry for that day.
If you recently updated a driver, right-click Start, select Device Manager, right-click that device, choose Properties, open the Driver tab and click Roll Back Driver.
If the file belongs to antivirus, VPN or anti-cheat software, uninstall it from Settings > Apps > Installed apps (Windows 11) or Settings > Apps > Apps & features (Windows 10). Microsoft Defender turns on automatically.
If you just installed new hardware, shut down, remove it and restart.
Use the PC normally. If the crashes stop, check the vendor's website for a fixed version before reinstalling.

2. Install Windows updates and update drivers

Menu paths differ between Windows 11 and Windows 10

Windows 11: go to Start > Settings > Windows Update and select Check for updates. Windows 10: go to Start > Settings > Update & Security > Windows Update and select Check for updates.
Install everything offered, including items under Advanced options > Optional updates (driver updates).
Right-click Start, select Device Manager and look for any device with a yellow exclamation mark. Right-click it and choose Update driver, or uninstall it and restart.
Download the latest graphics, chipset and storage drivers from your PC maker's or the component maker's website (NVIDIA, AMD, Intel).

3. Repair system files and check the disk

Select Start, type cmd, right-click Command Prompt and choose Run as administrator.
Run: DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
Run: sfc /scannow and wait until it reaches 100%.
Run: chkdsk C: /f /r then type Y to schedule the scan and restart the PC. The scan runs before Windows loads and can take a long time on large drives.
If chkdsk keeps finding bad sectors, run your drive maker's diagnostic tool and back up your files, as the drive may be failing.

4. Test your RAM and turn off memory overclocking

Save your work, select Start, type Windows Memory Diagnostic, open it and choose Restart now and check for problems.
After Windows restarts, open Event Viewer, go to Windows Logs > System, and look for the MemoryDiagnostics-Results entry to see the result.
If you use XMP or EXPO in the BIOS/UEFI, disable it (or set memory to default/Auto) and test whether the crashes stop.
On a desktop, shut down, unplug, and reseat the RAM sticks. If you have more than one, test with one stick at a time to find a bad module.
For a more thorough check, run MemTest86 from a USB stick for at least one full pass. Replace any module that shows errors.

5. Reset the paging file to automatic

Press Windows key + R, type sysdm.cpl and press Enter.
On the Advanced tab, under Performance, select Settings.
Open the Advanced tab and under Virtual memory select Change.
Tick Automatically manage paging file size for all drives, select OK and restart.
Make sure the system drive has at least 10 to 15% free space.

6. If Windows crashes before you can sign in, use Safe Mode or recovery

Windows 11 and Windows 10

Force the PC off during startup twice in a row. On the third start Windows opens Automatic Repair. Select Advanced options.
Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode or 5 for Safe Mode with Networking.
In Safe Mode, roll back or uninstall the suspect driver or antivirus as in the first fix.
If Safe Mode doesn't help, return to Troubleshoot > Advanced options and choose System Restore (pick a point before the crashes began) or Uninstall Updates > Uninstall latest quality update.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the error continues after a clean driver setup, a passing memory test and a clean chkdsk, the fault is probably hardware: a RAM module that only fails under load, a failing SSD or a motherboard problem. Run the diagnostics built into your PC (most Dell, HP and Lenovo PCs have them on F12 or F2 at startup) and contact the maker if the PC is under warranty. If you want a definite answer, share the crash dump files from C:\Windows\Minidump on the Microsoft Q&A forum, or open them with WinDbg and run !analyze -v, which names the faulting module. As a last software step, Settings > System > Recovery > Reset this PC (Windows 11) or Settings > Update & Security > Recovery (Windows 10) reinstalls Windows and can keep your files.

Questions people ask

Does PAGE_FAULT_IN_NONPAGED_AREA mean my RAM is bad?

Not necessarily. Faulty drivers and antivirus software cause it at least as often. Run Windows Memory Diagnostic or MemTest86 to check. If the "What failed" file is the same driver every time, suspect that driver first.

Can a failing SSD or hard drive cause this error?

Yes. Microsoft lists a corrupted NTFS volume as a cause, and ntfs.sys often shows up as the failed file in those cases. Run chkdsk C: /f /r and the drive maker's health tool, and back up your data if errors keep appearing.

Is it a virus?

Rarely. The error is almost always caused by a driver, security software or hardware. A malware scan with Microsoft Defender is still worth running if you also notice other strange behavior.

Will this error damage my computer or delete files?

The crash itself doesn't damage hardware, but any unsaved work is lost and repeated sudden shutdowns can corrupt files. If the cause is a failing drive or RAM, back up your important files now.

Why did I get a black screen instead of a blue screen?

Starting with Windows 11 version 24H2, Microsoft shows stop errors on a black screen. The stop code means the same thing and the fixes are identical.

Sources

Related errors