I have recently got myself a GTX Titan X (Maxwell) to play around with and wanted to retire my GTX 1050 Mobile for playing games. However, I am getting a graphics driver error/crash when I try to render a 3D scene in a game. I think this might be a driver issue caused by the Titan being one generation older, because using the 1050 (Pascal) in these games worked just fine (apart from performing horribly).

So the problem is that as soon as I load a save or really try to load and render a 3D scene in a game, the game locks up and I get the following errors in the dmesg:

[16142.416523] NVRM: Xid (PCI:0000:06:00): 32, pid=70106, name=GameThread, Channel ID 0000008c intr 00040000
[16142.416970] NVRM: Xid (PCI:0000:06:00): 32, pid=70106, name=GameThread, Channel ID 0000008c intr 00200000

[15971.823098] NVRM: Xid (PCI:0000:06:00): 32, pid=69348, name=GameThread, Channel ID 0000009c intr 00040000
[15971.823553] NVRM: Xid (PCI:0000:06:00): 32, pid=69348, name=GameThread, Channel ID 0000009c intr 00200000
[15971.823727] NVRM: Xid (PCI:0000:06:00): 13, pid=69348, name=GameThread, Graphics Exception: Class 0x0 Subchannel 0x0 Mismatch
[15971.823732] NVRM: Xid (PCI:0000:06:00): 13, pid=69348, name=GameThread, Graphics Exception: ESR 0x4041b0=0x0
[15971.823736] NVRM: Xid (PCI:0000:06:00): 13, pid=69348, name=GameThread, Graphics Exception: ESR 0x404000=0x80000002
[15971.824079] NVRM: Xid (PCI:0000:06:00): 13, pid=69348, name=GameThread, Graphics Exception: ChID 009c, Class 0000b197, Offset 00001538, Data 00000001

The game I tested the most with was Cyberpunk 2077. So here's a quick overview of how to trigger the crash with this GPU. You can also try to load a save instead of the benchmark, but the benchmark is probably more consistent:

1. Start Cyberpunk 2077 through Proton (e.g. Proton GE)
2. Go to Settings > Graphics and start the Benchmark.
3. Observe loading screen working fine.
4. As soon as the loading is done, i.e. the loading bar hits about half fullness, the game freezes and the Xid errors are printed.

I also tested with another game, Grounded, and the same behaviour occurs as soon as I load the first 3D scene. I don't really have any other DX12 games but I assume that similar issues might be observed there too.

I know that this is probably a driver issue from Nvidia and thus not really fixable in VKD3D. So I am really hoping that there might be a workaround or something I could try to disable to make it work, without loosing too much performance (see below). I don't really know anything about Vulkan myself so maybe there is something obvious which would fix this or which I have not tried. I could also report this directly to Nvidia, but given the generation of this GPU (Maxwell) I seriously doubt that it'll get fixed on their side.

If this is indeed the case, feel free to close this issue. Otherwise, thanks for any help/directions/hints for what I could try here in advance.

Workaround for Cyberpunk 2077

After some desperate trial and error I eventually found a workaround that worked for Cyberpunk 2077. The game works (i.e. the 3D scenes actually load and show) but performs poorly when using:

VKD3D_CONFIG=single_queue

I am however not really satisfied with this fix as the performance is pretty bad with that. It performs worse than what my GTX 1050 Mobile could do, and is pretty much unplayable even at 720p. I don't really know how much better it would be without single_queue (it never worked without it). The only thing I notice about half the FPS on the initial loading screen which might or might not mean something.

What's interesting is that this workaround does not work for Grounded, allthough they fail with the same Xid errors. So really not sure why this works for Cyberpunk in the first place.

I also experimented with other config options and noticed that with force_static_cbv Cyberpunk already crashed during the initial loading screen with the same Xid errors, instead of only when entering the first 3D scene. All other config options I have tried didn't seem to have any effect.

Software information

The issue seems to happen across many different games, so it is not directly related to one game. I have tested mainly with Cyberpunk 2077 Version 2.21 with Phantom Liberty from GOG via Heroic Games Launcher.

Additionally, I was able to reproduce the issue with Grounded Version 1.4.1.4706 Rel in DX12 mode launched from Steam. What is weird though is that the workaround did only work in Cyberpunk 2077.

I did most of the testing in GE Proton 9-26 but could reproduce all the issues in older proton versions (e.g. GE 7-41) and Valve's Proton Experimental. I also reproduced the issue with VKD3D built from latest master, inserted into GE 9-26, and the logs below are all captured with that build. Also note that I have the VKD3D shader cache disabled for all testing.

System information

• GPU: Nvidia GTX Titan X (Maxwell)
• Driver: Nvidia 570.124.04
• Wine version: GE Proton 9-26
• VKD3D-Proton version: built from latest master (a7159b80e165bfa311eb1e8f39aceba7e696e555)

I have done some testing with the same GPU in two different systems and the issue persists across both of them. So it really seems to be a driver issue and not caused by some other part of the system. However for completeness, here's a quick word on them:

• Desktop with AMD Ryzen 4750G with Radeon graphics, on Endevaour OS (Linux 6.13.7, KDE Wayland)
• Laptop with Intel Core i7-8565U with integrated graphics, on Arch Linux (Linux 6.13.7, Hyprland). The GPU is used as an eGPU and the wayland compositor is running on the eGPU directly (i.e. no PRIME offloading going on).

Log files

Here's everything I think might be interresting. Note that I am hosting the trace logs myself as they are absolutely massive.

• vulkaninfo of the intel system
• Cyberpunk 2077 Logs (to reproduce, go into settings and run the benchmark, settings are low and upscaling disabled)
  • Cyberpunk 2077 crash
  • Cyberpunk 2077 crash with VKD3D_DEBUG=trace
  • Cyberpunk 2077 working fine with VKD3D_CONFIG=single_queue
  • Cyberpunk 2077 working fine with VKD3D_DEBUG=trace and VKD3D_CONFIG=single_queue
• Grounded Logs (to reproduce, go into single player and open a new empty playground with default settings)
  • Grounded crash
  • Grounded crash with VKD3D_DEBUG=trace
  • Grounded crash with VKD3D_CONFIG=single_queue
  • Grounded crash with VKD3D_DEBUG=trace and VKD3D_CONFIG=single_queue

I am happy to provide more/other logs and try out patches or other workarounds.