| Previous | Next |
| DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED | DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED
What Windows rejected: surface being rendered
DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED, value 0x88980801, is produced by dcomp when a new rendering operation was requested while BeginDraw state was already active for the surface. The investigation should stay attached to DirectComposition surface update lifetime and to the exact generation in which it was obtained.
This result: DirectComposition batches changes until Commit, while surface drawing has its own BeginDraw/EndDraw lifetime. Treat those two transactions separately in traces and cleanup. The built-in one-line message identifies the immediate result; diagnosis also needs the producing API, object ownership and the display generation current at the time.
Build a useful diagnostic record
| Capture item | Why it matters for it |
|---|---|
| Current graph state | DirectComposition device, target, visual tree and surface update transaction |
| Supporting trace | BeginDraw/EndDraw or target-creation sequence, Commit result, HWND ownership and CheckDeviceState output |
| Object identity | DirectComposition surface update lifetime |
| Rejected boundary | a new rendering operation was requested while BeginDraw state was already active for the surface |
| Decisive capture | surface identity, BeginDraw/EndDraw pairs, update rectangle, drawing thread and exception paths |
Preserve the unsigned HRESULT, symbolic name, first failing API and timestamp in one record. If cleanup later fails too, keep that secondary result separately from this result.
Separate state from capability
- Freeze the result generation. Record surface identity, BeginDraw/EndDraw pairs, update rectangle, drawing thread and exception paths. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. call BeginDraw twice without the matching EndDraw and compare with a balanced update. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
- Observe the layer after it. for it, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the boundary was crossed.
- Repeat it through a lifecycle transition. for it, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that it does not reuse stale handles.
The comparison with DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED is especially useful: DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED is the opposite imbalance. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Verify the repaired path
Serialize surface updates and guarantee EndDraw through structured cleanup before beginning another frame. Repair of it is complete only when the original call succeeds or returns its documented nonfatal status and the same lifetime test remains correct after a second display transition.
- The result trace identifies one producing API and one current graphics object, rather than only the final UI symptom.
- The passing run changes exactly the condition described for it; unrelated adapter, monitor and application state remains unchanged.
- debug-layer, ETW or driver diagnostics no longer report the rejected DirectComposition surface update lifetime contract during the same scenario.
- The application handles recurrence of it without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes
Log BeginDraw/EndDraw or target-creation sequence, Commit result, HWND ownership and CheckDeviceState output. When the path returns a count, size, status flag or replacement object, retain it even on a nonfatal result because it can direct the next call.
A production fallback for it should be explicit: pause rendering, re-enumerate, rebuild one cache entry, recreate a device, or decline a protected path only when this layer calls for that action. Reinstalling every display component, deleting all caches or forcing a resolution change is not an evidence-based fix for it.
Technical references
- Microsoft: DirectComposition error codes — background for the DirectComposition surface update lifetime boundary involved in it.
- Microsoft: DirectComposition reference
- Microsoft: IDCompositionDevice::Commit
- Microsoft: IDCompositionDevice::CheckDeviceState
Looking for a different code? Search another status or error code.