How to Fix PAGE_FAULT_IN_NONPAGED_AREA on a Lenovo Laptop

PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) means Windows reached for data that was supposed to be locked in physical memory — and it was not there, or it was corrupted. It is one of the most common blue screens on Lenovo laptops, and the cause splits three ways: bad RAM, a bad driver, or a bad disk. The fixes below help you figure out which one you have.

Pay attention to the pattern: same driver named every time means driver; random crashes mean RAM; crashes during disk-heavy work mean disk.

Why this happens

• Defective RAM: Bad memory cells corrupt or lose data in the nonpaged pool — the most literal cause.
• Faulty drivers referencing bad addresses: A driver tries to read memory that was freed or never allocated, triggering the fault.
• Antivirus filter drivers: These live in the nonpaged area; buggy versions crash it directly.
• Corrupted page file or disk errors: Damage to the pagefile.sys or system files on bad sectors surfaces as page faults.
• Overclocked or mismatched RAM: Unstable memory timings corrupt kernel memory regions.
• Failing SSD/HDD: A dying drive returns garbage instead of data, which the memory manager reads as a fault.
• Corrupted system files: Damaged Windows memory-management components fault on their own data.

How to fix it

Work through these in order, starting at Fix 1.

Fix 1: Note the faulting driver from the crash dump

The dump often hands you the answer on a plate.

1. Press Win + R, type %SystemRoot%\Minidump, press Enter, and open the newest dump in BlueScreenView (free, NirSoft).
2. If a specific .sys file is highlighted (e.g. ntfs.sys, nvlddmkm.sys, a VPN/antivirus driver), that driver is your prime suspect — skip to Fix 3 with that name in hand.
3. If every dump blames something different, or just ntoskrnl.exe, suspect RAM or disk instead and continue to Fix 2.

The update-related variant is covered in our PAGE_FAULT_IN_NONPAGED_AREA after Windows 11 update guide .

Fix 2: Test the RAM thoroughly

The definitive hardware check — do not skip it.

1. Press Win + R, type mdsched.exe, press Enter → Restart now and check for problems.
2. For a deeper test, consider MemTest86 booted from USB (free) — it catches errors Windows’ built-in test misses.
3. Check results in Event Viewer > Windows Logs > System under source MemoryDiagnostics-Results.
4. Errors found → reseat the sticks; if errors persist, replace the faulty module (Fix 7). Clean → move to Fix 3.

Fix 3: Update or roll back the suspect driver

1. Open Device Manager (Win + X > Device Manager).
2. If the dump named a driver, find its device → right-click → Update driver > Search automatically for drivers.
3. Then run Lenovo Vantage > System Update for Lenovo-validated versions of chipset, storage, and graphics drivers.
4. If crashes began after a recent driver update, use Properties > Driver > Roll Back Driver instead.
5. Restart and stress-test with the workload that used to trigger the crash.

Fix 4: Remove third-party antivirus temporarily

A fast, high-value diagnostic for this specific stop code.

1. Settings > Apps > Installed apps → uninstall your third-party antivirus. Windows Security activates automatically.
2. Restart and use the laptop normally for a day or two, including the workload that triggered crashes.
3. If crashes stop, the antivirus filter driver was at fault — reinstall only the latest version from the vendor’s site, or stay with Windows Security.
4. Related memory-class crashes are covered in our MEMORY_MANAGEMENT BSOD guide .

Fix 5: Disable automatic paging and check the disk

Rebuild the page file and verify the drive behind it.

1. Press Win + R, type sysdm.cpl, press Enter → Advanced → Performance Settings → Advanced → Change under Virtual memory.
2. Uncheck Automatically manage, select No paging file, click Set, restart. Then return and re-enable Automatically manage paging file size — this forces Windows to build a fresh pagefile.sys.
3. Open Terminal (Admin) and run chkdsk C: /f /r (type Y, restart to run).
4. If CHKDSK finds bad sectors, back up immediately — and check SSD health with Lenovo Vantage’s hardware scan.

Fix 6: Repair system files

1. In Terminal (Admin) (Win + X > Terminal (Admin)), run sfc /scannow.
2. Then DISM /Online /Cleanup-Image /RestoreHealth.
3. Restart and retest. These repair the Windows memory-management components themselves when they are the corrupted party.

Fix 7: Reseat or replace RAM, update BIOS

The hardware endgame.

1. If memory tests reported errors and your Lenovo model has SODIMM slots (many ThinkPad T/P and Legion models do), power off, reseat the sticks firmly, and retest one at a time to isolate the bad module.
2. Replace with matching memory. If soldered (Yoga, thin IdeaPad), contact Lenovo support — back up first.
3. Update the BIOS via Lenovo Vantage > System Update or the Lenovo support site — firmware memory-training fixes resolve marginal-RAM crashes.
4. Microsoft’s general crash guidance is on the Windows support page .

Fix 8: Update the BIOS and run Lenovo’s hardware scan

The last firmware-and-hardware pass for stubborn 0x50 crashes.

1. Update the BIOS via Lenovo Vantage > System Update — memory-training improvements in newer firmware resolve marginal-RAM page faults that software cannot.
2. In Lenovo Vantage, go to Device > Device diagnostics (or Hardware Scan) and run the full storage and memory scans, not just the quick test.
3. For the drive specifically, check its SMART health in the scan results: reallocated sectors or a dropping health percentage means the drive is the fault source — back up and replace it.
4. If all hardware passes and crashes continue, consider a clean Windows reinstall as the final software step: back up, create installation media, and install fresh rather than layering more repairs on a damaged system.

Closing

PAGE_FAULT_IN_NONPAGED_AREA demands that you read the pattern before reaching for the screwdriver: a consistently named driver means update or roll back that driver; chaos across dumps means test the RAM; disk-heavy triggers mean check the drive. On Lenovo laptops, the Vantage update tool plus a proper memory test resolves the vast majority of 0x50 crashes without any hardware spending — and when the memory test does fail, at least you know exactly what to replace instead of guessing.

Frequently asked questions