FatsharkAlan

Hi Amao. Perhaps there is some mistake? When I looked at your account, your zealot operative was already named “Zealot.” Is there perhaps a different name you wish to use?

Hi Gatlas. Sorry to see you’ve had such trouble.

Please provide a crash report or console log from a crashed session so that we may take a closer look at why this is happening.

Hello!

The name should be changed now. Please let me know if there are any mistakes.

A post was merged into an existing topic: KNOWN ISSUE: “Access violation (0xc0000005)” Crash

This one is on us. We’re looking into getting it fixed ASAP. Sorry about this in the meantime!

All done! Enjoy being toasty and buttery.

Sorry about that. This should be fixed in one of our next updates.

Please see this thread for more information:

I actually can look this up! It is admittedly a bit of a hassle, as it won’t let me simply copy some segments correctly for whatever reason, and requires a considerable amount of time to present here. (Hopefully this doesn’t become a common request! )

On that note, might I suggest creating a discussion over at our Gameplay Feedback section to propose a feature to view one’s own operative background information? Perhaps if enough players show interest in the idea, it could be read and considered by our developers.
https://forums.fatsharkgames.com...

Hi there. The new names should be in place now. Enjoy!

Hello. I’ve changed your ogryn’s name for you.

Hi kaiserno.

Other than disabling mods, have you attempted any other troubleshooting steps? We have a fair number of suggestions in this link, which may be of some help:

That’s great! Well done. Let us know if the problem continues.

On another note, our engine developers were pretty sure some of those crashes might have had something to do with a program of yours called Overwolf. They’ve since been in contact with some Overwolf representatives, who have recently pushed out an update they hope will fix the issue potentially causing these crashes. If you can, please update and restart Overwolf, and let us know if you have any more problems.

Hello! Sorry to see you’ve been having such a difficult time.

These crashes are all deadlocks, which can be particularly tricky to pin down. However, there is a correlation between Ryzen 5 CPUs and frequent crashing, and AMD have confirmed that updating the BIOS can resolve that. If you wouldn’t mind, could you please try performing a BIOS update? Please see the motherboard manufacturer’s website for instructions on how to do this.

I’ve asked our engine developers to take a look at your crashes. Until then, hopefully a BIOS update is all it will take to get this sorted. Keep us posted on your situation!

Hi Arc. Is this on Xbox or Steam?

Hi Beerman. I sent you a private message. Please respond to me there.

I couldn’t say why it started happening recently, but I’m glad it worked for you!

Hello.

I can see that you are encountering an Access Violation and have a Ryzen 5 CPU. This can usually be solved by updating your motherboard BIOS and limiting the number of Worker Threads used by Vermintide 2. Please give the directions in this link a try and let me know how it goes for you.

Please have your friend update Windows. If they still get this message after having the latest Windows 10 updates installed, share these steps to run the Windows System File Checker.

Hi Mackeviallean. Let’s start by making sure there isn’t some other program interfering with your input. A ‘Selective Startup’ can help diagnose whether a background application is resulting in your issue. This can be performed by:

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

Should you still lose control, then we know it isn’t another application at fault. However, if the issue no longer persists after having performed the Selective Startup, you will need to re-enable each of your usual background applications one-by-one until the problem reoccurs, to determine which is interfering with your character movement.