Comparison reviews

How to fix the “page fault in non-paged area” blue screen in Windows 10

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 non-paged pool on a PC with 32 GB of physical RAM is only 951 MB. Windows only allocates the least amount of memory for this set of “locked” memory pages. (Image source: techy’s hardware)

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?

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button