PAGE_FAULT_IN_NONPAGED_AREA is Windows stop code 0x00000050. It means Windows referenced invalid system memory, but the message does not identify one universal cause. A faulty driver or service, antivirus software, NTFS corruption, defective RAM, video memory, cache, or another hardware fault can all be responsible. The safest fix is a controlled sequence: capture the crash evidence, correlate it with Event Viewer, test recent driver or service changes, check memory and storage, repair Windows files, and use Driver Verifier only if the earlier steps do not identify the fault.
What PAGE_FAULT_IN_NONPAGED_AREA means
Microsoft defines PAGE_FAULT_IN_NONPAGED_AREA as bug check 0x00000050. Windows has referenced an invalid address in memory that should have been available immediately. The stop code describes the failure, not the component that caused it.
As an Amazon Associate I earn from qualifying purchases.
The blue screen may display a module name ending in .sys. That name is useful evidence, especially when the same module appears in several crashes, but it is not automatically proof of responsibility. ntoskrnl.exe, for example, is a Windows kernel component that often appears while the kernel is handling a fault caused elsewhere.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsDocumented causes
| Possible source | Why it can produce 0x50 | Most useful first check |
|---|---|---|
| Device or filter driver | Bad pointers, invalid memory access, or incompatible code can corrupt memory used by Windows. | Record the named module, then update or roll back the related device driver from its manufacturer. |
| System service or antivirus software | A service that changed recently can interact with kernel memory or other drivers. | Temporarily disable one suspected service or security product and see whether the crash stops. |
| Physical memory | Defective or unstable RAM can return corrupted data when Windows reads it. | Run Windows Memory Diagnostic and review its result in Event Viewer. |
| Video memory or other hardware | Faulty video RAM, cache, motherboard circuitry, or another component can corrupt memory. | Use the computer maker’s hardware diagnostics and remove recently added hardware for a controlled retest. |
| NTFS volume corruption | File-system errors can make data or metadata unavailable where Windows expects it. | Back up important files, then run chkdsk /f /r. |
Windows 10 and Windows 11 unexpected restarts can result from a hardware device, its driver, or software. If the crash began while launching a game, waking from sleep, or installing an update, that timing is a valuable clue; it does not by itself establish the cause.
#1 Best Overall
- Disclaimer: Maximum Speed requires overclocking/PC BIOS adjustments. Maximum speed and performance depend on system components, including motherboard and CPU
- Hand-sorted memory chips ensure high performance with generous overclocking headroom
- VENGEANCE LPX is optimized for wide compatibility with the latest Intel and AMD DDR4 motherboards
- A low-profile height of just 34mm ensures that VENGEANCE LPX even fits in most small-form-factor builds
- A solid aluminum heatspreader efficiently dissipates heat from each module so that they consistently run at high clock speeds
Before changing anything: preserve evidence and protect your data
- Photograph the blue screen. Capture the exact text, the hexadecimal code, and any “What failed” or
.sysmodule name. Write down whether the crash occurred at startup, during a game, when the computer resumed from sleep, or after an update. - Save unsynced work and back up important files. A disk check and repeated crashes can add stress to a failing drive. Copy irreplaceable saves, documents, and recordings to another drive or a trusted cloud location before deliberately testing storage.
- Change one variable at a time. Updating several drivers, removing multiple services, and changing memory modules together makes it impossible to know which action mattered. Record every change so you can undo it.
- Do not assume that a single crash proves a failed component. The stop code is a symptom. A repeatable pattern and corroborating diagnostic result are needed before replacing RAM, a drive, or a graphics card.
Step 1: use Event Viewer to connect the crash to a component
Event Viewer can show critical events in the same period as the blue screen and may identify a device, service, or driver that was active immediately beforehand.
- Press
Windows, type Event Viewer, and open it. - Expand Windows Logs, select System, and choose Filter Current Log… in the Actions pane.
- Filter for Critical and Error events around the crash time. Also inspect entries from the Windows Memory Diagnostic source later in this guide.
- Open events that mention the same device, driver, service, disk, or bug check. Use the displayed module name as a lead rather than a verdict.
- Write down the event source, Event ID, timestamp, and any device path or driver filename. Those details are more actionable than the generic 0x50 text when you contact the computer or component manufacturer.
If Event Viewer contains only a generic unexpected-shutdown entry, continue with the physical and file-integrity tests. Lack of a named driver does not rule out a driver fault.
Step 2: investigate recent driver, service, and antivirus changes
Update or roll back a device driver
- Right-click Start and open Device Manager.
- Expand the category suggested by the crash pattern: Display adapters for a graphics-related failure, Network adapters for a network-triggered failure, or the relevant audio, storage, USB, or chipset category.
- Right-click the suspected device and choose Properties. On the Driver tab, note the provider, date, and version.
- If the problem began after an update, choose Roll Back Driver when that button is available. Otherwise obtain the current driver from the device or computer manufacturer’s support page and install it according to that vendor’s instructions.
- Restart and test the same action that previously triggered the blue screen. Do not install several unrelated driver packages at once.
For a gaming PC, a repeatable crash only when a particular title starts can point toward the graphics stack, but the same symptom can also come from RAM, storage, or another kernel component. Test rather than infer.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- Simple design to perfectly protect the cooling module with high thermal conductive adhesive
- Supports Intel & AMD motherboards
- Selected high-quality IC
- Supports XMP2.0
- Energy saving with ultra-low working voltage
Test a recently changed service
- Press
Windows+R, entermsconfig, and press Enter. - Open the Services tab. Select Hide all Microsoft services before changing any third-party entry.
- Clear one recently added or suspected service, select Apply, then restart. Reproduce the workload that caused the crash.
- If stability returns, re-enable services individually until the failure reappears. Restore unrelated services when testing is complete.
This controlled approach is reversible. Do not disable Microsoft services indiscriminately; doing so can create new startup problems that obscure the original fault.
Check antivirus changes without leaving the PC unprotected longer than necessary
If the crash started immediately after an antivirus update or configuration change, use that product’s documented pause, rollback, or uninstall option for a short, controlled test. Disconnect from risky networks while protection is paused, reinstall or re-enable protection after the test, and never treat the stop code alone as evidence of malware.
Step 3: test physical memory with Windows Memory Diagnostic
Windows Memory Diagnostic checks physical memory; it does not repair a defective module. Remove any recently installed RAM, overclocking profile, or other memory change temporarily before testing so you can distinguish a new configuration from a component failure.
Rank #3
- Disclaimer: Maximum Speed requires overclocking/PC BIOS adjustments. Maximum speed and performance depend on system components, including motherboard and CPU
- Hand-sorted memory chips ensure high performance with generous overclocking headroom
- VENGEANCE LPX is optimized for wide compatibility with the latest Intel and AMD DDR4 motherboards
- A low-profile height of just 34mm ensures that VENGEANCE LPX even fits in most small-form-factor builds
- A solid aluminum heatspreader efficiently dissipates heat from each module so that they consistently run at high clock speeds
- Save work and close applications.
- Press
Windows+R, typemdsched.exe, and press Enter. Alternatively, search for Windows Memory Diagnostic from Start. - Choose Restart now and check for problems if you can interrupt the current session, or schedule the check for the next restart.
- Allow the test to finish. Windows will reboot automatically.
- After Windows starts, open Event Viewer, go to Windows Logs > System, and find the MemoryDiagnostics-Results event.
An error result is evidence that the memory subsystem is not reliable under the test conditions. Power the computer down, reseat modules only if the manufacturer permits it, test one module or slot at a time using the computer maker’s procedure, and run the manufacturer’s hardware diagnostics. If errors follow one module or remain in one slot, retain the test records and have the confirmed failing part serviced or replaced. A clean Windows Memory Diagnostic result does not exclude video memory, a motherboard fault, a driver, or an intermittent problem.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Step 4: check for NTFS and storage errors with CHKDSK
Microsoft recommends chkdsk /f /r when a corrupted NTFS volume may be involved. The /f switch repairs logical file-system errors; /r locates unreadable sectors and attempts to recover readable information. The scan can take a long time, especially on a large or unhealthy drive.
- Back up important files first. If the drive is making unusual noises, disconnecting, or reporting rapidly increasing errors, prioritize data recovery and professional diagnosis over repeated scans.
- Search for Command Prompt, right-click it, and choose Run as administrator.
- At the elevated prompt, enter
chkdsk C: /f /r, replacingC:with the affected volume letter. - If Windows says the volume is in use and asks to schedule the check at the next restart, type
Y, press Enter, and restart at a convenient time. - Let the operation finish without powering off. Review the result after Windows starts and check whether the original crash pattern returns.
CHKDSK addresses NTFS consistency and readable-sector recovery; it cannot repair defective RAM or a faulty driver. If it reports recurring bad sectors, use the drive manufacturer’s diagnostic and plan for replacement after securing your data.
Rank #4
- Supports Intel Coffee Lake Processors and Intel Extreme Memory Profile (Intel XMP) Standards.
- Aluminum heat sink
- Speeds up to 3200 MT/s / Timing 16-18-18-38 / Voltage 1.35V / Unbuffered / 8GB based
- Backed by a lifetime warranty to promise complete services and technical support.
- Advertised speeds are reached via XMP or the equivalent profile (such as DOCP or A-XMP) in your BIOS profiles. Actual performance varies by system configuration (Motherboard/CPU compatibility). Plug-and-play speeds follow JEDEC standards.
Step 5: repair Windows components and protected system files
Corrupted Windows components can make otherwise valid code fail. Run DISM first, then SFC, from an elevated Command Prompt.
- Open Command Prompt as administrator.
- Run
DISM.exe /Online /Cleanup-image /Restorehealthand wait for it to reach completion. Do not close the window because the percentage may pause while DISM works. - After DISM completes, run
sfc /scannow. - Restart Windows and repeat the workload that previously caused PAGE_FAULT_IN_NONPAGED_AREA.
DISM repairs the Windows component store used for servicing; SFC checks protected system files against that store. If either command reports that it could not complete, record the exact message and use Windows recovery or manufacturer support rather than repeatedly guessing at unrelated drivers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Step 6: use Driver Verifier only for an unresolved driver problem
Driver Verifier is built into Windows and applies additional checks to driver behavior, including memory-resource use. Those checks add overhead and can deliberately trigger a crash when a faulty driver is exercised. Microsoft advises selecting the smallest possible set of drivers; enabling verification for every third-party driver at once creates unnecessary instability and makes the result harder to interpret.
Best Value
- Requires overclocking/BIOS adjustments. Maximum speed and performance depends on system components, including motherboard and CPU.
- G.SKILL RipjawsV Series DDR4 U-DIMM Memory Kit, Model: F4-3200C16D-16GVKB
- Non-ECC, DDR4 U-DIMM, 288-pin, for Desktop PC & Gaming
- Includes JEDEC default profile, and Intel XMP memory overclock profile
- Do not mix memory kits. Memory kits are sold in matched kits that are designed to run together as a set. Mixing memory kits will result in stability issues or system failure.
Configure a narrow test
- Save work and create a restore point if System Protection is enabled.
- Press
Windows+R, typeverifier, and press Enter. - Choose Create standard settings, select the option to choose driver names from a list, and mark only the suspected third-party driver or the smallest related group. Avoid selecting Microsoft-provided drivers unless a support technician directs you to do so.
- Finish the wizard and restart. Use the computer normally or reproduce the specific action that has caused the blue screen.
- If a new crash names the same driver, save the dump and event details, then obtain an updated or rolled-back version from the device manufacturer.
Turn Driver Verifier off after the test
Do not leave verification enabled as a permanent performance setting. Open an elevated Command Prompt and run verifier /reset, then restart. If Windows cannot boot normally, enter Windows Recovery Environment, choose Troubleshoot > Advanced options > Command Prompt, run verifier /reset, and restart. If the command does not clear the configuration, use System Restore or the recovery options offered by your PC manufacturer.
Step 7: recover when the blue screen prevents normal startup
- Interrupt startup two or three times by holding the power button only when Windows is beginning to load. Windows should enter its recovery environment automatically; avoid interrupting a disk check that is already running.
- Select Troubleshoot > Advanced options > Startup Settings > Restart, then choose Safe Mode or Safe Mode with Networking when you need vendor support files.
- In Safe Mode, remove or roll back the change that immediately preceded the crashes, review Event Viewer, and run the DISM/SFC commands if Windows can access them.
- If the machine was stable before a known driver or update, use Troubleshoot > Advanced options > System Restore and select a restore point from before that change. A restore point does not replace a backup and may not exist.
If recovery tools cannot start, stop repeated power cycling and use another computer to obtain the manufacturer’s recovery instructions. Preserve crash dumps and event details for support.
How to interpret the results and choose the next action
| Finding | Likely direction | Next action |
|---|---|---|
A repeated third-party .sys name and the crash began after its update |
Driver or related service | Roll back or update that specific package, then retest. |
| MemoryDiagnostics-Results reports errors | RAM, memory slot, or memory controller | Test modules and slots individually using the manufacturer’s procedure; replace only the confirmed failing part. |
| CHKDSK reports recurring file-system or sector errors | Storage device or NTFS volume | Secure data, run the manufacturer’s storage diagnostic, and plan service or replacement if hardware errors persist. |
| DISM and SFC repair files and crashes stop | Windows component or protected-file corruption | Keep the repaired system under observation and avoid restoring the change that preceded the corruption until verified. |
| All basic tests are clean but Driver Verifier identifies one driver | Subtle driver memory misuse | Remove verification, then update, roll back, or replace that driver and provide the dump to its vendor. |
| Crashes continue across clean drivers, repaired files, and passing software tests | Intermittent hardware or an interaction not yet isolated | Use the computer manufacturer’s full diagnostics and retain all logs before replacing components. |
When hardware replacement is justified
Do not buy RAM, a graphics card, or an SSD solely because the stop code says PAGE_FAULT_IN_NONPAGED_AREA. Replace a component when a repeatable diagnostic identifies it, errors follow that part during isolation, or the manufacturer confirms failure. If the computer is under warranty, provide the stop-code photograph, Event Viewer entries, memory result, CHKDSK output, and any dump files. That evidence can prevent unnecessary replacement of working parts.
Keeping the problem from returning
- Install device drivers from the computer or component manufacturer’s support channel, and keep a record of versions that were stable.
- Apply Windows updates during a maintenance window so a rollback or diagnostic session does not interrupt important work.
- Keep free storage space available and investigate repeated disk warnings promptly.
- Use the system at default memory settings while diagnosing instability; reintroduce performance profiles only after several successful tests.
- Keep current backups of game saves and personal files. A backup protects your data even when the eventual cause is hardware rather than Windows.
PAGE_FAULT_IN_NONPAGED_AREA is best treated as an investigation, not a one-click diagnosis. The most specific evidence wins: a verified driver, a reproducible service change, a memory-test error, or a storage diagnostic result is more useful than the 0x50 label by itself.
Quick Recap
If you prefer an optional shortcut after trying the manual checks, Outbyte PC Repair can look for common Windows issues, including broken system elements, invalid redirects, shared DLL problems, settings that increase CPU, RAM, or disk load, temporary and cache files, privacy risks, missing updates, and potentially unwanted applications. It also includes a real-time boost, file shredder, and app-crash log. It runs on Windows 11, 10, 8, and 7; a free trial is available by category for at least two days, followed by a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
