Warhammer: Vermintide 2 Dev Tracker

Add the game to your anti-virus whitelisting, or disable your anti-virus entirely

I understand communication is lacking and I’ve pressed for an update. I’ve also stressed that this is our most concerning issue at current.

It’s no secret that we’re having a hard time with this.

There are some potential remedies in the upcoming patch but we don’t know exactly how this will interact with the internal_error (Error Code: 2007). Failing that, additional logging has been added to help our developers pin it down.

I promise, once I have more to share, I will - please believe me when I say I’m not purposely withholding any information.

Please post your console and dark tide launcher logs

I don’t know bud. Please stop bumping this.

We are currently looking in to an issue where players can crash upon pressing ESC when in Hadron’s new menu.

Existing reports may be merged here, to help us keep track of the issues being reported.

This should now be resolved!

Perhaps it’s worth looking through here: https://support.fatshark.se/hc/en-us/articles/360038965013--PC-How-to-Resolve-PC-Crashes-Loss-of-Responsiveness-or-Blue-Screens-BSOD-

Have you used the ‘Verify Integrity of Game Files’ option? https://support.fatshark.se/hc/en-us/articles/360021233534--PC-How-to-Verify-Integrity-of-Game-Files-via-Steam

We’re looking in to it. Thank you.

I’ve passed this on to our developers. Thank you for your reports.

Can you screenshot your virtual memory settings again?

Also how much free space do you have on your C:\ and D:\ ?

Any luck with the above?

Sounds like a bad time. We’re working on it!

Not sure on this one unfortunately, but I’ll make sure it’s added to our database.

Thank you, I’ve added your report to our database.

Does the Easy Anti-Cheat loading screen appear prior to your crash?

It looks like your installation may be incomplete. Try: https://support.fatshark.se/hc/en-us/articles/360021233534--PC-How-to-Verify-Integrity-of-Game-Files-via-Steam

Crash #1 is on our radar, crash #2 appears to be one of the notorious GPU-related crashes we’re contending with.