| Previous | Next |
| DXGI_DDI_ERR_UNSUPPORTED | D3D11_ERROR_TOO_MANY_UNIQUE_STATE_OBJECTS |
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.
DXGI_DDI_ERR_NONEXCLUSIVE: Do not erase all shader caches or recreate every graphics object before preserving the first failing call. For DXGI_DDI_ERR_NONEXCLUSIVE, Cache, policy, remote-session and device-lifetime failures have different recovery rules. For DXGI_DDI_ERR_NONEXCLUSIVE, 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
| Capture item | Why it matters for DXGI_DDI_ERR_NONEXCLUSIVE |
|---|---|
| Object identity | exclusive GPU counter ownership |
| Rejected boundary | a performance counter was already owned by another process or Direct3D device |
| Decisive capture | counter identifier, requesting device, active profilers, process list, acquisition and release timestamps |
| Current graph state | DXGI factory, adapter, device, resource or cache session |
| Supporting trace | DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters |
For DXGI_DDI_ERR_NONEXCLUSIVE, 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_DDI_ERR_NONEXCLUSIVE.
Separate state from capability
- Freeze the
DXGI_DDI_ERR_NONEXCLUSIVEgeneration. Record counter identifier, requesting device, active profilers, process list, acquisition and release timestamps. Before diagnosingDXGI_DDI_ERR_NONEXCLUSIVE, do not resize, hot-plug, recreate or release the object under examination. - Run the narrow
DXGI_DDI_ERR_NONEXCLUSIVEcomparison. close the competing profiler or device and request the same counter again. During theDXGI_DDI_ERR_NONEXCLUSIVEcomparison, keep every driver, monitor, resource format and unrelated policy unchanged. - Observe the layer after
DXGI_DDI_ERR_NONEXCLUSIVE. ForDXGI_DDI_ERR_NONEXCLUSIVE, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that theDXGI_DDI_ERR_NONEXCLUSIVEboundary was crossed. - Repeat
DXGI_DDI_ERR_NONEXCLUSIVEthrough a lifecycle transition. ForDXGI_DDI_ERR_NONEXCLUSIVE, 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_NONEXCLUSIVE is especially useful: DXGI_ERROR_NONEXCLUSIVE is the application-visible form of exclusive-resource contention. For DXGI_DDI_ERR_NONEXCLUSIVE, 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 DXGI_DDI_ERR_NONEXCLUSIVE 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_DDI_ERR_NONEXCLUSIVEtrace 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_DDI_ERR_NONEXCLUSIVE; unrelated adapter, monitor and application state remains unchanged. - For
DXGI_DDI_ERR_NONEXCLUSIVE, 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
DXGI_DDI_ERR_NONEXCLUSIVEwithout an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes for DXGI_DDI_ERR_NONEXCLUSIVE
For DXGI_DDI_ERR_NONEXCLUSIVE, log DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters. When the DXGI_DDI_ERR_NONEXCLUSIVE 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_DDI_ERR_NONEXCLUSIVE 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_DDI_ERR_NONEXCLUSIVE.
Technical references
- Microsoft: DXGI error codes — background for the exclusive GPU counter ownership boundary involved in
DXGI_DDI_ERR_NONEXCLUSIVE. - Microsoft: DXGI overview — background for the exclusive GPU counter ownership boundary involved in
DXGI_DDI_ERR_NONEXCLUSIVE. - Microsoft: Direct3D 12 shader cache StoreValue — background for the exclusive GPU counter ownership boundary involved in
DXGI_DDI_ERR_NONEXCLUSIVE. - Microsoft: Handle device-removed scenarios — background for the exclusive GPU counter ownership boundary involved in
DXGI_DDI_ERR_NONEXCLUSIVE.
Looking for a different code? Search another status or error code.