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.dllin turn loads theEasyAntiCheat.sys-driver, which resides inProgram Files (x86). Sometimes theEasyAntiCheat.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).