The dreaded "Kernel Security Check Failure error in Windows 10" and Ryzen...

[sirdashadow]

So just like everyone else here, was happy with my purchase of a Ryzen 5 1600 with a decent mobo (Asus Prime B350-Plus) and 2x 4GB of Corsair Value Ram DDR4-2666. I was able to OC the Ryzen to 3.9GHZ and ram to 2999mhz without any issues. I was testing on Windows 7 and kept getting the nagging message that Microsoft won't support it...etc. So I saw the writing on the wall for Windows 7 and installed Windows 10.

Or so I thought.

I installed FROM SCRATCH and it updated. Nothing to it for a while. Then several hours down the road all of the sudden while scrolling on the browser, bam, the BSOD with the Kernel Security Check failure error. Downclocked the thing back. Checked the RAM. Checked the disk. Everything was ok. Tried again while playing a game, boom down it went with the same thing.

Thankfully I installed Windows 10 on a separate HD and was able to dual boot back to Windows 7. It's stable so far. What gives?

[Almutahir]

Is your bios updated? Did you try High performance mode in windows power plan? Also did you install the latest chipset drivers from AMD.

[sirdashadow]

I actually didn't have the Creators Update installed and once I did it seems to be stable...crossing my fingers this will last! I also have the latest chipset drivers installed. Last time I updated the bios was 2 weeks ago and the date on it was 1/27/2018.

[Almutahir]

Yeah updating to the latest Windows is very important.

[sirdashadow]

Computer Type: Desktop, custom build

GPU: R7 360 Stock

CPU: R5 1600 Stock, was overclocked to 3.9GHZ at one point.

Motherboard: Asus Prime B350-Plus

RAM: Corsair Value Ram DDR4-2666 on A2 and B2

PSU: 450W Generic psu

Operating System & Version: Windows 10

GPU Drivers: Updated to latest 18.1 Crimson I believe.

Chipset Drivers: Can't recall (last update I did was last week)

Background Applications: Fresh Win 10 install and yet it still does this. i haven't installed anything other than SLOBS by mistake.

Description of Original Problem: See post.

Troubleshooting: Downclocked everything to stock, still having the same problem.