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

Unless otherwise stated, all of the following crash to desktop immediately after loading into the ship lobby.

GUID: af37233e-171d-44fc-8274-7162e211c707
Log File: console-2022-11-29-01.49.59-af37233e-171d-44fc-8274-7162e211c707.log (153.1 KB)
[Crash Link]: crashify://af37233e-171d-44fc-8274-7162e211c707

  • Left recommended settings on for the first try of this experimental branch. Still getting the DXGI_ERROR_DEVICE_HUNG error.

GUID: 04540906-4b8b-4683-bb10-376356c63f78
Log File: console-2022-11-29-01.55.07-04540906-4b8b-4683-bb10-376356c63f78.log (289.1 KB)
[Crash Link]:crashify://04540906-4b8b-4683-bb10-376356c63f78

  • Turned DLSS OFF, Vsync on, Workers 13.

GUID: dabd5c66-61c0-469e-84ad-af2d72d0188a
Log File: console-2022-11-29-02.00.05-dabd5c66-61c0-469e-84ad-af2d72d0188a.log (102.0 KB)
[Crash Link]: crashify://dabd5c66-61c0-469e-84ad-af2d72d0188a

  • Framecap at 60, DLSS OFF, Vsync ON, Workers 13, lasted slightly longer than previous.

GUID: 9ebcbd92-7b62-4acc-a758-d4ceb70e0af9
Log File:
console-2022-11-29-02.04.19-9ebcbd92-7b62-4acc-a758-d4ceb70e0af9.log (444.8 KB)
[Crash Link]: crashify://9ebcbd92-7b62-4acc-a758-d4ceb70e0af9

  • Played a full game at 30 fps cap, workers 13.

5th

GUID: 65fc0044-57e7-422e-b5d7-4b169a6afcb9
Log File:
Info Type:


5th
crash in less than 1 minute entering the map

GUID: d8fb5e0c-a8a8-483f-acac-bac9a8a90a5d
Log File:
Info Type:


Fatshark please be aware it appears your log files are not reporting the correct operating system version. It may be that this problem is prevalent on Windows 11 but your logs would cause you to miss that fact. I am running Windows 11 but your launcher log says I’m using Windows 10. I included my dxdiag in my last crash report so you can compare.

Still getting crashes using the latest experimental build

the build number will easily filter that out. Windows 10 and 11 have very different build numbers

GUID: b92b0cd9-a94b-4c63-af6a-7f526989fd5a
Log File:
Info Type:


console-2022-11-29-03.05.34-b92b0cd9-a94b-4c63-af6a-7f526989fd5a.log (98.9 KB)
crash_dump-2022-11-29-03.05.34-b92b0cd9-a94b-4c63-af6a-7f526989fd5a.dmp (1.1 MB)
DxDiag.txt (95.7 KB)

Please note I’m on Windows 11, not Windows 10 as your launcher log indicates.

5th
Introduced mouse lag issue. Did not crash though! :slight_smile:

Have always had issues with crashing to desktop, win 11, 13900k, 4090, 32gigs ddr5 6800. I installed the 5th iteration of the test and this is the first time I never even made it into the game, I crashed in the ā€œtowerā€ right as I was loading in. I did turn worker threads up to 12 and dlss back on in the launcher. I’ve only been able to play by either capping my fps to 60 or worker threads at 1. I can’t complete a single mission without ctd if I don’t do one of those things.

GUID: cc6832dc-54e8-4ca7-a147-b4d20d8dbd51
Log File:
Info Type:


EDIT: I verified game files and restarted steam, I was able to enter the game and select my mission but I crashed within 2 mins of playing, basically right as we found the first enemies.

GUID: 0ff9928d-f8fc-4ef7-9588-b2b2752e3224
Log File:
Info Type:


I checked mine , thats true.
My intuition tells me it might be the key.
Someone said in DC, he and his friend, even with exact same type of PC from one manufacturer , win11 has crashing problem while Win10 not.

yes my 2 buddies are on Windows 10 and have no problems. I have much better hardware but Windows 11 and I crash constantly.

Yeah i saw that mentioned earlier, that windows 11 users are struggeling the most.

No cigar.

GUID: 994815bb-70bb-4677-a70b-5097998379a3
Log File:
Info Type:


I have been crashing consistently, I cannot even complete a single mission.

CPU: Ryzen 3900x
GPU: RTX 3080 FE (stock settings)
OS: Windows 11
GPU Drivers: I have done a clean/fresh install using DDU.
BIOS: Updated to the latest version available for my motherboard.

Event viewer snippet shows multiple nvlddmkm errors.

I can say wholeheartedly, that it didn’t matter whether I was on Win10, or 11- I still crashed. Admittedly the frequency was far worse on Win11, until I fiddled around a bit.

Now, I’ve not gone back to a different version of Win11 or anything like that, but for those of you, who in your event viewer get the warning & error messages citing ā€œnvlddmkmā€, I believe I’ve found a bandaid. Well, at least until Fatshark manage to find a way to remove the abhorrent strain the game seems to place on the GPU.

Simply put: Go into your Power Options, hit the PCI Express dropdown & make sure you’ve got power savings set to off >>>(I’d not advise doing this if you haven’t got a strong PSU to back up the additional power usage) <<<. As many have surmised, the game seems to chug heavily on the GPU juice, and ever since I’ve made the switch, I’ve crashed once in 3 games. Before this, I wasn’t even able to reach the vendor on the Mourning Star without the game closing. It may not sound much, but, given the frequency of it happening before? Yeah…

I’ve taken two more crash logs, on before I made the change, and then the only one I’ve suffered post. I’d be interested to see if the reason for crashing is the same as the one prior to the change.

Pre the above changes made, crash on the Mourning Star

GUID: 7f5c0146-e85a-43e3-a9b5-1fd6d7c12e5a
Log File:
Info Type:


console-2022-11-29-02.39.19-7f5c0146-e85a-43e3-a9b5-1fd6d7c12e5a.log (48.3 KB)

"Post changes being made, mid-mission crash & still showing as an "nvlddmkm" in the event manager

GUID: c44f85d7-553e-4083-ba25-8f548ad17f43
Log File:
Info Type:


console-2022-11-29-02.51.35-c44f85d7-553e-4083-ba25-8f548ad17f43.log (242.1 KB)

As a final note:
-These are the relevant specs: Win 11, 1080 ti, i7 10700k & 16gb of good DDR4.
-As for display: 12 threads, frame rate capped to 60 & medium to low graphical settings being used across the board.
-I’ve also not launched the latest experimental build either.

1 Like

Crashed under newest experimental again.

GUID: 658ed959-194c-4446-b966-6fbd89b06a37
Log File:
Info Type:


I know I’m a bit late to this particular issue, but I’ve had some recent GPU related problems as well that have been quite nerve-wracking. Both with Darktide and with other games (BF2042, Evil West, Assissin’s Creed, really anything graphics’s intensive).

I dunno is this little suggestion here will help, for Nvidia users at least, but one suggestion I found on the Internet is to turn on Debug Mode in the Nvidia control panel.

I can’t explain it, but it fixed my particular issue (for Darktide, I still need to test other games) and maybe it’ll fix the problem for others here. I can’t say that I have read every single post in this thread, but I suppose it’s worth a try for some.

Good Luck.

Fifth potential fix: Crash at the exact same spot in the post-prologue cutscene (made a new character just to have that cutscene as a benchmark, don’t have time to play before work).
I’ll provide my DXDiag as well, in case it helps narrow things down any.

EDIT: Also, I too have ā€œDisplay driver nvlddmkm stopped respondingā€¦ā€ in Event Viewer, I’ll put that in here as well.
And I am on Windows 11, despite the console logs saying Windows 10.

GUID: 57ca59af-a659-4307-923d-f7e9822e8624
Log File:
Info Type:


crash_dump-2022-11-29-05.12.40-57ca59af-a659-4307-923d-f7e9822e8624.dmp (828.3 KB)
console-2022-11-29-05.12.40-57ca59af-a659-4307-923d-f7e9822e8624.log (835.5 KB)
DxDiag.txt (112.9 KB)
EventViewer.txt (1.3 KB)

After 83 hours in the Beta, I can now say that locking FPS to 60 is BY FAR the biggest help, once I turn it down the amount of crashes is severely reduced.

Total War Warhammer 3 had the same problems that Darktide seem to have;
Windows 11 + High end pc = a really bad time.

3080TI
12th Gen Intel(R) Coreā„¢ i9-12900K 3.19 GHz
64G Ram
Windows 11.

EDIT: worker threads are likewise a big factor in crashes.
My fix to have as few crashes as possible; NO DLSS, Low worker threads but there are still crashes at 2+ threads, cap framerate at 60, low to medium settings.

Uh i seem to have missed a fifth branch yesterday, i’ll hop ingame immediately and test it out!