I do not know if this is just my computer or not, but I’ve had this issue twice now within the last 3 days. I’ve successfully played the game within those 3 days, but this can happen I guess for 1 in 5 tries.
Blue screen caused after hitting the Play button in the launcher. No log file created.
Blue screen says:
Stop code: PAGE FAULT IN NONPAGED AREA
What failed: EasyAntiCheat.sys
OS is Windows 10 64bit.
Side Effect: game is suddenly not detected on steam, thinking I have to do a full installation. My drive still has the files. All other games on the same drive are detected in steam and launch fine.
Easy Anti-Cheat are keen to hear from players with this issue. Would you be willing to email our Easy Anti-Cheat representative if I were to provide you with his email address, please?
Same problem, has happened twice since Grail Knight update, once on launch day, once today. Press play on launcher and get BSOD. It seems to uninstall something in Steam as well as the game itself. Steam has to verify its installation, then the game has to partially reinstall itself, which is something like a 30 minute process… not great.
Which Windows build are you running? Is it a normal build or any of the developer previews?
Does it matter which other programs you have running at the same time? (i.e., if it has happened multiple times, do you have any suspects?)
Practically 0x50 means that EAC (or another application, but in this case the BSOD point out EAC) tried to read from memory which is not in a paged area (i.e. used).
If you want to try some things during the weekend (i.e. before the EAC-rep gets back), I have two hypothesis:
The first thing EAC (easy anti cheat) does is to inspect all running software on your system. If it only hangs at startup it is likely that something is fishy with something already running (could be anti-virus or malware). Try doing full system scans and also try disabling anti-virus at startup of Vermintide (EAC has a history of not always playing ball with antivirus).
It is possible to get 0x50 when paging aggressively (i.e. writing or reading system memory contents to / from disk). How much RAM do you have? This would probably require 8Gb or less unless you are doing a lot of work in the background (like VMs or something else eating memory) to get an error of this kind at startup (i.e. I’m mentioning it because it is possible, not likely).
Windows 7, 64-bit, normal VT2 build / official realm, 16gb RAM, only sanctioned mods
Nothing specific comes to mind for other programs that would alarm EAC… stuff that was running at the time: Webroot, Razer Synapse, possibly Firefox
The game has run normally several times in between the two crashes. Not super eager to run it again to test because the recovery period is significant.
Windows 10, 64-bit here. 16GB of RAM. Official realm with a lot of sanctioned mods as well.
Stuff I usually have running in the background is firefox, discord, and an Autohotkey script. I personally wrote this script myself, and all it does is essentially let me activate my ult key with 2 different buttons – intended for ults you need to aim with (waystalker, bounty hunter, and pyromancer, maybe slayer :v).
Anyway, I’ve installed the game on a different drive. No bsods so far.
Razer Synapse 3, Razer Cortex, and Razer Chroma Kit are known to have had issues with EAC, but I thought they were fixed quite a while ago (before Vermintide supported Chroma).
I have no experience with Webroot though.
If you want to try something try disabling Chroma and Webroot. But intuitively I think it’s something else, both of them should be known by EAC, and EAC known by them.
EAC definitely identifies AHK, I thought it wouldn’t allow it actually, but should lead to “unsafe state” and not a crash.
Have you had any other memory related issues? Does the temperature of the room affect results? I.e. more likely to crash during the day when it is hotter?
I found something interesting when googling a bit, try “easyanticheat.sys page_fault_in_nonpaged_area”.
There are many reports saying that removing EasyAntiCheat.sys (default location C:\Program Files (x86)\EasyAntiCheat\) fixes it. EAC will just download a new version of it next time you run it, so don’t worry about it.
But to be safe, perhaps copy it to a backup location first so you can restore it if needed.
(I’m a bit involved in the EAC on Wine efforts, so EAC is particular interest of mine)
I deleted / reinstalled EAC and have run the game once since then. No loading problems, but I’d been able to run the game in between the two crashes before, so I can’t say if anything is quantifiably different. I’ll update again here if I get another BSOD.
Did you remove EasyAntiCheat.sys before, or did you leave it?
Is your Windows instance weird in any way? (i.e. beta-build, developer-build, not an activated instance of windows, etc?)
Just to be clear, the BSOD is a consequence of the kernel driver EasyAntiCheat.sys somehow mismatching with your system (could be wrong version of the driver, modified windows kernel (such as a insider ring build), or something external causing the mismatch (such as overheating)).
Technically, this is (basically) the order of things when you start the game:
The launcher starts
You press play, which launches the actual game
The actual game, during launch, loads EasyAntiCheat_x86.dll (which resides in the game folder in steam, i.e. if you install the game again you will get a new version of this file)
EasyAntiCheat_x86.dll in turn loads the EasyAntiCheat.sys-driver, which resides in Program Files (x86). Sometimes the EasyAntiCheat.sys-driver is updated as well, although it seems a bit random when it is actually updated
Now the game actually continues to launch, either normally if EAC loaded correctly, or with the “untrusted state” marker in the upper right corner if something went wrong with EAC.
EasyAntiCheat.sys-driver is the one creating your BSOD, since it is a kernel driver it can do “everything” on your computer and crashes the entire machine, rather than just the program (as would have been the case if EasyAntiCheat_x86.dll did something fishy).
I did not remove it. I saw your post after I reinstalled to another drive a day or two later. I figured not to change anything else unless I get the issue again.
Also, my Windows instance is just a 64 bit Windows 10. Windows Pro that is.
