bsod BSOD Kernel Security Check Failure

[TheOriginalMissQuackers]

Hello! I've recently been getting lots of BSOD. At first, I got memory_management. Overtime, the BSODs were either Kernel Security Check Failure or Memory Management. I figured out the memory management; I replaced my motherboard because my old one had some broken DIMM slots. I thought this would also solve Kernel Security Check Failure; however, I just now got a BSOD even after replacing my faulty motherboard. I also still have my old motherboard's drivers installed because I'm not sure the best way to switch motherboard drivers. Thanks for your time! More information below.

OS: Windows 10 Home 64-bit 10586.104

CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20 GHz

GPU: PowerColor Radeon R9 380 4GB PCS+ Video Card

Motherboard: Intel DH67CL

BIOS Version: Intel Corp. BLH6710H.86A.0156.2012.0615.1908

Power Supply: Cooler Master VSM 650W

Information collected by Sysnative

Information collected by PERFMON

Update: I woke up this morning, and I planned on doing a MemTest. I turned on my computer, and before windows could load, I got another BSOD that said irql_not_less_or_equal. It would not stop, so I wiped my SSD. I installed Windows 7 Home (I plan on upgrading to Windows 10 again later tonight, but I don't feel like doing it right now). I'll do a MemTest later tonight as well. Oh, and since I wiped my SSD, I went ahead and installed the drivers for my new mobo.

 

FINAL UPDATE: I gave in and purchased a new motherboard. I was not able to RMA because I got no response from asrock.

[TetraSky]

Did you test your RAM with Memtest? because really, that's the main reason for getting that kind of BSOD.

[TheOriginalMissQuackers]

18 hours ago, TetraSky said:

Did you test your RAM with Memtest? because really, that's the main reason for getting that kind of BSOD.

I had a new BSOD this morning (edited the original post). Could it be something else if I'm getting both of those? Also I will do the MemTest tonight.

[TetraSky]

7 minutes ago, TheOriginalMissQuackers said:

I had a new BSOD this morning (edited the original post). Could it be something else if I'm getting both of those? Also I will do the MemTest tonight.

The most likely culprit to BSOD is generally bad RAM. It could also be a software issue, such as bad drivers, but it's still worth testing the RAM.
Be sure to let memtest run for at least 12 hours, but recommended to let it run 24+hours. It doesn't always find issues in the first few hours after all.

[TheOriginalMissQuackers]

2 hours ago, TetraSky said:

The most likely culprit to BSOD is generally bad RAM. It could also be a software issue, such as bad drivers, but it's still worth testing the RAM.
Be sure to let memtest run for at least 12 hours, but recommended to let it run 24+hours. It doesn't always find issues in the first few hours after all.

Having a new issue with downloads (guessing it's from the new Intel Network driver). I wouldn't be able to run a memtest even if I wanted to. Going to create another post, and then get back to you when that's fixed.

[TheOriginalMissQuackers]

On 2/20/2016 at 3:03 PM, TetraSky said:

The most likely culprit to BSOD is generally bad RAM. It could also be a software issue, such as bad drivers, but it's still worth testing the RAM.
Be sure to let memtest run for at least 12 hours, but recommended to let it run 24+hours. It doesn't always find issues in the first few hours after all.

Result of MemTest