Change Details

Issue is that the PC crashes with BSoD with message KERNEL_SECURITY_CHECK_FAILURE when I've my Fanatec hardware plugged in and I launch a game that has BattlEye anti-cheat enabled. I crashes right when the game is launched, it still allows launcher usage, so this is something related to BattlEye. It doesn't crash if I unplug my Fanatec hardware or I disable the BattlEye anti-cheat from the game, but of course then I can't go play in public multiplayer. Also remembering to unplug Fanatec hardware everytime I want to play the game(s) isn't nice and can't always remember to do that. The games that at least have this issue are Arma 3 and Arma Reforger. Somehow DayZ doesn't have this problem even though it also uses BattlEye. PC hardware: - Intel(R) Core(TM) i7-2600K CPU @ 4,6GHz - G.Skill RipjawsX 2x8,0GB @ CL9 2133MHz - Zotac RTX 3080 12GB (GA102 (LHR)) - System type 64-bit operating system, x64-based processor Windows: - Edition: Windows 10 Pro - Version: 21H2 - OS build: 19044.2728 - Experience: Windows Feature Experience Pack 120.2212.4190.0 Fanatec Hardware: - Gran Turismo DD Pro Wheel Base - ClubSport Universal Hub Xbox V2 I tried to message BattlEye this issue because it's something with their anti-cheat software and your drivers/firmware/hardware conflict and maybe something to do with some specific games they support, but obviously didn't get any response and it hasn't been fixed in after reporting it months ago.

Issue is that the PC crashes with BSoD with message KERNEL_SECURITY_CHECK_FAILURE when I've my Fanatec hardware plugged in and I launch a game that has BattlEye anti-cheat enabled. I crashes right when the game is launched, it still allows launcher usage, so this is something related to BattlEye. It doesn't crash if I unplug my Fanatec hardware or I disable the BattlEye anti-cheat from the game, but of course then I can't go play in public multiplayer. Also remembering to unplug Fanatec hardware everytime I want to play the game(s) isn't nice and can't always remember to do that. The games that at least have this issue are Arma 3, DayZ and Arma Reforger. PC hardware: - Intel(R) Core(TM) i7-2600K CPU @ 4,6GHz - G.Skill RipjawsX 2x8,0GB @ CL9 2133MHz - Zotac RTX 3080 12GB (GA102 (LHR)) - System type 64-bit operating system, x64-based processor Windows: - Edition: Windows 10 Pro - Version: 21H2 - OS build: 19044.2728 - Experience: Windows Feature Experience Pack 120.2212.4190.0 Fanatec Hardware: - Gran Turismo DD Pro Wheel Base - ClubSport Universal Hub Xbox V2 I tried to message BattlEye this issue because it's something with their anti-cheat software and your drivers/firmware/hardware conflict and maybe something to do with some specific games they support, but obviously didn't get any response and it hasn't been fixed in after reporting it months ago.

Issue is that the PC crashes with BSoD with message KERNEL_SECURITY_CHECK_FAILURE when I've my Fanatec hardware plugged in and I launch a game that has BattlEye anti-cheat enabled. I crashes right when the game is launched, it still allows launcher usage, so this is something related to BattlEye. It doesn't crash if I unplug my Fanatec hardware or I disable the BattlEye anti-cheat from the game, but of course then I can't go play in public multiplayer. Also remembering to unplug Fanatec hardware everytime I want to play the game(s) isn't nice and can't always remember to do that. The games that at least have this issue are Arma 3 and Arma Reforger.3, Somehow DayZ doesn't have this problem even though it also uses BattlEyeand Arma Reforger. PC hardware: - Intel(R) Core(TM) i7-2600K CPU @ 4,6GHz - G.Skill RipjawsX 2x8,0GB @ CL9 2133MHz - Zotac RTX 3080 12GB (GA102 (LHR)) - System type 64-bit operating system, x64-based processor Windows: - Edition: Windows 10 Pro - Version: 21H2 - OS build: 19044.2728 - Experience: Windows Feature Experience Pack 120.2212.4190.0 Fanatec Hardware: - Gran Turismo DD Pro Wheel Base - ClubSport Universal Hub Xbox V2 I tried to message BattlEye this issue because it's something with their anti-cheat software and your drivers/firmware/hardware conflict and maybe something to do with some specific games they support, but obviously didn't get any response and it hasn't been fixed in after reporting it months ago.