| Previous | Next |
| DWMERR_THEME_FAILED | DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
DWMERR_CATASTROPHIC_FAILURE
The scope of DWMERR_CATASTROPHIC_FAILURE is a severe DWM internal failure. DWM encountered a severe internal failure for which the public API exposes no narrower recovery code. Keep 0x88980702 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.
Subsystem boundary
When it is returned, a catastrophic DWM result is intentionally broad. It should trigger preservation of the first API call, session and desktop state, graphics device events, window lifetime, and DWM-related event records before restarts erase the sequence. Narrower DWM theme or transition errors should not be collapsed into this catch-all.
Inspect the following boundary: the first DWM call, composition event, device event, or service transition preceding the catch-all status.
Do not hide the original condition
This is broader than THEME_FAILED or STATE_TRANSITION_FAILED; those should be preferred whenever their narrower condition is observed. Do not assume the application can safely continue issuing the same DWM calls after a catastrophic result without rebuilding its dependent state.
Facts worth preserving
| Record | Why it matters here |
|---|---|
| Exact DWM API and arguments | Preserving exact DWM API and arguments provides the evidence needed to test this distinction: this is broader than THEME_FAILED or STATE_TRANSITION_FAILED; those should be preferred whenever their narrower condition is observed. |
| Session, desktop, HWND lifecycle, and process architecture | Recording session, desktop, HWND lifecycle, and process architecture separates the a severe DWM internal failure boundary from a later wrapper symptom. |
| Graphics device-removal or TDR evidence | In this result diagnostics, recording graphics device-removal or TDR evidence ties the HRESULT to the a severe DWM internal failure boundary rather than to the final visible failure. |
| DWM, Application, and System event timeline | Comparing DWM, Application, and System event timeline shows whether this result follows input, object state, or environment. |
Isolation procedure
Reproduce with a single window and one documented DWM call, then compare another process in the same session and the same process in another session., this separates application state from compositor-session or device-wide failure.
- When it is returned, reproduce with a minimal top-level window and one DWM operation.
- Remove unsupported hooks and custom composition paths.
- check whether the failure is session-wide or process-specific.
- When it is returned, preserve logs before restarting DWM-dependent components or the session.
What each result would imply
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If this result disappears with a smaller faithful case, complexity within a severe DWM internal failure is implicated. | Keep exact DWM API and arguments fixed while simplifying graphics device-removal or TDR evidence. |
| Same input, fresh object generation | If this result changes after rebuilding state, examine ownership across the caller’s HWND lifecycle, DWM attribute or transition request, theme layer, and compositor session. | Place session, desktop, HWND lifecycle, and process architecture on the timeline of the last successful transition. |
| Same operation on a controlled second path | If this result follows one environment, the failure is not explained by source data alone. | Compare desktop and session, composition state, active theme, window generation, and graphics event timeline while preserving DWM, Application, and System event timeline. |
Verification after repair
A correction for it should let the operation at the a severe DWM internal failure boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Reproduce with a minimal top-level window and one DWM operation” and confirm that the following lifecycle step also succeeds. Keep the original failing sample and one deliberate negative case so fallback cannot be mistaken for repair.
Technical references
When it is returned, these references define the public API family, object model, or error list used to interpret this status.
- Microsoft: COM error codes for Input and graphics.
- Microsoft: Desktop Window Manager API.
- Microsoft: DwmSetWindowAttribute.
- Microsoft: DWM composition overview.
Looking for a different code? Search another status or error code.