DIRTY_MAPPED_PAGES_CONGESTION
Code: 0xeb (235)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x00eb (235)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x00eb (235)
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 |
Description
The DIRTY_MAPPED_PAGES_CONGESTION bug check has a value of 0x000000EB. This indicates that no free pages are available to continue operations.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Cause
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. 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, 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.
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.
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0xeb | 78.11011 | %1 |
| dsreg.dll | 0xeb | 11 | Recovery COM notification subscriber reported an error %1 |
| kernel32.dll | 0xeb | 1011 | The action requested resulted in no work being done. Error-style clean-up has been performed. |
| webservices.dll | 0xeb | 78.11011 | Unable to initialize critical section. |
| 4 entries | |||