Engine Error: Deadlock Detected

[DeSky]

GUID: bb57600b-1eb6-4e9f-b01a-d68ca09ca936
Log File:
Info Type:
-----------------------------------------------
[Engine Error]: Deadlock detected. Update was not called for 15 seconds. You need to supply a crash dump or a crashify link in the report since the callstack for this crash is irrelevant.
-----------------------------------------------
[Crash Link]:
crashify://bb57600b-1eb6-4e9f-b01a-d68ca09ca936

Please any one, help me with this error, I've played this game normally for a week and then yesterday this begin to happened.
The game crash after 3 intro in the loading scene, before getting in the menu
I tried everything, restart PC, reinstall the game, validate it. But the game still crashed. I dont know why and really hopeless right now
If any1 know how to fix this, pls let me know
Thanks

[Amber Baal]

DeFragged님이 먼저 게시:

I got this and sent a support ticket. This is the reply:

Julia from Fatshark has replied to:
Crash as host
Hey (name)!

Thank you for your report. Should you encounter the deadlock crash again, applying the change below may assist in resolving your issue:

1. Press the Windows key + R
2. Enter %appdata% into the search input
3. Navigate to 'Fatshark' > 'Vermintide 2'
4. Right-click 'user_settings.config' and open in Notepad or a similar program
5. At the TOP, add the line:
deadlock_timeout = 60

Thank you,

Fatshark Support

Try it, it may help.

I had this error and since i did this i dont get deadlock crashes anymore after changing it from 15 to 60 as suggested by someone from the company.

Problem is i still get DX11 crashes, rarely. (They already confirmed its on there side and not my PC)

[Amber Baal]

I take the above comment back, just crashed again because of "deadlock error" even after changing it to 60 seconds...Company support i got was no help at all.

[Bob]

Amber Baal님이 먼저 게시:

I take the above comment back, just ♥♥♥♥♥♥♥ crashed again because of "deadlock error" even after changing it to 60 seconds...Useless company support.

This thread from a couple weeks ago is from a different problem pre 1.0.7

The current one seems to have to do with horde spawning (or so we think.. not entirely sure). I think with the changes to spawning in general that it isn't so farfetched though.

[Amber Baal]

Bob님이 먼저 게시:

Amber Baal님이 먼저 게시:

I take the above comment back, just ♥♥♥♥♥♥♥ crashed again because of "deadlock error" even after changing it to 60 seconds...Useless company support.

This thread from a couple weeks ago is from a different problem pre 1.0.7

The current one seems to have to do with horde spawning (or so we think.. not entirely sure). I think with the changes to spawning in general that it isn't so farfetched though.

Oh fair enough didnt check dates, still not acceptable though.
No way to fix it on my end?

[Bob]

Amber Baal님이 먼저 게시:

Bob님이 먼저 게시:

This thread from a couple weeks ago is from a different problem pre 1.0.7

The current one seems to have to do with horde spawning (or so we think.. not entirely sure). I think with the changes to spawning in general that it isn't so farfetched though.

Oh fair enough didnt check dates, still not acceptable though.
No way to fix it on my end?

If any of the 3 others I play with or I find a way.. we'll let you know, though we all just stopped playing until they hotfix it. This is being reported everywhere right now and it only started happening after the update.

If there is a quick fix, no one has posted about it yet.

[Amber Baal]

Bob님이 먼저 게시:

Amber Baal님이 먼저 게시:

Oh fair enough didnt check dates, still not acceptable though.
No way to fix it on my end?

If any of the 3 others I play with or I find a way.. we'll let you know, though we all just stopped playing until they hotfix it. This is being reported everywhere right now and it only started happening after the update.

If there is a quick fix, no one has posted about it yet.

Hmk, any news on DX11 crashes? Thats the only other time i crash.

[Bob]

Amber Baal님이 먼저 게시:

Bob님이 먼저 게시:

If any of the 3 others I play with or I find a way.. we'll let you know, though we all just stopped playing until they hotfix it. This is being reported everywhere right now and it only started happening after the update.

If there is a quick fix, no one has posted about it yet.

Hmk, any news on DX11 crashes? Thats the only other time i crash.

Never experienced it myself, but you might want to check the bug section to see if anyone has been mentioning it. Reddit also has occasional posts on these crashes.

[RedSamovary]

Same here. Did all the "fixes": voip, integrity of cache, time limit 60... the game still hang up and CTD with deadlock message. For me , the game was running perfect until the 20gb patch came along. Now i can play less than a match before the crash... For me the game hangs any time: no specific time or map or location in the game. Time to play other game. Sad for you Fat Shark, quality control is not a strength in your dev team.

Update:

Maybe a lucky guess but i've rolled back my display drivers (AMD to 18.2.1) and i've been able to play 3 hours straight in a row without a hitch. I've sended a ticket to AMD to see if the may update is in fact the problem.

[Lebonty]

Yesterday I uninstalled the latest windows 10 updates and reinstalled a clean version of the Nvidia drivers that released when the game came out... Had 5 crashes in 5 games prior to this . None since.

I'm not saying this will fix everyone's problems but just saying it may not be the 1.08 update.