Do not disable the page file because of the stop-code name
The “nonpaged area” in this bugcheck does not mean the Windows page file is automatically at fault. Keep the page file Windows-managed during diagnosis so crash dumps can be written. Back up data before testing storage that shows errors or freezes.
Use the crash pattern to set priorities
| Pattern | Check first |
|---|---|
| Same third-party driver appears | That device or software driver. |
| Begins after antivirus/VPN update | Kernel filter conflict. |
| Different codes and modules | RAM, tuning, storage. |
| Crashes during file access | Storage, file system, RAM. |
| Only under heavy load | RAM, GPU, thermals, power. |
1. Reverse a recent driver or software change
Disconnect a newly added device, roll back its driver or uninstall the recent security, VPN, backup or hardware utility tied to the first crash. Use the vendor’s official uninstaller for products that install filter drivers.
2. Test Safe Mode
Choose Startup Settings → Restart → Safe Mode from recovery. Stability here supports a non-essential driver or service cause. Remove the specific suspect and restart normally; do not treat Safe Mode as the permanent operating state.
3. Preserve and compare minidumps
Check C:\Windows\Minidump after restarting. Compare the faulting module across several crashes. A repeatable third-party driver is stronger evidence than one isolated mention of a Windows component.
4. Test RAM at default settings
Disable XMP/EXPO, overclocking and undervolting. Run Windows Memory Diagnostic, followed by an extended supported test if required. Any repeatable error matters. Isolate modules and slots only using the hardware manufacturer’s service procedure.
5. Install stable device drivers
Prioritise the driver named in repeated dumps and recently changed chipset, storage, network and graphics packages. Use Windows Update or the device manufacturer. Avoid installing unrelated drivers in one batch.
6. Check antivirus, VPN and disk filters
Update the product first. If its change precisely matches the crashes, temporarily remove it with the official cleanup method and keep Microsoft Defender or organisation-approved protection active. Reinstall only after confirming compatibility.
7. Repair Windows and the file system
Run DISM.exe /Online /Cleanup-Image /RestoreHealth, followed by sfc /scannow. Use chkdsk C: /scan for an online file-system check. Repeated corruption after repair requires memory and storage investigation.
8. Keep the page file Windows-managed
Open advanced system performance settings and confirm virtual memory is automatically managed unless a documented workload or organisation policy requires otherwise. Restoring automatic management can undo unsafe “performance tweaks,” but it is not a substitute for testing RAM.
9. Inspect the SSD and controller path
Run the SSD manufacturer’s diagnostic and review disk/controller errors. Update model-specific storage and chipset drivers or firmware when the manufacturer documents the fix. Back up immediately if the drive disappears, stalls or reports health problems.
10. Escalate persistent crashes
Check thermals, power and new hardware. Crashes during recovery, memory testing or clean installation point beyond normal application software. Replace hardware only after isolating the failing module, slot, drive or device path.
Avoid these common mistakes
- Do not disable the page file as a generic fix.
- Do not delete a driver file manually.
- Do not ignore repeatable RAM errors.
- Do not run aggressive disk repair before backing up unstable storage.
Frequently asked questions
Does PAGE_FAULT_IN_NONPAGED_AREA mean bad RAM?
Bad RAM is common, but drivers, antivirus filters, storage corruption and unstable tuning can also reference invalid memory.
Should I disable pagefile.sys?
No. The stop code does not directly blame the page file, and disabling it can create new problems and prevent useful crash dumps.
Why is a driver name shown?
That driver may have made the invalid access, or earlier memory corruption may only have surfaced while it was running. Compare multiple dumps and recent changes.
Technical steps align with Microsoft guidance for bug check 0x50, Startup Settings, Windows Memory Diagnostic, driver management, DISM and System File Checker.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.