What does BSOD 253 (DIRTY_NOWRITE_PAGES_CONGESTION) mean?

 
Previous Next
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY BUGCODE_USB_DRIVER

DIRTY_NOWRITE_PAGES_CONGESTION

Dirty no-write page congestion for DIRTY_NOWRITE_PAGES_CONGESTION

DIRTY_NOWRITE_PAGES_CONGESTION is bug check code 0x000000FD. This memory-management bug check points at dirty pages that are not eligible or able to be written back, causing the system to run out of usable memory-management options. Storage, paging, cache manager, file systems, and filters can all be involved.

How to read it in a dump for DIRTY_NOWRITE_PAGES_CONGESTION

  • Look at dirty-page, modified-page writer, and storage stack state.
  • This is not simply low free RAM; the writeback path and page attributes matter.
  • File-system or filter drivers can keep pages dirty or unwritable.

What to check for DIRTY_NOWRITE_PAGES_CONGESTION

  • Inspect storage errors, modified page writer state, and file-system filter drivers.
  • Check paging file configuration and disk health.
  • Use a full kernel dump because page lists and file objects are central.

References for DIRTY_NOWRITE_PAGES_CONGESTION

Dump evidence for DIRTY_NOWRITE_PAGES_CONGESTION

For DIRTY_NOWRITE_PAGES_CONGESTION, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “DIRTY_NOWRITE_PAGES_CONGESTION”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for DIRTY_NOWRITE_PAGES_CONGESTION

  • Run WinDbg !analyze -v, then inspect the documented meaning of each DIRTY_NOWRITE_PAGES_CONGESTION parameter instead of relying only on the probably-caused-by line.
  • For DIRTY_NOWRITE_PAGES_CONGESTION, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with dirty / nowrite / pages / congestion.
  • For DIRTY_NOWRITE_PAGES_CONGESTION, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by DIRTY_NOWRITE_PAGES_CONGESTION before collecting the dump and event logs. For DIRTY_NOWRITE_PAGES_CONGESTION, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for DIRTY_NOWRITE_PAGES_CONGESTION

For DIRTY_NOWRITE_PAGES_CONGESTION, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “DIRTY_NOWRITE_PAGES_CONGESTION”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for DIRTY_NOWRITE_PAGES_CONGESTION

  • Run WinDbg !analyze -v, then inspect the documented meaning of each DIRTY_NOWRITE_PAGES_CONGESTION parameter instead of relying only on the probably-caused-by line.
  • For DIRTY_NOWRITE_PAGES_CONGESTION, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with dirty / nowrite / pages / congestion.
  • For DIRTY_NOWRITE_PAGES_CONGESTION, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by DIRTY_NOWRITE_PAGES_CONGESTION before collecting the dump and event logs. For DIRTY_NOWRITE_PAGES_CONGESTION, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

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