Freze and crash game+ steam app (deadlock)

Issue Type (Required):

Crash - During Play

Issue Description (Required):

GUID: d757e7ee-b4a7-42fa-b655-863e6c30499e

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.
module ‘steamclient64’. This module is related to Steam

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

No, I don’t use mods

Reproduction Rate (Required):

Common (<50%)

Platform (Required):

Steam (PC)

Player ID (Optional):

Upload Supporting Evidence (Optional):

user_settings.config (8.35 KB)
crash_dump-2025-11-30-18.28.03-a82fdb24-afa9-48a5-83ef-883f17f005e2.dmp (870 KB)

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

console-2025-11-30-19.29.58-022e7e8a-f4ad-40d9-8f3f-834c65d00bf0.log (4.38 MB)

@Ichi I believe I responded to your Steam forum post already, but I’ll copy it here too and we can chat on whichever you prefer :slight_smile:

You’re running into a Deadlock type crash, which can be quite notorious. There are some references to the Steam client here. In some past cases, players with a similar error, had this caused by Steam VoIP. Can you please try disabling this to see if there’s any difference?

Otherwise, please ensure that you have latest Steam client updates and Windows updates installed - as this can sometimes be the cause of some unusual issues.

@FatsharkLev
still the same problem, I was playing now and it crashed again with the same error, I have everything updated, turned off what is necessaryhttps://drive.google.com/file/d/1f0274lscrvsrDjSyzWrVTSRkDsb3cGdj/view?usp=drive_link

@FatsharkLev
and now i have this :confused:
GUID: 66c7f1d1-5b5a-4771-8091-81e1f56d426d
Log File:
Info Type:

[Engine Error]: WaitForSingleObject failed with error code: ‘WAIT_TIMEOUT’ and waited for more than 15000 seconds.

At `D:\a\d\vt2-stingray\vt2\release\release_hon_2025_05_12_event_level\runtime\d3d12_render_device\d3d12_render_device.cpp:1536` in function `stingray::D3D12RenderDevice::end_frame`


[Crash Link]:
crashify://66c7f1d1-5b5a-4771-8091-81e1f56d426d

Sorry to hear this. Unfortunately there aren’t any clear indicators from the new crash reports either. I can only really recommend some more general things you could try next:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.