What does HRESULT 0x887B0003 (DXGI_DDI_ERR_NONEXCLUSIVE) mean?

DXGI_DDI_ERR_NONEXCLUSIVE

What Windows rejected: ddi err nonexclusive

DXGI_DDI_ERR_NONEXCLUSIVE, value 0x887B0003, is produced by dxgi error when a performance counter was already owned by another process or Direct3D device. The investigation should stay attached to exclusive GPU counter ownership and to the exact generation in which it was obtained.

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

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.

Separate state from capability

1. Freeze the result generation. Record counter identifier, requesting device, active profilers, process list, acquisition and release timestamps. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow this result comparison. close the competing profiler or device and request the same counter again. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. 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.
4. 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 DXGI_ERROR_NONEXCLUSIVE is especially useful: DXGI_ERROR_NONEXCLUSIVE is the application-visible form of exclusive-resource contention. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Serialize counter ownership and always release the counter on device teardown or abnormal capture cancellation. 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 exclusive GPU counter ownership 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 DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters. 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 error codes — background for the exclusive GPU counter ownership boundary involved in it.
• Microsoft: DXGI overview
• Microsoft: Direct3D 12 shader cache StoreValue
• Microsoft: Handle device-removed scenarios

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