| Previous | Next |
| DXGI_STATUS_MODE_CHANGE_IN_PROGRESS | DXGI_STATUS_DDA_WAS_STILL_DRAWING |
DXGI_STATUS_UNOCCLUDED
Interpret the result in its owning layer: status unoccluded
Windows reports DXGI_STATUS_UNOCCLUDED (0x087A0009) at the dxgi status checkpoint. Here, DXGI detected that a previously hidden target became visible again. That narrows the first investigation to swap-chain return to visibility instead of the entire GPU stack.
DXGI_STATUS_UNOCCLUDED: A DXGI status can describe a successful or temporarily invisible presentation. For DXGI_STATUS_UNOCCLUDED, Converting every non-S_OK value into device recreation destroys useful state and can create a full-screen transition loop. For DXGI_STATUS_UNOCCLUDED, 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
| Capture item | Why it matters for DXGI_STATUS_UNOCCLUDED |
|---|---|
| Decisive capture | last occluded result, DXGI_PRESENT_TEST cadence, HWND visibility, output attachment and first normal Present result |
| Current graph state | swap chain, target window, output and Present call |
| Supporting trace | Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity |
| Object identity | swap-chain return to visibility |
| Rejected boundary | DXGI detected that a previously hidden target became visible again |
For DXGI_STATUS_UNOCCLUDED, 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 DXGI_STATUS_UNOCCLUDED.
Reproduce one variable at a time
- Freeze the
DXGI_STATUS_UNOCCLUDEDgeneration. Record last occluded result, DXGI_PRESENT_TEST cadence, HWND visibility, output attachment and first normal Present result. Before diagnosingDXGI_STATUS_UNOCCLUDED, do not resize, hot-plug, recreate or release the object under examination. - Run the narrow
DXGI_STATUS_UNOCCLUDEDcomparison. fully cover the window, enter the idle loop, then uncover it and observe the unoccluded notification. During theDXGI_STATUS_UNOCCLUDEDcomparison, keep every driver, monitor, resource format and unrelated policy unchanged. - Observe the layer after
DXGI_STATUS_UNOCCLUDED. ForDXGI_STATUS_UNOCCLUDED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that theDXGI_STATUS_UNOCCLUDEDboundary was crossed. - Repeat
DXGI_STATUS_UNOCCLUDEDthrough a lifecycle transition. ForDXGI_STATUS_UNOCCLUDED, 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 DXGI_STATUS_OCCLUDED is especially useful: DXGI_STATUS_OCCLUDED is the earlier state that should have caused rendering to pause. For DXGI_STATUS_UNOCCLUDED, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Recovery contract
Leave the idle path and resume rendering without recreating the device merely because visibility changed. Repair of DXGI_STATUS_UNOCCLUDED 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
DXGI_STATUS_UNOCCLUDEDtrace 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
DXGI_STATUS_UNOCCLUDED; unrelated adapter, monitor and application state remains unchanged. - For
DXGI_STATUS_UNOCCLUDED, debug-layer, ETW or driver diagnostics no longer report the rejected swap-chain return to visibility contract during the same scenario. - The application handles recurrence of
DXGI_STATUS_UNOCCLUDEDwithout an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes for DXGI_STATUS_UNOCCLUDED
For DXGI_STATUS_UNOCCLUDED, log Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity. When the DXGI_STATUS_UNOCCLUDED 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 DXGI_STATUS_UNOCCLUDED 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 DXGI_STATUS_UNOCCLUDED.
Technical references
- Microsoft: DXGI status codes — background for the swap-chain return to visibility boundary involved in
DXGI_STATUS_UNOCCLUDED. - Microsoft: DXGI overview and presentation — background for the swap-chain return to visibility boundary involved in
DXGI_STATUS_UNOCCLUDED. - Microsoft: DXGI_PRESENT flags — background for the swap-chain return to visibility boundary involved in
DXGI_STATUS_UNOCCLUDED. - Microsoft: DXGI best practices — background for the swap-chain return to visibility boundary involved in
DXGI_STATUS_UNOCCLUDED.
Looking for a different code? Search another status or error code.