So, how can I test an experimental build at Gamepass? You merged my tread here, so I ask. Despeartely want to play normally 
Already one hundred and fifty crash (counting starts from the closed beta), hooray!
Happens randomly: can be in the hub, can be on a mission. I checked all known solutions, reinstalled everything possible, tried all combinations of graphics settings, experimental build, etc.
The crash always happens the same way: the sound hangs/freezes along with the picture, everything is fine for a couple of seconds, then the game crashes.
GUID: f6256112-c75e-4ab6-9904-7c6e3a6cbf42
Log File:
Info Type:
console-2023-03-23-12.49.35-50a97ff9-6b0c-44d1-9ada-7dba745b33ac.log (162.6 KB)
console-2023-03-23-13.20.44-8f284260-27b5-4e7a-b69c-b3023b055c1a.log (341.8 KB)
1 Like
HELP! I need the new experiment buildā¦ after today patch there is no more experiment build and my game keeps crashing againā¦ damn fix those avatars pleeeeasse ā¦ T_T
Support, please reply here!
Issue Description:
As above, Iāve been largely unable to play without crashing since Patch #4. I took a break from the game because the crashing had become so bad and having recently reinstalled Windows on my PC, I thought Iād return to see if the issue had resolved itself. Very occasionally, I can complete a mission without issue, but some missions seem to always crash no matter how many times I attempt to rejoin them.
Help would be much appreciated!
Crash Report (If Applicable):
crash_dump-2023-03-26-18.21.27-003c0088-9a09-418e-a1b4-9fd183ccebfd.dmp (939.3 KB)
crash_dump-2023-03-26-19.28.42-96ec1f0c-b794-4734-b967-b4ddb7a18beb.dmp (767.4 KB)
crash_dump-2023-03-26-19.37.10-32609edc-d9d8-4a31-9b1e-5283bedb70bd.dmp (770.3 KB)
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
- Start Mission (currently playing Ogryn, seems to affect multiple maps)
- Attempt to play
- Crash (sometimes seconds after the start of a mission, otherwise at seemingly unimportant moments)
Mission Name (If Applicable):
I donāt know the mission names, but certainly the missions which incorporate the brighter, sandy outdoor areas seem to crash even more often than others.
Platform:
Steam
Player ID:
wallflowerninja
Approx. Time of Issue & Timezone:
Constantly since Patch #4
The logs Iām providing are from three crashes that took place this evening between 7:45PM and 8:45PM (GMT+1).
Reproduction Rate:
Constant (100%)
Upload Console Log:
console-2023-03-26-18.21.27-003c0088-9a09-418e-a1b4-9fd183ccebfd.log (191.2 KB)
console-2023-03-26-19.28.42-96ec1f0c-b794-4734-b967-b4ddb7a18beb.log (107.0 KB)
console-2023-03-26-19.37.10-32609edc-d9d8-4a31-9b1e-5283bedb70bd.log (69.4 KB)
Upload darktide_launcher.log:
darktide_launcher.log (284.0 KB)
We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.
Issue Description:
Crashing Whenever I load into a Mission, Or even sometimes when another player is loading in.
This issue is weird because I wasnāt having this problem before the new update, and I also updated my NVIDIA drivers to the most recent ones. Iāve also had FPS/ or screen lag when theirs hordeās or fire sometimes, which I never had before as well. Iāve watched task manager to see if my usage is spiking and there is no evidence of any spiking or even high GPU/Memory/ or CPU usage whenever the crash or FPS lag happens.
Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]
GUID: 56b49c6e-0cd7-43f7-b5a5-564c89dafcd2
Log File:
Info Type:
Error Displayed (If Applicable):
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
- Load into a game thatās in the middle of a horde
- Have another player load into the game while in the middle of a horde
- Join a Mission using quick play.
Mission Name (If Applicable):
Platform:
[Steam/Microsoft Store]
Steam: Grahambro
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Steam Community :: Graham (In game name on this current Character Hyde on darktide)
Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]
03/26/2023
1:34-1:35 am
Iāve also had it happen throughout the last few days
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Common
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
- Press the Windows key + R
- Enter %appdata% within the search input and select āOKā
- Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
- Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
- Upload here
console-2023-03-26-08.33.10-ded15aa1-54b7-4bef-a23b-18a0d2c13fc3.log (58.5 KB)
console-2023-03-26-07.56.49-56b49c6e-0cd7-43f7-b5a5-564c89dafcd2.log (238.5 KB)
Upload darktide_launcher.log:
- Press the Windows key + R
- Enter %appdata% within the search input and select āOKā
- Navigate to AppData\Roaming\Fatshark\Darktide
- Locate the darktide_launcher.log in this directory
- Upload here
darktide_launcher.log (721.2 KB)
Issue Description:
I have been crashing consistently since the patch of 24/02/2023 - every time, itās the same - no issues in the Mourningstar, but near-immediate crash once in a mission or soon after attempting to rejoin a mission.
I gave up on trying for a while and have this morning wiped and reinstalled Windows on my PC. Unfortunately, this issue remains and I crashed twice in quick succession - the latter attempt using the experimental branch which appeared to make no difference.
Before Patch #4, Iād not experienced any crashes - during the beta or after launch - but now Iām seemingly unable to play.
Any help would be much appreciated.
Crash Report (If Applicable):
crash_dump-2023-03-26-14.34.29-ef789ea9-5d62-45ef-a6da-50fabb2e3827.dmp (829.3 KB)
crash_dump-2023-03-26-14.47.29-00279326-2a37-4474-8c47-c6b824be562f.dmp (896.8 KB)
Steps to Reproduce:
- Start Mission
- Move for <30 seconds
- Crash
Platform:
Steam
Player ID:
wallflowerninja
Approx. Time of Issue & Timezone:
03/26/2023, 15:30PM BST
Reproduction Rate:
100%
Upload Console Log:
console-2023-03-26-14.34.29-ef789ea9-5d62-45ef-a6da-50fabb2e3827.log (137.4 KB)
console-2023-03-26-14.47.29-00279326-2a37-4474-8c47-c6b824be562f.log (113.6 KB)
Upload darktide_launcher.log:
darktide_launcher.log (93.6 KB)
Could we have an update on this issue, rather than having our threads repeatedly merged here, out of the way? The experimental build is not working and, without another solution, the game is being rendered unplayable.
Iām sure the developers are seeing the increased crash dumps coming in. Anywayā¦ I was mostly crash free, for the last 4-5 weeks, up until this weekend. Iām now regularly crashing again (only after mission load).
I reverted to the experimental branch and noticed it doesnāt download. The mod patch .bat still reports the .exe is unchanged. 
GUID: 5195f6b1-e97d-445c-ba9d-c5aee97ce7f4
Log File:
Info Type:
Crash does not seem to be linked to anything in particular. Might be a runtime error or maybe linked to sound files as it occurs frequently while I ADS and fire the 2rnd-burst Headhunter rifle.
A new experimental build is in the works!
Experimental is now available.
1 Like
Itās seemingly made no difference for me, unfortunately.
I managed to get most of the way through the forge mission before my first crash:
crash_dump-2023-03-28-19.38.51-8eb7b73f-66ce-47d0-a649-9e0a40296ab3.dmp (847.5 KB)
console-2023-03-28-19.38.51-8eb7b73f-66ce-47d0-a649-9e0a40296ab3.log (107.3 KB)
Then I started another mission - whichever of the assassinations that start in the sewer - and made it about three steps before crashing to desktop:
crash_dump-2023-03-28-19.58.32-36a3c7a7-58a2-4677-bdaf-f2ee50f50c9b.dmp (817.4 KB)
console-2023-03-28-19.58.32-36a3c7a7-58a2-4677-bdaf-f2ee50f50c9b.log (176.6 KB)
Is there anything else we can try? Are there any specific graphics settings which have been linked to the crashes?
If you havenāt already, could you try to wipe your %Appdata%/roaming/Fatshark/Darktide folder from .hans and .pso_lib files, also clear your windows Shader cache. (Using Disk Cleanup tool)
Just to make sure your issues arenāt stemming from cached broken shaders somehow.
1 Like
Hello, afraid I have the same issue as reported and it persists on the experimental build. I even have the blank profile icons too! The crashes are getting very frequent.
I am running a 7900XTX, 7900X, Windows 10pro. Everything is the latest, already tried reinstalling drivers.
GUID: 57fb6c58-e4c3-4add-9351-74d4c67a93b8
Log File:
Info Type:
I followed the instructions above and managed to complete a whole mission (the one where you retrieve munitions from trains) without crashesā¦ and then three seconds into joining another mission (the disease vault mission, with outdoor areas), I crashed. Itās getting really disheartening now! Here are the logs:
crash_dump-2023-03-29-09.16.36-31a12a94-ff98-41fe-a472-5bb3cec8e511.dmp (756.5 KB)
console-2023-03-29-09.16.36-31a12a94-ff98-41fe-a472-5bb3cec8e511.log (232.2 KB)
Thank you developers! You have made great progress on the gpu hang issue last February and I can report I no longer crash in Darktide. I used to crash every other match, but those frustrations are now gone. Iām enjoying the game much more! I canāt thank you enough.
2 Likes
Ok so some developments, played quite a few games over the past 2 days after a FULL reformat. The issue persisted after even reformating my entire PC.
I disabled wallpaper engine and so farā¦ no issues, yet. Will keep it posted but I am starting to suspect recent updates to Darktide are somehow messing with, or calling for drivers similarly/at the same time or something?
UPDATE!!! I fixed it
Steps on how to fix the issue.
- Install GeForce Game Ready Driver 531.29
- Run the installation file.
a. Press āOKā to accept the installation path.
b. Press āNextā after the following loading time.
c. Choose āAdvancedā installation options.
d. Select the ācleanā installation and run the installation.
e. After the installation is done, reboot your PC. - Go to Darktide in your Steam library.
a. Right klick on Darktide.
b. Go to āLocal filesā and left klick on āVerify integrity of game filesā¦ā - Run Darktide.
Old -----------------------------------------------------------------------------------------------------------------------------------------
Something is now broken after i installed the Nvidia 531.41 driverā¦ It crashes on boot after iāve pressed the āstartā button from the small game window.
What iāve tried so far:
- Removed all the mods, didnāt help.
- Tried to use the Beta-Experimental build, didnāt help.
2.1. Rebooted PC, didnāt help. - Tried to lower the worker threads incrementally from 5 down to 1, didnāt help.
- Complete clean re-install of the Nvidia 531.41 driver, didnāt help.
4.1. Rebooted PC, didnāt help. - Downloaded Nvidia driver 531.29 from Nvidias webpage with a clean installation, didnāt help.
5.1. Rebooted PC, didnāt help.
I also looked into the DT launcher.log files and saw a repeating Error message.
11:14:58.951 [Launcher] !! Error parsing settings for āgammaā! Default value invalid! Returning generic!
11:15:22.383 [Launcher] [Launch Game] !! Error parsing settings for āgammaā! Default value invalid! Returning generic!
DT launcher.log
darktide_launcher.log (645.5 KB)
DT console.logs from all todays crashes.
console-2023-04-01-10.30.02-aacf13a4-d963-4ac1-b415-58bd9944a234.log (12.2 KB)
console-2023-04-01-10.29.23-8e37936d-73e5-4a40-9491-758a28c46ce4.log (12.2 KB)
console-2023-04-01-10.28.28-cf2819aa-f0ba-43f9-865e-34b843e597d2.log (12.2 KB)
console-2023-04-01-11.01.14-6c55d3be-2607-452b-81ce-c6d695da4f07.log (12.0 KB)
console-2023-04-01-10.58.14-a2df1029-6d2c-4f43-af17-a3a90e69ece0.log (12.2 KB)
console-2023-04-01-10.17.02-1076f964-228d-436b-a7f3-5e1a2e741cb3.log (12.2 KB)
console-2023-04-01-10.14.04-52f67854-2cf3-494a-8a41-cae54d5ad89d.log (12.0 KB)
console-2023-04-01-10.09.57-c3ef7d5a-2ab0-4910-a03d-6ac2899a11fb.log (12.3 KB)
console-2023-04-01-10.04.35-5732570b-3ba0-436d-8e39-93c2df5e5567.log (12.3 KB)
console-2023-03-31-19.20.50-9b097f2e-3f04-4b51-8281-ee732c9d9a96.log (2.7 MB)