Crashing When Loading into Hub

Issue Type (Required):

Crash - During Play

Issue Description (Required):

For the last week or so every time I load into the game I get crashes within 5 seconds. I have tried with and without mods and still get the same crash but sometimes a different error.

I have moved installation folders, deleted Darktide folder in AppData, upgraded drivers, tested RAM, disabled startup items, etc.

I was able to play the game at the beginning of the Rations event but have been noticing these crashes quite a bit since latest hotfix. I have only been able to successfully play the game once since then.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

[PC] Crash Report (Optional):

GUID: 285e716a-484c-4705-9c8b-e053a5f6391f
Log File:
Info Type:

[Engine Error]: Trying to bind to a slot of type ‘0’, name ‘#ID[b5639618]’ using a uninitialized value 0

Assertion failed value != 0 && value != 0x66666666 at D:\a\d\rel_engine_darktide\release\2025_08_20_Patch1.9.x\runtime\d3d12_render_device\shader\d3d12_resource_binder.cpp:526 in function stingray::d3d12_resource_binder::validate_resource_handle


[PC] Upload Console Log & darktide_launcher.log (Optional):

darktide_launcher.log (282 KB)
console-2025-11-11-20.46.45-285e716a-484c-4705-9c8b-e053a5f6391f.log (38.7 KB)

I suspect this could be a shader caching issue. I understand you’ve already deleted your AppData, but please disable Steam Cloud Saving beforehand to make sure it isn’t automatically restored:

Step 1: Disable Steam Cloud Saving

  1. Navigate to your Steam library
  2. Right-click Darktide
  3. Select ‘Properties’
  4. On the ‘General’ tab, scroll down to ‘Steam Cloud’
  5. Disable ‘Keep game saves in the Steam Cloud for Warhammer 40,000: Darktide’

Step 2: Delete AppData

NOTE: By deleting your AppData, your loadouts and custom keybindings will be reset. You may wish to make a back-up of the directory in the event deleting your AppData does not work to resolve the issue.

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to: AppData\Roaming\Fatshark
  4. Delete the entire ‘Darktide’ directory

Step 3: Verify Integrity of Game Files

You will then need to use the ‘Verify Integrity of Game Files’ option, which is accessible via the Steam client and will ensure the installation is complete.

  1. Right-click Darktide in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify Integrity of Game Files’ button
  5. When complete, close and reopen Steam

I have done these steps previously and don’e them again just to make sure and I am still receiving crashes with 10 seconds of running in the hub with the same error popping up:

GUID: 15059466-39ef-4ef0-b5a9-0a3ff192ed57
Log File:
Info Type:

[Engine Error]: Trying to bind to a slot of type ‘0’, name ‘#ID[cfb440f0]’ using a uninitialized value 0

Assertion failed value != 0 && value != 0x66666666 at D:\a\d\rel_engine_darktide\release\2025_08_20_Patch1.9.x\runtime\d3d12_render_device\shader\d3d12_resource_binder.cpp:526 in function stingray::d3d12_resource_binder::validate_resource_handle


Also I sometimes get this error in between the errors above but not as frequent:

GUID: db0a0213-442d-4ae5-835e-d5e8d6440de4
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build fb0f6d54fb7ca448cb818f78892c15c7a24f961a

accessing address 0000000000000000 from 00007FF703FBD747

Thanks for the update. These are some unique crashes, so I’ve raised this with our Engine Developers to see what their recommendations are - I’ll keep you posted.

So it is possible that it was a CPU issue. I ended up doing a partial rebuild and I am now able to play again.

My original CPU was a 13900k and I know that they have had issues with them. Based on research the errors I was getting that were referring to 0xc000005 and correlated with unstable cores even though the error was pointing to potential issues with memory. I tested a couple other games and some threw that error while others were fine.

Since the partial rebuild I am not seeing these errors in Darktide and the other ones that threw 0xc000005.

Thanks!