Issue Type (Required):
Crash - During Play
Issue Description (Required):
The game consistently freezes and crashes with a “Deadlock detected” error approximately 4–6 minutes after starting the Prologue tutorial. This issue is 100% reproducible across multiple independent gaming sessions.
The crash also occurs randomly in the Hub and during Missions, but the Prologue provides a stable reproduction environment for debugging.
Troubleshooting Steps Already Attempted (None Resolved the Issue)
Verified Steam game file integrity
Reinstalled Microsoft Visual C++ Redistributable (2015–2022)
Updated NVIDIA graphics driver
Updated / rolled back Realtek audio driver
Changed in-game audio settings
There is no dump file this time.
Please let me know if you need any more logs or testing information. Thank you!
[PC] Do You Use Mods? (Optional):
No, I don’t use mods
Reproduction Rate (Required):
Constant (100%)
Platform (Required):
PC - Steam
[PC] Crash Report (Optional):
[WwiseUpdateThread] Stall 8145 ms: Wwise::wait_for_event
[WwiseUpdateThread] Stall 18993 ms: Wwise::wait_for_event
<>Deadlock detected while waiting on main thread. Update was not called for 16.0 seconds.
<>deadlock
module ‘msvcp140.amd64’
…
NtWaitForAlertByThreadId
RtlSleepConditionVariableSRW
[PC] Upload Console Log & darktide_launcher.log (Optional):
console-2026-06-22-13.18.41-a3e14b58-8cd0-4298-8f50-2e3d82846186.log (45.9 KB)
It would be really helpful if you could throw us some additional console logs so we can make comparisons. Thank you 
console-2026-06-08-05.18.55-ab1aa275-1e5c-4d32-810c-74812ccd83fa.log (40.6 KB)
console-2026-06-08-07.04.22-0bc17982-b2d7-4e1b-afb9-26b07201b56f.log (84.0 KB)
console-2026-06-08-05.41.50-bc7543fc-9e79-453e-918e-8b941af1540e.log (71.9 KB)
console-2026-06-08-05.32.35-9bd7345c-5c4a-4c5b-b2a1-821ca738438b.log (64.1 KB)
crash_dump-2026-06-08-04.57.04-741962a8-13a3-42fe-923c-cffdf8fe8614.dmp (961.3 KB)
crash_dump-2026-06-08-07.04.22-0bc17982-b2d7-4e1b-afb9-26b07201b56f.dmp (1.2 MB)
crash_dump-2026-06-08-05.41.50-bc7543fc-9e79-453e-918e-8b941af1540e.dmp (1.0 MB)
crash_dump-2026-06-08-05.32.35-9bd7345c-5c4a-4c5b-b2a1-821ca738438b.dmp (1.2 MB)
Hello,these are all the files I could find out.
Please note that these logs record crashes that occurred prior to a recent game reinstallation (please refer to the timestamps in the filenames for exact dates), and are not from the most recent sessions.
If you need me to run additional tests (e.g., enabling specific debug modes, running with audio devices disabled, etc.), please let me know and I will cooperate and provide new logs.I really want to enjoy Darktide.
Thank you for your patience and support！
Thank you! I understand you’ve already updated your NVIDIA drivers - do you know which version you’re using now? I ask ask in every log it looks like the drivers date back to 2024, so it would be super to know whether the update to a more recent version has been successful.
Hello, attached is the latest crash log I recorded after updating the game to version 1.12.
This crash occurred in the Prologue tutorial, approximately 2 minutes after entering the game. The Wwise audio thread stalled for 17.5 seconds before triggering the deadlock crash.
I look forward to further updates from the official team. If any additional information is needed, I will do my best to cooperate. Thank you!
console-2026-06-23-11.04.38-7103d3e3-0117-456d-b2f1-e493723f751f.log (62.9 KB)
Thank you, I can see your drivers are up-to-date now, which is super. To rule out any caching issues, could you try deleting your AppData using the instructions below?:
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
Hello.I have done as you said. After that, I launched the game twice. The first time, it crashed very quickly. The second time, after a short while, the voice-over dialogue suddenly disappeared, and then the game crashed when entering an animated CG.
If any additional information is needed, I will do my best to cooperate. Thank you!
console-2026-06-23-14.22.47-65e409e4-b63e-4593-a997-dc0f839ae8b5.log (69.6 KB)
console-2026-06-23-14.34.35-a1bdb03f-1dde-44be-893d-b8d8fb84dac9.log (60.1 KB)
crash_dump-2026-06-23-14.22.47-65e409e4-b63e-4593-a997-dc0f839ae8b5.dmp (998.3 KB)
crash_dump-2026-06-23-14.34.35-a1bdb03f-1dde-44be-893d-b8d8fb84dac9.dmp (1.1 MB)
It appears to continue crashing in the render thread unfortunately. Could you try a ‘Selective Startup’ to rule out whether an overlay or other application is interfering?:
- Press the Windows key
- Type ‘msconfig’ and select ‘System Configuration’
- On the ‘General’ tab, select ‘Selective Startup’
- Deselect ‘Load Startup Items’
- Reboot your PC
- Launch as normal, and see if the issue persists
I have done as what u said.I do also have conducted further testing and captured three additional crash logs for your reference.
i think i should mention that I have already disabled the Steam in-game overlay prior to the last test, and no AMD-related settings are enabled in the game options.
If any additional information is needed, I will do my best to cooperate. Thank you!
crash_dump-2026-06-24-04.22.45-74ede83c-4e52-44d6-bbb5-f0746a47515f.dmp (1.0 MB)
crash_dump-2026-06-24-04.31.21-ed4c0027-ee90-4ad6-a9de-10ff94085858.dmp (1.5 MB)
crash_dump-2026-06-24-04.34.01-0023a3d8-3ce0-4bb7-b966-46920786811d.dmp (1.0 MB)
console-2026-06-24-04.22.45-74ede83c-4e52-44d6-bbb5-f0746a47515f.log (61.9 KB)
console-2026-06-24-04.31.21-ed4c0027-ee90-4ad6-a9de-10ff94085858.log (59.0 KB)
console-2026-06-24-04.34.01-0023a3d8-3ce0-4bb7-b966-46920786811d.log (62.4 KB)
Hello,I wonder if anyone is still watching this thread? 
I just hope to get a little response.I dont wanna spend money for nothing after all
Sorry about that! It looks like the crash is occurring inside an overlay, so I’d recommend disabling any overlays - including the Steam Overlay - that you have running.