| 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 context
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.
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.
Evidence to preserve
- Exact DWM API and arguments
- Session, desktop, HWND lifecycle, and process architecture
- Graphics device-removal or TDR evidence
- DWM, Application, and System event timeline
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.
- 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.
- Preserve logs before restarting DWM-dependent components or the session.
Technical references
Looking for a different code? Search another status or error code.