This crash reboots my pc


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

Issue Description:
Loading in to lobby normally now after a few min causes a hard crash rebooting my desktop, sometimes I can play through some of a mission then its a hard crash no BSOD.
I have a 3090FE, 5900X, Asus Crosshair VIII (latest bios as of current release corresponding to this post) 1200W Corsair HX1200i. This game is unplayable for me. 13.7 hours played in this game and I’m only level 6, have hard crashed MANY MANY times.
Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Load up the game
  2. Playing through mission/waiting in lobby causes a hard crash no bsod.

Mission Name (If Applicable):


Player ID:

Approx. Time of Issue & Timezone:
12/09/2022 7:55pm PST
Reproduction Rate:
Constant (100%)

Upload Supporting Evidence:
03:36:24.179 error: [Lua] ERROR [ItemPackage] Unable to find item content/items/characters/player/human/cine_props/bonesaw_01
AND on a different log [D3D12_RENDER_DEVICE] SL Error: '[09.12.2022 19-55-48][streamline][error]commoninterface.h:336[set] Setting ‘common’ constants with the same frame index several times per frame, this needs to be fixed!
those are ending errors of my log ^^^

console-2022-12-10-03.35.22-c97195da-ba96-4077-8394-75826727c19b.log (36.4 KB)
console-2022-12-10-03.51.24-adab0fde-2043-40f8-b3c7-b1a35901a826.log (97.3 KB)

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

This is usually the result of a driver or hardware-related instability. Please see: