How to Fix PAGE_FAULT_IN_NONPAGED_AREA

PAGE_FAULT_IN_NONPAGED_AREA is a Windows stop error with the bug-check value 0x00000050, and the most common cause is defective RAM, because Windows requested data that should have stayed in memory and could not be found. The error also follows a faulty driver, corrupt system files, and a conflicting antivirus that intercepts memory operations. This article explains what PAGE_FAULT_IN_NONPAGED_AREA means, names the common culprits, and gives the step-by-step fixes that resolve it.

Each fix names the exact Windows tool, including the Windows Memory Diagnostic, MemTest86, BlueScreenView, Device Manager, SFC, DISM, and the Fast Startup and pagefile settings. The fixes are ordered from the most common, such as testing and reseating RAM, to driver updates, system-file repair, and Fast Startup changes.

Apply the fixes in order and test stability after each one, because a single memory or driver fault usually accounts for this stop code. A diagnostic table near the end maps each cause to its confirmation method and first fix.

What Does PAGE_FAULT_IN_NONPAGED_AREA Mean?

PAGE_FAULT_IN_NONPAGED_AREA means Windows looked for data in the nonpaged area of memory, a region that must always stay resident, and the data was missing or invalid, so the kernel halted. The points below explain the common sources, ranked from most to least frequent.

• Defective RAM. Bad memory cells lose or alter the data that should be resident, which is the leading cause of this stop code.
• A faulty or outdated driver. A driver that references freed or invalid memory triggers the page fault in the nonpaged region.
• Corrupt system files. Damaged Windows components from a failed update or disk error cause invalid memory references.
• A conflicting antivirus. Third-party antivirus that hooks memory operations can reference an address that is no longer valid.
• A corrupt pagefile or failing disk. A damaged pagefile or bad sectors corrupt the data Windows pages in and out.

Test the RAM with Windows Memory Diagnostic and MemTest86

Testing memory is the first step for PAGE_FAULT_IN_NONPAGED_AREA, because defective RAM is the most common cause of this stop code. Windows includes a built-in tester, and MemTest86 catches intermittent faults the built-in tool misses.

1. Type Windows Memory Diagnostic in Windows Search and open it.
2. Select Restart now and check for problems and let every pass complete.
3. Read the result in Event Viewer under the MemoryDiagnostics-Results source.
4. Run MemTest86 from a USB drive for several full passes to confirm an intermittent fault.
5. Record any errors, because even a single error confirms a module that must be reseated or replaced.

Reseat and Test One RAM Module at a Time

Reseating the modules and testing one stick at a time isolates a single failing module and clears a contact fault that mimics defective memory. The method confirms which module or slot to act on.

1. Shut down the computer, unplug it, and open the case.
2. Remove each memory module, clear the slot contacts, and reseat the module firmly until it clicks.
3. Boot with a single module in the first supported slot and run Windows Memory Diagnostic or MemTest86.
4. Repeat with each module individually in the same slot to find the failing stick.
5. Replace any module that produces errors and confirm the modules match the board.

Confirm the modules match the board specification and sit in the correct slots, as covered in the guide to how RAM works. When swapping or adding memory, the steps to install RAM show the correct seating and slot order.

Update or Roll Back Device Drivers

Updating a faulty driver, or rolling back a driver that began crashing after an update, resolves cases where a driver references invalid memory. Storage, graphics, and network drivers are the usual culprits.

1. Open the latest minidump in C:\Windows\Minidump with BlueScreenView to find any named .sys file.
2. Open Device Manager and expand Storage controllers, Display adapters, and Network adapters.
3. Right-click the suspect device, select Update driver, then Search automatically for drivers.
4. Download the newest driver from the device or PC maker if Windows reports none.
5. If crashes began after a driver update, open Properties, the Driver tab, and Roll Back Driver.

Run SFC and DISM to Repair System Files

Repairing corrupt system files removes invalid memory references caused by damaged Windows components. SFC and DISM are built-in command-line tools.

1. Right-click Start and open Terminal or Command Prompt as administrator.
2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
3. Run sfc /scannow to scan and repair protected system files.
4. Restart the computer after both tools report completion.
5. Re-run sfc /scannow once more to confirm no further corruption remains.

Disable Fast Startup

Disabling Fast Startup stops the hybrid shutdown that can leave a stale memory image and trigger the page fault on the next boot. The setting sits in the Control Panel power options.

1. Open Control Panel, then Hardware and Sound, then Power Options.
2. Click Choose what the power buttons do.
3. Click Change settings that are currently unavailable.
4. Clear the Turn on fast startup (recommended) checkbox.
5. Save changes, restart, and test stability across several full shutdowns.

Disable a Conflicting Antivirus

Removing a conflicting third-party antivirus clears the memory-hooking conflict that references an invalid address. Security tools that intercept memory operations are a frequent trigger.

1. Open Settings, then Apps, then Installed apps, and locate the third-party antivirus.
2. Uninstall it, then run the vendor removal tool to clear its kernel driver fully.
3. Rely on Microsoft Defender to test stability after the removal.
4. Restart and confirm the crash is gone before reinstalling a current, supported version.

Check the Pagefile and Reset Virtual Memory

Resetting the pagefile clears a corrupt virtual-memory file that produces invalid page references. The setting sits in the advanced system performance options.

1. Open System Properties, then Advanced system settings, then Settings under Performance.
2. Open the Advanced tab and click Change under Virtual memory.
3. Clear Automatically manage paging file size, select the system drive, and choose No paging file, then Set.
4. Restart to clear the old pagefile, then return and set the size back to System managed.
5. Restart again and test stability with the rebuilt pagefile.

Run chkdsk to Check the Disk

Running chkdsk finds and repairs the bad sectors that corrupt the data Windows pages in and out, which also damages the pagefile. The tool is built into Windows.

1. Open Terminal or Command Prompt as administrator.
2. Run chkdsk C: /f /r to fix errors and recover readable data from bad sectors.
3. Type Y to schedule the scan at the next restart when prompted.
4. Restart and let chkdsk complete every stage before Windows loads.
5. Read CrystalDiskInfo afterward to confirm the drive health status is Good.

Reset an Overclock and Memory XMP Profile

Returning memory and the processor to stock speeds removes the instability that loses resident data and triggers the page fault. An XMP or EXPO profile or a manual overclock can push the memory past a stable point.

1. Enter the BIOS or UEFI during startup by pressing the setup key shown on the boot screen.
2. Load optimized or default settings to clear any manual overclock.
3. Disable the XMP or EXPO memory profile and run the memory at its default JEDEC speed.
4. Save and exit, then test stability under normal use for several hours.
5. Re-enable a memory profile only after confirming the system is stable at stock speeds.

If the crashes stop at stock speeds, the previous memory profile exceeded what the modules or controller could sustain and should remain disabled or replaced with a slower profile.

Disable Automatic Restart to Read the Stop Code

Turning off automatic restart keeps the PAGE_FAULT_IN_NONPAGED_AREA screen visible long enough to record any failing .sys file when the system reboots too fast to read it. The setting sits in System Properties.

1. Open System Properties, then Advanced system settings.
2. Under Startup and Recovery, click Settings.
3. Clear the Automatically restart checkbox.
4. Confirm a small memory dump is selected so a minidump is written after each crash.
5. Save changes so the next crash holds the stop code and any file name on screen.

Prevent PAGE_FAULT_IN_NONPAGED_AREA From Returning

Keeping the fault from returning depends on healthy memory, current drivers, and a clean boot configuration. A few routine actions hold the system stable.

• Run a memory test after any RAM change. Confirm new or reseated modules pass Windows Memory Diagnostic or MemTest86 before relying on the system.
• Install drivers from the device maker. Manufacturer storage and graphics drivers avoid the invalid memory references behind the code.
• Leave Fast Startup off on prone systems. The hybrid shutdown reintroduces stale memory images on some hardware.
• Monitor disk health. Replace a drive once CrystalDiskInfo reports rising reallocated sectors, which protects the pagefile.

PAGE_FAULT_IN_NONPAGED_AREA Causes and Fixes

Key Takeaways

• The error is a missing memory reference. Windows could not find resident data in the nonpaged area, named by bug-check 0x00000050.
• Test RAM first. Windows Memory Diagnostic and MemTest86 confirm the defective memory that is the leading cause.
• Reseat and isolate modules. Test one stick at a time to find the failing module or a contact fault.
• Check drivers and system files next. Update the named driver and run DISM then SFC to clear invalid references.
• Disable Fast Startup and reset the pagefile. Both clear stale or corrupt memory images that trigger the fault.

Last Thoughts on PAGE_FAULT_IN_NONPAGED_AREA

PAGE_FAULT_IN_NONPAGED_AREA is resolved by finding the memory or driver fault that leaves resident data missing, because the bug-check 0x00000050 points first to defective RAM, then to a faulty driver, corrupt files, or a conflicting antivirus. Testing and reseating RAM, updating the named driver, repairing system files with DISM and SFC, and disabling Fast Startup cover the common sources. The full crash workflow and the meaning of every code are covered in the guides to fixing the Blue Screen of Death and reading BSOD stop codes.

Related stop codes are handled in the steps to fix SYSTEM_SERVICE_EXCEPTION and fix KERNEL_SECURITY_CHECK_FAILURE. Because faulty memory drives this code, the explanation of how RAM works and the steps to install RAM confirm a module fault before replacement.