FIX · CRASHES AND BLUE SCREENS
PAGE_
This stop code means Windows referenced system memory that was not valid. The address is usually wrong or points at memory that was already freed. Microsoft names five usual suspects, and each one has its own test, so you can rule them out instead of reinstalling Windows.
Updated .
TECHNICAL SUMMARY
| Stop code | 0x00000050 |
|---|---|
| Meaning | Invalid system memory was referenced |
| Usual causes | Driver or system service, antivirus, corrupted NTFS volume, faulty hardware |
| Hardware most often involved | RAM: main memory, L2 cache or video RAM |
| PC Tweaker plan | No control fixes it; Tweaky Driver lists your drivers |
What Microsoft says causes it
Microsoft lists a faulty system service or driver, antivirus software, a corrupted NTFS volume, and newly installed or failing hardware, usually defective RAM. That can be main memory, L2 cache or video RAM.
Test one suspect at a time
Start with whatever changed just before the crashes began, then go through the rest. Change one thing, then see whether the blue screen comes back.
- Driver: if the blue screen or event log names one, ask its vendor for an update
- System service: disable it, confirm the error stops, then contact its maker
- Antivirus: disable it, confirm the error stops, then contact its maker
- Disk: run chkdsk and the disk maker's own diagnostics
- Memory: run Windows Memory Diagnostic
- Hardware: remove anything added recently, and replace a part that has failed
If Windows will not start
When the error appears during startup, Microsoft points to the Windows repair options. Use them to reach a point where you can undo the last change.
Do it by hand
Check the System log (read-only)
Critical and error entries from the last 24 hours. Move StartTime back if the crash was earlier, and look for a device or driver named close to the time of the blue screen.
PowerShellGet-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-1)} -MaxEvents 30 | Format-Table TimeCreated, ProviderName, Id -AutoSizeRepair the disk (as administrator)
On the system drive, the scan starts at the next restart. Microsoft recommends this for a corrupted NTFS volume.
cmdchkdsk C: /f /rTest the memory
Windows Memory Diagnostic restarts the PC to run. Save your work first.
cmdmdsched.exeRead the memory test result (read-only)
An error saying no events were found means no memory test result has been logged yet.
PowerShellGet-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-MemoryDiagnostics-Results'} -MaxEvents 1 | Format-List TimeCreated, Message
With PC Tweaker
PC Tweaker does not read crash dumps, and none of its controls fixes this error. If the logs point to a driver, Tweaky Driver, our free driver update checker, shows that device's driver version, the updates available and where the package comes from before you install anything.
Rather not edit the registry by hand?
PC Tweaker shows the exact change before it runs, records the value it replaces and puts it back with Restore. The Free plan needs no account. If a payment fails or a plan ends, Pro tools lock; changes already applied stay as they are and Restore still undoes them.
Common questions
Is PAGE_FAULT_IN_NONPAGED_AREA a RAM problem?
It can be. Microsoft says failing hardware is usually defective RAM, but it also lists drivers, system services, antivirus software and corrupted NTFS volumes.
How do I fix PAGE_FAULT_IN_NONPAGED_AREA?
Check the System log for a named driver or device, update it, test antivirus and recent services by disabling them, run chkdsk /f /r, run Windows Memory Diagnostic, and remove recently added hardware.
Can antivirus cause PAGE_FAULT_IN_NONPAGED_AREA?
Yes, Microsoft lists antivirus software as a possible trigger. Disable it to test, and if the error stops, contact its maker about an update.
Try PC Tweaker
Free download for Windows 10 and Windows 11.