Windows errors

Blue screen: PAGE_FAULT_IN_NONPAGED_AREA stop code

This blue screen means Windows tried to access a piece of memory that should always be available but wasn't, usually pointing to faulty RAM, a failing drive, or a bad driver.

Difficulty
Intermediate
Time
1–3 hours
DIY cost
$0–$60
Pro cost
$100–$200

Symptoms

  • Blue screen specifically names PAGE_FAULT_IN_NONPAGED_AREA
  • May mention a specific driver or system file
  • Can happen randomly or during specific tasks like copying files
  • PC restarts after the crash

Likely causes

  • CommonFaulty RAMThis is one of the classic stop codes associated with bad memory.
  • CommonFailing hard drive or SSDCorrupted or unreadable disk sectors, especially in the page/swap file area, can trigger this.
  • PossibleCorrupted or incompatible driverCertain drivers can cause this by mismanaging memory access.
  • PossibleCorrupted system or paging fileDamage to the file Windows uses as extended memory can cause this specific error.
  • Less commonOverheating causing memory instabilityExtreme heat can occasionally cause memory-related errors like this one.

What to do

  1. Run Windows Memory Diagnostic ('mdsched' from the Run dialog) and complete at least one full pass to check for RAM errors.
  2. Run 'chkdsk C: /f /r' from an administrator Command Prompt to check the drive for bad sectors, especially around the page file area.
  3. Run 'sfc /scannow' to repair damaged system files that might be involved.
  4. Check Device Manager for any drivers with warning icons and update them from the manufacturer's site.
  5. If the crash mentions a specific driver file, search for known issues with that driver and update or roll it back accordingly.
  6. Consider temporarily disabling the page file (System Properties > Advanced > Performance Settings > Advanced > Virtual Memory) to see if crashes stop, which would point to page file corruption specifically; re-enable it afterward once resolved.
  7. If RAM tests pass and drive checks come back clean but crashes continue, test with one RAM stick at a time to catch an intermittent module a full diagnostic pass might miss.

Tools and parts

  • None beyond what's built into Windows
nameSearch: “search”

When to call a pro

If chkdsk reports bad sectors or memory tests are inconclusive while crashes continue, a technician can do deeper diagnostics on the drive and RAM together.

Safety

Generally low risk

Generally low risk for a careful person. Stop if anything looks different from what this guide describes.

Related guides

Operator provides AI-generated troubleshooting information. It can be wrong. For safety-critical, electrical, gas, structural, medical, automotive safety, or other high-risk problems, consult a qualified professional.