JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by SonicFusion: 9/30/2021 5:00:50 AM
1

KERNEL_SECURITY _CHECK_FAILURE Blue Screen when Battleye Launches Destiny

Ever since Battleye was released alongside Season of the Lost, everytime Destiny 2 is launched via steam/shortcut, the battleye launching text pops up, and a KERNEL_SECURITY_CHECK_FAILURE blue screen happens shortly afterwards. After restarting the computer, the game appears as "not installed" on steam, and prompts another installation, even if all the files are intact. This happens EVERYDAY, and after 1 or 2 bluescreens and reinstallations the game works as normal. Fixes I've tried that have not worked: - Verifying Integrity of Game Files before launching Destiny 2 - Uninstalling and reinstalling Battleye (gets BSoD when battleye launches) - Running destiny2.exe, destiny2launcher exe, BEServicex64.exe, BEService_d2.exe, steam.exe as administrator (Worked for about a week, then the blue screens started happening again) - Allowing the above applications and their respective folders through Windows Firewall and Windows Defender Antivirus - Completely uninstalling and reinstalling Destiny 2 (via Revo Uninstaller) - Removing BEService and BEDaisy registers via regedit - Checking for Windows updates - Updating graphics drivers (Up to date) This isn't an isolated case since this has been an issue in almost every other game that adopted Battleye. Searching the problem via Google is inconclusive because most of those discussions either end with either party giving up, or the problem disappearing altogether. I love this game wholeheartedly, but it's already been a month into the season and it's unbelievable that Bungie has yet to address this issue at all. [spoiler]Moderator edit: This thread has been updated with tags that are more appropriate. Feel free to private message the moderator who moved your post, link to topic, for further clarification about why this topic was moved.[/spoiler]

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • It has been two months and this issue has yet to be addressed in any way. I was hoping you would at least try to change anything before witch queen but still nothing has happened.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon