FatsharkLev

Sorry about that @conv

So we can take a look, please can you provide a crash report or your console log from the session this happened?

Hi @BullHorn,

The logs indicate a GPU-related crash. I recommend running through some potential solutions here:

Thanks for the report @BelgiasVT, we’re aware of this crash and on the case!

Apologies for any inconvenience.

Thanks @BelgiasVT,

I’ve passed this on internally - we’ll have more crash fixes coming soon!

Apologies for the inconvenience.

Hi @Kertious,

Sorry about that! This specific crash is on our radar, but the fix didn’t make it into the 4.6.2 hotfix. It should hopefully be addressed in the next one!

Apologies for the inconvenience in the meantime.

A new hotfix 4.6.2 is live which should address the common crashes - once you’ve downloaded the hotfix please let us know if you run into any further issues. Thanks!

A new hotfix 4.6.2 is live which should address the common crashes - once you’ve downloaded the hotfix please let us know if you run into any further issues. Thanks!

Hotfix 4.6.2 is now live which should address the most common crashes occurring. Please ensure you have the hotfix installed and let us know if you run into any further issues. Thank you!

I’ve queried this internally, and we believe all of the crashes here are linked to one notorious one that is very much on our radar. We’ve got a fix in the works - hoping to have this resolved soon!

Hi @Mfer_since98,

Please check you have the hotfix installed, otherwise please bear with us whilst we work to address the remaining crashes. Apologies for the inconvenience.

Appreciate the detailed write up! I’ve passed this on and we’ll investigate.

Apologies again for the inconvenience!

We’re on the case and working to resolve this ASAP. Apologies for the inconvenience.

We’ve released a hotfix to address some of the known crashes. If you run into this again please let me know!

Hi @Rodo,

We’re working to resolve this ASAP. Apologies for any inconvenience in the meantime!

I’m also a fan. BOOOOOM!

Sadly I’ll pass this on for a fix though. Thanks!

Hi @TempestWolf, I can confirm this is one of the known crashes - we’re on it! Thank you for the report.

Super, I’ll pass this on - thank you!

Hi @Kitten,

Sorry about that. So we can take a look at this can you please provide us with your console log from the session this happened?

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs
4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
5. Upload the appropriate console log to us

If the log is too big to upload here, you can upload it to a reputable host service (e.g. Google Drive) and link it here, or send it directly to me via Discord - Lev#8708

Thank you in advance!

No worries! The GUID strings are just unique identifiers so we can search up the logs for the specific crashes the actual logs show you ran into the same error.

Appears to be the same error - this one is a nuisance we’re working on it, thanks again!