BSOD Kernel Security Check Failure (ntoskrnl.exe)

axe0 said:

OK, please scan your system with a full scan from Windows Defender and Malwarebytes free

In the installation of Malwarebytes, be sure to uncheck the trial option for the premium version.

sure

axe0 said:

OK, please scan your system with a full scan from Windows Defender and Malwarebytes free

In the installation of Malwarebytes, be sure to uncheck the trial option for the premium version.

ran the above utilities and all came out clear/ no problems

in process of downloading the latest drivers from amd in hopes that it is simply a bad driver

axe0 said:

If the newest doesn't help, install an older version.

while installing the drivers it was saying that the ones I had were in fact out of date...?

so I went through with installation and unchecked the catalyst control panel icon so hopefully no more problems....

I will report back if it BSOD's in the near future and after 30 days i will mark as solved if no more problems arise

axe0 said:

I didn't say they were out of date, but they might need updating.
If updating doesn't work either, then try an older version and see if it helps.

i know you didn't say that, but the installer did

OOOOOKKKKKKK Had another BSOD now this time it was a Driver irql not less or equal.


note: again this happened while watching youtube also heres the .zip with dump files and stuff....

Attachment 36393

axe0 said:

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

If MemTest results are positive (zero errors) then try

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial 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.

ok I will run memtest86 in a few minutes then i will run driver verifier after I get that done.