Issue Type (Required):
Crash - During Play
Issue Description (Required):
I crash whenever I try to do anything before Missions even start. I am still using a GTX 1080 Ti so I was wondering if that might be a problem.
[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):
Engine Error: Deadlock detected while waiting on renderer thread
Upload Supporting Evidence (Optional):
Sorry to hear this @Sheev9001
You’re running into a Deadlock type crash which are quite notorious. The underlying cause isn’t clear from the logs alone, but here’s a few things to try!
Please let me know how you get on!
GUID: 27cb4a29-64b2-4807-98e1-dec672b665c6
Still the same issue. All the top Fixes didn’t work. Is there maybe an issue with the fact that I am still using a GTX 1080 Ti.
Log File:
Info Type:
[Engine Error]: Deadlock detected while waiting on renderer thread. Update was not called for 16.1 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.
Currently the process might be stuck in module ‘NvMemMapStoragex’.
The issue could also be related to the following modules found in the stack trace:
module ‘nvwgf2umx’. This module is related to Nvidia drivers. If this is a recurring issue please try clean install drivers.
@Sheev9001 thanks for the update. This is an engine error that I’m not familiar with. I’ve raised this with our engine developers and I’m waiting to hear back from - I’ll let you know when I do. Thank you for your continued patience.
That said, in the meantime, as the error still references NVIDIA drivers, I recommend uninstalling your GPU drivers using a dedicated driver removal tool e.g. Display Driver Uninstaller - and then reinstalling your GPU drivers with a clean slate.
Please let me know how it goes.
Just got a response! Unfortunately our engine developers couldn’t find anything in particular in the log or dump.
They recommend to try switching to DirectX 11 if the issue persists and see if the crash persists - you can switch DirectX version using the ‘Settings’ menu within the Vermintide 2 launcher.
After switching to DirectX 11 I get the following crash report. It is not exactly the same as before. And this time I crashed while trying to set my key binds.
GUID: e20678bc-9cf3-4ecd-8fc5-583e861b525a
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.
Sorry to hear you ran into another crash. It’s a generic Deadlock type crash, and the cause isn’t clear from the logs 
Unfortunately, I can only suggest running through any of our general crash solutions that you may have not tried already:
https://support.fatshark.se/hc/en-us/articles/360021422873--PC-How-to-Resolve-Crashes-in-Vermintide-2
Otherwise, if we can’t resolve the crashes, I’d be happy to assist with a refund. I appreciate that it isn’t an ideal outcome - but please let me know if it’s something you wish to do.
I appreciate the help. But I do not want a refund. I will be looking into some potential hardware issues. Maybe something there is causing the crashes.
I managed to get it to work again. The problem was that the port my Sata SSD was plugged into was unstable. The fix was just to plug it into another port.
Ah, good catch! Thank you for the update - glad to hear you were able to resolve the issue 