FatsharkLev

FatsharkLev



02 Feb

Comment

Hi @eddiespaghetti,

The crash report indicates a GPU-related crash. I recommend running through potential solutions here:

Read more
Comment

Hi @SolStrike,

The crash report references GPU drivers, so I recommend to try reinstalling your drivers. When updating your drivers, please perform a clean installation which will ensure all previous versions have been removed.

Read more

01 Feb

Comment

The error in the log DXGI_ERROR_DEVICE_REMOVED indicates a GPU-related crash.

If you’ve found that changing to DirectX 11 works I’d recommend sticking with it!

Though, you can try other potential solutions here:

Read more

28 Jan

Comment

Hi @GiantFriendCrab,

This is possibly related to your user_settings.config being set to ‘Read-only’. Please check this article out:

Read more

25 Jan

Comment

Thanks @wufo, we’ll take a look and see if we can reproduce this.


24 Jan

Comment

Hm okay :frowning: If you haven’t already it may be worth trying a BIOS update. You’ll have to check your motherboard manufacturer’s website for instructions on how to do this.

Otherwise, I’d recommend running through the general ‘go to’ crash solutions here:

Read more
Comment

Hi @Truly,

It appears you’re running into Access Violation type crashes. A couple of things you can try first -

The error in the log references Direct X12 in a few places. Can you try changing to Direct X11 and see if this improves stability?

I also see you have a Ryzen CPU, so I recommend to try lowering your Worker Threads count. Please check out how to do so here:

Read more
Comment

Hi @utrOne_byt,

I’ve checked your account in the backend and can see your progress appears to be intact. Is it possible that you played in ‘Offline’ mode instead? This could explain starting over as ‘Offline’ mode progress is stored locally, whereas your ‘Online’ mode progress is stored our side.

Comment

Hi @AzumgiEnjoyer

Could you please provide us with your console log 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

Thank you in advance!

Comment

Hi @wufo,

Could you please provide us with your console log 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

Thanks in advance!

Comment

Thanks for clarifying! So, this is a separate issue that we’re aware of, which I believe is experienced worse with slower hard drives. I’ve added your reports to the existing entry in our database and given it a nudge.


21 Jan

Comment

Hi @jsinisi001, can you remember if you started this expedition from the start at the lobby, or if you joined the expedition part way during a level? I believe for the challenge to unlock the full expedition from the start would have to be completed.

Comment

As above, were any items passed between you and another player? There is a current known bug that passing an item can cause weapons to become locked out in this way. This is something that we’re currently investigating.


19 Jan

Comment

No problem! of course feel free to continue posting :slight_smile: hopefully a resolution can be found!

If you ran into a BSOD then it’s likely that the issue runs a little deeper.

You have a Ryzen CPU so it could be worth updating your BIOS. Please check out the April 2021 update in this article. Other potential solutions here may also be of help:

Read more

18 Jan

Comment

Sorry to hear that :frowning:

Being honest, as you’ve exhausted all of the ‘go to’ options I’m at a bit of a loss. I’m happy to contact Steam and request they process a refund for you - let me know if this is something you would wish to do.

Comment

The crash report shows another GPU-related crash :thinking:

When performing a Selective Startup did you disable all of your background applications? They’ll differ between individual setups, so you’ll want to try disabling all of your startup items and re-introducing them one-by-one.


17 Jan

Comment

Hm, so your most recent log actually indicates a GPU-related crash this time.

I appreciate you have already tried a few of these, but it’s worth ensuring you’ve run through all of the potential solutions here:

Read more

14 Jan

Comment

Ah okay :frowning: righto, I’ve sent you a message with something else we can try.

Comment

Ah okay :frowning: it seems you’re still running into an Access Violation crash.

Can you try switching from DX 11 to DX 12 and see if stability improves?

I also recommend running through our general ‘go to’ crash solutions here:

Read more
Comment

Hi @Weeed,

I have responded to your support portal ticket :slight_smile:

Though, for anyone else who may come across this post I’ll drop the answer here too -
Activating a Collector Edition key will simply upgrade the account, and nothing e.g. DLC will be lost.