Windows · Windows Server  ·  high  ·  Core Windows faults

STOP 0x00000050 — PAGE_FAULT_IN_NONPAGED_AREA

Something referenced memory that was not there. Faulty RAM and bad drivers produce this in roughly equal measure.

What you see

Bugchecks at unpredictable times, sometimes under load, sometimes idle. Often accompanied by other random bugcheck codes rather than the same one every time.

What is actually wrong

Physical memory errors, a driver writing outside its allocation, or failing paging on a dying disk. The variety of accompanying codes is the clue: one consistent code suggests a driver, a scatter of different ones suggests hardware.

Codes and articles

0x000000500x50PAGE_FAULT_IN_NONPAGED_AREA

Fixes (2)

Test the memory properly
Boot mediaSeveral hourslow riskreversible

Mixed bugcheck codes, or the machine has had a RAM change, an overclock or an XMP/EXPO profile enabled.

  1. If any memory overclock profile is enabled in firmware — XMP, DOCP, EXPO — turn it off and run at the JEDEC default first.

    These profiles are factory overclocks. A kit that is unstable at its rated speed on this particular board is extremely common and looks exactly like failing RAM.

  2. Run MemTest86 from USB for at least four full passes. Windows' own memory diagnostic is not thorough enough to clear a stick.

    Single-pass tools routinely pass modules that fail on pass three.

  3. If errors appear, test one stick at a time to identify which.

  4. If it is clean at default speed but fails with the profile on, the kit or the board is the problem, not Windows.

Confirm it workedFour clean MemTest86 passes and no further bugchecks over several days of normal use.
If you need to undo itRe-enable the memory profile if testing exonerates it.
Catch the driver with Driver Verifier
Elevated command prompt1–2 days of normal usehigh riskreversible

Consistently the same code and memory tests clean. Read the rollback step BEFORE starting — Verifier deliberately bugchecks the machine and can leave it unbootable.

  1. Make sure you can get into Safe Mode, and know how to reach WinRE. You will very likely need it.

    Verifier crashes the machine on purpose the moment it catches a driver misbehaving, which can happen during boot.

  2. Enable a standard rule set against non-Microsoft drivers only.

    Command Prompt
    verifier /standard /driver.exclude ntoskrnl.exe

  3. Alternatively use the GUI and select "Automatically select unsigned drivers" for a narrower net.

    Command Prompt
    verifier

  4. Restart and use the machine normally until it bugchecks.

  5. Analyse the dump — with Verifier active the driver named is reliable.

    Command Prompt
    !analyze -v

  6. Turn Verifier off as soon as you have your answer.

    Command Prompt
    verifier /reset
Confirm it workedA specific driver is named in the dump and updating or removing it stops the crashes.
If you need to undo itBoot into Safe Mode and run verifier /reset. If Safe Mode will not start either, use WinRE → Command Prompt and run verifier /reset from there, or use System Restore.

Reference

Bug Check 0x50 — Microsoft Learn ↗Driver Verifier — Microsoft Learn ↗

Related faults

STOP 0x00000139 — KERNEL_SECURITY_CHECK_FAILUREWindowsSTOP 0x0000009F — DRIVER_POWER_STATE_FAILUREWindowsSTOP 0x0000001E — KMODE_EXCEPTION_NOT_HANDLEDWindowsRandom crashes and corruption — testing for bad memoryWindowsSTOP 0x0000007B — INACCESSIBLE_BOOT_DEVICEWindowsSTOP 0x00000133 — DPC_WATCHDOG_VIOLATIONWindows

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.