Constant crashes upon trying to load matches, psykanum, and Mourningstar after error 2006

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

Issue Description:
Whenever I try to enter the Psykanum, the game will go to the loading screen, lock up, then crash to desktop. Whenever I try to join a match, the game will find a match, go to a black screen, before I hear an error sound and am kicked. It gives an error 2006 when it manages to reload the mourningstar, but most of the time it will crash like when entering the psykanum.
Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

GUID: 788f3d54-3eea-4427-ae19-f5edf8a7a3be
Log File:
Info Type:

Error Displayed (If Applicable):
When getting kicked before the crash, it gives an error 2006

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

If trying to get to the Psykanum:

  1. Launch game and load into the Mourningstar.
  2. Enter Psykanum.
  3. Crash to desktop on load screen.

If matchmaking:

  1. Launch game and load into the Mourningstar.
  2. Begin matchmaking, get put into fireteam.
  3. Upon loading the fireteam and map, the screen will go black, before error 2006 code happens.
  4. Either the game will (rarely) reload you back at character selection, or (usually) crash to desktop.

[Steam/Microsoft Store]


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

Approx. Time of Issue & Timezone:
4/10/2023, ~12:00 AM, Midnight, Eastern Time

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

100%, constant

Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

The crash in matchmaking happens much in the same style of the Psykanum crash, but recording it results in a file too large to upload.

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-2023-04-10-04.47.36-a8f38889-2beb-40bb-a8e6-9caa459a6062.log (61.8 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 (819.6 KB)

logs refer that you run experimental build, could you try running normal one?

The same problem occurs regardless of the build, I tried the experimental just because it was said to possibly fix any gpu crashes.
Idk if this is solely a gpu crash because the game crashed a ton on my 3070 too, but it’s looking that way since I can’t load into any game of Darktide at all on my 7900xtx regardless of resetting my drivers, resetting shader cache, resetting game settings and worker thread count, etc etc

Which version of Windows are you running please?

I am running on the latest update of Windows 10

Could you double-check for updates? It seems to think you’re running an outdated Windows build for some reason.

Okay so, something very weird happened. I had everything updated and such, but I decided to go into my properties for all launcher instances of the game and enable admin privileges for the launcher exe, game exe, and EAC exe. This seemed to completely fix the problem, and I have no idea what could’ve been the issue with it prior XD

Anyway, the game is working fine now that I put admin priv on the exe files, and I’ve successfully loaded into the Psykhanium multiple times in a row since, with no issues.