What does HRESULT 0x887A0036 (DXGI_ERROR_ALREADY_EXISTS) mean?

DXGI_ERROR_ALREADY_EXISTS

Locate the failing graphics boundary: already exists

Windows reports DXGI_ERROR_ALREADY_EXISTS (0x887A0036) at the dxgi error checkpoint. Here, creation requested an element whose identity is already present in the relevant DXGI collection. That narrows the first investigation to DXGI-managed named or keyed element instead of the entire GPU stack.

DXGI_ERROR_ALREADY_EXISTS: Do not erase all shader caches or recreate every graphics object before preserving the first failing call. For DXGI_ERROR_ALREADY_EXISTS, Cache, policy, remote-session and device-lifetime failures have different recovery rules. For DXGI_ERROR_ALREADY_EXISTS, 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.

Evidence that makes this result actionable

For DXGI_ERROR_ALREADY_EXISTS, 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_ERROR_ALREADY_EXISTS.

A controlled comparison

1. Freeze the DXGI_ERROR_ALREADY_EXISTS generation. Record element name or key, factory/device identity, creation call, existing object lifetime and concurrent creators. Before diagnosing DXGI_ERROR_ALREADY_EXISTS, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow DXGI_ERROR_ALREADY_EXISTS comparison. run two synchronized creators with the same identifier and then repeat with a unique identifier. During the DXGI_ERROR_ALREADY_EXISTS comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after DXGI_ERROR_ALREADY_EXISTS. For DXGI_ERROR_ALREADY_EXISTS, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_ERROR_ALREADY_EXISTS boundary was crossed.
4. Repeat DXGI_ERROR_ALREADY_EXISTS through a lifecycle transition. For DXGI_ERROR_ALREADY_EXISTS, 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_NAME_ALREADY_EXISTS is especially useful: DXGI_ERROR_NAME_ALREADY_EXISTS is the older named-resource result and may arise from a different API family. For DXGI_ERROR_ALREADY_EXISTS, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Correction and proof

Reuse the existing object when contracts match or allocate a unique name; do not delete unrelated cache or device state. Repair of DXGI_ERROR_ALREADY_EXISTS 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_ERROR_ALREADY_EXISTS 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_ERROR_ALREADY_EXISTS; unrelated adapter, monitor and application state remains unchanged.
• For DXGI_ERROR_ALREADY_EXISTS, debug-layer, ETW or driver diagnostics no longer report the rejected DXGI-managed named or keyed element contract during the same scenario.
• The application handles recurrence of DXGI_ERROR_ALREADY_EXISTS without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for DXGI_ERROR_ALREADY_EXISTS

For DXGI_ERROR_ALREADY_EXISTS, log DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters. When the DXGI_ERROR_ALREADY_EXISTS 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_ERROR_ALREADY_EXISTS 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_ERROR_ALREADY_EXISTS.

Technical references

• Microsoft: DXGI error codes — background for the DXGI-managed named or keyed element boundary involved in DXGI_ERROR_ALREADY_EXISTS.
• Microsoft: DXGI overview — background for the DXGI-managed named or keyed element boundary involved in DXGI_ERROR_ALREADY_EXISTS.
• Microsoft: Direct3D 12 shader cache StoreValue — background for the DXGI-managed named or keyed element boundary involved in DXGI_ERROR_ALREADY_EXISTS.
• Microsoft: Handle device-removed scenarios — background for the DXGI-managed named or keyed element boundary involved in DXGI_ERROR_ALREADY_EXISTS.

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