I crashed (on) the Mourningstar

Warhammer 40,000: Darktide Technical Support
1

Issue Type (Required):

Crash - During Play

Issue Description (Required):

I was walking around the Mourningstar as my Arbi and the game crashed.

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

No, I don’t use mods

Reproduction Rate (Required):

Rare (<10%)

Platform (Required):

PC - Steam

Player ID (Optional):

Mersi

[PC] Crash Report (Optional):

GUID: 0f334d75-9129-4f07-b163-8db62048211a
Log File:
Info Type:

[Engine Error]: Deadlock detected while waiting on main thread. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since we need both logs and crashdump to investigate this.

The issue could be related to the following modules found in the stack trace:
module ‘tier0_s64’. This module is related to Steam.

2

Looks like an issue occurred with the Steam client here. If this was only a one-time occurrence, I wouldn’t worry. :slight_smile:

3

I am worried, actually because then this happened just now:

GUID: ee872f65-5e02-4d30-97bf-31d3e3d66167
Log File:
Info Type:

[Engine Error]: Deadlock detected while waiting on renderer thread. Update was not called for 16.0 seconds. You need to supply a crash dump or a crashify link in the report since we need both logs and crashdump to investigate this.

4

:backhand_index_pointing_up:

5

This is a nondescript Deadlock crash, which I understand occurred on switching to Discord. To rule out existing issues tied to Frame Generation, what happens if you disable ‘AMD FSR 3.1 Frame Generation’ in the launcher’s ‘Settings’ menu?

6

If I do that then the game has an unplayably slow FPS that regularly dips into the single digits.

7

What is it exatly that I uploaded in the text from the crash report, then?

8

I understand this can have a severe impact on performance, but you didn’t crash I take it?

We’re working on this issue as a priority, so you should soon be able to play with this option enabled - without crashing. :pray: