What PAGE_FAULT_IN_NONPAGED_AREA means

Some memory must stay in RAM at all times. When Windows asks for such a page and it is invalid, the system cannot recover. Faulty RAM, a driver writing to the wrong address, or a damaged file system are the usual explanations, and security software that hooks deep into the system has also been implicated.

Common causes

  • Faulty or badly seated RAM
  • A driver or security tool corrupting memory
  • File system corruption on the system drive
  • A memory overclock or XMP/EXPO profile that is not stable

How to fix PAGE_FAULT_IN_NONPAGED_AREA

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

  1. Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
  2. Reseat and isolate the RAM sticks. Power off, unplug the PC and reseat each stick firmly. If you have more than one, test with a single stick in the slot your motherboard manual recommends, then swap sticks. A crash that follows one stick identifies it.
  3. Scan the file system. Open Terminal (Admin) and run chkdsk C: /scan. It checks the volume without taking it offline. Back up first if the drive is old or has shown errors.
  4. Return the PC to stock settings. Reset the BIOS to defaults, then leave XMP or EXPO, CPU or GPU overclocks and undervolts (including per-core offsets such as Curve Optimizer) switched off while you test. If the crashes stop, re-enable one setting at a time to find the unstable one.
  5. Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
When to stop and protect your data

Memory errors in a test mean replacing the stick, not tuning around it. If tests pass but crashes continue, look at the most recently installed drivers and security software.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other memory errors