My pc keeps getting PAGE_FAULT_IN_NONPAGED_AREA

PAGE_FAULT_IN_NONPAGED_AREA, MEMORY_MANAGEMENT, and ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY together strongly indicate a low‑level memory problem: typically a faulty driver, system service, antivirus filter, disk/NTFS corruption, or failing hardware (often RAM/CPU/GPU VRAM), even if basic checks pass.

Work through these steps in order; test games after each major step:

1. Check Event Viewer and identify the culprit

• Open Event Viewer → Windows Logs → System.
• Look for critical/ error events at the same time as the crashes (Kernel-Power, disk, driver names, or BugCheck events).
• If a specific driver or service name appears, update/disable/uninstall that component and retest.

2. Update or roll back drivers and system services Bug check 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) is often caused by faulty drivers or system services.

• Display/GPU driver: clean‑reinstall the graphics driver from the GPU vendor (NVIDIA/AMD/Intel) rather than relying on “already up to date”.
• Storage / chipset drivers: install the latest from the motherboard or laptop vendor.
• Third‑party system utilities (RGB tools, overclocking tools like Armoury Crate, vendor “optimizer” suites, monitoring overlays): temporarily uninstall them. Similar cases have been fixed by removing vendor tuning/overclocking tools.
• Antivirus: temporarily disable or uninstall any third‑party antivirus and test. Antivirus filter drivers are a known cause of 0x50.

3. Check for faulty system services and antivirus From the 0x50 documentation:

• Faulty system service: disable the suspect service and confirm if crashes stop. If so, contact the vendor for an update.
• Antivirus: disable the program and confirm if the error stops. If it does, contact the AV vendor for an update.

4. Check disk and file system more thoroughly Even though chkdsk reported fine, 0x50 can be triggered by a corrupted NTFS volume.

• Run chkdsk /f /r on the system drive from an elevated Command Prompt.
  • This will schedule a scan at reboot; allow it to complete. This can take a long time.
• Afterward, test games again.

5. Run deeper memory and hardware diagnostics Basic Windows Memory Diagnostics can miss intermittent issues.

• Run Windows Memory Diagnostics again (Control Panel → search “Memory” → Diagnose your computer’s memory problems) and check results in Event Viewer → System → source MemoryDiagnostics-Results.
• If possible, run more extensive third‑party memory tests and GPU stress tests.
• If hardware was recently added (new RAM, GPU, SSD), temporarily remove or reseat it and test.
• If the CPU or motherboard is suspect (as in similar cases), test with default BIOS settings (no XMP/overclock) and, if possible, cross‑test components.

6. Use Driver Verifier to catch bad drivers (advanced) If crashes continue and no driver is obvious:

• Use Driver Verifier to stress non‑Microsoft drivers so that the faulty one is forced to fail and be identified.
• Before enabling it, create a system restore point.
• After enabling, use the system normally (including gaming) until a BSOD occurs and a new minidump is created.
• Analyze the dump (or share it with a specialist) to see which driver is named.

7. Debugging with WinDbg (if comfortable) If access to the minidumps and WinDbg is available:

• Use !analyze -v to get detailed info about the bug check and the faulting module.
• Check MODULE_NAME and FAULTING_MODULE to see which driver referenced invalid memory.
• Use .trap from the TRAP_FRAME in the output, then kb to inspect the stack.
• Use lm t n to list loaded modules and correlate with third‑party drivers.

8. If a specific driver or hardware is identified

• Driver: update, roll back, or uninstall it. If it is tied to a specific app (e.g., vendor tuning tool, crash defender, overlay), uninstall that app.
• Hardware: if RAM, GPU, or CPU is confirmed faulty, replace the component. Similar cases have been resolved only after replacing a faulty CPU or removing problematic vendor tools that were destabilizing CPU frequencies.

If, after all of the above, crashes only occur under gaming load and never at idle, focus on GPU driver, GPU hardware, PSU, and any vendor performance/overclocking utilities.

References:

• Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
• Troubleshooting Windows unexpected restarts and stop code errors
• Stop error in Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2: "0x00000050 PAGE_FAULT_IN_NONPAGED_AREA"
• Trying to figure out this Windows Error Reporting 1001 event (Event Name: Bluescreen) - Microsoft Q&A
• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A
• My Windows 11 PC Hard Freezes for about 30 seconds to a minute when I play certain games. - Microsoft Q&A
• Kernel_Security_Error BSOD. Driver Verifier causing bootloop. - Microsoft Q&A
• PROBLEMAS COM ATUALIZAÇÃO 02/10/2025 WIN - Microsoft Q&A