Skip to content

Kernel_security_check_failure Windows 10 Fix

Last updated on 27th January 2020

I recently started using a machine with an AMD A10-7870K, an older AMD APU from their FM2+ socket. After installing the latest version of Windows 10 version 1903 everything seemed to run great, noticeably faster than my older i3-2120 machine.

Anyway after a short-while of usage a kept receiving a BSOD with the error message “Kernel_security_check_failure” and then my machine would just reboot, after fiddling around with many drivers and browsing numerous support forums I came to the conclusion that the issue was with the Meltdown and Spectre patches being applied to my system via Windows update, I tried uninstalling the supposed Windows updates which proved to have no effect I still kept having random BSOD with the same error message.


My last effort before going back to my previous i3-2120 would be to upgrade the micro code on my processor, apparently micro code is now installed via Windows update though obviously for my processor this was not the case. I searched Google for my motherboard model, headed to the manufactures website for my specific model and saw that there was a beta BIOS available for my motherboard which came with “AGESA code” update which is micro code for the processor, however as this was a beta BIOS I was fairly hesitant to flash though I had ran out of options and ideas to stop the BSOD for happening, after flashing I haven’t witnessed the BSOD so I’m going to assume the micro code fixed my issue.

To identify your motherboard you can either download a free tool called CPU-Z or simply take the side panel off your machine, your model should be printed somewhere on your motherboard, BIOS flashing is fairly risky I recommend flashing via USB using DOS rather than within Windows.

I take no responsibility for incorrectly flashing your system, if you’re unsure on what you’re doing please consult a professional.


Published inWindows

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *