Game Crash Can only play for so long

Miscellaneous Linux Discussion
1

I have posted before but will use new template just for future info.

Ever since the march 17th patch went live i have been constantly getting a game crash,Kde Desktop environment/gpu driver crash. I can most of the time load in then walk up to the expeditions terminal screenshot at the bottom and after 5 min the game will 90% of the time crash. if i just go play a mission it will hang on longer and during the expedition i can sometime make it to the second zone and then the game will suddenly become unresponsive and crash 50.50 the game and then the gpu driver will crash. i have tried play a normal mission board missions and it will still happen random in the level as well. this crash is sometime gives a crash log most of the time not but in the console log i can see sometimes it will crash cleanly with a <>Deadlock detected while waiting on renderer thread. Update was not called for 16.1 seconds. but allot of the time it just stops with out any reason. there has been a few times i have play a full level of expeditions but after i get back into the morning start it then mostly crashes then or stating next game

This is a list of things i have done

  • Multiple Reinstalls
  • Both with and without mods -mod seem to have no affect on crash
  • reinstalled from my steam games ssd to my main OS drive
  • Gone threw multiple versions of proton
  • tested different launch commands
  • Swapped between different versions of bazzite to try different mesa versions
  • Temps all good
  • fresh usersetting file

I have been on and off this for the last few weeks trying to see if i can fix it but it worked perfectly before the update and it ran great. i have donā€™t have much experience with Linux as i only swapped a few months ago and this is the only game that seems to have a problem as other DirectX 12 games i run at full load, and run without issue.

I suppose i can only hope for anybody else with a solution or if we can get future support from Fatshark maby the next hotfix changes somthing or if anybody else know a fix.

I cant be the only one as since the update a few people on ProtonDb have talked about the game runs but has random Crash the GPU/DE and saying not recommended they all seem to be people with AMD gpu but could be the AMD curse

System Info

Steam Proton Version: Proton Experimental / ProtonGE

Launch Commands: ā€“lua-heap-mb-size 2048

CPU: AMD 3900x
GPU: 7900xtx

Linux Distro: Bazzite 43.20260406 stable
Kernel Version: Linux 6.17.7-ba29.fc43.x86_64
Desktop Environment: KDE plasma
Display Server/Protocol: wayland

Deadlock ā€”console-2026-04-08-08.59.20-c45203bd-7aeb-4481-a125-5cd5f6b44deb.log (714.8 KB)ā€”ā€”- This a a crash with a deadlock happening

console-2026-04-10-12.34.06-caad5cba-0bdb-44e9-b3cd-d9e92525715c.log (504.3 KB)ā€”ā€“ and this is one without but i tried this one with the new proton experimental but after the second zone in expeditions it just stopped

crash_dump-2026-04-10-13.05.45-214b51d8-77dc-4f19-94f1-4e2908d2c92e.dmp (357.9 KB) Most newest one i think

crash_dump-2026-04-08-08.59.20-c45203bd-7aeb-4481-a125-5cd5f6b44deb.dmp (300.0 KB) and a older one just to have too

20260321133650_1
20260321133650_11920Ɨ804 492 KB

2

Kind of a random shot, but there was a general crashing issue of Darktide on Linux that could be fixed by setting the Texture Quality to Low or Medium instead of High. It fixed frequent random crashes for me back in 2025. Maybe try this, if only to rule it out.

(See the Workaround paragraph in the opening post there.)

3

Which Proton-GE version are you using? The current one is 10-34.

4

i have tested medium as i always ran high and had no affect and i also been using protonGE 34 -all the way to proton ge 26 aswell as the valves 10.4/ 9.0 ones and it seems to have no affect

ā€˜ will try a run on low nowā€

5

Sorry, but then Iā€™m out of ideas. Iā€™m also using Bazzite and Proton-GE 10.34 on a Ryzen 7 5800XT and an RX 9060 XT, and I only have the occasional crash every other week or 10-12 hours playtime.

6

yeh running on low dos not change it aswell will the network_settings = {
try_nat64 = false
} thing i saw aswell but owell

Edit: nothing changed still just crashes

well i can only hope something changes on next update

7

Go to {path to game}/Warhammer 40,000 DARKTIDE/bundle/application_settings/win32_settings.ini and change the line deadlock_detector_enabled = true to false and save the file.

I donā€™t know if this will cause other problems in a longer session but itā€™s worth a shot. Linux isnā€™t supported anyway so itā€™s not like it will invalidate a crash support in the official tech support forum page.

Btw if you go back to GE you can use FSR4!

These would be your launch commands if you still wanted to use the lua heap thing with it

PROTON_FSR4_RDNA3_UPGRADE=1 PROTONFIXES_DISABLE=1 %command% --lua-heap-mb-size 2048

GE has the launcher skip built in but you can still run it if you add that protonfix line. Your call

8

when trying that as soon as i loaded into the morning start after 5 seconds of walking forward it just freezes but with the deadlock setting to false at least i can force close the game after it happens

9

Interesting, I had seen one post a while back saying that solved their issues :thinking:

Youā€™ve tried GE and official protons so itā€™s not NTSYNC (on itā€™s own at least)

Well hereā€™s a small list of environment variables and other things that may or may not help if youā€™re open to experimenting

AMD Smart Access Memory toggle. On by default for large VRAM GPUs. Accepted values sam or nosam

RADV_PERFTEST=nosam

VKD3D raytracing support toggle. On by default, this disables it. Shouldnā€™t matter but you never know.

VKD3D_CONFIG=nodxr

Darktide DirectStorage settings changeable via your user settings.
You should find an empty direct storage bracket near the top of the file with these being the defaults:

direct_storage = {
	enabled = true
	disable_bypass_io = false
	force_file_buffering = false
	force_mapping_layer = false
}

These are the usual default values but this one is interesting on linux! According to the old dev post mentioning these disable_bypass_io is supposed to have the same value as force_file_buffering but when I check my logs disable bypass io is on regardless of what I set it to and force file buffering wasnā€™t changed with it.

Despite that it just works for me? My CPU is a 7900X which is also a dual CCD chip but much newer so maybe itā€™s able to just brute force whatever issue this causes? Just theorizing.

The intended configs are

  1. As it is above
  2. disable_bypass_io and force_file_buffering both set to true
  3. Disabling directstorage by setting enabled to false

force_mapping_layer just isnā€™t used so ignore it /shrug

I recommend trying the directstorage stuff before disabling SAM just to not change too many things at once

10

i have tested with no luck above as direct storage seems to work fine but i have found somthing new not 100% sure yet but on the 12th a mod called error tracker came out https://www.nexusmods.com/warhammer40kdarktide/mods/824?tab=files at the time of writing 1.1 version does not function for me but the first version 1.0 causes massive performance costs as it tracked to aggressively but for some bazzare reason i cant get it to crash and have been able to play full games (with using amd fsr 4 upgrade and frame gen as this may be problematic at the moment) so not 100% sure what the mod is affecting or if there is some form of error that cuased the gpu crash but it work for now somehow

11

Thatā€™s really weird. Thereā€™s one more thing I can think of and thatā€™s the launcher not having a settings tab means you have to edit your number of render threads into your users settings manually.

Put this in your user settings:

max_worker_threads = X

and change X to whatever you want your render threads to be. Iā€™ve seen some Windows advice where lowering it can help stop crashes with the deadlock detector error. Iā€™d try 6 or lower as the 3900X is a dual CCD chip and has 6c/12t each on two separate chiplets

12

The mod seem to not change anything in the end, as i tested it alone with no mods so i must of got lucky as it started happening again so back to square one and hope a future update fixes whatever is wrong ;(

13

I also got an AMD system:

image
image990Ɨ494 36.8 KB

I recommend you try vanilla Arch Linux with GNOME instead of niche ā€œgamingā€ distros all the kids are raving about. Youā€™ll probably have a better time.