Warhammer: Vermintide 2 Dev Tracker

Hi @checking27,

Sorry to hear this.

Your crashes logs are truncated and unfortunately due to being cut off are missing data to help with troubleshooting.

I can see an Exit Code produced (0xC0000409), which can possibly indicate an issue with corrupted files. So, a couple of things worth trying first:

• Verify Integrity of Game Files

1. Right-click Vermintide 2 in your Steam library sidebar
2. Select ‘Properties’
3. Select the ‘Local Files’ tab
4. Select the ‘Verify the Integrity of Game Files’ button
5. When complete, close and reopen Steam

• Failing this, a clean re-installation may be helpful
  ...

@Geltern, oh that’s interesting!

The last update for EAC (v2305.2) was put live on 1st June, which included a single crash fix for games that don’t use DirectX 11 & 12. So, this update shouldn’t have changed anything for Vermintide 2.

Though perhaps their crash fix doesn’t get on with your specific anti-virus software.

Unfortunately I don’t have any access to any further detail than this - but it may be worth reaching out to EAC directly, here:
...

It’s genuinely very strange. I queried this with our console developers and was told there shouldn’t be any criteria needed to access Cinematics. We tested this internally for both Xbox and PS and could not reproduce the issue

Our console developers are going to continue to look into this, although sadly I don’t have an immediate solution to this for you.

The only suggestion I can give for now would be to try a clean reinstallation of Vermintide 2, but I can’t guarantee if this will resolve the issue.

Please let me know how it goes if you try this!

Hm okay! That’s interesting that Modded realm doesn’t work either.

So it may not be purely EAC-related. Though the exception to add for EAC I posted above - underneath the link.

If adding the exceptions above doesn’t work, can you please try reinstalling your Anti-Virus software?

Please let me know how it goes!

To add, which Anti-Virus software do you use?

I’ve noticed the Exit Code 0xFA718003 produced in your launcher log.

In the past, this error code has usually indicated a conflict with Anti-Virus software. Please see:

Hi @Geltern,

Sorry to hear this.

Are you able to launch the game successfully in Modded realm? (chosen from the launcher options)

I ask this, because Easy Anti-Cheat is only applied to Official realm, so this can help to determine if the issue is EAC-related here.

Also, are any other specific messages shown on screen when the crash occurs?

Thanks!

Thanks I’ve dropped you a message

Hi @Ancalagon,

Sorry to hear this. Sometimes it’s possible for DLC to become temporarily desynced with the backend - especially if you’ve returned from a break.

Can you please try restarting Vermintide 2 (possible a few times) and check if the DLC becomes available to you again?

If not, can you please provide me with your Xbox Gamertag so we can take a look at your account in the backend.

Please let me know how it goes!

Hi @NoMoreRush,

This happens with our players from countries such as Turkey and Argentina due to prices dropping beneath Steam’s set threshold during a sale period, unfortunately!

Hi @FelixMann,

We’ve been unable to reproduce this. If possible could you provide us with a video of this issue please?

Hi @ValkyrUmbra,

Sorry to hear this.

From what you describe (Game Security Violation Detected (#0000000E)) there appears to be a conflict with EAC going on. Can you please try disabling any RGB controller software if you use any and see if this helps?

I can also recommend performing a Selective Startup, which can help diagnose whether a background application is resulting in the issue. This can be performed by:

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

If the issue no longer persists after having performed the Sel...

Ah nice one! Glad to hear the issue is resolved and thanks for sharing how

Thanks @Fashinok! That’s super helpful. I’ve passed these screenshots on internally and we’ll continue investigating. Apologies that I don’t have an immediate solution, and thank you for your patience.

Unfortunately not - our investigation was unable to uncover any common factors or correlation between reports. What we did notice was that occurences of these errors sharply dropped off and seemingly improved.

If you haven’t already, then I recommend to try our connectivity solutions, here:

I wonder if this might be mod-related. I can’t determine which one specifically from the log, but can you please try disabling all mods and see if the issue persists?