FatsharkLev

Hi @Tundrarich,

Sorry to hear that. So we can take a look at this for you, can you please message me with your Steam Profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/)

Can you also please provide your console log from the session in which the Grudge Marked Minotaur was killed but the challenge did not complete?

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 lo...

Huzzah! glad to hear that it’s stable again

We haven’t received widespread reports of the latest driver version causing issues - but we are monitoring things.

Hm, hard to say! You can try updating drivers again at any point, and check to see if things remain stable. Worst case scenario you may have to rollback again, skip this driver version and wait for the next.

Hi @Chad_Overlord,

From what I can see, this appears to be mod-related, though I’m unsure of the culprit. I can only suggest disabling your mods and re-enabling them to see if you can determine this.

If you can pinpoint a specific mod causing the crash this would be something best taken up with the mod-author to fix.

Hi @thuanken,

The log doesn’t give us much to go on unfortunately.

Though, I recommend to try running through steps here:

Hi @dannis,

We can try replacing the untrusted bundle file - I’ve sent you a message.

HI @TheVisitor,

The crash report indicates a GPU-related issue.

It may be worth rolling back to a previous driver version, as you mention the issue is a recent one.

Also, I recommend running through all of the possible solutions here:

Hi @Jadjad91,

That’s interesting to see. Thank you for sharing!

I’ve made an update to our FAQ article - hopefully this can help others in future too

Hi @Romucha,

Appears to be a Deadlock crash which I suspect could be mod-related. Though, I’m unsure which!

In any case, I’ve added this to our database to look at, just in case it is something on us.

Thanks for the report!

Interesting, thanks for the update! * fingers crossed * that this has resolved the issue for you.

Hi @walkertrips,

You mention trying all culprits - just to check, have you run through all of the potential solutions here?

Hi @PersianGreen1,

Is this only an issue while playing Vermintide 2? or is this happening with other games?

Could you try a ‘Selective Startup’ and see if the issue persists, please?:

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, and see if the issue persists

Hi @Kurotenno,

Sorry to hear that. I recommend running through some potential solutions in this article:

Ah gotcha No problem - if you do change your mind let me know.

You can try a fresh re-install - just in case!

I can’t see any mods enabled from your logs, but if you are using any mods, please try disabling them.

You mention the crash occurring when another player joins your lobby… It’s a shot i the dark, but if you’re using a VPN, perhaps try disabling this also.

Unfortunately you’re still running into a similar Deadlock crash

I can see you’re still using DX 11. When switching DirectX versions, did you find DX 12 to be any more stable at all?

As you’ve tried all of the usual solutions I’m happy to contact Steam and request a refund for you. I appreciate it’s not ideal, but let me know if this is something you’d wish to do.

Hi @GreyFalcon,

Past the standard audio fix solutions I don’t have an immediate fix I can suggest. Though, I’ve passed this information on internally for investigation and we’ll keep an eye out for other reports of this.

If your friend could provide any videos of this happening with special spawns, and the console log from their sessions this would be helpful to look at.

To provide a console log:

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 @StinkEye,

This one is another similar Deadlock crash. As I suggested in your other post, please can you try changing DirectX version and see if this improves stability for you.

Hi @StinkEye,

From the logs I can see you’re running into a Deadlock crash, which can be a little tricky to troubleshoot.

Can you please try changing from DirectX 11 to DirectX 12 and see if this helps? You can switch DirectX versions using the ‘Settings’ menu within the Vermintide 2 launcher.

Hi @mashmonster,

Looking at the two crash reports provided you’re running into an Access Violation type crash. However, the first log references an issue with your GPU drivers, and second log references NVIDIA PhysX.

The logs definitely nod toward it being a GPU issue, so I recommend trying solutions here:

Hi @KalleCarrion,

Based on the information in the logs, it appears that Microsoft Basic Render Driver is set as your default GPU. Do you have another GPU that is not being detected?

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:
  • For AMD GPUs: ...

Hi @Rbl,

You’re encountering a Deadlock crash which can be tricky to troubleshoot.

To start, I recommend running through our general crash solutions here: