I am getting kernel security check failure blue screen when i am launching D2. it has been 6 days already
Windows 10 Home 64
HELP ME
English
-
Oh, also, here are some more threads you may be able to use for visibility, that I can't add to the catalog above because they marked a progress update as an answer which blocks editing (AHEM!) 4 [url=https://www.bungie.net/en/Forums/Post/259531302]Great Job Bungie...Ruin the Weekend... Destiny 2.exe file missing!!!!! What are you doing to fix it?[/url] 8 [url=https://www.bungie.net/en/Forums/Post/259531682]Can't launch D2 after Update to Season of the Lost and Installing Battleye [Win7|64 Bit][/url] 1 [url=https://www.bungie.net/en/Forums/Post/259536671]Cant launch Destiny 2 after the update of Season of the Lost and the installation of BattlEye because of a mysterious missing file on PC[/url]
-
Kernel security check? Don't think I've seen that one. Especially given the circumstances, I would advise both pursuing it in related threads like this one AND making your own with detailed info including a screenshot and system specs if possible. I wish you luck, season start is the hardest time to get bugs fixed because there are so many of them due to management choices regarding resourcing.
-
Edited by PhellAsleep: 8/29/2021 7:47:50 PMKernel security sounds like it might be an issue with Battleye. But for that to go BSOD sounds like there's something else going on with his computer.
-
No, no, for it to go BSOD with something like Battleye is entirely to be expected. That's a natural consequence of super-invasive software that amounts to a rootkit. So it could very well be entirely Battleye's fault. Battleye is likely injecting code into the kernel, and if anything tampers with that process at all that could lead to anything from BSOD to hard freeze to processes terminating. That said, it could be a lot of other things, too, and since it appears to be a rare error, it could take a long time to get fixed or even sufficiently noticed. Which, of course, is why I tried to give him as many resources as practical to get that process started.
-
Then he shouldn't be in this thread, since this issue has already been traced to Destiny's side of the code. He needs to start a new ticket to get them to check Battleye for his problem.
-
He's still in the same boat as us, though, and I feel for him. So I suggested he pursue all options.