BSOD 77 (NO_PAGES_AVAILABLE): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: NO_PAGES_AVAILABLE identifies a Windows bug check whose dump parameters and stack determine the failing component.

Previous	Next
FATAL_UNHANDLED_HARD_ERROR	PFN_LIST_CORRUPT

NO_PAGES_AVAILABLE

The result bug check has a value of 0x0000004D. This indicates that no free pages are available to continue operations.

Important

Parameter	Description
1	The total number of dirty pages
2	The number of dirty pages destined for the page file
3	The size of the nonpaged pool available at the time the bug check occurred
4	The most recent modified write error status.

To see general memory statistics, use the !vm 3 extension.

This bug check can occur for any of the following reasons:

A driver has blocked, deadlocking the modified or mapped page writers. Examples of this include mutex deadlocks or accesses to paged out memory in file system drivers or filter drivers. This indicates a driver bug. If Parameter 1 or Parameter 2 is large, then this is a possibility. Use !vm 3.
A storage driver is not processing requests. Examples of this are stranded queues and non-responding drives. This indicates a driver bug. process 0 7.
This situation is difficult to analyze. Try using !ready. Try also !process 0 7 to list all threads and see if any have accumulated excessive kernel time as well as what their current priorities are. Such processes may have blocked out the memory management threads from making pages available.
This indicates a driver bug.

If Parameter 3 is small, then this is a possibility. Use !vm and !poolused 2.

If the problem cannot be found, then try booting with a kernel debugger attached from the beginning, and monitor the situation.