I’d like to report that the crashes with some vkd3d titles (FH5, etc.) on pre-Turing hardware, seem to be fixed in the latest beta 555.52.04 as well as 550.40.63 vulkan dev beta.
In addition, after this regression fix, it was finally possible to test the Xid error fixes for FH5 implemented in 550.40.07-550.54.14.
So, I can report that FH5 didn’t crash once in hours of gameplay. It was finally possible to use unlocked framerate with a mix of Ultra and High graphical settings (~90-100fps) on my 1080ti. :)
I tried The last of us and the XID 109 crash is still there. It seems like the first run with new drivers the game seems to work. The next time you start the game it will start crashing and will continue to do so until you update the drivers again.
[tis jun 11 11:04:24 2024] NVRM: GPU at PCI:0000:01:00: GPU-c527f869-4b6b-fb00-51ea-f36233874170
[tis jun 11 11:04:24 2024] NVRM: Xid (PCI:0000:01:00): 109, pid='<unknown>', name=<unknown>, Ch 0000009e, errorString CTX SWITCH TIMEOUT, Info 0x54c050
Tested Elden Ring again with the latest drivers since the new DLC came out, and still get crashes in anywhere between 5 and 15 minutes of gameplay. Completely unplayable, not even in short sessions. Tested stable, beta and Vulkan dev drivers: 550.90.07, 555.52.04 and 550.40.63.
Also confirmed that, on my setup and with this game, crashes happen even right after driver updates.
Running an RTX 2060 Mobile on Arch Linux with standard kernel 6.9.5.
Two more crashing applications on my RTX 2060 Mobile: Risk of Rain 2 and Final Fantasy XIV. Both games worked fine a couple months ago. At this point I’m unsure if my graphics card is faulty or what might be causing the problem besides lack of support for this issue. Will start testing different distros this week to make sure I don’t have a botched Linux install. This is incredibly frustrating.
I’ve encountered the dreaded xid 109 system freeze on multiple games, from BG3 and The First Descendant to Disciples 2 (yep, even that one). Independent of proton version or tinkering steps, both BG3 and FD first ran fine for more than an hour, then the day after they started freezing after ~5-10 mins of gameplay. Elden Ring ran fine for like an hour on first day too, haven’t tested after. nvidia-bug-report.log.gz (413.3 KB)
Tested Elden Ring. Ran with zero issues for ~5h yesterday, however, today it freezes after ~10 minutes of gameplay. You can see the xid 109 error in the logs. nvidia-bug-report.log.gz (450.6 KB)
Tested on Helldivers 2, Ghost of Tsushima, and CS2. HD2 and GoT end up crashing with Xid 109, with seemingly no fixed time after which they crash - sometimes it’s 30 mins, sometimes it’s 10 mins. CS2 runs without any issues, tested on matchmaking, deathmatch, and casual.
Crash seems to occur both with and without “undervolting” (+core offset and a clock limit).
Here are my specs:
Tumbleweed 20240711, running KDE + Wayland
Linux v6.9.7-1-default
AMD Ryzen 7 5800X3D
RTX 3080 FE 10G (nvidia driver 550.90.07)
32GiB DDR4 RAM
You may update your Tumbleweed. Kernel 6.9.9 and nvidia 550.100 should already be installed. Not that I expect it to fix the issue but since you’re running an older GPU driver it might be worth a shot.
Then re-try and also post nvidia-bug-report.tar.gz obtained with sudo nvidia-bug-report.sh.
Hello, the same problem (error 109) with pytorch - it’s working on cloud server, but not on my local machine. I was tested with Driver Version: 560.35.03, NVIDIA GeForce RTX 4090
I was bored and took another look at this, seems to be a race condition, if you wait a bit, maybe 10-15 seconds at the main menu before loading a save, the game seems to work. If you load a game too fast, it will crash with XID 109. I managed to recreate the same crash in windows too using vkd3d-proton. So, yeah… either it’s a general driver issue or it’s something in vkd3d-proton.