Your PC freezes, the screen turns blue, and you see the words PAGE_FAULT_IN_NONPAGED_AREA. It feels random and frightening, but it is actually one of the more readable blue screens once you understand what it is telling you. The message means Windows went looking for a piece of data in memory that was supposed to be sitting there — and found nothing. The question is never whether something is wrong; it is which component lost that data.
There are three usual suspects: your RAM, a driver, or your storage drive. The skill that saves you hours is knowing which one to test first instead of blindly reinstalling Windows. If you want the broader context first, our general guide to blue screens in Nigeria and our structured BSOD diagnosis guide cover the wider family of crashes. This article zooms in on this specific stop code.
What the error actually means
Windows keeps some data in a protected pool of memory called the "nonpaged area" — memory that must stay resident and can never be swapped out to the drive. When a process asks for an address in that pool and the data is missing or corrupt, Windows cannot safely continue, so it halts with this blue screen to protect your files.
Because the fault is about data that should have been in memory, the root cause is almost always one of three things: the memory itself is faulty, something wrote bad instructions into that memory (a driver), or the data was corrupted before it even loaded (storage or system files). Your job is to work out which.
The three suspects — and how to read the clues
Before testing anything, look at the blue screen itself. Many versions of this stop code name a specific file ending in .sys — for example a graphics, storage or network driver file. That single line often tells you the answer in seconds, so write it down. Then weigh the suspects:
- RAM — the most common cause. Faulty memory modules or an unstable XMP/EXPO overclocking profile mean the data was never stored reliably in the first place.
- Drivers — a buggy or corrupt driver, most often graphics, storage or network, writes to the wrong place in memory and triggers the fault. A named .sys file points straight here.
- Storage and system files — a failing drive or corrupt Windows files mean the data loaded into memory was already broken, especially common after sudden power loss.
How to decide which to test first
Do not test all three at random. Let what recently changed guide your order:
- If the crashes started after a driver change or update, or the blue screen names a .sys file — start with drivers.
- If they started after fitting new RAM, or after enabling an overclock or XMP/EXPO profile — start with RAM.
- If nothing obvious changed, work in order of effort and likelihood: RAM first (free to test and the most common culprit), then drivers, then storage.
Reading the named file or the crash dump narrows things down faster than any guesswork, so always start there.
Testing RAM first
RAM is the most common cause and costs nothing to rule out, so it is the sensible default. Restart and enter your BIOS, then disable any XMP or EXPO profile so your memory runs at safe stock speeds. If the crashes stop, your modules were simply being pushed too hard — our guide to RAM overclocking with EXPO and XMP in Nigeria explains how to tune that profile properly instead of running it unstable.
If disabling the profile does not help, run MemTest86 from a bootable USB stick and let it complete several full passes overnight. Any errors at all mean a module is faulty. If you have two sticks, test them one at a time to find the bad one. In Lagos heat, also reseat the modules — a half-seated stick in a dusty slot behaves exactly like a failing one.
Testing drivers, then storage
If a .sys file was named, or the trouble began after a driver update, focus here. Cleanly reinstall the suspect driver rather than installing over the top of the old one, and if a recent update caused it, roll that update back. Always download drivers from the chipset or component maker, never a random third-party site. For graphics specifically, our guide to fixing GPU driver crashes walks through a clean reinstall, and our driver update strategy for 2026 explains how to keep them stable long term.
If RAM and drivers are clear, suspect storage. Open Command Prompt as administrator and run chkdsk /f /r to repair the drive, then sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth to repair Windows system files. This matters enormously in Nigeria: a power cut while Windows is mid-write can corrupt system files or a driver, and SFC and DISM are exactly what fix that. Finally, check the drive's SMART health — our guide on how to tell if your hard drive is failing shows the warning signs of a dying drive.
Frequently Asked Questions
The blue screen names a file like nvlddmkm.sys — what do I do? Any .sys file is a driver. In that example it is the NVIDIA graphics driver, so do a clean reinstall of your graphics driver first. The named file is your single best clue, so trust it before testing RAM or storage.
Can a sudden power cut cause this error? Yes, indirectly. If NEPA cuts the power while Windows is writing system files or a driver, those files can be left corrupt, and the next time Windows tries to load them you get this blue screen. Running SFC and DISM repairs the damage. A UPS prevents it happening again.
Should I just reinstall Windows to fix it? Not yet. A reinstall hides faulty RAM or a dying drive without fixing them, so the crashes return. Test RAM and storage health first — if the hardware is sound, the SFC and DISM repairs usually fix it without wiping your data.
The One Thing to Remember
This blue screen is not random — it is a missing-data error with exactly three suspects. Read the named .sys file and ask what changed recently, then test in order: RAM first because it is free and most common, then drivers, then storage. That sequence finds the cause far faster than reinstalling and hoping.
Still crashing after working through all three? It may be a deeper hardware fault that needs hands-on diagnosis. Talk to our team for a proper assessment, or if you have decided your ageing machine has had enough, build a stable new PC with quality RAM and storage chosen to last.