What does HRESULT 0x087A0008 (DXGI_STATUS_MODE_CHANGE_IN_PROGRESS) mean?

DXGI_STATUS_MODE_CHANGE_IN_PROGRESS

What Windows rejected: status mode change in progress

DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, value 0x087A0008, is produced by dxgi status when another device was changing full-screen or windowed mode when the caller requested a conflicting operation. The investigation should stay attached to exclusive-mode transition arbitration and to the exact generation in which it was obtained.

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

For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, 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_MODE_CHANGE_IN_PROGRESS.

Separate state from capability

1. Freeze the DXGI_STATUS_MODE_CHANGE_IN_PROGRESS generation. Record SetFullscreenState and ResizeTarget call order, owning HWND, output identity, message-pump state and competing process activity. Before diagnosing DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow DXGI_STATUS_MODE_CHANGE_IN_PROGRESS comparison. start one controlled full-screen transition and issue the second request before the first transition completes. During the DXGI_STATUS_MODE_CHANGE_IN_PROGRESS comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after DXGI_STATUS_MODE_CHANGE_IN_PROGRESS. For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_STATUS_MODE_CHANGE_IN_PROGRESS boundary was crossed.
4. Repeat DXGI_STATUS_MODE_CHANGE_IN_PROGRESS through a lifecycle transition. For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, 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_ERROR_MODE_CHANGE_IN_PROGRESS is especially useful: DXGI_ERROR_MODE_CHANGE_IN_PROGRESS is a failing API result; this status can be returned as nonfatal transition feedback. For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Serialize mode changes, keep the window message pump responsive and retry after the transition settles. Repair of DXGI_STATUS_MODE_CHANGE_IN_PROGRESS 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_MODE_CHANGE_IN_PROGRESS 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 DXGI_STATUS_MODE_CHANGE_IN_PROGRESS; unrelated adapter, monitor and application state remains unchanged.
• For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, debug-layer, ETW or driver diagnostics no longer report the rejected exclusive-mode transition arbitration contract during the same scenario.
• The application handles recurrence of DXGI_STATUS_MODE_CHANGE_IN_PROGRESS without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for DXGI_STATUS_MODE_CHANGE_IN_PROGRESS

For DXGI_STATUS_MODE_CHANGE_IN_PROGRESS, log Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity. When the DXGI_STATUS_MODE_CHANGE_IN_PROGRESS 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_MODE_CHANGE_IN_PROGRESS 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_MODE_CHANGE_IN_PROGRESS.

Technical references

• Microsoft: DXGI status codes — background for the exclusive-mode transition arbitration boundary involved in DXGI_STATUS_MODE_CHANGE_IN_PROGRESS.
• Microsoft: DXGI overview and presentation — background for the exclusive-mode transition arbitration boundary involved in DXGI_STATUS_MODE_CHANGE_IN_PROGRESS.
• Microsoft: DXGI_PRESENT flags — background for the exclusive-mode transition arbitration boundary involved in DXGI_STATUS_MODE_CHANGE_IN_PROGRESS.
• Microsoft: DXGI best practices — background for the exclusive-mode transition arbitration boundary involved in DXGI_STATUS_MODE_CHANGE_IN_PROGRESS.

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