ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

PAGE_FAULT_IN_NONPAGED_AREA

PAGE_FAULT_IN_NONPAGED_AREA (0x50) on Windows: invalid system memory was referenced

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Medium

Proceed carefully and stop if the check is unclear.

Urgency

High

Quick answer

Windows tried to use system memory at a wrong or already freed address. Note any driver shown, test memory with Windows Memory Diagnostic and check the disk with chkdsk.

Safety first

Stop and check this first

  • A 0x50 does not prove the RAM is broken: drivers, antivirus or a damaged volume cause the same stop. Ask for a memory test result before paying for a new module.

Safe checks you can perform

  • Named driver and recent programs
  • Windows Memory Diagnostic
  • Disk errors with chkdsk
  • Test without third-party antivirus

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Dump analysis
  • Do not attempt this professional task: Maker's memory and disk diagnostics

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Dump analysis

    What they doIT support runs !analyze -v, reviews MODULE_NAME and FAULTING_MODULE, the stack and the operation type in parameter 2 (read, write or execute).

    They must show youthe output with the module involved.

    In writingwhich driver or service was updated or disabled.

  2. Maker's memory and disk diagnostics

    What they doThey run the system and drive makers' diagnostic tools and, if needed, Driver Verifier on the suspect driver.

    They must show youthe report from each diagnostic.

    In writingwhich component failed the test and, if replaced, its reference and reason.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Named driver and recent programs

    No special tools

    Who:
    you.
    How:
    photograph the blue screen, look for a .sys file and note which app or service you installed or updated before the first crash.
    Result that matters:
    whether a driver or program lines up.
    If one does:
    update the driver or reinstall the recent program and watch for repeats.
    If not:
    go on to memory and disk.
    Evidence to keep:
    photo of the screen and name of the recent program.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA · Stop code error or bug check troubleshooting (IT professionals)

  2. Windows Memory Diagnostic

    No special tools

    Who:
    you.
    How:
    search Memory in Control Panel, choose Diagnose your computer's memory problems and let it restart and test; then open Event Viewer, System log, and find the MemoryDiagnostics-Results entry.
    Result that matters:
    whether the test reports errors.
    If it reports errors:
    keep the result and take it to IT support; it points at memory but must be confirmed.
    If no errors:
    physical memory is not flagged; continue with the disk.
    Evidence to keep:
    screenshot of the MemoryDiagnostics-Results entry.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

  3. Disk errors with chkdsk

    No special tools

    Who:
    you, as administrator.
    How:
    in Command Prompt as administrator run chkdsk /f /r; accept scheduling it and restart, because on the system partition the scan runs at startup.
    Result that matters:
    whether chkdsk reports fixed errors or bad sectors.
    If it fixed errors:
    a corrupted NTFS volume was a candidate; watch for repeats.
    If it reports bad sectors or does not finish:
    do not repeat it; ask IT support for the drive maker's diagnostics.
    Evidence to keep:
    screenshot or photo of the chkdsk summary.

    The scan can take a long time; do not switch the PC off while it runs. If you have files without a backup, copy them first.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA · Stop code error or bug check troubleshooting (IT professionals)

  4. Test without third-party antivirus

    No special tools

    Who:
    you.
    How:
    temporarily disable any antivirus other than Windows Security and use the PC normally.
    Result that matters:
    whether the blue screen stops.
    If it stops:
    ask the antivirus maker for an updated version.
    If it repeats:
    turn it back on.
    Evidence to keep:
    dates and antivirus version.

    Keep Windows Security on for the duration of the test.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x00000050
  • 0x50
  • PAGE FAULT IN NONPAGED AREA
  • STOP 0x00000050
  • stop code PAGE_FAULT_IN_NONPAGED_AREA

What it means

Microsoft defines 0x00000050 as a reference to invalid system memory: the address is wrong or points to freed memory. It can be triggered by a faulty system service or driver, antivirus software, a corrupted NTFS volume, or faulty or failing hardware, usually RAM, L2 cache or video RAM. If the driver is identified, its name appears on screen. The code alone does not tell which of these systems is failing.

Warnings and stop conditions

  • Mediumeditorial warning

    A 0x50 does not prove the RAM is broken: drivers, antivirus or a damaged volume cause the same stop. Ask for a memory test result before paying for a new module.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

Symptoms and causes

Probable causes · in order

  • Faulty driver or serviceCommon

    If the screen or log names a driver, Microsoft advises asking its maker for an update; if disabling it stops the crashes, it is confirmed.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA · Stop code error or bug check troubleshooting (IT professionals)

  • Corrupted NTFS volumePossible

    Told apart with chkdsk /f /r, which detects and repairs disk errors.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

  • Antivirus softwarePossible

    Microsoft lists it as a trigger. Temporarily disabling it tests this.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

  • Defective memoryPossible

    RAM, L2 cache or video RAM. Windows Memory Diagnostic gives a first indication; it is not a verdict on a specific part.

    Evidence: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

Virtual technician

Does PAGE_FAULT_IN_NONPAGED_AREA still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA

    Microsoft · 2026 · official_doc

  2. 2

    Stop code error or bug check troubleshooting (IT professionals)

    Microsoft · 2026 · official_doc

  3. 3

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

Sources: Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA · Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errorsreviewed 2026-10-03 · verified

Was this entry useful?