FatsharkJulia

Indeed all very useful information. Thank you!

Thank you for updating us with your solution, it’s much appreciated!

Locking post.

This has been addressed internally, to be included in an upcoming patch. Apologies for the inconvenience.

Apologies for the delays, @CoolHand. I hear you. One of our Engine Developers has looked in to your Access Violations but unfortunately could not determine the cause of the crashes.

In your most recent crash however, I see your GPU has essentially disconnected. This is unusual, as in most cases it would simply hang. It’s possible that some wonky GPU behaviour has contributed to the previous Access Violations, although it’s not clear what could be causing the continuous data corruption considering you’ve ran through the checklist with no problems.

The GPU disconnection is certainly something that needs to be addressed, as it’s unusual for an error of this kind to pop up out of the blue, but unfortunately there is no one shot panacea. Solutions include:

• Perform an...

I would certainly recommend reaching out to EE when you can, and perhaps request a new router.

Oh I’m so silly. I completely misread this post.

Thank you to the posters above.

Thank you @SmokerT69.

For anybody else also experiencing this issue, if restarting Steam doesn’t work, you can also try:

• Rebooting your PC
• Clearing Steam’s download cache
• Changing Steam’s download region

Very odd! Could you please ensure you have the latest updates installed?

Additionally, please verify integrity via Steam by:

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

From the Microsoft website:

The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

and

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

Sorry to copy pasta, but please read through Microsoft’s recommendations below:

Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more information about these procedures, see the owner’s manual f...

Oh no! Have you verified integrity via Steam?:

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

Hmmm it does appear your GPU is crashing at that point. It’s unfortunate that a clean re-installation of your GPU drivers didn’t help, could it be possible that your GPU is overheating? If you need help determining this, let me know.

@Para-Medic Please see my latest response to your ticket.

Hmmm! This is an unusual one, and admittedly I’m not sure how we would replicate this.

Could you try running through the solutions listed here for audio issues?

As above! Thank you @Haxorzist.

Give us a shout if this is still a problem for you @Lave_HD.

The crash upon exit is a known issue.

The bad news is, we usually see this error when a player has a bad router, but there is a couple of other solutions you can try:

• Port Forwarding. The required ports for Steam can be seen here: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711
• Contact your ISP and explain that you’re having problems with your connectivity to ...

Indeed all look to be Access Violations unfortunately, I’ve raised this internally. Hopefully one of our developers can shed some light on this.

The error indicates that one of your DLLs cannot initialise.

Seeing as this isn’t an issue in the modded realm, it’s likely to be related to our anti-cheat service, Easy Anti-Cheat.

Please try repairing it using the using the EasyAntiCheat_Setup executable located here:

C:\Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\installers\EasyAntiCheat

I hear you. We’re very disappointed that 1.6.0.1 didn’t resolve this. I’ve planted the seed and asked if extending the event would be an option, depending on when we can nip this crash in the bud.

Heroes!

Today we’ve put out 1.6.0.1 which addresses a few issues introduced in patch 1.6 - The Anniversary Update:

Fixes

• Fixed one case which could lead to a crash in the ‘Obese Megalodon’ on the event level ‘A Quiet Drink’.
• Changed the quest ‘No Bottle Left Unemptied’ so that it requires a total of 99 ales to be drunk, across all sessions. The quest tracks all party members, so if the host drinks 20 ales and each client drinks 20 ales, the total tracked progress would be 80 ales for each player’s quest progress. Prior to this patch, should a player have drunk 99 ales or more, the quest should auto-complete upon logging in once more during the event.
• Fixed erroneous rain sound effects heard whilst playing ‘A Quiet Drink’.
• Fixed a floating candle on ‘A Quiet Drink’.

EDIT: Unfortunately, it seems we didn’t catch all instances of the crash. We’re actively investigating, but not been able to reproduce...

One of the DLLs required to launch Vermintide 2 is missing.

Firstly, please run the Windows System File Checker by:

1. Launch the ‘Command Prompt’ as an administrator
2. If prompted for an administrator password or confirmation, enter the password or select ‘Allow’
3. Enter the command:
   sfc /scannow
4. Restart your PC once complete

Try launching Vermintide 2 afterwards.

If the problem persists, please launch the ‘vermintide2’ executable located within the binaries, here: C:\Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries

On doing so, an error should be displayed referencing which particular DLL is missing. Please let us know what this error says.