Windows 10: Random BSOD

every so often I get the kernel security check failure bsod. One point I wasn't running anything and it happened after boot. I added all my pc specs to my profile

:)

 

ntoskrnl.exe+1640e0 BSOD error

So far, with one memory chip no BSOD. But, getting a BSOD would be random and infrequent.

I've went through that article in the past and still have gotten BSOD.

 

DISM, Windows Reset/Refresh not working.

Faulty RAM can give rise to 'random' blue screens (BSODs).

 

Hi OutlawM2S,

Welcome to the 10forums.

Please remove the ASUS software, this software is known for causing BSOD's.

In case of

Please move some files from the G partition to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.


Warning Less free space could cause BSOD's






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.

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.

 

thanks for the reply the free space issue on my drive was only since yesterday it use to have 30% free on it while my BSOD issue has been going on longer then that. I removed the ASUS software it was from my old motherboard. I will try driver verifier later on and post back with the results