| Previous | Next |
| FATAL_UNHANDLED_HARD_ERROR | PFN_LIST_CORRUPT |
NO_PAGES_AVAILABLE
The NO_PAGES_AVAILABLE bug check has a value of 0x0000004D. This indicates that no free pages are available to continue operations.
NO_PAGES_AVAILABLE Parameters
| 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. |
Cause and diagnosis
NO_PAGES_AVAILABLE means the memory manager could not obtain pages needed to continue, commonly because dirty-page writers or the storage path stopped making progress. Parameter 1 reports the dirty-page count, Parameter 2 the portion destined for the page file, Parameter 3 the available nonpaged pool, and Parameter 4 the most recent modified-write error status.
Use !vm 3 to establish whether dirty pages or pool pressure dominate. Inspect blocked threads with !process 0 7 and !ready, paying particular attention to file-system filters, storage drivers, and modified-page writer threads. If Parameter 3 is unusually small, use !poolused 2 to identify a nonpaged-pool consumer.
Decode Parameter 4 and correlate it with storage events from the same incident. A persistent write error, a stranded storage queue, and a writer deadlock require different fixes even though all can end with the same shortage of reusable pages.
Official references
Looking for a different code? Search another status or error code.