| Previous | Next |
| DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED | WINCODEC_ERR_WRONGSTATE |
DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED
Locate the failing graphics boundary: surface not being rendered
Windows reports DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED (0x88980802) at the dcomp checkpoint. Here, EndDraw or an equivalent completion action was issued without an active surface rendering operation. That narrows the first investigation to DirectComposition surface completion state instead of the entire GPU stack.
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.
Evidence that makes the result actionable
| Capture item | Why it matters for it |
|---|---|
| Supporting trace | BeginDraw/EndDraw or target-creation sequence, Commit result, HWND ownership and CheckDeviceState output |
| Object identity | DirectComposition surface completion state |
| Rejected boundary | EndDraw or an equivalent completion action was issued without an active surface rendering operation |
| Decisive capture | surface identity, last successful BeginDraw, thread ownership, cancellation path and visual commit order |
| Current graph state | DirectComposition device, target, visual tree and surface update transaction |
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.
A controlled comparison
- Freeze the result generation. Record surface identity, last successful BeginDraw, thread ownership, cancellation path and visual commit order. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow it comparison. invoke EndDraw on a fresh surface, then compare with a correct BeginDraw/EndDraw pair. 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_BEING_RENDERED is especially useful: DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED reports a nested BeginDraw instead of an unmatched EndDraw. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Correction and proof
Track the active update explicitly and call EndDraw exactly once for each successful BeginDraw. 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 completion state 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 completion state boundary involved in it.
- Microsoft: DirectComposition reference
- Microsoft: IDCompositionDevice::Commit
- Microsoft: IDCompositionDevice::CheckDeviceState
Looking for a different code? Search another status or error code.