| Previous | Next |
| DXGI_STATUS_DDA_WAS_STILL_DRAWING | MSG_CI_MASTER_MERGE_STARTED |
DXGI_STATUS_PRESENT_REQUIRED
Interpret the result in its owning layer: status present required
The useful interpretation of DXGI_STATUS_PRESENT_REQUIRED (0x087A002F) starts at the dxgi status boundary: the operation succeeded but DXGI requires another Present at the next vertical synchronization even when application content did not change. In practical terms, inspect next-v-sync presentation contract 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
| Capture item | Why it matters for it |
|---|---|
| Supporting trace | Present/Present1 result history, WM_SIZE or WM_DISPLAYCHANGE messages, swap-chain description and current IDXGIOutput identity |
| Object identity | next-v-sync presentation contract |
| Rejected boundary | the operation succeeded but DXGI requires another Present at the next vertical synchronization even when application content did not change |
| Decisive capture | swap-chain type, Present flags, v-sync interval, dirty-rectangle usage and the first status following the successful call |
| Current graph state | swap chain, target window, output and Present call |
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
- Freeze the result generation. Record swap-chain type, Present flags, v-sync interval, dirty-rectangle usage and the first status following the successful call. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. honor the requested next-v-sync Present and compare display behavior with a run that intentionally omits it. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
- 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.
- 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 S_OK is especially useful: S_OK does not carry the additional obligation to present again. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Recovery contract
Schedule the required follow-up present while retaining the current device and resources. 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 next-v-sync presentation contract 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 next-v-sync presentation contract 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.