Skip to content
PCDecoder
0x00000050PAGE_FAULT_IN_NONPAGED_AREAStop codeWidely reported

PAGE_FAULT_IN_NONPAGED_AREA (0x50): what it means and how to fix it

By Gaurav Rawat · Updated Oct 2, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

PAGE_FAULT_IN_NONPAGED_AREA means Windows tried to read memory that wasn't there, typically because of a faulty driver, bad RAM, or damaged system or disk data. Test your memory, update recently changed drivers and repair system files.

What it means

Windows keeps some memory permanently in RAM (the non-paged area), because it must be available instantly. Bug check 0x50 means something referred to an address in that area and found nothing valid there.

The bad address almost always comes from one of three places: a driver that used a stale or wrong pointer, RAM that returned the wrong value, or corrupted data loaded from disk. Antivirus and backup software, which hook deep into Windows, are also known to trigger it.

When it appears right after an update

If the crashes started straight after a Windows or driver update, removing that update is often the fastest fix while you wait for a corrected version.

Common causes

  • Faulty or unstable RAM.
  • A buggy or incompatible driver.
  • Third-party antivirus or backup software.
  • Corrupted system files or file system errors on the drive.
  • A recent Windows or driver update.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Test your RAM

    If the crashes are random, or this stop code alternates with other memory-related ones.

    1. Save your work, press Win + R, type mdsched.exe and press Enter.
    2. Choose Restart now and check for problems, and let the test run to the end.
    3. When Windows starts, check the result notification, or Event Viewer > Windows Logs > System, filtered for MemoryDiagnostics-Results.
    4. Any errors mean a memory problem. Reseat the sticks, test them one at a time, and replace any that fail.
    Did this fix it?

  2. Remove the update that started it

    If the blue screens began right after a Windows or driver update.

    1. Open Settings > Windows Update > Update history and note what installed the day the crashes started.
    2. For a Windows update, scroll to Related settings > Uninstall updates and uninstall it.
    3. For a driver, open Device Manager, right-click the device, choose Properties > Driver > Roll Back Driver.
    4. Restart and see whether the crashes stop.
    Did this fix it?

  3. Repair Windows system files

    If the crashes started after an update, a power cut or a forced shutdown.

    1. Right-click Start and open Terminal (Admin).
    2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
    3. Then run sfc /scannow.
    4. Restart once both have completed.
    Did this fix it?

  4. Check the disk for errors

    If the PC was shut down by force or lost power before the crashes started.

    1. Open Terminal (Admin) and run chkdsk C: /scan.
    2. If problems are found, run chkdsk C: /f and restart when asked.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is PAGE_FAULT_IN_NONPAGED_AREA caused by RAM?

Often. Run Windows Memory Diagnostic first, then look at drivers if memory passes.

Can antivirus cause PAGE_FAULT_IN_NONPAGED_AREA?

Yes. Third-party antivirus drivers run deep inside Windows, and an incompatible version can trigger it.

Can I fix it without reinstalling Windows?

Usually. Memory tests, driver changes and system file repair fix most cases.

Written by

Gaurav Rawat

Gaurav Rawat is a full-stack developer from Jaipur with a B.Tech in Information Technology. At PC Decoder, he writes practical guides on Windows 11 updates, error codes, and fixes for apps that stop working after an update, with an emphasis on clear steps that actually solve the problem.

More from Gaurav Rawat

More stop codes decoded