PAGE_FAULT_IN_NONPAGED_AREA (0x50): A Driver Read Memory That Wasn't There
In plain English
The PAGE_FAULT_IN_NONPAGED_AREA stop code, usually shown with 0x50, means Windows tried to read memory that should always be available, but the read failed. If you want the bigger picture on crashes like this, see blue and black screen stop codes in plain English.
First safe step
If Windows still starts, disconnect any newly added device and undo the most recent driver change first, before you assume the RAM is bad.
Drivers first, RAM second. Do not swap that order.
The PAGE_FAULT_IN_NONPAGED_AREA stop code, usually shown with 0x50, means Windows tried to read memory that should always be available, but the read failed. If you want the bigger picture on crashes like this, see blue and black screen stop codes in plain English.
In real life, 0x50 is often a driver problem first, not a mystery memory failure. A bad display, storage, antivirus, VPN, or device driver can point Windows to the wrong place and trigger this crash. If the blue screen names a file or a device, start there before you assume the RAM is bad.
This page follows that order. First, check the driver that changed or the file the crash points to. If the pattern looks more like failing memory, use the RAM route later, through the RAM test page if the crashes point to memory instead of a driver. If another crash screen keeps naming a driver file, you may also want the stop code page that often names the bad driver file.
What 0x50 means and why this page starts with drivers
PAGE_FAULT_IN_NONPAGED_AREA with 0x50 means Windows tried to use a part of memory that should always be available, and the read failed. In plain English, something asked for memory that should have been there, but it was missing, damaged, or pointed to the wrong place.
The two main causes are a bad driver and failing RAM. This page starts with drivers because they are often the faster thing to check, especially if the blue screen started after a new graphics, storage, antivirus, VPN, or device driver. A related pattern appears on the page for the other common driver crash, and some crashes are closer to the stop code page that often names the bad driver file.
Before you change anything, note the exact stop code, any file name shown on the blue screen, and what changed just before the crash. Think about a recent driver install, a Windows update, a new USB device, a dock, a new SSD tool, or security software that was just added or updated. If the first blue screen appeared right after Patch Tuesday or another update, see the first 30 minutes after an update crash.
If Windows still starts, your first safe step is to disconnect any newly added device and undo the most recent driver change first. If Windows will not stay up long enough to do that, use Safe Mode when Windows will not boot. If the pattern keeps looking more like memory than a driver, use the RAM test page if the crashes point to memory instead of a driver.
1 Check the driver first when the screen names a file or device Free
If the blue screen names a file ending in .sys, start there. A file like nvlddmkm.sys, rtwlane.sys, or a storage driver often points to the driver that made the bad memory read. This is also why the stop code page that often names the bad driver file can help if your crashes switch between codes.
Think about what changed right before PAGE_FAULT_IN_NONPAGED_AREA started. Common triggers are a new graphics driver, antivirus update, VPN software, SSD or chipset driver, docking station, USB adapter, external drive, or a device you just plugged in. If the crashes began right after Patch Tuesday or another update, check the first 30 minutes after an update crash before you make bigger changes.
Open Device Manager. Find the device that matches the named file or the thing you changed most recently. Right-click it, then try Properties and the driver tab. Use Roll Back Driver if the problem began after an update. If rollback is grayed out, try Update driver with the version from your PC maker or device maker, or choose Uninstall device and restart so Windows can reload it cleanly.
If Windows crashes too fast to do that normally, use Safe Mode when Windows will not boot and remove the suspect driver there. Pay extra attention to display, storage, network, and security software drivers, because they commonly cause this stop code and also the page for the other common driver crash. If no driver stands out after these checks, the next section helps you decide whether to use the RAM test page if the crashes point to memory instead of a driver.
2 Use Safe Mode to remove the bad driver cleanly Free
Safe Mode helps because Windows loads only the basics. If the PC crashes too fast to use normally, that stripped-down startup can stay stable long enough for you to remove the bad driver. If you cannot reach the desktop at all, use Safe Mode when Windows will not boot first, then come back here.
- Once you are in Safe Mode, open
Device Manager. Find the device you already suspect, open its properties, and tryRoll Back Driverfirst if that button is available. If it is not, choose uninstall for the device driver, restart, and let Windows load with the basic driver so you can install a cleaner version later. - If the driver came with third-party hardware software, remove that too before you restart. That includes graphics control suites, VPN apps, antivirus packages, docking software, audio tools, and device utilities that install their own
.sysfiles. UseControl PanelorSettingsto uninstall the related software, then disconnect the device for one test boot if it is easy to remove. - After the restart, use the PC for a bit before reinstalling anything. If a different stop code appears and it starts naming driver files more clearly, check the stop code page that often names the bad driver file or the page for the other common driver crash. If Safe Mode still crashes, or the pattern starts looking random instead of driver-linked, go to the RAM test page if the crashes point to memory instead of a driver.
✓ Crashes gone? You can stop here.
3 When to suspect RAM instead of a driver
Start thinking about RAM when the crashes look random instead of tied to one driver or device. You may see 0x50 in different places, during startup one time, in a browser the next time, then while the PC is idle. If removing or rolling back the likely driver does not change the pattern, hardware memory moves higher on the list.
Another clue is that the PC gets worse over time. A crash that began once every few days can turn into several blue screens in one afternoon. You may also see different stop codes mixed in with PAGE_FAULT_IN_NONPAGED_AREA, especially driver-looking crashes that do not stay tied to one file. In that case, check the RAM test page if the crashes point to memory instead of a driver.
This page is only the routing point for that memory path. The full test order, what to run, and how to read the results are kept on the MEMORY_MANAGEMENT page so the instructions stay in one place. If your crashes more often name a specific driver file instead, compare that pattern with the stop code page that often names the bad driver file.
4 If the crash keeps coming back, check recent changes and system files Free
If PAGE_FAULT_IN_NONPAGED_AREA keeps returning after you rolled back or removed the most likely driver, stop and review what changed right before the first crash. Check for a Windows update, a new USB device, dock, external drive, antivirus app, VPN app, BIOS change, or memory setting change in firmware. If the timing matches an update, start with the first 30 minutes after an update crash.
If Windows stays up long enough, run two simple repair checks from an elevated Command Prompt. First run SFC with sfc /scannow. Then run DISM with DISM /Online /Cleanup-Image /RestoreHealth. These checks can fix damaged system files, but they will not usually fix a bad third-party driver by themselves.
Also undo any recent BIOS or UEFI changes if you made them just before the crashes. Turn off new overclock, XMP, EXPO, or memory-tuning changes for one test. If the blue screen starts naming different files, or shifts toward a pattern where one driver file is called out, compare that pattern with the stop code page that often names the bad driver file or the page for the other common driver crash.
If none of those recent-change checks explain it, and 0x50 still appears after a clean driver rollback, the case for bad memory gets stronger. At that point, use the RAM test page if the crashes point to memory instead of a driver, rather than staying stuck in driver cleanup.
What to do next if 0x50 still appears
If PAGE_FAULT_IN_NONPAGED_AREA keeps coming back after a driver rollback or removal, stop guessing and follow the same order: driver first, then the RAM test page if the crashes point to memory instead of a driver. Start with the page for the other common driver crash if the blue screen keeps naming a file or device, or with the stop code page that often names the bad driver file when a specific .sys file shows up.
If the PC will not stay up long enough to work, or the crashes happen before Windows loads, contact the PC maker or a repair shop. That is the point where a clean driver fix or a memory test is no longer a quick home repair.
For the full stop-code map, go back to the blue and black screen stop codes in plain English page. If the pattern looks like a driver crash, the next most useful pages are the page for the other common driver crash and the stop code page that often names the bad driver file.
If the crashes keep pointing away from one bad driver and toward memory, use the the RAM test page if the crashes point to memory instead of a driver page for the next step.
Frequently asked questions
Can failing RAM make it look like a driver caused 0x50?
Yes. Bad memory can corrupt data a good driver is using, so a named driver file is a clue, not proof. If crashes stay random after that driver is removed, treat memory as the suspect.
Will reinstalling Windows fix PAGE_FAULT_IN_NONPAGED_AREA?
It is not a good first step. A reinstall can bring the same bad driver back, and it cannot fix failing RAM. Try the driver fix first, then test memory if the pattern points that way.
Can 0x50 damage my files?
The main risk is losing work that was open and unsaved when the crash hit. When the PC stays on long enough, save copies of important files before you do more testing.
The short version
If 0x50 has stopped, treat the last driver you removed or rolled back as the likely cause and leave that setup alone for a few normal days of use before you add anything back. One change at a time makes the next crash, if there is one, easier to read.
If it returns with no clear driver named, stop guessing at drivers and follow the memory path from there. A pattern you can describe, when it happens, what changed, and what file was named, is also the best help you can give a repair shop if the PC will not stay on.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.