| Previous | Next |
| DXGI_STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE | DXGI_STATUS_MODE_CHANGE_IN_PROGRESS |
DXGI_STATUS_MODE_CHANGED
Interpret the result in its owning layer: status mode changed
The useful interpretation of DXGI_STATUS_MODE_CHANGED (0x087A0007) starts at the dxgi status boundary: a display-mode change invalidated the first visibility attempt and DXGI retried presentation under the new mode. In practical terms, inspect swap-chain display-mode synchronization before changing application-wide graphics settings.
DXGI_STATUS_MODE_CHANGED: A DXGI status can describe a successful or temporarily invisible presentation. For DXGI_STATUS_MODE_CHANGED, Converting every non-S_OK value into device recreation destroys useful state and can create a full-screen transition loop. For DXGI_STATUS_MODE_CHANGED, 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_MODE_CHANGED |
|---|---|
| Object identity | swap-chain display-mode synchronization |
| Rejected boundary | a display-mode change invalidated the first visibility attempt and DXGI retried presentation under the new mode |
| Decisive capture | old and new output modes, WM_DISPLAYCHANGE/WM_SIZE order, swap-chain dimensions, refresh rate and Present statistics |
| 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 |
For DXGI_STATUS_MODE_CHANGED, 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_CHANGED.
Reproduce one variable at a time
- Freeze the
DXGI_STATUS_MODE_CHANGEDgeneration. Record old and new output modes, WM_DISPLAYCHANGE/WM_SIZE order, swap-chain dimensions, refresh rate and Present statistics. Before diagnosingDXGI_STATUS_MODE_CHANGED, do not resize, hot-plug, recreate or release the object under examination. - Run the narrow
DXGI_STATUS_MODE_CHANGEDcomparison. change resolution or rotate the output during presentation and compare with a stable-mode run. During theDXGI_STATUS_MODE_CHANGEDcomparison, keep every driver, monitor, resource format and unrelated policy unchanged. - Observe the layer after
DXGI_STATUS_MODE_CHANGED. ForDXGI_STATUS_MODE_CHANGED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that theDXGI_STATUS_MODE_CHANGEDboundary was crossed. - Repeat
DXGI_STATUS_MODE_CHANGEDthrough a lifecycle transition. ForDXGI_STATUS_MODE_CHANGED, 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_MODE_CHANGE_IN_PROGRESS is especially useful: DXGI_STATUS_MODE_CHANGE_IN_PROGRESS means a competing transition is still underway. For DXGI_STATUS_MODE_CHANGED, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Recovery contract
Refresh cached output information and resize buffers when the window receives the mode-change notifications. Repair of DXGI_STATUS_MODE_CHANGED 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_CHANGEDtrace 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_CHANGED; unrelated adapter, monitor and application state remains unchanged. - For
DXGI_STATUS_MODE_CHANGED, debug-layer, ETW or driver diagnostics no longer report the rejected swap-chain display-mode synchronization contract during the same scenario. - The application handles recurrence of
DXGI_STATUS_MODE_CHANGEDwithout an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes for DXGI_STATUS_MODE_CHANGED
For DXGI_STATUS_MODE_CHANGED, log Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity. When the DXGI_STATUS_MODE_CHANGED 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_CHANGED 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_CHANGED.
Technical references
- Microsoft: DXGI status codes — background for the swap-chain display-mode synchronization boundary involved in
DXGI_STATUS_MODE_CHANGED. - Microsoft: DXGI overview and presentation — background for the swap-chain display-mode synchronization boundary involved in
DXGI_STATUS_MODE_CHANGED. - Microsoft: DXGI_PRESENT flags — background for the swap-chain display-mode synchronization boundary involved in
DXGI_STATUS_MODE_CHANGED. - Microsoft: DXGI best practices — background for the swap-chain display-mode synchronization boundary involved in
DXGI_STATUS_MODE_CHANGED.
Looking for a different code? Search another status or error code.