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

Is there any way to use the experimental branch through Xbox Gamepass (PC)?

Experimental branch:

Are we going to get any compensation in the way of a ton of crafting materials for all the crashing we’ve had to put up with?

GUID: 440e82e4-75d4-4555-8eb6-9094bc30b2d0
Log File:
Info Type:


crash_dump-2022-12-23-15.59.58-440e82e4-75d4-4555-8eb6-9094bc30b2d0.dmp (842.2 KB)

I’ve tested the experimental branch for seven missions now. No crashes so far. I’ve raised worker threads to five and use the same graphical settings as before and I’m getting around 60-80 frames (capped to 80). The frames are pretty much the same as before, but the lower end of frames feel smoother. Even at 60 the game felt sluggish and it felt like some inputs didn’t register at all.

Issue Description:

Crash Report (If Applicable):

GUID: 8dd4f75f-a767-4fd5-80a6-8797230699c0
Log File:
Info Type:


Error Displayed (If Applicable):
Windows Event Viewer reports two Errors, both ā€œnvlddmkmā€

Steps to Reproduce:
Having worker threads >1 causes the game to crash to desktop. Cinematics always cause a crash.

Mission Name (If Applicable):
N/A

Platform:
Steam

Player ID:
Phobos89

Approx. Time of Issue & Timezone:
[12/23/2022, 11:40AM] [EST]

Reproduction Rate:
Constant

Upload Supporting Evidence:

Uninstalled/re-installed the game.
Uninstalled/re-installed GPU drivers.
Verified game files.

Only workaround is the Worker Threads = 1. I’ve been able to play the game without any crashes as of yet, though the game runs awfully. Almost a full month out from the official launch, and I can’t even utilize my PC’s full potential due to this issue that has persisted since the launch Beta.

console-2022-12-23-16.35.52-8dd4f75f-a767-4fd5-80a6-8797230699c0.log (121.0 KB)
darktide_launcher.log (307.4 KB)

The frequent crashing is 100% as bad as it was when this game was released.

2 Likes

Just spent 25 mins in a high hazard 5 mission and i get a crash at the end while leaving & can’t rejoin in time.
Lost all my materials, chance of a emp & MY TIME was wasted.

If you can’t reproduce it on your specific system, how about trying it on a system that is having these problems.
Surely 1 of your hundreds of staff will have crashing on their pc. Or maybe… just maybe… in future don’t put out a broken product, delay your game until it’s actually ready.
But noooo. you had to release it in this state. I’ve lost all faith in this company, i’ve supported you through Vermintide 1 & 2, bought all dlc’s every cosmetic & put up with your BS with and you still do the same crap.

I must be the idiot for still buying your products right?

I’ve never owned a game in a state as poorly as this, even Diablo 3 wasn’t this bad on launch, jeez.. if i remember correctly they even closed down the game for around 2 weeks to fix the issues.

And we still haven’t received an apology for this crap.

Even though it’s pointless here:
GUID: fb775469-b40b-48a4-a23c-16216912a039
Log File:
Info Type:


crash_dump-2022-12-23-15.59.58-440e82e4-75d4-4555-8eb6-9094bc30b2d0.dmp (842.2 KB)
crash_dump-2022-12-23-17.57.58-fb775469-b40b-48a4-a23c-16216912a039.dmp (1.4 MB)

EDIT:
another crash:
GUID: d61590d6-de91-4ae4-bfaf-2c7bc67f4caa
Log File:
Info Type:


crash_dump-2022-12-23-19.18.34-d61590d6-de91-4ae4-bfaf-2c7bc67f4caa.dmp (841.5 KB)

1 Like

Re the last stable patch: Is this related to EAC_EOS being removed (dll still in)?

Hi.

I have another thing you are welcome to try, and get back to me with wether it does any difference or not. It is to disable the mesh streamer, this will cause the game to require much more VRAM than usual, so if you have low VRAM (6Gb or so) this might not work for you.

Anyway, to disable the mesh streamer, browse to the games steam files.
Locate the file settings_common.ini in the folder bundle\application_settings
In that file, locate the section that says: mesh_streamer_settings = { … }
and change the ā€œdisable = falseā€ to ā€œdisable = trueā€ and save the file.

while you’re at it, or rather, if the mesh streamer hack doesn’t do anything for you, you can also try to disable the multi threaded texture streamer by changing the value
threaded_streamer = true to threaded_streamer = false in the section called feedback_streamer_settings = { … }

Disabling the threaded texture streamer will most likely degrade your performance slightly. Just so you are aware. But I am interested in seeing if any of these actions helps for you who experience these crashes all the time.

7 Likes

I’ll try this now and get back to you whether it has any impact. Sorry for my ranting btw, it’s just that i love the game & simply want it to stop crashing.

1 Like

Just crashed with mesh_streamer_settings = disable = true

crash_dump-2022-12-23-20.39.51-91193b3f-9c66-4ce3-9055-5aa5638acafe.dmp (1.2 MB)

Will try other disabling threaded texture streamer now.

RTX 4090
Ryzen 9 7900x
32 GB DDR5 6000

Quick update for me: I have been playing for the last 6 hours and have not had a single crash. I cannot say that this has fixed it for me but it is a significant improvement. Currently using 13/16 threads. One thing to note is I have my max FPS set to 60 in both nvidia control panel and in-game settings due to another workaround thread. I am going to remove the 60 fps limit and see if the game still crashes. I will report back.

Update: I had a single crash on the desert map since removing the fps limit. Overall this experimental patch has been a huge improvement over the main branch. It has eliminated 95% of my crashing. Thank you for working on this!

I must say, disabling DLSS seems to make the game crash less. Don’t get me wrong, it still crashes too often to be acceptable but I feel like I get like 2x less crashes just by disabling DLSS. Try it guys and let us know if that’s the case for you as well.

1 Like

Personally for me, it’s every other game i’m crashing, i play one game fine then the next i crash every single time.

On experimental branch crashed with both:

mesh_streamer_settings = { … }
disable = true

threaded_streamer = false

GUID: b7aa6df2-0f1c-462b-930e-a9b68f1b60ed
Log File:
Info Type:


crash_dump-2022-12-23-21.42.44-b7aa6df2-0f1c-462b-930e-a9b68f1b60ed.dmp (1.2 MB)

Nevermind, after 4 matches with no crash I just had a match where I crashed once and then another match where I crashed 5 times. F.cking hell…

GUID: b0da75ee-cc33-43ac-833c-e8fdac32b7b8
Log File:
Info Type:


GUID: 4954d874-e29e-4ca5-954c-b5fd5e95ac83
Log File:
Info Type:


Only a couple of crashes today, even dipped my toe in Worker Threads @ 3

GUID: c3a5e6d6-926b-4d80-85d5-f5bd4a90cc22
Log File:
Info Type:


crash_dump-2022-12-23-22.36.00-c3a5e6d6-926b-4d80-85d5-f5bd4a90cc22.dmp (969.5 KB)

GUID: e177c39e-5026-4f75-a44a-c4ac39df1c3a
Log File:
Info Type:


crash_dump-2022-12-23-23.59.01-e177c39e-5026-4f75-a44a-c4ac39df1c3a.dmp (1003.5 KB)

Just FYI, you can replace the DLSS DLL now that EAC is not blocking stuff.
Not sure if that would help any…

1 Like

My crash related dumps and logs with some included Event Viewer.
Darktide logs and crashes to 24.12.zip (5.6 MB)
Darktide crashes - nvlddmkm and Darktide.exe dll crash.zip (2.2 MB)
Packed with 7zip as .zip files.

GUID: 8b94af4d-8a58-4304-8eaa-01e5c5de497b
Log File:
Info Type:


crash_dump-2022-12-24-01.08.58-8b94af4d-8a58-4304-8eaa-01e5c5de497b.dmp (985.7 KB)