kernel_security_check_failure

It is the same as

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

But less text.

axe0 said:

What are the malware scan results?

If the problem persist, just run the dm log collector again, upload the zip and give some description of what happened and what you were doing.

Malware scan results - Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
I ran with all 5 programs that you mentioned. But after the first scan there was nothing. Hope this helps.
-----------------------
Most recent crash log- Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The overall is that there are many different crashes, the 0x139 is the most common.
Please update the drivers below for ruling out outdated drivers
Driver Reference Table - athwbx.sys
Driver Reference Table - amdide64.sys
Please remove this file, this driver is known for causing bluescreens on some systems.

Code:

c:\program files\amd\ati.ace\fuel\amd64\aoddriver2.sys

If after removing and updating the above drivers bluescreens still appear I suggest to enable driver verifier.
Instructions for driver verifier are below.

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 to run driver verifier.

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.

axe0 said:

The overall is that there are many different crashes, the 0x139 is the most common.
Please update the drivers below for ruling out outdated drivers
Driver Reference Table - athwbx.sys
Driver Reference Table - amdide64.sys
Please remove this file, this driver is known for causing bluescreens on some systems.

Code:

c:\program files\amd\ati.ace\fuel\amd64\aoddriver2.sys

If after removing and updating the above drivers bluescreens still appear I suggest to enable driver verifier.
Instructions for driver verifier are below.

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 to run driver verifier.

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.

Welp like a sign from above. after doing all of the first 3 things and restarting it very quickly crashed . So I guess I'm going to try this stress test of sorts :/ (24 hours in, still no BSOD)

Actually the crash isn't from driver verifier.
Please keep driver verifier running until the 48h have passed.