HRESULT 0x887A0035 (DXGI_ERROR_CACHE_HASH

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

A cache entry was found, but the key provided does not match the key stored in the entry.

Previous	Next
DXGI_ERROR_CACHE_FULL	DXGI_ERROR_ALREADY_EXISTS

DXGI_ERROR_CACHE_HASH_COLLISION

What Windows rejected: cache hash collision

DXGI_ERROR_CACHE_HASH_COLLISION, value 0x887A0035, is produced by dxgi error when the hash bucket contained an entry whose complete key did not equal the caller-provided key. The investigation should stay attached to shader-cache key integrity and to the exact generation in which it was obtained.

DXGI_ERROR_CACHE_HASH_COLLISION: Do not erase all shader caches or recreate every graphics object before preserving the first failing call. For DXGI_ERROR_CACHE_HASH_COLLISION, Cache, policy, remote-session and device-lifetime failures have different recovery rules. For DXGI_ERROR_CACHE_HASH_COLLISION, 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_ERROR_CACHE_HASH_COLLISION`
Rejected boundary	the hash bucket contained an entry whose complete key did not equal the caller-provided key
Decisive capture	full key bytes, hash function input, stored key, cache namespace, driver version and whether keys were truncated or serialized differently
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
Object identity	shader-cache key integrity

For DXGI_ERROR_CACHE_HASH_COLLISION, 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_CACHE_HASH_COLLISION.

Separate state from capability

Freeze the DXGI_ERROR_CACHE_HASH_COLLISION generation. Record full key bytes, hash function input, stored key, cache namespace, driver version and whether keys were truncated or serialized differently. Before diagnosing DXGI_ERROR_CACHE_HASH_COLLISION, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow DXGI_ERROR_CACHE_HASH_COLLISION comparison. store two controlled keys with the same supplied hash while preserving their distinct full key data. During the DXGI_ERROR_CACHE_HASH_COLLISION comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after DXGI_ERROR_CACHE_HASH_COLLISION. For DXGI_ERROR_CACHE_HASH_COLLISION, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_ERROR_CACHE_HASH_COLLISION boundary was crossed.
Repeat DXGI_ERROR_CACHE_HASH_COLLISION through a lifecycle transition. For DXGI_ERROR_CACHE_HASH_COLLISION, 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_ALREADY_EXISTS is especially useful: DXGI_ERROR_ALREADY_EXISTS means the desired element itself already exists. For DXGI_ERROR_CACHE_HASH_COLLISION, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Use stable complete keys, handle collisions explicitly and replace only entries proven to belong to the same key. Repair of DXGI_ERROR_CACHE_HASH_COLLISION 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_CACHE_HASH_COLLISION 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_CACHE_HASH_COLLISION; unrelated adapter, monitor and application state remains unchanged.
For DXGI_ERROR_CACHE_HASH_COLLISION, debug-layer, ETW or driver diagnostics no longer report the rejected shader-cache key integrity contract during the same scenario.
The application handles recurrence of DXGI_ERROR_CACHE_HASH_COLLISION without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `DXGI_ERROR_CACHE_HASH_COLLISION`

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

Technical references

Microsoft: DXGI error codes — background for the shader-cache key integrity boundary involved in DXGI_ERROR_CACHE_HASH_COLLISION.
Microsoft: DXGI overview — background for the shader-cache key integrity boundary involved in DXGI_ERROR_CACHE_HASH_COLLISION.
Microsoft: Direct3D 12 shader cache StoreValue — background for the shader-cache key integrity boundary involved in DXGI_ERROR_CACHE_HASH_COLLISION.
Microsoft: Handle device-removed scenarios — background for the shader-cache key integrity boundary involved in DXGI_ERROR_CACHE_HASH_COLLISION.

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