PAGE_FAULT_IN_NONPAGED_AREA (stop code 0x00000050) is Windows discovering that a piece of memory that must always be present has gone missing. The “nonpaged area” is kernel memory locked into RAM — drivers and the kernel store critical data there precisely because it can never be swapped out. When a driver references an address in that area and the data isn’t valid, Windows crashes rather than act on garbage.

On HP laptops, this crash usually comes down to three stories: a driver passing a bad address (the crash screen often names the .sys file), failing RAM returning garbage for a valid address, or disk corruption in the paging path. The fix order below is built to distinguish those three quickly — because the treatment for each is completely different.

Why this happens

  • Buggy driver referencing invalid memory: A driver bug computes a wrong address in the nonpaged pool. When the crash screen names a .sys file, this is almost certainly your cause.
  • Failing RAM: Bad memory cells return corrupt data for valid addresses. The reference was correct; the RAM lied — and the crash looks identical to a driver bug.
  • Corrupt system files: Damage to memory-management components causes bad references system-wide.
  • Disk errors and pagefile corruption: Bad sectors in paging areas corrupt the data structures tracking nonpaged memory.
  • Antivirus and filter drivers: Kernel-level security software with memory bugs is a known source of bad nonpaged references.
  • Overclocked or unstable RAM: Marginal memory timings corrupt addresses under load — common on HP OMEN/Pavilion Gaming models with XMP enabled.
  • Recently updated drivers: A new driver version introducing a regression right after Windows Update or a manual update.

How to fix it

Work through these in order — use the named file on the crash screen to shortcut the hunt when it’s there.

Fix 1: Note the file named on the blue screen

Free diagnosis, if you caught it.

  1. The next time it crashes, photograph the screen — look for a filename like ntfs.sys, nvlddmkm.sys, or rtwlanu.sys near the stop code.
  2. That file is your prime suspect. Search its name to identify the owning hardware or software.
  3. If no file is named, or it’s ntoskrnl.exe (the kernel itself — usually a red herring for RAM), proceed with memory testing in Fix 3.
  4. A named third-party driver means: update or roll back exactly that driver (Fix 2), and you’re likely done.

Fix 2: Update or roll back the suspect driver via HP

Targeted driver surgery, HP sources first.

  1. Open HP Support Assistant and install all driver updates, or download them from HP Support with your serial number.
  2. If the named driver is graphics-related, do a clean install of HP’s graphics driver: uninstall in Device Manager (tick driver removal), restart, install HP’s version.
  3. If crashes started right after a driver update, use Properties > Driver > Roll Back Driver instead of updating further.
  4. Intel-based HP laptops: the Intel Driver & Support Assistant catches Wi-Fi and chipset updates relevant to memory-reference crashes.

Fix 3: Test your RAM thoroughly

This stop code correlates with bad memory more than most.

  1. Press Win + R, type mdsched.exe, press Enter, choose Restart now and check for problems.
  2. Any error = bad RAM. But clean results don’t fully clear it for this code — run MemTest86 overnight (4+ passes) for the conclusive answer.
  3. If MemTest86 finds errors on socketed RAM, test sticks individually. Soldered RAM errors mean a service visit.
  4. Also disable XMP in the BIOS (F10 at the HP logo) during testing — unstable timings fake hardware failure.

Fix 4: Check the disk and rebuild the pagefile

Paging-path corruption produces this exact crash.

  1. In Terminal (Admin), run chkdsk C: /f /r, confirm with Y, and reboot for the scan.
  2. Check drive health with CrystalDiskInfo or the manufacturer’s SSD tool.
  3. Reset the pagefile: System Properties > Advanced > Performance Settings > Advanced > Virtual memory > Change — set No paging file, reboot, set back to System managed size, reboot again.

Fix 5: Remove or update antivirus and filter drivers

Kernel security software with memory bugs is a classic cause.

  1. If the named .sys file belongs to an antivirus product, update that product to the latest version first.
  2. If crashes persist, uninstall it completely using the vendor’s removal tool (not just the standard uninstall).
  3. Test with Windows Security alone for a few days. If crashes stop, the antivirus driver was guilty — reinstall only the latest version.

Fix 6: Repair system files

Corruption in the memory manager’s own components.

  1. In Terminal (Admin), run sfc /scannow.
  2. Then DISM /Online /Cleanup-Image /RestoreHealth.
  3. Restart. This addresses the “bad reference from corrupt OS components” scenario.

Fix 7: Update the BIOS

HP BIOS updates fix memory-compatibility issues that surface as page faults.

  1. Check your version with msinfo32 and compare against HP Support .
  2. Flash with the charger connected.
  3. BIOS updates also reset memory training — which alone can resolve marginal-RAM page faults.

Fix 8: Clean-boot, then service if needed

Last software isolation before hardware conclusions.

  1. Run msconfig, hide Microsoft services, disable the rest and all startup items, restart, and test.
  2. If clean-boot is stable, bisect to find the conflicting program.
  3. If everything fails and MemTest86 is clean, suspect the motherboard’s memory controller — back up and visit HP service with your test results.
  4. For the sibling memory stop code, see how to fix stop code MEMORY_MANAGEMENT on HP .

Closing

PAGE_FAULT_IN_NONPAGED_AREA on an HP laptop is a “who gave the bad address?” mystery, and the crash screen often hands you the answer in the form of a .sys filename. Named driver? Update or roll it back from HP’s sources. No name, or the kernel blamed? Test the RAM like you mean it — overnight MemTest86, not just the quick check. Work the list in that order and you’ll land on the right fix instead of replacing parts on a hunch. For the broader memory-stop-code family, the MEMORY_MANAGEMENT BSOD guide covers the shared diagnostics.

Frequently asked questions

What does PAGE_FAULT_IN_NONPAGED_AREA mean?
Windows tried to read data from the ’nonpaged area’ — memory that’s supposed to always stay in RAM and never be swapped to disk. The data wasn’t there, which means the reference was wrong (bad driver or corrupt pointer) or the RAM itself failed to return it.
Is PAGE_FAULT_IN_NONPAGED_AREA caused by bad RAM?
Very often, yes — this is one of the most RAM-correlated stop codes. But drivers passing bad memory addresses and disk corruption damaging the pagefile produce the identical crash. Test the RAM, but don’t skip the driver checks.
Why does it name a .sys file on the blue screen?
When Windows can identify which driver made the bad memory reference, it prints the driver’s filename on the crash screen. That file is your prime suspect — update or roll back exactly that driver first.
Can a Windows update cause this error?
Yes. Updates replace drivers, and a new driver version with a memory bug — or a mismatched driver pair after a partial update — triggers this crash. If it started right after an update, roll back the suspect driver or the update itself.