STOP 0x00000050
PAGE_FAULT_IN_NONPAGED_AREA
Windows asked for a piece of memory that must always be present — and it wasn't there. Classic causes: faulty RAM, an aggressive antivirus driver, or a buggy device driver referencing memory it already freed.
Likely causes, most common first
- Faulty RAM or an unstable XMP/EXPO memory profile
- Antivirus or security software's filter driver
- A buggy device driver using freed memory
- A corrupted NTFS volume or failing disk
How to fix it
1. Test your RAM moderate
- Run Windows Memory Diagnostic (Start → type "memory") and let it reboot and test.
- Disable XMP/EXPO in the BIOS temporarily if enabled.
- For persistent crashes, run MemTest86 from USB for at least 4 passes.
2. Update or remove the identified driver easy
- Update the named driver from the vendor's site (link in the driver card).
- If it belongs to antivirus/security software, temporarily uninstall that product and watch for a week — filter drivers are a classic 0x50 cause.
3. Check the disk easy
- In an admin terminal run: chkdsk C: /f — confirm the scan on next reboot.
- Also run: sfc /scannow
The four parameters on the blue screen
Windows shows four hex numbers with this stop code. Here's what each means — our analyzer decodes them automatically from your dump file.
| Parameter 1 | Memory address that was referenced |
| Parameter 2 | Access type: 0 = read, 1 = write, 2/10/11 = execute variants |
| Parameter 3 | Address of the instruction that referenced it |
| Parameter 4 | Reserved |
Got a crash dump? Get your verdict in seconds
Drop the .dmp file into our analyzer — it runs entirely in your browser. No upload, no size limit, no account.
Analyze my dump file →