Hello everyone,
I recently upgraded to Windows 10 and have been receving BSODs fairly frequently. After using BlueScreenView it seems that ntoskrnl.exe and null.sys are the common culprits. Seems like Googling around is not working so a catered fix would be most appreciated.
Hi tsujin,
Welcome to the 10forums.
This KERNEL_SECURITY_CHECK_FAILURE has a parameter 3 that means that it may hard to find the culprit because it is a list_entry.
Because it is a security error it is recommended to do a full scan with your AV program to start with.
Because there are only windows drivers blamed, which are rarely truly the cause, we need to find the real culprit by stressing it out.
Warning
Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.
Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Quote