How to Fix PAGE_FAULT_IN_NONPAGED_AREA

What Causes PAGE_FAULT_IN_NONPAGED_AREA?

The code fires when the kernel references memory in the nonpaged area that is missing or invalid, and four causes account for almost every case. The nonpaged area must always stay resident, so a bad reference there is fatal rather than recoverable.

A corrupt pagefile or a failing disk is a less frequent source: bad sectors corrupt the data Windows pages in and out. For the wider crash workflow and the meaning of every code, see the guides to fixing BSOD stop codes and how to fix the Blue Screen of Death.

How Do You Fix PAGE_FAULT_IN_NONPAGED_AREA?

Work through the fixes in order and test stability after each one, because a single memory or driver fault usually accounts for this stop code.

• Test and reseat the RAM. Run Windows Memory Diagnostic, then MemTest86 from a USB drive for several full passes. Reseat each module and test one stick at a time to isolate a failing module or a contact fault. A single error confirms a module to replace.
• Update or roll back drivers. Open the latest minidump in BlueScreenView to find any named .sys file, then update that storage, graphics, or network driver from the device maker. If crashes began after a driver update, use Roll Back Driver instead.
• Run SFC and DISM. In an administrator terminal, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, and restart. Re-run sfc /scannow once more to confirm no corruption remains.
• Disable a conflicting antivirus. Uninstall a third-party antivirus, then run the vendor removal tool to clear its kernel driver fully. Rely on Microsoft Defender to test, and reinstall a current version only if the crash is gone.
• Disable Fast Startup. In Power Options, open Choose what the power buttons do, click Change settings that are currently unavailable, clear Turn on fast startup, and do a full shutdown so the kernel starts cold without a stale memory image.

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. Faulty memory can also surface as high memory usage before it triggers a stop code.

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 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 with kernel filter drivers 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.

Disable Fast Startup

Disabling Fast Startup stops the hybrid shutdown that can reload a stale kernel and driver state 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, do a full shutdown, and test stability across several boots.

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

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 or rolling back the named driver, repairing system files with DISM and SFC, disabling a third-party antivirus, and turning off 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.

Because faulty memory drives this code, the explanation of how RAM works and the steps to install RAM confirm a module fault before replacement. This stop code sits alongside the other faults collected in the hub on common PC problems.

Key Takeaways:

• PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) means Windows could not find resident data in the nonpaged area of memory.
• Defective RAM is the single most common cause, so test memory first with Windows Memory Diagnostic and MemTest86.
• Reseat and test one module at a time to isolate a failing stick or a contact fault.
• A faulty driver named in the minidump is the next suspect; update it or roll it back from the device maker.
• Run DISM then SFC for corrupt system files, and remove a third-party antivirus that hooks memory.
• Disable Fast Startup and reset the pagefile to clear stale or corrupt memory images that trigger the fault.

Frequently Asked Questions (FAQs)