Windows 10: BSOD While Gaming (Kernel_Security_Check_Failure)

Anyone that could help, I appreciate it! This issue started yesterday, and I can't pinpoint what started it. I finished my last final for the semester, and I went to open Batman: Arkham Knight. The launcher opened and got to the main menu, but then I got the BSOD saying Kernel_Security_Check_Failure. I have done some reading, and it seems that it's most likely due to a driver issue. I've recently had some issues with trying to force my laptop to use my Nvidia GPU instead of the on board graphics, but that's the only thing I've been changing lately. It was several days before I tried gaming, after which I was able to play Arkham Knight just fine. Other applications so far don't seem to affect it, and after I post I will test a few other games.

Other information: I'm on vacation right now, and can't backup to be able to do a fresh install of win 10. I'd like to be able to game while I'm still on vacation.

Attached are my dump files. I ran the driver verifier, and have the results from that in the updated zip file. I don't know what files to go to to see what driver(s) are the issue that's causing the crash.

:)

 

KERNEL_SECURITY_CHECK_FAILURE while gaming.

The latest errors were MEMORY_MANAGEMENT (1a) stop errors that appears to be related to the NVIDIA graphics driver.

However one of the minidump files showed the following:

BugCheck 1A, {8887, ffffae000c6591f0, ffffae000c471bd0, 504}

Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )

That may indicate an issue with the system RAM or video RAM.

 

KERNEL SECURITY CHECK FAILURE

I'm playing a lot of new games these days.... however some of these seem to crash my pc... That BSOD appears and says "KERNEL_SECURITY_CHECK_FAILURE".

A game (Witcher 3) that worked before updating now crashes too.

I think it is the buggy update. Games worked fine before the update. But for now, any help?

 

You are required to remove every bypass/crack on your system before we proceed.
Forum rules

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.

 

I uninstalled Daemon Tools, but it didn't help. I started going through my drivers, and found that my onboard Intel graphics driver was out of date, even though I had made sure my Nvidia one is up to date. I still can't get my pc to use only the Nvidia one. Would you know anything about that? The Physx engine never changes from the onboard to the Nvidia when I open any game.

Anyways, since updating my graphics driver, it hasn't had a BSOD again.

 

Switchable GPU's are known for causing problems

For example
Today I installed the AMD stuff for my AMD GPU, but hibernation didn't work, screen flashed twice before logging in and the Catalyst software couldn't open. All this and more always happen when I install the AMD stuff to use the AMD GPU. I have never been able to use the AMD GPU for a second without problems and always have used my Intel GPU even though the AMD GPU is by far better.

 

Wow, that's interesting. I have an Nvidia, and in the control panel everything is set to use it, but it still isn't being utilized. It says it's still a render-only card. Is there a way to switch that, or do I just have to wait until I have a new rig?

 

I don't have an nvidia card and thus never seen it what you mean, you likely get an answer here: Graphic Cards - Windows 10 Forums

 

Perfect, thank you for your help!

 

Are you using 361.43 version of nVidia driver ? If that is correct, rollback to 359.06 version and report back.

 

Yes, I am... The same one that requires that I run as administrator, otherwise it decides to ask for a smart card. I'll roll back.

 

I rolled back to 359.06, and no BSOD under the same conditions now. Turns out the issue was the Nvidia driver update!