FatsharkLev

Hm okay. I wonder if there’s an issue with the installation after the recent updates. Can you please try a clean reinstallation of Vermintide 2? As this can often resolve more unusual/complex issues.

This crash is on our radar and should be resolved soon. Thanks for the report!

Sorry to hear this @Amrik

I can see you’re running into Access Violation type crashes, however the root cause of this isn’t clear.

I recommend running through our general crash solutions, here:

Ah Hmm. This is a little unusual then!

Are any specific errors shown on screen? I ask, as there are quite a few that relate to EAC. Here’s our support FAQ for EAC related errors, which I’m hoping if an error is visible to you one of these may cover!

Thanks for the update! This definitely indicates an EAC-related issue.

Next, please try a ‘Selective Startup’, which can help determine if a background application is the culprit:

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 Selective Startup, you will need to re-enable each of your usual background applications one-by-one until the error reoccurs, to determine which is interfering with Easy Anti-Cheat.

Please let me know how this goes!

Sorry to hear this @M3rrick,

Based on the exit code 0xC0000005 in your logs, I suspect the issue is Easy Anti-Cheat related, and a possible conflict with your Anti-virus or Firewall.

Are you able to launch successfully in Modded realm? (chosen from the launcher options). I ask this, as EAC only applies to Official realm - so this can help us to determine if the issue is EAC-related.

If so, please try adding Anti-Virus and Firewall exceptions for both Vermintide 2 and Easy Anti-Cheat. Please see:

Hi @Mushrum,

Unfortunately I don’t have an immediate solution for this, but please rest assured the crash rate for Chaos Wastes - especially for console - is very much on our radar!

This is something we’re aiming to improve in future updates.

We’re currently digging into this issue, and it’s likely going to require a fix in an upcoming hotfix. (It won’t be in the very next hotfix, but hopefully this will be resolved very soon).

Thank you for your patience.

Gotcha, thanks for the clarification! I’ll pass this on to our backend team and we’ll investigate.

I’ll let you know when I have any updates.

Hi @snf5trov,

Can I just confirm if you were attempting to apply the illusions while in the Versus Keep? or the usual Keep?

I ask, as there’s a known issue with the old deprecated UI allowing access to crafting menus while in the Versus Keep - which isn’t intended and will have issues.

Please let me know.

@kuli, that’s my bad! I saved to the wrong sub-category when I added the tag

This issue is on our radar, and only affects the old UI. Thanks for the report!

Ah, that’s interesting to hear! As you’re not crashing on launch, then the exit/error codes in your logs may have been printed incorrectly then

Good spot with the RAM and that replacing it will do the trick!

@lysolet, glad to hear stability has improved!

This crash differs and is an Access Violation type crash. Did this crash occur when trying to launch Vermintide 2?

The exit code in the log “0xFA718003” and the error “Access Violation (0xc0000005)” usually point towards an issue with Anti-Virus/Firewall.

If you find that the crashing persists, then I recommend ensuring you have appropriate Anti-Virus and Firewall exceptions in place. Please try adding following exceptions:

• vermintide2.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries
• vermintide2_dx12.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries_dx12
• ...

Hi @Madrock,

Sorry to hear this!

So we can look into this, could you please provide me with your console log from a session this issue occurred?

To do so:

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

Thanks in advance!

Hi @lysolet,

Your logs show you’re running into a GPU-related crash. I recommend running through our GPU crash solutions, here:

Hi @PhonkEnjoyer,

Sorry to hear this.

Historically, Backend Error 1010 has been linked to temporary server disruption and usually clears up after a short period.

Is the error still occurring now?

We haven’t made any recent network updates. However, OS updates have been made and something hasn’t been playing nicely recently. Unfortunatley this isn’t something that we are able to fix on our end.

As I mentioned before, several players facing these errors have been able to resolve them by downloading the latest Windows updates. If possible, I recommend to try this.

Thanks! I’ve manually unlocked the Amulet of Ashur and you should hopefully be able to speak to Oleysa and proceed as normal now. Please let me know if there’s any issue.

Hi @deviani,

Could you please provide me with your Steam profile URL (e.g. Steam Community :: [Fatshark] Lev) so we can look into this?

Thanks!

Hi @okesska,

Sorry to hear this.

Recently we’ve seen a spike of SSL_CONNECT_ERROR and SSL_BACKEND_ERROR which seems to be being caused by something not playing nicely with Windows.

Many other players have had success resolving these errors by installing the latest Windows updates. Please ensure you have the latest updates and let me know if the error persists.