Blue Screen every time I try to start PUBG. Error Code 'Kernel Security Check Failure'

[PNOENICKER]

I have tried literally everything I can and nothing has worked. I even factory reset my pc, wiping all drives and the issue persists.
Any ideas are greatly appreciated.

[Goku]

reset your bios and see

[speedydust]

https://forums.pubg.com/topic/181292-read-me-first-troubleshooting-steps/

[Mekish]

If someone is still having this problem, then try to disable "driver verifier", apparently it sometimes happens to cause problems with Battleye. Hope it helps.

[Mekish]

Автор сообщения: milkweed

Автор сообщения: TheVictim

If someone is still having this problem, then try to disable "driver verifier", apparently it sometimes happens to cause problems with Battleye. Hope it helps.

How do you do that?

You run command prompt, type "verifier", that opens "Driver verifier manager". While in that you have to check "Delete existing settings" and Finish. That worked for me.

Edit: I have just tried it out after restart of computer, and it looks like you need to do this after every start of your computer.

[binco93]

hi juanitor , i have the same problem...pubg kernel securty check with fanatec csw2.5 + fanatec v3 ....it's impossible to fix this error?

Автор сообщения: El Juanitor

Автор сообщения: norm

I just uninstalled PUBG. That helped for me.

Gottem

[PNOENICKER]

Автор сообщения: binco93

hi juanitor , i have the same problem...pubg kernel securty check with fanatec csw2.5 + fanatec v3 ....it's impossible to fix this error?

Автор сообщения: El Juanitor

Gottem

No sir, just unplug everything from Fanatec from the USB ports and restart the pc. So when you then start PUBG, you shouldn't have the error!

[I-hunt-alone]

Every time I try to start PUBG. [ Blue Screen Of Death ] B.S.O.D Error Code 'Kernel Security Check Failure' was happening and every time I restart the laptop the game would ask me to install PUBG [ Player Unknown's Battle Grounds ] and when I click install it would check the existing install and says installed.

I simply went to Windows Defender and selected " Virus and threat protection " and under [ Virus and threat protection settings ] I selected " Add or remove exclusions " under [ Exclusions ] and added entire " Steam folder " [ C:\Program Files (x86)\Steam ] to exclusions and the problem is solved. The problem never happened again. I played a game, closed the game and restarted the game and both times the problem did not happen while it was happening again and again previously.

Hence problem solved.

[zumime]

Автор сообщения: PNOENICKER

So you reckon 16GB isnt enough? :p
Nah I managed to fix it by unplugging my wheel and pedals that I use for simracing. I guess the software of those interfered with the drivers pubg uses.

Thank you for bringing my attention to my sim racing equipment. I unplugged my Fanatec stuff, but that didn't solve it, but then I remembered that I also use VR. So I unplugged my VR headset and that solved it.

TLDR: Unplug VR!

[76561199496871797]

Автор сообщения: klonE

Автор сообщения: Shazam!

I've found a fix for this.

- Update all your drivers.
- Uninstall or disable expired Anti-virus software.
- Copy and paste the below in launch options for the game.
(-malloc=system +mat_antialias 0 window -USEALLAVAILABLECORES -sm4)

This helped me.

I just uninstalled PUBG. That helped for me.

Thanks Man this worked !

[Ranime]

I Disabled Kernel protection in Windows Security center. that "fixed" it for me...

[ScoobyDrew]

Literally that error was being caused for me because my ♥♥♥♥♥♥♥ Xbox controller was plugged in and pubg was throwing a fit. I read somewhere of someone having the same issue and literally just disconnected his controller and it worked. Same happened to me.

[crtk6]

kurwo niedziala

[Bbits]

Автор сообщения: ScoobyDrew

Literally that error was being caused for me because my ♥♥♥♥♥♥♥ Xbox controller was plugged in and pubg was throwing a fit. I read somewhere of someone having the same issue and literally just disconnected his controller and it worked. Same happened to me.

Holy crap good callout. After an hour of driver updating, memory diagnostic, reinstalling, and reading forum posts, this is what fixed it for me.

[Tris The]

I get the same issue made a posting on multiple forums about this, BE hates certain drivers, specifically for me ASIO related stuff. https://www.reddit.com/r/Focusrite/comments/1huuraf/comment/m69ik4u/?context=3