Game crashes after about 1 minute in game, whether I am at the select screen, in the Keep, or loading into an Adventure mission. I was getting an “Error 32” from EAC previously when trying to launch the game (it seems EAC was updated in this patch?). It happened about 5 times and has not come back since. Something about not being able to create a file.
This happens in the Official Realm only, even with all mods disabled. I tested in the Modded Realm, where EAC is not used, and the sudden crash did NOT occur. This confirms my suspicions that this is EAC related.
When I crash, the console log doesn’t include a crash report. The game process seems to just suddenly stop.
EAC hasn’t actually received any updates recently afaik. However, we do have some solutions to Error Code: 30005 (CreateFile Failed with 32.) which I believe you’re experiencing:
I tried following that support article (added exclusion to Windows Defender), but it did not help. Again, I am not actually receiving the EAC Error when starting the game anymore.
Another thing to note is that I recently updated to Windows 11 24H2 (from 23H2). I never had any problems like this prior to the latest game update and OS update.
Why wouldn’t the game be generating a report in the log file? If it is an EAC-related error, why doesn’t the game process know about it? Why does it crash out in the middle of operation with no crash report?
Apparently, there is an issue with EAC driver pre-April 2024 with Windows 11 24H2. I am not getting a BSOD, though. Only this game is crashing (that I’ve tried). And the issue is supposed to be limited to Intel 12th-gen CPUs. I am on an AMD Ryzen 7900X.
Hm I see, did you try the other solutions e.g. Selective Startup and checking that EAC services are properly enabled?
Otherwise, are you able to start Vermintide 2 and remain in-game without crashing in Modded realm? Easy Anti-Cheat isn’t applied to Modded realm, so this can help to confirm if the issue is indeed EAC-related still.
Sometimes crashes will occur without our crash reporter tool kicking in. Though a console log should still be being generated. Some of your logs above are abruptly cut off - so something is flat out stopping all game and error reporting processes there.
I believe you should be okay regarding that prior known issue with 24H2 as your system doesn’t have Intel 12th gen, and you’re not running into BSOD errors.
I think I found the culprit. It is a software called DSX (from Steam) for using a DualSense controller in Windows (similar to DS4Windows). Closing out of that software caused the game to stop crashing. That is curious though, as there was no indication from EAC it was closing the game for this reason.
I don’t always have that open, so it makes sense I had not experienced this before. Is there any kind of list of EAC-incompatible programs for VT2 we could add that too? Or perhaps have EAC display a message indicating the reason it is closing the game?
Not sure if EAC was changed for the Versus release. Perhaps the restrictions are a bit tighter now?
Thanks for the update! I’m glad to hear you found the culprit program.
Unfortunately no list. As for error messages, this would be down to Easy Anti-Cheat to implement. Our logs can capture some information, but usually not the specifics of external programs sadly.
No change to EAC for Versus release. Though last general EAC update appears to have been around mid-November. We’re currently using an old version of EAC and will be transitioning to Easy Anti-Cheat EOS early next year, so it’s possible once we’re on the newest version that it may be more compatible with various programs
