What does HRESULT 0x087A0002 (DXGI_STATUS_CLIPPED) mean?

DXGI_STATUS_CLIPPED

Interpret the result in its owning layer: status clipped

The useful interpretation of DXGI_STATUS_CLIPPED (0x087A0002) starts at the dxgi status boundary: the frame was accepted while only part of the swap-chain target was visible. In practical terms, inspect presentation clipping state before changing application-wide graphics settings.

This result: A DXGI status can describe a successful or temporarily invisible presentation. Converting every non-S_OK value into device recreation destroys useful state and can create a full-screen transition loop. 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.

Capture before recreating objects

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.

Reproduce one variable at a time

1. Freeze the result generation. Record window rectangle, clipping region, desktop scaling, output rectangle and Present statistics around the transition. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow this result comparison. move another top-level window over only part of the target and compare with full occlusion. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. 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.
4. 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 DXGI_STATUS_OCCLUDED is especially useful: DXGI_STATUS_OCCLUDED means no part of the presentation was visible. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Recovery contract

Treat the status as visibility feedback, not as a device failure; continue or reduce work according to application policy. 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 presentation clipping 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 Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity. 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: DXGI status codes — background for the presentation clipping state boundary involved in it.
• Microsoft: DXGI overview and presentation
• Microsoft: DXGI_PRESENT flags
• Microsoft: DXGI best practices

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