| Previous | Next |
| THREAD_STUCK_IN_DEVICE_DRIVER | SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT |
DIRTY_MAPPED_PAGES_CONGESTION
The DIRTY_MAPPED_PAGES_CONGESTION bug check has a value of 0x000000EB. This indicates that no free pages are available to continue operations.
DIRTY_MAPPED_PAGES_CONGESTION Parameters
| Parameter | Description |
|---|---|
1 |
The total number of dirty pages |
2 |
The number of dirty pages destined for the page file |
3 |
Windows Server 2003 only: The size of the nonpaged pool available at the time of the bug check (in pages) Windows Vista and later versions: Reserved |
4 |
Windows Server 2003 only: The number of transition pages that are currently stranded Windows Vista and later versions: The most recent modified write error status |
Cause and diagnosis
The memory manager could not recycle dirty mapped pages because the write path stopped making progress. A blocked file-system or filter driver, a stalled storage request path, or a modified-page writer deadlock can leave too few clean pages available without the system being simply “out of RAM.”
Compare Parameter 1 (all dirty pages) with Parameter 2 (dirty pages destined for the page file). On Windows Vista and later, Parameter 4 is the most recent modified-write error status and should be decoded before blaming memory pressure. On older systems, interpret Parameters 3 and 4 according to the documented version-specific meanings in the table above.
Use !vm 3 to measure modified-page pressure, then inspect blocked writers and storage/file-system stacks with !process 0 7. If nonpaged-pool pressure is also implicated, !poolused 2 can help identify the owner. Preserve the write status and blocked stacks from the same dump so a storage stall is not confused with a pool or file-system deadlock.
Official references
Looking for a different code? Search another status or error code.