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

Warhammer 40,000: Darktide Technical Support
263

again…new crash…
crash_dump-2022-12-02-17.44.46-0e4e7aba-343b-44c2-a417-1655b7e1fa18.dmp (717.4 KB)
console-2022-12-02-17.44.46-0e4e7aba-343b-44c2-a417-1655b7e1fa18.log (99.2 KB)

i reached 2 hours of launching game , crash and crash report … i win something in this game ?

264

stable 3 games , crash on 4th
GUID: 499893ea-a7ba-4513-92da-f637fd4f9952
Log File:
Info Type:

265

Loaded the game, got to Operator selection. Clicked the button to choose my operator. Game crashed.

This is getting a bit silly now…

GUID: d670a296-b7f6-4ede-be55-e89e1029c709
Log File:
Info Type:

266

Has your team looked into whether or not these crashes are influenced by windows 11 vs windows 10? Just skimming through the reports from this thread and the one from the beta, windows 11 seems to be a culprit

267

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

Hello and Good Morning/Evening!

I would like to report recent crashes I have experience while playing Dark tide.

Issue Description:
Crash 1:
First Crash happen while loading into the “Coolant Rod Map”. It happens when the screen is changing to first person then it crashes sending me to desktop. Sadly I did not save crash report.

Crash 2 and 3:
Both these crashes are similar and happen approx 5 mins to each other, the map played is the “Silo Strike Map”. The trigger happen when I rapidly switch weapons from melee to range, triggering the crash to desktop. It may also happen when I switch weapons while reloading.

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Crash 2:
GUID: abdcbf42-ab50-4337-9b70-2950f08a4984
Log File:
Info Type:

Crash 3:
GUID: 9bdd7d5a-0c71-48f9-b6a7-dd603c237b7a
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]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)

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
268

And another one, end-phase of a mission with no other issues.

GUID: a6b58901-769d-4fb5-b64f-8881a976c8b9
Log File:
Info Type:

269

GUID: 67dde4c3-98b2-446c-9a95-49466bd22256
Log File:
Info Type:

PLEASE POST CRASHES AND ERRORS IN THE ‘TECHNICAL SUPPORT’ CATEGORY INSTEAD
console-2022-12-01-13.16.08-67dde4c3-98b2-446c-9a95-49466bd22256.log (145.7 KB)
darktide_launcher.log (726.4 KB)

We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.

Issue Description:

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. Navigate to the medical station before Burnside
  3. Crouch-slide into the dumpster next to the blue and white Tertium sign
  4. Get stuck

Mission Name (If Applicable):

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)

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
270

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

Issue Description:

Crash Report (If Applicable):

Platform:
Microsoft store

Player ID:

Reproduction Rate:
100%
console-2022-12-01-02.45.55-c4fee5b8-54fa-45bf-9d10-47f25f97b57d.log (17.4 KB)
console-2022-12-01-02.29.05-296d46ab-4090-4e1e-b82a-19568f062750.log (79.1 KB)
console-2022-12-01-02.39.05-830f6928-df16-4708-90c5-4253096c555c.log (30.9 KB)
console-2022-12-01-02.42.51-9f90ee6d-9f37-4642-89c7-1a8fff1049ef.log (20.7 KB)
console-2022-12-01-02.43.47-8f10ae6a-f788-4c96-861a-5dd428649aff.log (16.6 KB)
console-2022-12-02-17.33.46-2dc7d316-da21-4578-b9cc-7179908c6f40.log (59.7 KB)

271

the new fatshark game is out !!! The game is : launch game , crash , report crash , check your driver installation , change setting of ours 7/8 thousands dollars Gaming PC and repeat, repeat repeat…
Nice gameplay !

272

hahahahaha!

tysm for the laughs! for real… this is beyond dumb… out of 20 or so runs, i’ve managed to complete 1…

i am just playing on repeat now, so i can submit logs! >.> its so stupid…

273

is a shame to release something so broken , a shame

274

man, if they had any respect for themselves, they would shut this game down and refund people while they fix it… this is not release worthy at all

275

Problem description:

Game crashed 4 missions in a row. Specific circumstance is unclear. It only crashed mid-mission, but not during specific objective events or similar things. No crashes on mission start, in the lobby or in the main hub.

RTX 3060ti
i7 10700k

Raytracing is off (and performance got way better with the last patch, nice :slight_smile: ).
Alternating between 8 and 14 working threads did not solve the problem.

GUID: c81de89d-2aa3-403d-949f-1418f554177a
Log File:
Info Type:

276

GUID: 3327c97e-3d9a-4bb1-8917-87b73f9d3014
Log File:
Info Type:

Yesterday patch was fine, today 1 session, afterwards 2 crashes in 3 minutes:
crash_dump-2022-12-02-18.30.32-bc020b9b-7ac6-424e-910c-ec3997997c88.dmp (843.6 KB)
crash_dump-2022-12-02-18.56.56-3327c97e-3d9a-4bb1-8917-87b73f9d3014.dmp (800.6 KB)

277

GUID: d98dfe23-bf30-4aa0-9313-cc22ddf7bda7
Log File:
Info Type:

278

honestly, this is pre-alpha build quality… it would be nice if you guys hired in some game testers before launching a totally broken game… you’d think this would be a common thing to do these days… but i guess they save in cash where they can…

console-2022-12-02-17.41.10-eb4271cd-670c-4301-81f5-57593cb637f9.log (116.9 KB)

console-2022-12-02-17.56.16-fbf80ed9-b081-4d24-82d4-19293e108cde.log (168.7 KB)
console-2022-12-02-18.42.33-b6cd52a2-b72b-4d5f-93b6-aa15f5d1858a.log (58.3 KB)
console-2022-12-02-18.46.43-b9d39447-7455-4007-9010-c425644f340b.log (153.0 KB)

279

Tried to fully uninstall and reinstall the game.
No dice.

console-2022-12-02-19.20.20-a4054ff6-758f-41cd-bca6-7c0137ea81a9.log (60.0 KB)
crash_dump-2022-12-02-19.20.20-a4054ff6-758f-41cd-bca6-7c0137ea81a9.dmp (857.2 KB)

Also tried to turn off DLSS and FSR on (even though I don’t think we should have to do stuff like that to just make the game work).
Crashed even before the post-prologue cutscene started this time. I usually almost get to the train at least.

crash_dump-2022-12-02-19.31.23-18d8cf8a-9ac2-43c1-9bc5-ac76d185a715.dmp (829.4 KB)
console-2022-12-02-19.31.23-18d8cf8a-9ac2-43c1-9bc5-ac76d185a715.log (53.3 KB)

280

GUID: 1b7a6975-bbcb-42ad-9b89-bb0407a13827
Log File:
Info Type:

281

Two new tries with various settings adjusted.

GUID: 7efd6ea6-a740-4ed5-a802-3cb1c9f29bd6
Log File:
Info Type:

console-2022-12-02-19.40.22-7efd6ea6-a740-4ed5-a802-3cb1c9f29bd6.log (54.5 KB)
crash_dump-2022-12-02-19.40.22-7efd6ea6-a740-4ed5-a802-3cb1c9f29bd6.dmp (857.1 KB)
darktide_launcher.log (88.1 KB)
user_settings.config (3.5 KB)

One less working thread:
GUID: 05ec2b2e-d343-4eb4-8eb0-f419186231fa
Log File:
Info Type:

console-2022-12-02-19.44.49-05ec2b2e-d343-4eb4-8eb0-f419186231fa.log (56.1 KB)
crash_dump-2022-12-02-19.44.49-05ec2b2e-d343-4eb4-8eb0-f419186231fa.dmp (821.0 KB)
darktide_launcher.log (119.1 KB)
user_settings.config (3.5 KB)

I think this is it. I’m just not going to try again before this is fixed. I don’t see how you can get any more info from this, as every crash log is the same.

282

Game still crashes from shader cache error = 1.