Trail of Treachery - Access Violation Crash

Warhammer: Vermintide 2 Technical Support
1

Issue Description:
The game crashes on Trail of Treachery for a friend of mine, on version 4.9.3.

Crash Report (If Applicable):
14:14:16.263 <>Access violation (0xc0000005) in build e525b7aaa11015d4031daf6a7a112007c0c07bad
accessing address FFFFFFFFFFFFFFFF from 00007FF661C03733<>

Steps to Reproduce:
At the final part of the sledge where you first start near the small camp site once you get to that first corner it was just crashing every single time (Twitch related? Not sure.)

Map Name (If Applicable):
Trail of Treachery.

Platform:
[Steam/Xbox/PlayStation]
Steam

Reproduction Rate:
It happened every time.

user_settings.config (58.0 KB)
console-2023-03-29-13.17.31-be712d2c-0271-469b-bd47-815f86a7c945.log (1.6 MB)

1 Like
2

Another crash in Trail of Treachery.

“Crashed again when playing trail of treachery hypertwitch deed this time solo with bots (It seems to only be when playing trail of treachery after this new 4.9 patch released)”

<>Access violation (0xc0000005) in build e525b7aaa11015d4031daf6a7a112007c0c07bad accessing address 0000000000000020 from 00007FF70AA81D9D<> (edited)

console-2023-04-03-08.10.27-62cfa5b2-7c44-449a-88d5-0313542ad9f9.log (1.4 MB)
user_settings(1).config (62.6 KB)

1 Like
3

Hi @Haiken,

I’ve raised these crashes in our database and we’ll investigate.

It’s difficult to determine from the logs if this is purely code-related, or another factor.

I’d recommend for your friend to run through our general crash solutions, just in case something helps:

In any case, we’ll look into this.

Apologies for any inconvenience.

1 Like
4

Thanks for the suggestion, but sadly the crash solutions did not work.
After testing some more, it seems to be twitch related, but still specific to this map. He doesn’t get the Access Violation crash when Twitch isn’t active. He also doesn’t get the Access Violation crash on other maps when playing with Twitch.

The crash also seems to occur when he reaches where the player is in the below video at 31:12.

In any case, thank you for looking into this. ^^

1 Like
5

@Haiken,

Thanks for the update and the added information. I’ve passed this on to the developer who is investigating this crash. Much appreciated!

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.