What does HRESULT 0x88980802 (DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED) mean?

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.

DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED: DirectComposition batches changes until Commit, while surface drawing has its own BeginDraw/EndDraw lifetime. For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, Treat those two transactions separately in traces and cleanup. For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, 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 this result actionable

For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.

A controlled comparison

1. Freeze the DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED generation. Record surface identity, last successful BeginDraw, thread ownership, cancellation path and visual commit order. Before diagnosing DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED comparison. invoke EndDraw on a fresh surface, then compare with a correct BeginDraw/EndDraw pair. During the DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED. For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED boundary was crossed.
4. Repeat DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED through a lifecycle transition. For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that this result 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. For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED; unrelated adapter, monitor and application state remains unchanged.
• For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED

For DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED, log BeginDraw/EndDraw or target-creation sequence, Commit result, HWND ownership and CheckDeviceState output. When the DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED 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 DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.

Technical references

• Microsoft: DirectComposition error codes — background for the DirectComposition surface completion state boundary involved in DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.
• Microsoft: DirectComposition reference — background for the DirectComposition surface completion state boundary involved in DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.
• Microsoft: IDCompositionDevice::Commit — background for the DirectComposition surface completion state boundary involved in DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.
• Microsoft: IDCompositionDevice::CheckDeviceState — background for the DirectComposition surface completion state boundary involved in DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED.

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