HRESULT 0x087A002F (DXGI_STATUS_PRESENT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The present succeeded but the caller should present again on the next V-sync, even if there are no changes to the content.

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.

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

For DXGI_STATUS_PRESENT_REQUIRED, 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_PRESENT_REQUIRED.

Reproduce one variable at a time

Freeze the DXGI_STATUS_PRESENT_REQUIRED generation. Record swap-chain type, Present flags, v-sync interval, dirty-rectangle usage and the first status following the successful call. Before diagnosing DXGI_STATUS_PRESENT_REQUIRED, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow DXGI_STATUS_PRESENT_REQUIRED comparison. honor the requested next-v-sync Present and compare display behavior with a run that intentionally omits it. During the DXGI_STATUS_PRESENT_REQUIRED comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after DXGI_STATUS_PRESENT_REQUIRED. For DXGI_STATUS_PRESENT_REQUIRED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_STATUS_PRESENT_REQUIRED boundary was crossed.
Repeat DXGI_STATUS_PRESENT_REQUIRED through a lifecycle transition. For DXGI_STATUS_PRESENT_REQUIRED, 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 S_OK is especially useful: S_OK does not carry the additional obligation to present again. For DXGI_STATUS_PRESENT_REQUIRED, 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 DXGI_STATUS_PRESENT_REQUIRED 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_PRESENT_REQUIRED 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_PRESENT_REQUIRED; unrelated adapter, monitor and application state remains unchanged.
For DXGI_STATUS_PRESENT_REQUIRED, 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 DXGI_STATUS_PRESENT_REQUIRED without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `DXGI_STATUS_PRESENT_REQUIRED`

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

Technical references

Microsoft: DXGI status codes — background for the next-v-sync presentation contract boundary involved in DXGI_STATUS_PRESENT_REQUIRED.
Microsoft: DXGI overview and presentation — background for the next-v-sync presentation contract boundary involved in DXGI_STATUS_PRESENT_REQUIRED.
Microsoft: DXGI_PRESENT flags — background for the next-v-sync presentation contract boundary involved in DXGI_STATUS_PRESENT_REQUIRED.
Microsoft: DXGI best practices — background for the next-v-sync presentation contract boundary involved in DXGI_STATUS_PRESENT_REQUIRED.

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