Hi @benjiro,

Sorry to hear that.

It appears you ran into an Access Violation crash and I notice you have a Ryzen CPU. I recommend to try lowering your ‘Worker Threads’ count. Please check this article out:

Hi @Tauron,

All of the crash reports and your two recent console logs indicate a GPU-related crash.

It appears that you’ve already tried a few of our ‘go to’ suggestions, but I’d recommend running through (or re-running) each step in this article:

Hi @CommanderCatastrophe,

Our Backend Engineer has taken a look at this - can you please try again?

The issue should hopefully be resolved now.

Glad to hear you resolved it

Thanks for the report @Blazer, this particualar crash is on our radar and we’re investigating. Apologies for any inconvenience.

Conservative Shooter should only return 1 ammo per shot. We’ll take a look, thanks!

Hi @Maraddor,

Hmm, we haven’t received any recent widespread reports of this challenge not unlocking.

Perhaps you were just unlucky with your attempts There are some useful player created guides online, I believe some recommend Stormvermin to be the easiest targets for this challenge.

We’ll monitor for any further reports just in case, but good luck on your next attempt!

Hi @Berettadin,

As the ‘go to’ for this, could you please try running through all potential solutions here?

Hi @Screamingrock

I’ve checked your account and not to worry, I can see your purchased item and a remaining Shillings balance of 288.

We’ve been encountering a spike of Backend Error 1051 occurrences, which we are monitoring. Once the backend stabilizes, this should hopefully resolve the crashes and your Shillings balance should appear correctly again.

Sorry for any inconvenience!

Hi @Eldrig,

Not to worry. I’ve checked your account and can see a hat purchased today in your inventory, and a remaining Shillings balance of 313.

We’ve been experiencing a spike of Backend Error 1051 occurrences, which we are monitoring. Once the backend stabilizes, this should hopefully resolve the crashes and your Shillings balance should straighten itself out again.

Sorry for any inconvenience caused!

Hi @BelgiasVT,

We’re aware of a spike in Backend Error 1051 occurrences - which we are monitoring.

Once the backend errors stabilize, this should hopefully also resolve these crashes, as they are likely related.

Apologies for any inconveience caused during this time

Hi @Kheotour

Based on the information in the logs, it appears your Intel(R) HD Graphics is set as your default GPU, as opposed to your NVIDIA GeForce GTX 1650 .

This is consequently resulting in your crashes in Vermintide 2, as your default GPU cannot handle the demand.

Please see below for our solutions for this problem:

• Ensure your monitors are plugged in to the dedicated (as opposed to the integrated) GPU ports on the back of your PC
• Perform a clean re-installation of your GPU drivers using the appropriate instructions below:
  • NVIDIA GPUs: ...

Hi @Pr0t0n

I’ve sent you a message, as we’ll need your Steam Profile information to look into this for you.

Sorry about that. I’ve added the crash to our database for investigation.

Hi @Imahealer1x

The crash report indicates a GPU-related issue.

I recommend running through potential solutions here:

It should resolve in the same way for Xbox!

Hi @WindblownRebel,

It’s likely due to a backend hiccup - this kind of issue tends to resolve after restarting the Steam client (possibly a few times).

I suspect that the lobby may have become corrupted. Usually this is the case if a player is unable to join, even after a direct invite.

It’s a nuisance, but in uncommon cases of this happening I think creating a new lobby is the only solution.

To everyone who participated… THANK YOU!

The passion for Vermintide is clear in all of your utterly INCREDIBLE creations.

From everyone here at Fatshark YOU. ARE. THE. BEST!

Picking our winners has been very, very tough. However…please join us in congratulating them below!

...

We’ll check this out.

Could you both please provide your console logs from the session that this happened?

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