FatsharkLev

Hm, they are still GPU errors

To check, have you disabled overlocks (if any)?
Changed your DirectX version?

This crash report doesn’t appear to be GPU-related, but unfortunately doesn’t provide much information of use to go on

I can only really suggest you run through all of our general crash solutions, so we can exhaust the ‘go to’ options:

The two crash reports above indicate a GPU-related issue. Please try running through the possible solutions here:

Ahh, so tt appears your account had become corrupted in the backend, but one of our Backend Engineers has taken a look at this for you and the issue should now be resolved. Could you try again?

We recently had to revert an update. Could you close down Vermintide 2 and Steam and then re-launch?

With our upcoming PC update today, it’s likely that some mods will encounter issues in the short term and may require updating by the mod creators. So, once the update is live I would strongly recommend keeping mods disabled and to try re-enabling them once they’re proven without issue or have been updated by the mod creators.

As for the new crash report, the error indicates a GPU-related issue. Try running through the solutions here:

Hm, that’s a mixed bag of errors. The very last crash report is a known issue and we’ve yet to fix it, but we’re working on it.

As for the others, it’s possible a mod could be the cause. Could you try disabling any mods and see if the crashes persist? If not, it may require re-enabling your mods one-by-one to determine the culprit.

Hi @DickHouse,

So, the crash reports provided all indicate a GPU-related issue.

You’ve tried some of the ‘go to’ solutions, but it may be worth running through them all a further time.

It’s also possible that the issue could be mod-related, as I can see you use various mods. If you disable your mods does the crashing persist? It may require introducing them one-by-one to determine if the issue is being caused by one specifically.

Hi @silencshadow,

Hmm, so the log doesn’t provide anything concrete to go on. Could you provide an additional crash report to compare with please?

Also, are you using any mods?

Hi @Muehlen, that’s strange! does the issue persist even after restarting the game?

Also, does the issue occur only in the Keep, or in maps?

I recommend to try the following:

• Disable any mods
• Perform a Selective Startup (programs such as SteelSergies Engine can interefere with input)

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

• Disable V-Sync (if applicable)

Two of those crash reports are Access Violation errors again, though the third is a unique one that I haven’t come across before and it seems you are the only person to have encountered it - likely an unlucky one-off.

Have you tried running through all of the possible solutions here?

Apologies @Richielb, I didn’t realize you are playing on Xbox! Please ignore my previous comments.

To echo Saryk above, if you ‘Leave mission’ from the Prologue what happens then?

The backend error seems to have been a temporary Steam issue - which appears to have stabilized now.

Glad to hear that lowering worker threads did the trick!

Sorry all, it appears to have been a temporary Steam hiccup, but things seem stable again now.

When you launch Vermintide 2, from the launcher next to the ‘Play’ button it is possible to choose either ‘Offial realm’ or ‘Modded realm’ - ensure you have ‘Official realm’ selected here.

Yep, it’s another non-descript Access Violation crash.

It may also be worth running through some general ‘go to’ solutions here:

Hi @Richielb,

Are you able to quit the Prologue from the menu and return to the game menu screen?

Also, curious, are you playing on ‘Official’ realm? (this can be set via the Vermintide 2 launcher settings)