Game Audio Cuts Out, Game Freezes, then Game Crashes to Desktop

Warhammer 40,000: Darktide Technical Support
1

Issue Type (Required):

Crash - During Play

Issue Description (Required):

My game crashes quite frequently. In a 2 hour session I can expect upwards of 4 crashes, if not more. What happens is the audio cuts out, the game freezes, and then the game crashes to desktop.

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

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

[PC] Crash Report (Optional):

GUID: b15a3199-cd21-4cf7-b259-d6afc67ebdb5
Log File:
Info Type:

GUID: 8b3c3c77-695e-45c3-907a-868538e606bc
Log File:
Info Type:

GUID: 2c7ce75a-d229-40cf-b40c-db5fe7137eba
Log File:
Info Type:

GUID: 26545d33-78fd-4c3c-a880-6f721763794c
Log File:
Info Type:

GUID: 4867d8a7-0cd1-4f05-bcb1-7bfd7b755942
Log File:
Info Type:

GUID: 31cb0609-fb23-4fc8-a61f-843f3b024636
Log File:
Info Type:

GUID: 15b5aead-ee8e-42cd-9190-4e93b294830f
Log File:
Info Type:

GUID: 6ac5c14e-9d1b-44d4-aa72-78042d091b12
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 79ef8e45-7d29-4c0f-90c5-b6142f1ac95f
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

3

It looks like this is potentially related to the Steam Overlay. Could you try disabling it please?

2 Likes
4

Steam overlay is not enabled for Darktide and I still crash, unfortunately, but I believe it was still enabled for all of the posted crash logs.

I’ve basically tried everything in the “How to Resolve Crashes in Darktide” article as well. Nothing seems to make a difference.

5

Here is a fresh crash report with Steam Overlay disabled:

GUID: 3cde0dd4-fe93-4e3f-817f-eeba2e08d3de
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

6

And still more crash reports from over the weekend. Hope this helps find a fix! If something else is needed or whatever, let me know.

GUID: b640d995-7698-4036-a9fd-5971e14417be
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: d7c10c5f-0e83-42c8-9fb0-3f47fe72fe19
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 1860e737-ef7c-44e8-a723-2b368b7a0fb0
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: f51e8d80-ce72-4b6b-a2f2-faf1d54b9c3a
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: cae2db55-9901-4316-9675-01b44529aab3
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 29af1983-3878-46cc-a730-c56876d53c1c
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 0d966ef1-91c6-4721-8d29-ddec5e67c545
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

7

All these crashes happened in about 45 minutes. The game is borderline unplayable for me at this time. Any ideas?

GUID: 03d8231b-5f47-4193-8a76-1650922145cb
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: bdd8528f-1d56-4609-aa36-5e926b3e7d79
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: ab032699-2361-4272-af01-e262862249b9
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 92baea66-36e3-4d15-be3e-6cf78fb173a9
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

GUID: 1b6df3ed-6109-49c5-9465-28c7591bfe75
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

8

Hi Menti, apologies, I did share this with our Engine Developers on Tuesday but I didn’t comment here at the time.

We believe we have some clues on what the issue is but it’s my understanding that we need to continue delving in to it.

With that in mind, these investigations can take some time. I understand this is not ideal, so I can assist with a refund if you prefer.

1 Like
9

I don’t need a refund, but thank you for offering. I understand it can take time and that’s fine. I’m just glad to know that something is happening, even if it isn’t quite the something I would like.

10

Hi there! Just checking in to see if there has been any progress on this issue. I’m hoping maybe there will be a fix in the next patch coming up.

11

Hi all,

Would also like to know what’s causing this or if there’s a solution. Tried to come back to this game for new update but repeated audio stutter followed by crashing is preventing me from playing.

GUID: 1108b1e9-3457-4f52-a63f-3c3bfa4955bd
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

12

So… it’s been over a month. Any news on this issue? I’d like to play the game again but it’s still crashing the exact same way.

13

Could you try out our experimental build?:

  1. Open the Steam client
  2. Right-click Darktide in your Steam library
  3. Select ‘Properties’
  4. Select ‘Betas’
  5. Enter the password cTYPtKTsfMDsLHAV
  6. Select ‘Check Code’
  7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
  8. Select experimental - Experimental Builds
  9. Close the pop-up window
  10. A download should now start
14

Thank you for the response. Sorry it took me 10 days to get back to you on it, lol.

Unfortunately, the experimental build does not seem to help the issue. I logged in, took two steps, and crashed again.

Here’s the crasify report thing for this crash:

GUID: 5826eb85-6cdc-4f2b-88b2-5c1b5ed35e6f
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.

Currently the process might be stuck in module ‘PhysXCommon_64’.

15

I did the obvious thing here and uninstalled/reinstalled PhysX. It lasted much longer but still crashed after about 20 minutes when I was leaving the mastery window.

GUID: bfbeb901-c4ce-4d5d-84af-2fb99f34003a
Log File:
Info Type:

[Engine Error]: Deadlock detected. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.