Also reported at https://github.com/ValveSoftware/Proton/issues/9734
Expected behaviour: When DXVK loads a state cache and detects a GPU/driver mismatch (different vendorId, deviceId, or driver version embedded in the cache header), it should silently discard the cache
No, it shouldn't. Cached entries are generally not a problem because device properties that affect the cached code generation are part of the shader key, so the Intel driver should never even get to see any of the code generated for the Nvidia card. There might be a bug in that area, but then the expectation should be to find and fix that bug and not just toss the entire feature.
Either way I don't have an Intel setup so can't really do anything in the way of reproducing/debugging this. All I know is that NV<->AMD generally works fine.
Thank you for the clarification. A few additional points that might be helpful:
This issue started appearing after one of the recent Overwatch updates. During that same period, Proton was also updated several times, so it's unclear whether this is a regression on the game side or the Proton/DXVK side.
I use Proton for several other games including CS2, and none of them exhibit any similar issues. The problem appears to be specific to Overwatch with this hardware configuration.
I'm happy to provide any information needed to help debug this. I can also provide more logs, if that would help narrow down where in the cache reading process the crash occurs.
I saw a suspicious line in the log file:
15137.752:01c0:0264:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Cannot load existing on-disk cache due to driver version mismatch.
I'm not sure if it was the direct cause of the crash, but does that mean it might be a problem with vkd3d-proton?
are you using d3d12?
That error is expected when switching between GPUs there.
No, I'm using d3d11, in the game I specifically configured it to use DirectX 11.
https://github.com/Digger1955/dxvk-gplasync-lowlatency/pull/83
Can you try these patches for state cache, it fixes stuttering and other issues especially when using hybrid graphics.
DXVK_FILTER_DEVICE_NAME="NVIDIA"x1 2026-05DXVK_STATE_CACHE=0x1 2026-05prime-run %command%x1 2026-05
Software information
System information
Apitrace file(s)
Not applicable — crash occurs before any rendering takes place.
Log files
steam-2357570.log
Description
On hybrid Intel+NVIDIA laptops using PRIME render offload (prime-run), the DXVK state cache causes a hard crash on every launch after the first.
Root cause: The state cache (.dxvk.bin / .dxvk.lut) is written by the NVIDIA dGPU during the first successful session. On the next launch, DXVK reads the state cache before PRIME has fully redirected Vulkan device selection. At that point the active Vulkan device is the Intel iGPU (the system default), which reads a cache generated by a completely different GPU/driver. Instead of gracefully discarding the mismatched cache and rebuilding it, DXVK crashes the application.
Evidence:
Expected behaviour: When DXVK loads a state cache and detects a GPU/driver mismatch (different vendorId, deviceId, or driver version embedded in the cache header), it should silently discard the cache and start fresh rather than crashing. This is especially critical on hybrid GPU systems where the Vulkan device enumeration order at cache-read time may not match the rendering device at cache-write time.
Confirmed workarounds: