Windows 10 blue screen error

Comments (3)


As BSODs go, PAGE FAULT IN NONPAGED AREA is as cthua as Windows comes khổng lồ saying “invalid memory reference.” To really understand what’s going on, one needs lớn understvà paged memory, which divides addressable memory space up into lớn a collection of 4K-sized memory pages. The OS can address a very large number of pages, where only some of those pages will actually be resident in RAM.

Bạn đang xem: Windows 10 blue screen error

In most cases, when a program or the OS references a specific memory page, if it’s not resident in RAM, the page manager throws a “page fault” (page not present) status. Ultimately, this means the requested page gets read from the page file. To make room for something new if room is needed, an old memory page (one that hasn’t been accessed recently) will be swapped out khổng lồ make room for the new page as it gets swapped in.

Certain pages that the OS uses frequently are “locked-in” to lớn RAM. That is, they do not participate in memory paging & should always be present và available when requested. Windows refers lớn this memory allocation as the “Non-paged pool” và it appears as such in Task Manager, as shown below.

The non-paged pool on a PC with 32 GB of physical RAM is only 951 MB. Windows allocates only the barest minimum khổng lồ this collection of “locked-in” memory pages. (Image credit: Tom"s Hardware)

The PAGE FAULT IN NONPAGED AREA BSOD signals a condition where the OS has requested a locked-in page, and gets a page fault instead. The reason why Microsoft handles this as a stop code and generates a BSOD is because this error is not supposed to occur, và it directly affects the operating system (only highly privileged, important memory pages get allocated inlớn the non-paged pool).


As described in the Microsoft Docs page for PAGE FAULT IN NONPAGED AREA, this particular stop code may follow after installation of what it calls “a faulty system service or faulty driver code.” By & large, system services come from Microsoft as part of OS releases, upgrades or updates. If they’re at fault, you’ll figure this out quickly because Microsoft will include this possibility in its “Known Issues” lists for such things. Likewise, there will be plenty of online traffic to report, document, and exclalặng about such problems.

While bad Windows updates bởi happen from time to time, the PAGE FAULT IN NONPAGED AREA code is far more likely khổng lồ come from a faulty driver. To see if the problem is caused by a driver, note the tệp tin listed on the BSOD (ex: nvlddmkm.sys) & consider whether you’ve recently updated a driver or installed a new device.


When it comes lớn faulty system services, the best approach is lớn uninstall (or roll bachồng from) the upgrade or update that caused the problem. If it came from a clean Windows install, it’s time khổng lồ bởi another one, using a different (and known khổng lồ be good and working) OS version instead. See our article on how khổng lồ vày a 30-minute repair reinstall of Windows.

If the problem comes from a driver, first kiểm tra the device manufacturer’s trang web for a newer version of the driver. If so, tải về & install it. If not, try rolling baông xã khổng lồ a prior version. To roll baông chồng a driver:

1. Launch Device Manager.

Xem thêm: Những Lợi Ích Của Việc Làm Việc Nhóm, Khám Phá 7 Lợi Ích Lớn Khi Làm Việc Nhóm

You can get there from the Windows + X thực đơn.

(Image credit: Tom"s Hardware)

However, many devices won’t have sầu the Roll Baông chồng Driver button enabled and, even then, it will only take you bachồng one version. Otherwise, you’ll need lớn hunt for an older driver through the manufacturer’s site (or some reputable third-tiệc nhỏ source, such as the excellent French Station Drivers website).

Look for Disk Problems

Disk errors or specific problems with system files can also cause the PAGE FAULT IN NONPAGED AREA BSOD. In order to lớn rule out or fix these issues:

1. Open a comm& prompt as administrator. You can get there by searching for cmd, right clicking & selecting Run as administrator.

(Image credit: Tom"s Hardware)

2. Enter DISM /Online /Cleanup-image /Restorehealth to find and replace any damaged OS components.

(Image credit: Tom"s Hardware)

These aren’t the most likely cause of a Page Fault in NonPaged Area BSOD, but they are quiông xã và easy steps you can take which may solve sầu the problem.


Other potential causes for the PAGE FAULT IN NONPAGED AREA BSOD include memory problems. This might mean issues with RAM, L1 or L2 cabít on the CPU chip itself, or even video clip RAM on a graphics thẻ. Finding such issues requires a process of elimination. It’s easiest lớn check RAM, và more difficult to lớn check CPU cađậy và đoạn Clip RAM.

The không lấy phí, open-source Memtest86+ utility is a good tool for checking PC RAM. I keep a bootable version of MemTest86+ on my Ventoy repair flash drive sầu (it’s named mt531b.iso, to reflect the most current MemTest86+ version). Using the tool generally requires an overnight run, so I boot khổng lồ the MemTest image just before I go to lớn bed, & let it run all night so I can see what it’s doing (and finding).

Malaysian logger offers an interesting danh sách of 6 không tính phí programs to lớn kiểm tra your đoạn phim thẻ memory for errors. I’m not aware of any tools that kiểm tra CPU cađậy per se, though I did find an interesting StackOverflow cống phẩm that uses DotNet libraries to come cthua kém.

If memory problems are indeed present and none of the other techniques I’ve sầu described lead khổng lồ solutions, keep your eyes peeled for related stop codes. These can help point you more directly at potential causes and fixes: