FatsharkJulia

As requested!

Hm looking in to this!

If your data corruption errors are persistent, there may be something else at play here. Please see: https://support.fatshark.se/hc/en-us/articles/360021425793--PC-How-to-resolve-data-corruption-errors

Apologies for the delayed response, what exactly did you try - launching in the Modded realm?

This should now be resolved.

Could you try a Selective Startup, to see if any of your programs are conflicting with Easy Anti-Cheat?:

1. Press the Windows key
2. Type ‘msconfig’ and select ‘System Configuration’
3. On the ‘General’ tab, select ‘Selective Startup’
4. Deselect ‘Load startup Items’
5. Reboot your PC
6. Launch Vermintide 2 as normal

Our developers are looking in to this.

I asked QA to look in to this. This was the outcome:

Cannot repro this. However I think it might be the case of them changing character when they are returned to their keep.
So if I am Kerillian in my keep, I join another lobby where my character is picked so I have to pick another character. This will result in me becoming Kerillian again when I get kicked to my lobby.
So if I open a chest as (lets say Bardin) when I’m in another player’s keep and then I get kicked midway, I will be Kerillian in my keep. If I then look at my salvage section as Kerillian I will only be able to see Neckless/Charm/Trinkets that I got from that chest because I opened it as Bardin and any weapon in it would then be for Bardin and would not show up for me as Kerillian

I’m assuming you’ve restarted your PC since reverting these changes, and the performance issues persist?

Unfortunately this crash is occurring as a result of an issue in our backend. We’re working on it - apologies for the inconvenience.

I haven’t had any experience with Error Code 0x0003 but it appears to be an error produced by NVIDIA GeForce Experience.

Sorry, AMD* driver.

Unfortunately I don’t know - may simply be a driver instability, perhaps wait for the next NVIDIA driver or roll back a version and see if the issue persists.

This will likely be due to your high ‘Worker Thread’ count. I’d recommend lowering it within the launcher’s ‘Settings’ menu for improved stability.

It’s unfortunate because there isn’t a lot of consistency in your crashes.

I’d recommend a clean re-installation of your GPU drivers: https://support.fatshark.se/hc/en-us/articles/360021233554--PC-How-to-perform-a-clean-re-installation-of-your-NVIDIA-GPU-drivers

If unsuccessful, please run through the solutions here: ...

Sorry about this - we’ve addressed this crash internally and it will be put live with the release of Season 2, very soon.

Please lower your ‘Worker Thread’ count within the launcher’s ‘Settings’ menu down to 6, and see if there’s any improvement.

Unfortunately your Intel® Iris® Pro Graphics 580 does not meet the minimum requirements for Vermintide 2. This is likely to result in an unstable experience.

Should you encounter this again, it would be super if you could copy and paste the crash report pop-up (the long ‘GUID’ string provided) as we’re able to obtain even more important information from that. Thank you!

This will be addressed in our next patch, due in the next couple of weeks. Apologies for the inconvenience.