FatsharkLev

Hi @Kroq,

Sorry to hear this.

I can see you’re running into a Deadlock type crash, with some unusual references to ‘scepad’. Are you using a PlayStation controller or other controller?

If so, can you ensure any software for that is up-to-date.

Failing this, can you try disabling your controller and see if the issue persists?

Glad to hear you were able to delve into the issue and resolve things! Happy rat bashing!

This is quite unusual! and doesn’t appear to be something widely reported. It’s a shot in the dark, but do you use any mods? If so, can you please try disabling them and see if the issue persists?

Otherwise, I it may also be a local issue with your installation.

You can try verfying 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

Or, a clean reinstallation of Vermintide 2:

Hi @zeusfaber,

Your new log shows a non-descript Access Violation type crash, but unfortunately doesn’t indicate the exact cause.

I recommend to run through our general crash solutions, here:

Hi @zeusfaber,

Your logs show the following error/exit codes 0xFA718003 and 0xc0000005, both of which usually indicate a conflict with Anti-Virus/Firewall software.

I recommend checking out the following articles and ensuring you have appropriate exceptions in place for both Vermintide 2 and Easy Anti-Cheat:

Hi @Roibr,

This is quite an unusual engine crash. I recommend to try a clean reinstallation of Vermintide 2, as this can often straighten out more complex issues.

Hi @SiennaFuegonasus,

Sorry to hear this.

The first crash is GPU-related, though it’s not clear as to why. I can see you have up-to-date drivers and you’ve mentioned having tried several solutions already. I can only recommend to try our other solutions if you haven’t already e.g. disabling background apps, changing DirectX version, lowering worker threads etc. in our article, here:

I recommend checking our general audio solutions (e.g. updating audio drivers) here:

Hi @Kairos,

From your launcher log I can see there is some confusion over your GPU and your display adapter.

Your NVIDIA 3070 is being detected, and AMD Radeon Graphics, however no valid display is being returned for your NVIDIA 3070.

10:39:53.345 [Launcher] [Main Window] [SysInfo] !! DirectX returns no valid monitors attached for adapter 1 (NVIDIA GeForce RTX 3070 Laptop GPU)
10:39:53.345 [Launcher] [Main Window] [SysInfo] ?? Didn't find a valid display for adapter 1 (NVIDIA GeForce RTX 3070 Laptop GPU)?

It appears that it may be defaulting to Adapter 0 AMD Radeon Graphics.

I recommend ensuring your default GPU is set correctly. Please check out the following:

• • Ensure your monitors are plugged in ...

I’ve sent you a DM.

I have responded to your support ticket.

Hi @AlienBoi,

No problem! I have restored your Veteran’s Lasgun for you

Kantrael MG XII Infantry Lasgun (528)
Deadly Accurate 3
Falter 4

Hi @Bobba,

No problem! I have refunded this bundle for you and returned 2900 Aquilas to your balance.

Hi @nihilus,

I have restored your Veteran’s revolver for you

Zarona Mk IIa Quickdraw Stub Revolver (546)
Crucian Roulette 4
Hand-Cannon 4

Hi @SjharQa,

I suspect there may be an external application interfering here.

I recommend to try a Selective Startup, which can help to identify if this is the case. To do so:

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

If the issue no longer occurs after having performed the Selective Startup, try re-introducing your programs one-by-one to determine which is the culprit.

@SOULLESS, thanks again for your patience. The challenges for Zealot and Mercenary should now be completed and claimable for you.

We’re unsure why these kills weren’t tracking correctly, but we’ll look into it to see if there’s an underlying issue we need to fix.

Ah okay! I’ve passed this log on to our backend developer also.

Update to this! We’ve looked into it further, and found that the explosion doesn’t deal FF damage. However, the projectile itself does. This is intended!

I queried this and have been told that it should work for Trollhamer Torpedo. We’ll look into it!

Hi @SOULLESS,

Apologies - it’s been a busy period and I’m stil awaiting a response from our backend developers. I’ve given them another nudge and I hope they’ll be able to take a look at this soon.

Thank you for your patience.