BSOD 235 (DIRTY_MAPPED_PAGES_CONGESTION): causes and diagnosis

Status / error code:		Category:

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

Could be also:
Constant	Type	OS
ERROR_NO_WORK_DONE	Win32 error	Windows

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. For DIRTY_MAPPED_PAGES_CONGESTION, this indicates that no free pages are available to continue operations.

Important

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 for DIRTY_MAPPED_PAGES_CONGESTION

The file system driver stack has deadlocked and most of the modified pages are destined for the file system. Because the file system is non-operational, the system has crashed because none of the modified pages can be reused without losing data. Any file system or filter driver in the stack may be at fault.

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. For DIRTY_MAPPED_PAGES_CONGESTION, examples of this include mutex deadlocks or accesses to paged out memory in file system drivers or filter drivers. This indicates a driver bug. For DIRTY_MAPPED_PAGES_CONGESTION, if Parameter 1 or Parameter 2 is large, this is a possibility. Use !vm 3 .
A storage driver is not processing requests. Examples of this are stranded queues and unresponsive drives. This indicates a driver bug. For DIRTY_MAPPED_PAGES_CONGESTION, if Parameter 1 or Parameter 2 is large, this is a possibility. Use !process 0 7 .
Windows Server 2003 only: Not enough pool is available for the storage stack to write out modified pages. This indicates a driver bug.

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

Official references for DIRTY_MAPPED_PAGES_CONGESTION

Looking for a different code? Search another status or error code.