By /

PAGE_FAULT_IN_NONPAGED_AREA Boot Loop – Complete Fix Guide (2026)

Table of Contents

Hub: Windows 11 Troubleshooting Hub

Quick Answer
A PAGE_FAULT_IN_NONPAGED_AREA boot loop is a critical blue screen error that occurs when Windows attempts to access memory that is invalid or not properly allocated. The most common causes include faulty RAM, corrupted drivers, and incorrect page file settings. To resolve this error, boot into Safe Mode, run Windows Memory Diagnostic, update or roll back drivers using Device Manager, and run sfc /scannow from Command Prompt. If the boot loop persists, disable overclocking in BIOS and adjust your virtual memory settings. For more Windows troubleshooting, visit our Windows 11 Troubleshooting Hub.

Why PAGE_FAULT_IN_NONPAGED_AREA Boot Loop Happens

The PAGE_FAULT_IN_NONPAGED_AREA boot loop error occurs when Windows attempts to access memory that cannot be found or is not properly allocated. This stop code is categorized as a memory management error and typically points to issues with physical RAM, corrupted drivers, or incorrect system settings. For official documentation on this error, visit the Microsoft Bug Check 0x50 documentation.

The nonpaged area refers to memory segments that cannot be swapped to the page file on your hard drive. When the system requests data from this area but the memory address is invalid or corrupted, the kernel triggers a bug check and initiates a system crash. This is similar to other BSOD errors like KMODE_EXCEPTION_NOT_HANDLED and SYSTEM_SERVICE_EXCEPTION (ks.sys) which also point to driver or memory issues.

Common triggers include faulty RAM modules, outdated or incompatible drivers, corrupted system files, and improper virtual memory configurations. Overclocking instability and failing hard drives can also produce this error. In some cases, recent Windows updates or third-party antivirus software interfere with memory allocation and cause the boot loop. For more severe cases, this error may lead to a WHEA_UNCORRECTABLE_ERROR or Windows Error 0xc0000005 (Access Violation).

⚠️ Warning: The PAGE_FAULT_IN_NONPAGED_AREA error can be caused by both hardware and software issues. Always test your RAM first before proceeding with more invasive fixes like system reinstalls.

1. Boot into Safe Mode

Safe Mode loads Windows with minimal drivers and services, often allowing you to bypass the blue screen and access critical troubleshooting tools. This is your first line of defense against the boot loop. For a detailed guide on accessing Safe Mode, check our How to Boot into Safe Mode Windows 11 guide.

  1. Restart your computer and press F8 repeatedly during startup. If this doesn’t work, force shutdown your PC three times in a row during boot to trigger the Automatic Repair screen.
  2. Select Troubleshoot > Advanced Options > Startup Settings > Restart.
  3. Press 5 or F5 to select Safe Mode with Networking.
  4. Once in Safe Mode, you can access Device Manager, Command Prompt, and System Restore to apply the fixes that follow.

✅ Expected Result: Your system should successfully boot into Safe Mode with a black desktop background and minimal interface. From here, you can apply other troubleshooting methods without the blue screen interrupting the process.

2. Test Your RAM for Hardware Faults

Faulty RAM is one of the most frequent causes of the PAGE_FAULT_IN_NONPAGED_AREA boot loop. Testing your memory modules can identify defective hardware that requires replacement. For a comprehensive guide, visit our How to Check RAM Health Windows 11 article.

  1. Boot from a Windows installation USB, select “Repair your computer,” then navigate to Troubleshoot > Advanced Options > Command Prompt and run mdsched.exe.
  2. Alternatively, access it from Safe Mode by typing “Windows Memory Diagnostic” in the Start menu.
  3. Choose the immediate restart option and allow the test to complete, which may take 15-30 minutes depending on your RAM capacity.
  4. If errors are detected, you will need to replace the faulty RAM module. If you have multiple RAM sticks, test them individually by removing all but one module.

💡 Quick Tip: For more comprehensive memory testing, consider using MemTest86. This third-party tool runs from a bootable USB and performs more thorough tests than Windows’ built-in utility.

3. Disable CPU and RAM Overclocking

Overclocking pushes your hardware beyond manufacturer specifications and can cause memory instability that triggers blue screen errors. Many modern motherboards enable automatic overclocking through XMP (Extreme Memory Profile) or DOCP profiles.

  1. Access your BIOS/UEFI settings by pressing Del, F2, or F12 during startup.
  2. Look for overclocking sections typically labeled “AI Tweaker,” “Performance,” or “Extreme Tweaker.”
  3. Disable XMP profiles and reset CPU multipliers to default values.
  4. Memory frequency should be set to the JEDEC standard speed rather than the maximum rated XMP speed. For DDR4 systems, this typically means 2133MHz or 2400MHz.
  5. After applying these changes, save the BIOS configuration and restart your system.

⚠️ Warning: Resetting BIOS settings to defaults will remove any custom configurations you have set. Make note of any important settings before making changes.

4. Update or Roll Back Problematic Drivers

Drivers are software components that allow Windows to communicate with hardware. Outdated, corrupt, or incompatible drivers frequently cause the PAGE_FAULT_IN_NONPAGED_AREA boot loop. Pay special attention to storage, graphics, and network drivers. For a detailed guide, check our How to Update Drivers Windows 11 article.

  1. Access Device Manager by pressing Win + X and selecting Device Manager.
  2. Look for any devices with yellow exclamation marks. Right-click each device and select “Update driver.”
  3. If the boot loop began after a recent driver update, roll back the driver instead. Right-click the device, select Properties, then the Driver tab, and click “Roll Back Driver.”
  4. Storage controller drivers are particularly critical. Visit your motherboard manufacturer’s website to download the latest chipset and storage drivers directly.

❌ Common Mistake: Relying solely on Windows Update for driver updates. Microsoft often provides generic drivers that may lack important stability fixes. Always check the official hardware manufacturer website.

5. Run System File Checker (SFC) and DISM

Corrupted system files can cause memory access errors and trigger the PAGE_FAULT_IN_NONPAGED_AREA boot loop. System File Checker (SFC) scans for and repairs damaged Windows system files. DISM repairs the system image itself.

  1. Boot into Safe Mode with Command Prompt or use the recovery environment to access the command line.
  2. First, run DISM: DISM /Online /Cleanup-Image /RestoreHealth
  3. Wait for the operation to complete, which can take 10-15 minutes.
  4. Run the SFC command: sfc /scannow
  5. After both commands finish, restart your system and check if the boot loop persists.

✅ Expected Result: SFC will report one of three outcomes. The most common is “Windows Resource Protection found corrupt files and successfully repaired them,” which usually resolves the boot loop.

6. Check Disk for Errors and Bad Sectors

Hard drive corruption and bad sectors can contribute to the PAGE_FAULT_IN_NONPAGED_AREA boot loop by interfering with the page file and memory management operations. Running a disk check can identify and repair these issues.

  1. From Safe Mode or the recovery command prompt, run: chkdsk C: /f /r
  2. The /f parameter fixes errors, while /r locates bad sectors and recovers readable data.
  3. CHKDSK will display a message that the disk is in use and ask if you want to schedule the scan for the next reboot. Press Y and restart.
  4. If CHKDSK reports unreadable sectors or other serious drive issues, consider backing up your data immediately and planning for drive replacement.

🔁 Alternative Solution: For solid-state drives (SSDs), CHKDSK may not detect all potential issues. Consider using the manufacturer’s SSD diagnostic tool, such as Samsung Magician or Kingston SSD Manager.

7. Adjust Virtual Memory (Page File) Settings

The virtual memory system uses a page file on your hard drive to supplement physical RAM. Incorrectly configured page file settings can cause memory allocation failures that trigger the boot loop.

  1. Access virtual memory settings from Safe Mode by right-clicking This PC, selecting Properties, then Advanced System Settings > Advanced tab > Settings under Performance > Advanced tab > Change under Virtual Memory.
  2. Ensure the “Automatically manage paging file size for all drives” box is checked. If it is already checked, uncheck it and manually set the initial and maximum size to be at least 1.5 times your installed RAM capacity.
  3. If you have multiple drives, ensure the page file is configured on the system drive (typically C:) and not on a secondary drive that might be failing or disconnected.
  4. Click Set, then OK, and restart your computer.

💡 Quick Tip: If you are using an SSD as your system drive, ensure the page file remains on the SSD for optimal performance. Moving the page file to a slower mechanical drive can worsen system responsiveness.

8. Disconnect Non-Essential Hardware

Faulty external devices or internal components can cause memory conflicts that trigger the PAGE_FAULT_IN_NONPAGED_AREA boot loop. Disconnecting non-essential hardware helps isolate the problematic component.

  1. Start by unplugging all USB devices except for your keyboard and mouse. Remove external hard drives, printers, webcams, and USB hubs.
  2. If you have multiple monitors connected, try using only one display.
  3. Internally, consider removing any secondary hard drives or SSDs that are not essential for booting.
  4. If you have recently installed a new graphics card, network adapter, or RAM module, try removing it and testing with only the minimal configuration.

⚠️ Warning: When handling internal components, always power off the system, unplug the power cord, and ground yourself to prevent static electricity damage.

9. Perform System Restore or Startup Repair

If the boot loop began after a recent system change, System Restore can revert your system to a previous state without affecting personal files. For a detailed guide on System Restore, check our How to Use System Restore Windows 11 article.

  1. Access System Restore from the advanced boot options menu. Boot into the recovery environment, select Troubleshoot > Advanced Options > System Restore.
  2. Choose a restore point that predates the appearance of the blue screen error.
  3. If System Restore fails or no restore points are available, try Startup Repair from the same Advanced Options menu.
  4. This automated tool attempts to fix common boot problems by replacing corrupted boot files, fixing registry issues, and restoring system settings.

✅ Expected Result: System Restore should complete successfully with a message confirming the restoration. Your system will restart and should boot normally without the blue screen error.

10. Advanced Troubleshooting

If none of the previous methods resolve the PAGE_FAULT_IN_NONPAGED_AREA boot loop, consider these advanced approaches. These solutions are more invasive and should be attempted only after simpler fixes have failed.

Reinstall Windows Using In-Place Upgrade

An in-place upgrade reinstalls Windows while preserving your applications, settings, and files. This is less destructive than a clean installation and can repair corrupted system files that SFC and DISM cannot fix. Use the Media Creation Tool from the Microsoft website to download the latest Windows 11 installation media.

Disable Virtualization-Based Security (VBS)

Virtualization-based security features can cause memory management conflicts. From Safe Mode with Command Prompt, disable VBS by running bcdedit /set hypervisorlaunchtype off. Reboot and check if the boot loop resolves. For more information, see our How to Disable VBS Windows 11 guide.

Update Motherboard BIOS

Outdated BIOS versions can cause compatibility issues with modern hardware and memory configurations. Visit your motherboard manufacturer’s website to download and install the latest stable BIOS version. Follow the manufacturer’s instructions carefully when performing this update.

Check for Malware

Although less common, rootkits and other low-level malware can cause memory access violations. Run a full system scan using Windows Defender Offline or a reputable third-party antivirus bootable rescue disk. Visit our How to Scan Malware Windows 11 guide for detailed steps.

If you have exhausted all methods and the blue screen continues, contact Microsoft Support or your computer manufacturer for professional assistance. For similar BSOD issues, check our guides on KMODE_EXCEPTION_NOT_HANDLED Fix, Windows 11 BSOD Fix, and WHEA_UNCORRECTABLE_ERROR Fix.

Conclusion

The PAGE_FAULT_IN_NONPAGED_AREA boot loop is a serious system error that can feel overwhelming. However, following this troubleshooting sequence makes the resolution manageable and systematic. Start with Safe Mode access, test your RAM for hardware issues, and then address driver and system file corruption. If the problem persists, consider disabling overclocking, adjusting virtual memory settings, or performing a System Restore.

If you have exhausted all methods and the blue screen continues, contact Microsoft Support or your computer manufacturer for professional assistance. In some cases, the issue may require professional diagnostics or hardware replacement. Remember to back up your important files regularly to prevent data loss in the event of system failure.

For more Windows troubleshooting guides, visit our Windows 11 Troubleshooting Hub where you’ll find comprehensive solutions for common Windows errors including Windows Error 0xc0000005 and Windows 11 Update Stuck Fix.

Related Guides

FAQ

What causes the PAGE_FAULT_IN_NONPAGED_AREA boot loop?

This blue screen error is caused by memory access violations in the nonpaged area of system memory. Faulty RAM, corrupted drivers, bad system files, incorrect page file settings, and hardware conflicts are the most common triggers.

Can I fix PAGE_FAULT_IN_NONPAGED_AREA without reinstalling Windows?

Yes, in most cases. Booting into Safe Mode and running memory tests, driver rollbacks, and system file repairs typically resolves the issue without needing a full reinstall. System Restore is also highly effective.

How long does RAM testing take?

The Windows Memory Diagnostic tool typically takes 15 to 30 minutes to complete, depending on your RAM capacity and system speed. MemTest86 may take several hours for a comprehensive test.

Will disabling XMP fix the boot loop?

If overclocking instability is causing the error, disabling XMP and returning RAM to JEDEC standard speeds will often resolve the blue screen. This reduces memory speed but ensures system stability.

Can a failing hard drive cause this blue screen?

Yes. Bad sectors or corruption on the system drive can interfere with page file operations and trigger memory management errors. Running CHKDSK can identify and repair these issues.

What should I do if my PC keeps restarting before I can run fixes?

Force shutdown your PC three times in a row during boot to trigger Automatic Repair. From there, access Advanced Options and boot into Safe Mode with Command Prompt to run diagnostic commands.

How do I access Safe Mode when my PC is in a boot loop?

Interrupt the boot process three times by powering off during startup to trigger Automatic Repair. Then go to Troubleshoot > Advanced Options > Startup Settings > Restart and select Safe Mode with Command Prompt or Safe Mode with Networking.

What is the difference between nonpaged and paged memory?

Nonpaged memory must always remain in physical RAM and cannot be moved to the page file. Paged memory can be swapped to disk. The PAGE_FAULT_IN_NONPAGED_AREA error occurs when the system tries to access nonpaged memory that is unavailable or corrupted.

Is it safe to increase virtual memory to fix this error?

Yes, increasing the page file size is generally safe and can resolve memory allocation errors. Ensure the page file is on a drive with sufficient free space and set appropriate minimum and maximum sizes based on your installed RAM.

What are the long-term solutions to prevent this blue screen?

Regularly update drivers and Windows, keep your system free of malware, ensure adequate cooling for your components, and periodically check your hardware health using diagnostic tools. Avoid unnecessary overclocking and maintain a stable operating environment.

How do I perform a clean installation to fix this error?

Create a Windows 11 installation USB using the Media Creation Tool, boot from the USB, and follow the installation prompts. Choose “Custom: Install Windows only” and delete all partitions on the system drive before installing. This removes all software-related issues but will erase all data.

Can a faulty power supply cause this blue screen?

Yes, an unstable or insufficient power supply can cause random system crashes and blue screen errors, including the PAGE_FAULT_IN_NONPAGED_AREA boot loop. If other troubleshooting methods fail, testing with a known good power supply is recommended.

Can a faulty motherboard cause the PAGE_FAULT_IN_NONPAGED_AREA boot loop?

Yes, motherboard issues, particularly with the memory controller or DIMM slots, can cause memory allocation errors. However, this is less common than RAM, driver, or system file issues. Test with known working RAM modules in different slots to diagnose motherboard-related problems.

What is the best free software to test RAM?

MemTest86 is the most comprehensive free RAM testing tool available. It runs from a bootable USB and performs thorough tests that can detect subtle memory errors that Windows Memory Diagnostic may miss.

Can outdated BIOS cause the PAGE_FAULT_IN_NONPAGED_AREA boot loop?

Yes, outdated BIOS versions can cause compatibility issues with RAM modules, especially newer high-capacity or high-speed memory. Updating BIOS to the latest stable version from your motherboard manufacturer’s website can resolve these compatibility issues.

Will a clean installation of Windows 11 fix this error permanently?

If the error is software-related, a clean installation will resolve it permanently. However, if the issue is caused by faulty hardware, such as failing RAM or a damaged hard drive, a clean installation will not help, and the hardware will need replacement.

HowToFixPro Editorial Team

We’re a team of system administrators, technical writers, and platform specialists who genuinely enjoy solving the problems most users find frustrating. From persistent Windows errors and Android sync failures to browser crashes and network drops — we’ve seen it all, and we document every fix properly. Our guides are built on official documentation, direct testing, and real troubleshooting experience. No filler, no guesswork — just reliable, step-by-step solutions you can trust.

1 thought on “PAGE_FAULT_IN_NONPAGED_AREA Boot Loop – Proven Fixes (2026)”

  1. Pingback: Windows Restart Loop Error – Complete Fix Guide (2026)

Comments are closed.

Scroll to Top