console-2022-12-26-00.00.33-cd6c171d-0bdd-4ff3-8374-4b99fbd1c21b.log (487.1 KB)
crash_dump-2022-12-26-00.00.33-cd6c171d-0bdd-4ff3-8374-4b99fbd1c21b.dmp (709.3 KB)
If anyone is fed up with crashlog prompts, locate this file: launcher.config in the %appdata% fatshark folder and change the value SendCrashReports = true to false.
DebugLog = false
LastScreenIndex = 0
SendCrashReports = false
Please donāt. Everytime this prompt goes up, an automatic crash report is sent to our systems along with all logs and dumps. This helps us keep track of what crashes are most critical to prioritise. If a large enough player base does this, our systems will say that everything looks good.
On that note, itās entirely useless to post dumps and logs here, we already get all that informtaion in our system. All you need to post, if you want special assistance with a specific problem (that isnāt a GPU hang) is the GUID presented by the crash-promt. With this GUID we can look up this particular crash and get all the information available from it.
Also, GPU hangs in particular are an issue which occurs on the GPU, so crash dumps means absolutely nothing in that case unfortunately. This is also why GPU hangs are so notoriously hard to find the reason for. As there just isnāt any sort of information attached with it.
On that note, itās entirely useless to post dumps and logs here
Wow, youāre telling us now? After thousands of posts?
And after the other devs/customer service people have been repeatedly asking people to post their logsā¦
I did find it rather baffling that their ālive service gameā didnāt automatically upload crash logs.
still crashing
didnāt help either
I probably should elaborate. This is why we try to not say too much, as itās always being misinterpreted to a degree. Itās not useless to post logs and dumps for most issues. Itās useless for GPU hangs in particular, for us developers.
Our community managers are not developers, but they know how to categorize crashes based on quickly looking at the logs, so to them itās not useless in terms of giving accurate response and referring to possible known workarounds.
Another aspect of posting logs and dumps it that the community managers can easily refer to a specific case by just linking the forum post when communicating with us.
But yes, all crashes are automatically submitted and stored in our system so itās not strictly necessary to post it here. But itās also much quicker to just click on a log link here and have a look rather than looking up the crash in the crash database.
That said, posting 10-20 crash dumps here in a post doesnāt do much else than causing noise in the thread.
Even with the additional dumps from Aftermath/DRED? Figured a stack trace and mini-dmp would help a lot in backtracing. Are there additional live debugging tools that youād like us to run during scenarios/configurations where we are likely to encounter crashes? How can we help get you the biggest bang for the buck in terms of narrowing in on the issue(s)? Especially given that some of these appear to be related to memory addressing / access violations.
Itās still information that Iām sure a lot of people would have loved to have. It wouldnāt have been hard to communicate that logs are uploaded automatically, but also that posting logs can help CMs and technical staff on forums determine the type of crash, and perhaps even refer the poster to relevant fixes or troubleshooting resources - but that repeatedly uploading logs from presumably same type of crash is mostly a waste of everyoneās time.
You actually just did communicate that, soā¦ yeah Iām sure plenty of people would have liked to know that earlier, before spending time uploading tons and tons of logs.
More on-topic, the gpu hangs in this game are strange. Whenever I have encountered GPU hangs in other games (admittedly on other hardware and windows versions), they have almost always been accompanied by the gpu driver restarting, and/or strangeness in windows caused by the gpu driver having crashed and often a notification that the driver was recovering from an error.
No such thing with Darktide. Everything is behaving completely normally, itās just Darktide thatās crashing, not the gpu driver. Then again, I suspect gpu hang error might be a pretty generic error, andā¦ yeah not making it easy to hunt down.
Recently bought game, fresh installation on steam.
Updated AMD drivers after first crash.
Crash happens within minutes of starting mission. crashes game back to desktop.
Steam chat sessions able to continue.
No sign of anomoly to display as in some other graphics crashes.
Game able to relaunch but will again crash within minutes of rejoining party.
Have yet to get through a single mission.
Used to happen a lot in Vermintide 2 game as well. Seems limited to Fatshark titles.
No issue with Doom eternal/Valheim/Diablo titles.
The latest three crashdumps supplied. Crashify URLās are produced but go nowhere in a browser. What are these for and how are they supposed to be used?
crash_dump-2022-12-26-22.28.27-2cab70a8-7aba-4ff7-803c-c8c9b8b578ba.dmp (654.1 KB)
crash_dump-2022-12-26-22.06.54-c2b9bb8f-76e5-4461-bcbb-7ad434dd0a95.dmp (680.5 KB)
crash_dump-2022-12-26-21.42.18-8f48d0bf-9c22-41b9-8f88-2c1fd648e322.dmp (644.2 KB)
Update : I have tried with selective startup and it still fails.
Update : Set ragdolls to 3. Set working threads to 6. Set framerate limit to match monitor (60hz) . Moved game files from d:/ (HHD) to C:/ (SSD that holds OS) .
No more crashes, I have now completed 4 missions.
My game was crashing everyday, multiple times a day, multiple times during a single mission, it was 100% sure to crash when playing above 60fps and at 60fps it would still crash here and there, since FatsharkPdr gave us the password for the experimental build like 4 or 5 days ago, the game didnāt crash at all, not at low, not at high, 60, 120 or unlimited fps, it is so GOOD to finally be able to play the game, so I recommend to anyone that didnāt give it a shot to try it out, I also deleted that Darktide settings folder too (on on appdata), donāt know if helped or not, but Iām informing anyway just to be clear.
9900k, RTX 3090, 2x8gb DDR4 4266mhz, running the game on a NVME SSD, Windows 11, lastest nvidia drivers.
Experimental beta build password on Steam: cTYPtKTsfMDsLHAV
20+ games without crashes after I disable mesh_streamer, with exp branch, 2K DLSS and no fps cap , even running more smooth. I can now confirm its fixed for me cuz before the game would definitly crash in 1 to 4 games, never made out to 4.
Also, I shared this method in my countryās community, at least 5+ players claim their GPU problems been fixed, with cards like 3090 or 4090. Though there are still some players said the method changed nothin.
I gave a lot of crash reports here in this post, so if Devs wants to check out the differences, just do it.
Issue Description:
I crash in-missions if I use more than one worker thread.
Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]
Error Displayed (If Applicable):
None. The game just crashes.
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
Mission Name (If Applicable):
Any
Platform:
Steam
Player ID:
ForeignFlight
Approx. Time of Issue & Timezone:
12/23/2022 7:00PM PST
Reproduction Rate:
Constant (100%)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
Upload darktide_launcher.log:
Same issue. No pattern, game randomly freezes for 1 sec and crashes to desktop consistently every mission, sometimes a couple of times per mission. Turning worker threads to 1 makes fewer crashes, although it still happens.
Mission name:
Any
Steam, ID 76561197998842537
console-2022-12-24-14.58.30-e0227847-0d31-4c8b-bde4-0787bcf00d85.log (62.1 KB)
console-2022-12-24-15.10.12-f2147c6f-26c5-44d9-9829-06ff193fcbe5.log (226.5 KB)
console-2022-12-24-15.27.36-2163bd96-98eb-4845-b03e-5d35c10d8c6e.log (334.8 KB)
crash_dump-2022-12-24-14.08.50-6fba9020-3925-4c58-b972-78ff3b43ff19.dmp (797.9 KB)
crash_dump-2022-12-24-14.51.14-6f1c4381-dfeb-434e-b8fa-19a580afda18.dmp (706.5 KB)
crash_dump-2022-12-24-14.58.30-e0227847-0d31-4c8b-bde4-0787bcf00d85.dmp (721.9 KB)
crash_dump-2022-12-24-15.10.12-f2147c6f-26c5-44d9-9829-06ff193fcbe5.dmp (713.4 KB)
crash_dump-2022-12-24-15.27.36-2163bd96-98eb-4845-b03e-5d35c10d8c6e.dmp (832.6 KB)
darktide_launcher.log (604.3 KB)
We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.
Issue Description:
The game used to crash once per mission (early days even more) but later on could do a few missions w/o crashing. Just reinstalled windows (fresh) and all drivers as well as the game and it crashes every minute or soā¦
Crash Report (If Applicable):
Platform:
Steam
Approx. Time of Issue & Timezone:
All the f. time
console-2022-12-23-23.07.24-44750e99-3f0f-42b6-bf3f-a01d68e27a0d.log (18.3 KB)
darktide_launcher.log (174.0 KB)
console-2022-12-25-16.19.49-8854c41f-1aed-4627-8039-c9d61d72fbaf.log (186.4 KB)
crash_dump-2022-12-25-16.19.49-8854c41f-1aed-4627-8039-c9d61d72fbaf.dmp (621.6 KB)
god i wish i just had 3 crashes per hour
sitting at 209 in 40 hours of playtime
Thereās a lot of people getting results in the thread: KNOWN ISSUE: Crashing at Random, Due to GPU-Related Errors - #1492 by chris26609
Beta Branch info appears to have been helping some: KNOWN ISSUE: Crashing at Random, Due to GPU-Related Errors - #1403 by FatsharkPdr
Also some, including myself, have seen better stability by removing the settings folder and allowing it to be recreated by the game.