KNOWN ISSUE: Crashing at Random, Due to GPU-Related Errors

If I run the default settings “High, DLSS auto, raytracing medium, 3 worker threads” the game runs well, 50-70 fps, for a longer period of time before crashing, like 5-10 minutes.

If I turn worker threads down to 1, the game runs like garbage and I can complete missions, but it’s not very enjoyable playing at 15-60 fps on medium-low settings, with some areas being extremely heavy to run.

Yep Threads to 1 fixes like 99% of the crashes, not sure with DLSS but I turned it off as well. I just wanna play but yeah…Dem frames byebye

We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.


Issue Description:
So as the animation for walking off the ship ends and it goes first person my game crashes. It has happened 4 times in a row now and I am tired of starting up Darktide again. I dont even get a queue to reconnect.
Crash Report (If Applicable):
GUID: 723b8712-adb1-4f3c-b839-9cc9c55afbdf
Log File:
Info Type:


[Please see instructions on how to provide a crash report in the pinned Topic]

Error Displayed (If Applicable):

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Play Chasm Logistratum as Ogryn (Skullbreaker)
  2. Attempt to pick up the second Grimoire
  3. Crash

Mission Name (If Applicable):
Just all missions

Platform:
[Steam/Microsoft Store]
Steam
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
The Silver Moon
Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]
15:03 alaska time
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Constant
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here

Upload darktide_launcher.log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide
  4. Locate the darktide_launcher.log in this directory
  5. Upload here

console-2022-11-30-22.00.06-53b85683-9bfe-49aa-ad4e-675d69f5caf3.log (355.4 KB)

crash_dump-2022-11-30-22.00.06-53b85683-9bfe-49aa-ad4e-675d69f5caf3.dmp (885.9 KB)

Steam ID - Xeoah

I am unable to complete a match without crashing. No other game I own on steam has stability issues. Localized crashing to only this game.

GUID: bb9056f8-e98c-46c4-834d-d228763e2058
Log File:
Info Type:


I’ve tried every troubleshooting step. verify game files, experimental branch, uninstall and reinstall drivers, ddu uninstall, memory integrity check, reinstall cpp libs, disable overclocks, BIOS update, previous version of gpu drivers, etc. in beta a couple days ago i had more stability with FSR than DLSS, and now both are consistently giving crashes. about to try reinstalling OS and going back to windows 10 to see if that fixes it; but if the fine folks at fatshark have any insight before then, I’d appreciate it. Event viewer is showing an error with nvlddmkm

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

play game

Platform:
steam

Reproduction Rate:
constant

Upload Console Log:
console-2022-11-30-23.06.29-4dca1afb-7437-4a50-be21-a2ce9e2c585a.log (1.5 MB)

Upload darktide_launcher.log:
darktide_launcher.log (295.3 KB)

Upload crash dump
crash_dump-2022-11-30-23.06.29-4dca1afb-7437-4a50-be21-a2ce9e2c585a.dmp (706.5 KB)

My hardware:
Ryzen 3800x
32gb ram
3060ti
Windows 10 (see update below)
running with dlss/fsr now no problem

UPDATE!!!:
Reverting from windows 11 to windows 10 has resulted in complete stability. Kind of a drastic step to have to take; but it worked. I tried literally every other step. If you’re getting gpu hangs I would recommend it.

We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.


Issue Description:
I’ve encountered consistent crashing, I would crash multiple times throughout the tutorial, roughly around the time I’m about to extract with the lady I saved. Ended up speed running it to get to the main hub and didn’t encounter any issues for an additional 45 minutes or so. From there on, I am stuck on the cutscene where there are quite a few men/women (praying?) infront of two guards. Within the first 1-2 seconds of this cutscene I will crash to desktop, every time.

RTX 3080
I7 12700F
16gb

Game runs solidly otherwise, I’m beyond excited to jump back in once this issue is resolved!
Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]
GUID: aa705f02-5b66-4b8d-ace3-ae4ee94a0e39
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:]

  1. Play Chasm Logistratum as Ogryn (Skullbreaker)
  2. Attempt to pick up the second Grimoire
  3. Crash

Mission Name (If Applicable):

Platform:
[Steam/Microsoft Store]
Microsoft Store/PC Game Pass
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Impulsex67
Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]
11/30/2022, 6:52PM EST
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Constant
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here
    console-2022-11-30-23.51.31-aa705f02-5b66-4b8d-ace3-ae4ee94a0e39.log (55.3 KB)

Upload darktide_launcher.log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide
  4. Locate the darktide_launcher.log in this directory
  5. Upload here
    darktide_launcher.log (162.8 KB)

More crash logs.
console-2022-12-01-00.05.19-1c3570a3-415e-45af-a7f3-942e04498451.log (80.0 KB)
console-2022-11-30-23.56.44-f0a9e64e-8b65-4d7e-820b-706599e5dbe1.log (561.4 KB)
crash_dump-2022-12-01-00.05.19-1c3570a3-415e-45af-a7f3-942e04498451.dmp (1.1 MB)
crash_dump-2022-11-30-23.56.44-f0a9e64e-8b65-4d7e-820b-706599e5dbe1.dmp (873.0 KB)

I’ve also been having the same crashes I experienced back in Beta. All my problems are related to DLSS. having it on causes crashes 2-3 times a run, turned off I haven’t crashed yet.

GUID: e71edddc-c2dd-4f9a-a5b9-fbc1ff8718c0
Log File:
console-2022-11-30-22.33.14-bcebc9b9-d3d0-40fd-9d61-9e7e888f171c.log (960.4 KB)
crash_dump-2022-11-30-22.24.33-e71edddc-c2dd-4f9a-a5b9-fbc1ff8718c0.dmp (844.0 KB)
Info Type:

GUID: bcebc9b9-d3d0-40fd-9d61-9e7e888f171c
Log File:
console-2022-11-30-22.44.23-9aed9892-0f2e-47b9-a62b-281e854c1135.log (143.9 KB)

crash_dump-2022-11-30-22.33.14-bcebc9b9-d3d0-40fd-9d61-9e7e888f171c.dmp (817.9 KB)

Info Type:
darktide_launcher.log (290.5 KB)
DxDiag.txt (117.5 KB)

Updated my redistributables, reinstalled latest graphics drivers, and repaired corrupted windows files that were found with the DISM script. None of this has changed the outcome of my shader loading error = 1 crashes.

Starting to get annoying, might consider a refund.

GUID: b009c481-307c-44a0-81dd-ddabea05937e
Log File:
Info Type:


I have crashed multiple times in a middle of a game. Usually near the end. I have only gotten one single complete game today

Crashed first game of release, 13900k, 4090, 32 gigs ddr5 6800, windows 11. I crashed nonstop in the beta, I will be refunding as I can’t play the game.

GUID: 08df030b-4e7a-4778-a25e-03d3505f6ad0
Log File:
Info Type:


1 Like

Alright. I am officialy done ! Either this gets fixed in the next days or I am refunding ! I Loved Vermintide and this is just plain sad to see. Had such high hopes for this game…

GUID: ca16d060-cda3-4ec7-82e6-4052418d084e
Log File:
Info Type:


3 Likes

Even tried to play the PC Game pass version still crashing.
console-2022-12-01-02.02.13-31dd922c-1780-47b0-9794-36e01a5a13ba.log (221.6 KB)
console-2022-12-01-02.16.30-8b1f88b4-62a0-4e08-b8bf-1da81bc61b5f.log (110.3 KB)
console-2022-12-01-02.25.05-5dfdbdb5-ef3f-4acc-b815-d1819a9b153b.log (55.4 KB)
console-2022-12-01-02.27.31-6f1dd1d2-035a-4f45-b7b8-70486767663e.log (58.4 KB)
console-2022-12-01-02.32.45-66f3bb5d-8642-4a5e-bf34-caa826bf0f4a.log (56.0 KB)
console-2022-12-01-02.35.05-015b2725-abce-4b7d-b961-fabc52aaddd7.log (58.7 KB)
console-2022-12-01-02.39.21-11e5422a-1529-4a41-bf1c-1516480b1219.log (58.6 KB)
console-2022-12-01-02.40.42-3ff63363-169e-40ee-a6d7-b7ad4bd89ad4.log (97.5 KB)
crash_dump-2022-12-01-02.16.30-8b1f88b4-62a0-4e08-b8bf-1da81bc61b5f.dmp (794.0 KB)
crash_dump-2022-12-01-02.25.05-5dfdbdb5-ef3f-4acc-b815-d1819a9b153b.dmp (897.7 KB)

crash_dump-2022-12-01-02.25.05-5dfdbdb5-ef3f-4acc-b815-d1819a9b153b.dmp (897.7 KB)
crash_dump-2022-12-01-02.27.31-6f1dd1d2-035a-4f45-b7b8-70486767663e.dmp (799.8 KB)
crash_dump-2022-12-01-02.32.45-66f3bb5d-8642-4a5e-bf34-caa826bf0f4a.dmp (896.1 KB)
crash_dump-2022-12-01-02.35.05-015b2725-abce-4b7d-b961-fabc52aaddd7.dmp (832.1 KB)
crash_dump-2022-12-01-02.39.21-11e5422a-1529-4a41-bf1c-1516480b1219.dmp (925.8 KB)

already refunded on steam, constant in game crashes. I even tried it on game pass with the same issues. i7 12700k, 3080ti 32GB ddr5

3 Likes

GUID: 30fa8759-4e88-4716-8634-e4f32ed7a8c1
Log File:
Info Type:

crashing 100% of the time, within minutes of loading into a mission, plus one on the mourning star. crashes were not this bad during the beta period. I am attaching all 5 of my crash logs for the 30 minute session I had on 11/30.

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Play Delta map as vet
  2. Throw grenade at mobs
  3. Crash

Mission Name (If Applicable):
Just all missions

Platform:
[Steam/Microsoft Store]
Steam
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Demondog
Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]
11/30/2022, 7:00 PM Pacific
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Constant
console-2022-12-01-03.01.36-30fa8759-4e88-4716-8634-e4f32ed7a8c1.log (2.0 MB)
crash_dump-2022-12-01-03.01.36-30fa8759-4e88-4716-8634-e4f32ed7a8c1.dmp (943.8 KB)
crash_dump-2022-12-01-02.54.32-28e5a180-3309-4c0d-80f4-d36a53672d7f.dmp (940.8 KB)
crash_dump-2022-12-01-02.42.11-fbc8a037-077e-47b6-be52-79dc8d210d2f.dmp (924.1 KB)
crash_dump-2022-12-01-02.33.15-afaf1b6e-aa8d-4384-b3e6-61a9ef1725e0.dmp (1.1 MB)
console-2022-12-01-02.54.32-28e5a180-3309-4c0d-80f4-d36a53672d7f.log (149.6 KB)
console-2022-12-01-02.42.11-fbc8a037-077e-47b6-be52-79dc8d210d2f.log (147.6 KB)
console-2022-12-01-02.33.15-afaf1b6e-aa8d-4384-b3e6-61a9ef1725e0.log (580.9 KB)
console-2022-12-01-02.31.32-0cfcb5c0-410b-47fb-a3df-95a7134e9076.log (22.8 KB)

Issue Description:

Sometimes Crashes within 10 minutes of launching the game, while still in the mourningstar
Random crashes during missions
One in/immediately following the opening cinematic
Either get 30mins-1hr or 10 minutes of gameplay then caught in crash loop.
Happens at random times, could be while in my inventory, could be as soon as a horde spawns in, nothing consistent about the crashes I’m experiencing

I have uninstalled and reinstalled the game multiple times, both on my HDD and SSD, verified game file integrity, always in the green, and yet I can’t play this game.

Platform:
[Steam]

Player ID:
Steam ID: 76561198069778173

GUID: 6c37a97f-f0ec-42f9-80eb-146a74ba226f
Log File:
Info Type:


console-2022-12-01-04.36.13-dbfe2054-f098-4c31-bd54-b0df800db641.log (58.2 KB)
GUID: dbfe2054-f098-4c31-bd54-b0df800db641
Log File:
Info Type:


I played 3 missions without crashing with threads set to 1 (and horrible FPS, ranging from 30-60) and this crash happened right after I changed settings back to default