Windows 10: Persistent BSOD, Kernel Safety Check Failure, just reformatted and reinstalled Windows

I'm hoping someone with extensive BSOD knowledge can help determine the problem. I just reinstalled Windows, after experiencing strange issues after the latest update.

Please don't tell me to reinstall Windows again, as again this is a fresh installation and I shouldn't be having these issues.


Without running "Verifier", the screen gives a "KERNEL SAFETY CHECK FAILURE" message.While running "Verifier", I get the error: "IRQL_NOT_LESS_OR_EQUAL".


Minidumps and System Info can be viewed here!

:)

 

BSOD - Kernel Security Check Failure

Hi Ashton,

There's a lot of reason for booting in to a BSOD, like problems with the driver for your display adapter or the
video output is being sent to an unexpected port. KERNEL SECURITY CHECK FAILURE error is usually caused by Memory or Driver incompatibility issues or corruption of system data.
In order for us to efficiently assist you, we just have few questions for you:

• Were there any changes made to your computer prior to the issue?
• What troubleshooting steps have you done so far?

Regards.

 

BSOD Kernel security check failure


Attachment 29243

Recieving the BSOD once a day, at least. My drivers are up to date so far as I know and I've tried various methods of troubleshooting including the steps outlined here:

What does the Kernel Security Check Failure Blue Screen error mean?

Hoping you guys may have some insight...

 

BSOD Kernel Security Check Failure

You're welcome and you have a great day too!

Safe Mode does not load the NVIDIA graphics driver which has a good probability of causing the crash.

One of the minidump files showed the AEGPUSniffer.exe as the process that crashed.

The AEGPUSniffer.exe is an Adobe component and there have been reports of issues with the latest NVIDIA graphics driver (361.43) :

KERNEL_SECURITY_CHECK_ERROR - Google Suche

To avoid further BSODs I might suggest to uninstall he presently installed NVIDIA graphics and reinstall the previous stable version.

The issue has been reported on the GEFORCE Drivers forum:

{{MetaTags.og.title}}