As Blue screen of death Go, page faults in non-page areas are as close as Windows says “invalid memory reference”. To really understand what is going on, you need to understand paging memory, which divides the addressable memory space into a set of 4K memory pages. The operating system can address a very large number of pages, only some of which actually reside in RAM.
In most cases, when a program or operating system refers to a specific memory page, if it is not in RAM, the page manager will throw a “page fault” (page does not exist) status. Ultimately, this means reading the requested page from the page file. To make room for new pages when space is needed, old memory pages (pages that have not been visited recently) will be swapped out to make room for new pages when new pages are swapped in.
Certain pages frequently used by the operating system are “locked” in RAM. That is, they do not participate in memory paging, and should always exist and be available when requested. Windows refers to this memory allocation as “non-paged pool” and it appears as such in the Task Manager as shown below.
The PAGE FAULT in the non-page area BSOD indicates that the operating system has requested to lock the page and changed to get a page fault. The reason why Microsoft treats it as a stop code and generates a BSOD is because this error shouldn’t happen, and it directly affects the operating system (only highly privileged, important memory pages will be allocated to the non-paged pool).
What causes page faults in non-page areas?
As mentioned in Microsoft documentation page For page faults in non-page areas, this specific stop code may appear after installing what it calls “wrong system service or wrong driver code”. Generally speaking, system services come from Microsoft as part of the operating system release, upgrade or update. If they are at fault, you will quickly figure it out because Microsoft will include this possibility in the list of “known issues” for such things. Likewise, there will be a large amount of online traffic to report, record and exclaim such problems.
Although faulty Windows updates sometimes occur, page faults in non-page area codes are more likely to come from faulty drivers. To see if the problem is caused by the driver, please pay attention to the file listed on the BSOD (for example: nvlddmkm.sys) and consider whether you have recently updated the driver or installed a new device.
How to fix page faults in non-page area BSOD
When it comes to faulty system services, the best approach is to uninstall (or roll back) the upgrade or update that caused the problem. If it comes from a clean Windows installation, then it’s time to do another one, using a different (and known to be good and working) operating system version instead.Please refer to our article to learn how to do it Repair and reinstall Windows in 30 minutes.
If the problem comes from the driver, first check the device manufacturer’s website to obtain an updated version of the driver. If so, please download and install it. If not, try to roll back to the previous version. To roll back the driver:
1. Start the device manager. You can get there from the Windows + X menu.
2. Right-click the relevant device and select Properties.
3. Click the Roll Back Driver button.
However, many devices will not enable the “Roll Back Driver” button, and even so, it will only return you to a version. Otherwise, you will need to go through the manufacturer’s website (or some reputable third-party source, such as the excellent French Station driver website).
Find disk problems
Disk errors or specific problems with system files can also cause page faults in the blue screen of non-page areas. In order to eliminate or solve these problems:
1. Open a command prompt as an administratorYou can get there by searching for cmd, right-clicking and selecting run as administrator.
2. Enter DISM /online/Cleanup-image /Restorehealth Find and replace any damaged operating system components.
3. Enter SFC/Scan Check for damaged system files.
These are not the most likely causes of page faults in the non-paged area BSOD, but they are quick and easy steps you can take to solve the problem.
Memory may be the cause of BSOD page failure in non-page area
Other potential causes of BSOD page failures in non-page areas include memory problems. This may mean that there is a problem with the RAM on the CPU chip itself, the L1 or L2 cache, or even the video RAM on the graphics card. Finding such problems requires a process of elimination. It is easiest to check RAM, but it is more difficult to check CPU cache and video RAM.
Free, open source Memtest86+ utility It is a good tool for checking PC RAM. I kept a bootable version of MemTest86+ on my Ventoy repair flash drive (it was named mt531b.iso to reflect the latest MemTest86+ version). The tool usually needs to be run overnight, so I boot into the MemTest image before going to bed and let it run all night so that I can see what it is doing (and discovering).
Malaysian recorder Raymond.cc provides an interesting list 6 free programs to check your video card memory for errors. I don’t know of any tool that can check the CPU cache itself, but I did find an interesting one StackOverflow item Use DotNet library to approach.
If there is a memory problem and none of the other techniques I describe has a solution, please pay close attention to the relevant stop code. These can help you point out potential causes and repair methods more directly: