Page_Fault in nonpaged area

Hi,

Please share new minidumps.

Run Windows memory diagnostic tool and switch it to extended mode when it starts (F1 key). Note, test hang at ~21% for more than 5-8 hours means memory error too.

Turn off XMP mode in BIOS if it is turned on.

Hi,

some files are corrupted. Please update or at least reinstall all drivers from Dell support site.

The PAGE_FAULT_IN_NONPAGED_AREA stop code indicates that Windows tried to access memory that should always be resident (nonpaged) but was not available. This is a generic memory access failure that can be caused by:

• Faulty or unstable drivers
• Disk or file system corruption
• Defective RAM or other hardware issues

On Windows 10/11, unexpected restarts or blue screens with stop codes such as PAGE_FAULT_IN_NONPAGED_AREA are commonly linked to hardware devices, their drivers, or installed software. The stop screen may also show the module name that was executing when the fault occurred, which helps identify a problematic driver or component.

Given the history of a previously faulty motherboard and the fact that SFC is now reporting corruption where it did not before, both software and hardware should be checked systematically:

1. Check for driver or module indicated on the blue screen or in the dump
   • If the stop screen or minidump names a specific driver (for example a storage, graphics, or antivirus driver), update or temporarily remove that driver and retest.
   • If the dump points to a Windows component but not a third‑party driver, treat this as a possible hardware or disk issue as well.
2. Verify system files and component store
   • DISM and SFC are the correct tools. Since DISM reported no issues but SFC did, rerun SFC until it reports no integrity violations. If SFC repeatedly finds corruption, that can indicate underlying disk or hardware problems even when DISM appears clean.
3. Consider stress or verification tools for drivers
   • For driver‑related issues, Driver Verifier can be used to stress drivers and surface faulty ones. Enhanced I/O Verification (part of Driver Verifier’s I/O Verification in Windows 7 and later) can expose I/O‑related driver bugs that might manifest as memory faults. When enabled, violations will show as DRIVER_VERIFIER_IOMANAGER_VIOLATION (BugCheck 0xC9) rather than PAGE_FAULT_IN_NONPAGED_AREA, helping isolate a bad driver.
4. Treat PAGE_FAULT_IN_NONPAGED_AREA as a hardware/driver candidate
   • Microsoft documentation notes that PAGE_FAULT_IN_NONPAGED_AREA is a stop code commonly seen when Windows encounters serious problems, and that the underlying cause is often a hardware device, its driver, or software. Given the prior motherboard replacement and multiple storage devices, RAM and storage (including controllers) should be checked thoroughly with vendor diagnostics and memory tests.
5. Monitor for patterns
   • Note whether the crashes correlate with specific actions (such as file operations on a particular drive, or use of a specific application). If the issue appears when accessing a particular disk or volume, focus on that device and its driver/firmware.

If PAGE_FAULT_IN_NONPAGED_AREA continues to occur after drivers are updated, SFC is clean, and storage and memory diagnostics pass, the pattern of recurring BSODs after a past motherboard failure justifies engaging Dell support again with the minidump and error details for deeper hardware investigation.

References:

• Troubleshooting Windows unexpected restarts and stop code errors
• Enhanced I/O Verification
• "0x0000007E" or "0X00000050" Stop error when you run the Common Scenario Stress with IO test in Windows 7 or in Windows Server 2008 R2
• Stop error in Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2: "0x00000050 PAGE_FAULT_IN_NONPAGED_AREA"
• You receive "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)" or "Stop error code 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)" when you hot-replace memory on a Windows Server 2008-based computer