Issue Type (Required):
Crash - After Building Shader Cache
Issue Description (Required):
Game crashes on every attempt immediately after the Shader Cache build-up and steam displays “running” notification but nothing happens & Task manager does not display any game activity.
Without the mods, after reaching 100%, there is brief loading icon and a flash of black screen but I’m promptly moved back to the desktop; With the mods its exactly same situation without even a temporary black screen.
I’ve tried, reinstalling and checking file integrity several times, played around with different combinations of DLSS/Frame generation/Ray tracing options, performed game app Cache reinstallation multiple times, tried uninstalling GPUdetection and myriad other methods mentioned on your forums as well as other internet platforms but to no avail.
[PC] Do You Use Mods? (Optional):
Yes, and I’ve tried disabling them
Reproduction Rate (Required):
Constant (100%)
Platform (Required):
PC - Steam
Player ID (Optional):
Clu3Less
[PC] Crash Report (Optional):
GUID: 2e07201f-dbeb-46df-8042-69d8604641d8
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build 5ff3df374e5f4b558202ad2f8a63b073da34ffcb
accessing address 0000000000000000 from 00007FFB27A2901A
The crash occurred in module ‘sl.common’.
The issue could also be related to the following modules found in the stack trace:
module ‘amd_fidelityfx_framegeneration_dx12’.
module ‘amd_fidelityfx_loader_dx12’.
module ‘sl.dlss_g’.
module ‘sl.interposer’. This module is related to Nvidia streamline sdk. If this is a recurring issue disable features related to it and see if that helps.
module ‘unknown_module’.
Upload Supporting Evidence (Optional):
If you haven’t already done so, please try uninstalling your current GPU drivers using a dedicated driver removal tool e.g. DDU (Display Driver Uninstaller), and then reinstalling clean drivers.
Please let me know how this goes.
Will try it tomorrow, thanks for quick reply.
Unfourtunately this had not helped.
@Clu3Lees sorry to hear that. Could you please provide us with an additional crash report for comparison? Hoping this may give us some further clues. Thanks!
GUID: 08cc7bfb-3759-49ee-9eb6-809d916adee7
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build 5ff3df374e5f4b558202ad2f8a63b073da34ffcb
accessing address 0000000000000000 from 00007FFA2EB2901A
The crash occurred in module ‘sl.common’.
The issue could also be related to the following modules found in the stack trace:
module ‘amd_fidelityfx_framegeneration_dx12’.
module ‘amd_fidelityfx_loader_dx12’.
module ‘sl.dlss_g’.
module ‘sl.interposer’. This module is related to Nvidia streamline sdk. If this is a recurring issue disable features related to it and see if that helps.
module ‘unknown_module’.
Here it is. I’ve really been enjoying the game recently and it really would’ve been a bummer if I was not able to continue playing.
Thanks @Clu3Lees
I’ve shared this with our engine developers, and I’ll let you know once I’ve received a response from them!
@Clu3Lees they can’t see anything obvious in the crash dump, but they suspect it’s something related to DLSS. Can you try disabling this in your user_settings.config?
To do so:
- Press Windows + R
- Enter ‘%appdata%’ and press Enter
- Navigate to
\AppData\Roaming\Fatshark\Darktide
- Open your user_settings.config file
- Set
dlss_enabled = false and dlss_master = "off"
- Save changes, and launch Darktide
This has also not helped. I have not found “DLSS enable” line only “DLSS” = 1 so I changed it to 0 but this has also not helped.
I tried launching it through both the Launcher and the .exe file but it was the same result.
Hm okay, DLSS is still our top suspicion based on your log info.
Given you’ve clean reinstalled both your drivers, and Darktide, really your settings in user_settings.config should also have been cleared to defaults 
I would double-check your user_settings and ensure any DLSS settings are definitely disabled.
Also, tangent thought, but is your Windows OS up to date?
I have checked and my windows is up to date and below I will attach my config file if this would help in any way.
Thanks! I’ve spoken with our developers, and they informed me there’s no current way to disable Streamline outright, and as it’s crashing in Nvidia’s code they don’t believe we can do anything past what we’ve already tried. Hopefully we’ll be able to add a way to disable SL in the future, and future SL updates that contain bug-fixes may help with this.
It’s a shot in the dark, but I wonder if some conflicting settings might be causing issue e.g. you have Worker Threads set as both ‘21’ and then ‘22’ further down.
Can you try:
Step 1: Disable Steam Cloud Saving
If Steam Cloud saving is enabled for Darktide, this may automatically restore the AppData and consequently cause the issue to resurface.
- Navigate to your Steam library
- Right-click Darktide
- Select ‘Properties’
- On the ‘General’ tab, scroll down to ‘Steam Cloud’
- Disable ‘Keep game saves in the Steam Cloud for Warhammer 40,000: Darktide’
Step 2: Delete AppData
NOTE: By deleting your AppData, operative 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.
- Press the Windows key + R
- Enter %appdata% within the search input and select ‘OK’
- Navigate to:
AppData\Roaming\Fatshark
- 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.
- Right-click Darktide in your Steam library sidebar
- Select ‘Properties’
- Select the ‘Local Files’ tab
- Select the ‘Verify Integrity of Game Files’ button
- When complete, close and reopen Steam
This had also not worked. Well, thank you for trying anyway. As you said, hopefully this gets fixed with any upcoming patch.
Until then, Im gonna have to make so with Space Marine 2 and TW:Warhammer 3.
Cheers
