Warhammer: Vermintide 2 Dev Tracker

Unfortunately with a GPU so below the minimum requirements we are somewhat limited in the support we can provide. Though, I recommend running through possible solutions here:

Hi @Ruper1407,

That is… rather strange. If possible, could you please provide a console log from a session that you try to start this specific mission and encounter this behaviour? It would be very useful for us to look at.

You can locate your console logs via the following:

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 to us

Hi @Frimaire

I can see from your log that your GPU’s dectected are Intel(R) UHD Graphics 620 and Microsoft Basic Render Driver which are below minimum requirements, and consequently resulting in crashing as they cannot handle the demand.

Do you have another GPU that is not being detected?

Hi @Lutheren,

It looks like the ‘Crosshair Kill Confirmation’ mod could be the cause here. Could you try disabling this?

Hi @Five,

Sorry to hear that. If possible, so we can take a look under the hood, could you please provide your console logs and crash dump files from this session?

You can locate your console logs via the following:

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 to us

Your crash dump files can be found within the same parent directory:
AppData\Roaming\Fatshark\Vermintide 2\crash_dumps

Thanks in advance ...

Hi @SgtSmith95,

Sorry to hear that. We’re currently investigating a known issue with daily spikes of backend errors occuring between 12am - 1am BST. We hope to have this resolved as soon as possible.

I’ve also asked one of our Backend Developers to take a look at your logs, in case anything else is at play.

Hi @hollerbach, I don’t have any details off the bat, but I’ve added this to our database so we can take a better look.

If you could also provide your console log from this session it would be very helpful.

You can locate your console logs via the following:

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 to us

Thanks in advance!

It looks like the ‘Crosshair Kill Confirmation’ mod was the culprit here!

Sorry about this @Xanoth I’ve added it to the database.

@Gorius1990, we’ve received quite a few reports of players having some trouble since the latest NVIDIA GPU driver release. Could you try rolling back to an older driver version?
https://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Sorry to hear this we are aware of a couple of similar complaints. Regrettably I don’t have any immediate solutions for you other than what’s listed here: [Xbox One & PS4] How to Resolve Most Connectivity Errors – Fatshark but I don’t think that will be of any help in this scenario. We do have a report open in our internal database for these issues, so I’ll add what you’ve posted here to it.

Thank you @Harridas, I’ve passed this on. Thank you so much for including your launcher.log too!

Edit: This may be resolved with the latest update to Vermintide Mod Framework.

This is unfortunately one of those crashes that has no clear explanation. It is somewhat of a shot in the dark but you could try lowering your ‘Worker Thread’ count down to 6 within the launcher’s ‘Settings’ menu, and see if that helps.

Otherwise please continue to post your console logs here and we’ll look for patterns.

Edit: Also, make sure you try the Verify Integrity of Game Files option 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 Integrity of Game Files’ button
5. When complete, close and reopen Steam

In cases where the errors continue to occur even after using the Verify Integrity of Game Files option, we consider it to be persistent data corruption - which can unfortunately occur for a number of reasons.

We have a list of solutions here, which we’ve created based on what’s worked for players in the past: [PC] How to Resolve Data Corruption Errors – Fatshark

Let me know if you need any help!

Flushing or changing the DNS is usually the most reliable solution for resolving this. Please see: [PC] How to Resolve SIGN-IN TIMEOUT - COULDNT_CONNECT - CONNECTION TIMEOUT - COULDNT_RESOLVE_HOST Errors – Fatshark

Could you try reinstalling/repairing the Visual C++ 2015 Redistributables please?

Vermintide 2 relies on the Visual C++ 2015 Redistributables, and a broken installation may result in an unstable experience.

Please uninstall the existing version of the Visual C++ 2015 Redistributables, reboot your PC and reinstall from the Microsoft website: Download Visual C++ Redistributable for Visual Studio 2015 from Official Microsoft Download Center

If an error is displayed claiming the redistributables cann...

Hello! Unfortunately, many RGB controllers use old, exploitable drivers - another example is ASUS Aura Sync.

I have contacted Easy Anti-Cheat to request these are whitelisted in the past, but sadly they were unable to honour my request due to the reason above.

I can only recommend continuing to disable it prior to launch Vermintide 2. Apologies for the inconvenience.

REVERTED THIS HOTFIX DUE TO CAUSING A 100% CRASH

Hotfix 4.3.0.7

10 May 2021

• Fixed an issue where some Pilgrim’s Coins would not carry over between runs since 4.3.0.6.

REVERTED THIS HOTFIX DUE TO CAUSING A 100% CRASH

Look under ‘Menus’ → ‘Inventory Hotkey’

We’re working on it, apologies for the inconvenience.