We’re looking in to this. Thank you for your report.
These are the notorious GPU-related crashes, unfortunately, as you seem to have already discovered.
I’m 30+ minutes late in announcing this, but…:
FIFTH POTENTIAL FIX NOW LIVE on the experimental
branch for players impacted by GPU-related crashes.
Already have the experimental
branch selected? You might need to restart the Steam client for the download to initiate.
PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.
- Open the Steam client
- Right-click Darktide in your Steam library
- Select ‘Properties’
- Select ‘Betas’
- Enter the password
cTYPtKTsfMDsLHAV
- Select ‘Check Code’
- Select the ‘None’ dropdown, and
experimental - Experimental Builds
should now be within the list - Select
experimental - Experimental Builds
- Close the pop-up window
- A +52.3MB download should now start
- Play!
- Post here to let us know the outcome

This should now be resolved. Thank you for your patience.
Please let us know if Satoru’s recommendation above has helped.
We’re looking in to this particular crash. Thank you for your report.
I’ve raised this with our developers. Thank you.
Thank you for your superbly detailed report - I’ve added this to our database.
Thank you for letting us know, we’re on the case.
It’s in our database! Thank you.
I’ve raised this with our developers. Thank you.
Thank you for the update.
Thank you for your report, I’ve added it to our database.
Sounds like you’re experiencing all of the errors. Sorry about that, we’re working on it - I promise.
We’re working on a new build, unsure if it’s likely to be put on to experimental
tonight. I’ll keep you posted…
We are aware of and looking in to reports of players crashing on mission end.
Existing reports may be merged here, to help us keep track of the issues being reported.
UPDATE:
Read moreThis seems to occur when a user has picked up Plasteel or Diamantine during.
We’re working on it!
It would be super if you could include the associated console log. Thank you!
We’re working on this. Thank you!
We hope this will be resolved in our next patch. Thank you!