protonscr

Reproducible freeze in Kingdom Come Deliverance 2 when Global Illumination is set to Ultra or higher

vkd3dopen
HansKristian-Work/vkd3d-proton#2718 · opened 2025-11-20 by grumd · updated 2025-12-24 · 9 comments · github
Ggrumd 2025-11-20 github

Software information

Game: Kingdom Come Deliverance 2
Settings: Global Illumination set to Ultra or Experimental (can't reproduce on High).
Save file: save207.whs.zip
Video of the freeze: https://www.youtube.com/watch?v=LwCcfn-TZJg
Video of NO freeze with GI on Low: https://www.youtube.com/watch?v=-FqpZS-AZec

Steps to reproduce: open the game, load the save file provided. The game will freeze 0-1 seconds after the scene loads.

  • Freezes with Global Illumination on Ultra or higher
  • DOESN'T freeze with Global Illumination on High or lower
  • Freezes on my PC with 5080 on Bazzite
  • Freezes on my PC with 5080 on fresh install of CachyOS
  • DOESN'T freeze on my PC with 5080 in Windows
  • DOESN'T freeze on my laptop with 3060 on Bazzite (same nvidia driver versions, same Proton versions, same vkd3d-proton version)

System information

  • GPU: RTX 5080
  • Driver: 580.105.08 open kernel
  • Wine version: Running my game through Steam using Proton. Reproducible with Proton GE 10-25, latest Proton CachyOS
  • VKD3D-Proton version: 3.0

Logs

  • PROTON_LOG=1 VKD3D_DEBUG=trace VKD3D_SHADER_DEBUG=trace VKD3D_CONFIG=vk_debug: steam-1771300.zip
  • dmesg -w: [ 6195.165246] NVRM: Xid (PCI:0000:01:00): 109, pid=49662, name=Main, channel 0x00000038, errorString CTX SWITCH TIMEOUT, Info 0x3c044

Please let me know if there are any other logs I can attach.

Lluisalvarado 2025-11-21 github

I remember this happening but 8 months ago and was fixed around that time with a game update. I am testing (not with your save game) with 4 save games I have. I have everything on max on a 4090 and a 5090. Did 30 minutes each for a quick test. Both cases worked.

I also just tried today too with a 4070 and worked without issues. The 4070 was at 1080p if that helps at all while the 4090 and 5090 were at 4k (13900k and 14900k cpus)

KK0bin 2025-11-21 github

I can confirm that this does not impact Ampere (Nvidia 3000).

Ggrumd 2025-11-24 github

I remember this happening but 8 months ago and was fixed around that time with a game update. I am testing (not with your save game) with 4 save games I have. I have everything on max on a 4090 and a 5090. Did 30 minutes each for a quick test. Both cases worked.

I also just tried today too with a 4070 and worked without issues. The 4070 was at 1080p if that helps at all while the 4090 and 5090 were at 4k (13900k and 14900k cpus)

You should try running my save file, it could be a completely different bug than what happened 8 months ago. I'm of course using the latest version of KCD2. Can you try opening my save file on your 5090? All settings on Ultra.

BBlisto91 2025-11-24 github

It would likely be better to report it directly to Nvidia. None on the devs or affiliated testers have a 5000 series GPU to confirm with.

Lluisalvarado 2025-11-24 github

I remember this happening but 8 months ago and was fixed around that time with a game update. I am testing (not with your save game) with 4 save games I have. I have everything on max on a 4090 and a 5090. Did 30 minutes each for a quick test. Both cases worked.
I also just tried today too with a 4070 and worked without issues. The 4070 was at 1080p if that helps at all while the 4090 and 5090 were at 4k (13900k and 14900k cpus)

You should try running my save file, it could be a completely different bug than what happened 8 months ago. I'm of course using the latest version of KCD2. Can you try opening my save file on your 5090? All settings on Ultra.

Okay give me 2 hours.

Lluisalvarado 2025-12-02 github

I dont know if my technical report for your case ever got on time for the 1.5.2 (I doubt since it was less than 10 days ago) but here is my report

Image

After loading your save game, 2 seconds later it crashed. Using dmesg I got this:

[ 3907.780798] NVRM: GPU at PCI:0000:01:00: GPU-13c44046-56a6-74ab-e364-6dafc4f7b478
[ 3907.780815] NVRM: GPU Board Serial Number: 0
[ 3907.780818] NVRM: Xid (PCI:0000:01:00): 109, pid=27590, name=Main, channel 0x00000015, errorString CTX SWITCH TIMEOUT, Info 0xc014

My honest opinion: This is one of those game related issues. Even if it happens on Linux and not on Windows, testing for what I could around 100 other save games that I have (for some reason it saves anything I do to a file) and none of them froze the game in 10 seconds of testing. I got a hunch if you play in another save game or start from scratch with the 1.5.2 it would fix the issue.

Ggrumd 2025-12-05 github

@luisalvarado

Thanks for testing! You can also try setting Global Illumination to "High" or lower and the freeze will not be reproducible.

So this confirms that it's not just my PC and anyone with a Blackwell GPU can reproduce the freeze with my save file.

Considering this is only reproducible: on Blackwell, with Global Illumination on Ultra or higher, and on Linux -- I'll assume it's an issue related to Proton or vkd3d-proton, or Nvidia drivers on Linux. Maybe a wonky shader compilation crashes in that particular location?

I'll add that it's not just this save file. When I was playing in that general location, getting close to the camp froze my game multiple times. This save file is just a really good example because it just freezes in 2 seconds without you doing anything. I have other save files not far from that location that still freeze the game when you try to get close to the camp. Something in or around that camp just crashes the GPU pretty consistently.

Ssklynic 2025-12-24 github

Does that GI setting utilizes DXR? I had similar issue in another game with DXR GI (nvidia's RTXGI) enabled (#2599) and it only happen on ampere (3060, both desktop and mobile). In such case you should report to Nvidia.

Mmbriar 2025-12-24 github

Cryengine's SVOGI in this game doesn't use DXR.

Launch options