Random and constant BSODs, nearly all KERNEL_SECURITY_CHECK_FAILURE

Alright, so I'm at a loss here. I just put together this PC last week, and everything was working great until I decided to upgrade to Windows 10. I started having issues yesterday, when my PC randomly crashed with the error message "KERNEL_SECURITY_CHECK_FAILURE." I had not installed anything new and I was just browsing the internet, so I didn't think much of it and went back to messing around until it happened again about 30 mins later. Since then they seem to happen more and more often, and it doesn't matter what I'm doing...I can just sit on the desktop for a couple of minutes with nothing running and it will crash. I've tried to make sure all of my drivers are up to date, but please tell me if I missed something somewhere. Any help is greatly appreciated, my computer is practically unusable at this point due to the frequency of these crashes.

axe0 said:

Hi 098054,

Welcome to the 10forums.

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.

There are some drivers flagged, possibly installed with Driver Booster 3?

To start, please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff801`48c40000 fffff801`49733000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Sep 13 23:12:24 2015 (55F5E6B8)
    CheckSum:         00AB4A61
    ImageSize:        00AF3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please check your network drivers for updates.
Both drivers below are from Killer

Code:

0: kd> lmvm e24w10x64
start             end                 module name
fffff801`569c0000 fffff801`569e7000   e24w10x64 T (no symbols)           
    Loaded symbol image file: e24w10x64.sys
    Image path: \SystemRoot\System32\drivers\e24w10x64.sys
    Image name: e24w10x64.sys
    Timestamp:        Sun Aug 30 04:41:36 2015 (55E26D60)
    CheckSum:         0002C2BE
    ImageSize:        00027000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm bwcW10x64
start             end                 module name
fffff801`54b40000 fffff801`54ea4000   bwcW10x64 T (no symbols)           
    Loaded symbol image file: bwcW10x64.sys
    Image path: \SystemRoot\system32\DRIVERS\bwcW10x64.sys
    Image name: bwcW10x64.sys
    Timestamp:        Tue Sep 15 16:13:12 2015 (55F82778)
    CheckSum:         00030B00
    ImageSize:        00364000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Alright, so I've run in to some issues. I used the DDU and then installed the updated driver(s) from the links you provided for both my GPU and Network...however, I was still getting constant BSODs, and they got so frequent that I couldn't even do anything on my computer because they'd happen the second I'd get logged in to my profile or even before I could log in. I didn't know what the issue could be, so I formatted my drive and figured I would just reinstall Windows. This did not go so well, however, as every time I tried to reinstall Windows my computer would either freeze or the screen would go black a few minutes in to the installation. Most of the time it was just a black screen or completely frozen (and yes, I let it sit for about two hours to see if it was just frozen on my screen but still installing in the background - no luck), but I did have one BSOD actually pop up when trying to install, and I believe it was the same "KERNEL_SECURITY_CHECK_FAILURE." Thinking it might be my RAM, I ran memtest86+ for about 15 hours, went through 10+ passes, and got zero errors... tried it with one of each RAM stick and still got zero errors, tried switching slots on my motherboard, still zero errors; I tried each of the things when also attempting to reinstall, but no matter where my RAM was or which slot I had in it still didn't work. I took out my GPU and ran off of integrated graphics, still no luck. Tried installing to my HDD, still no luck. Thinking it might even just be something with Windows, I tried installing Ubuntu - same thing, screen freezes after a minute or two and will not unfreeze. I've tried installing with both a USB stick and DVD, but that didn't make any difference. About the only thing I can think of at this point is my motherboard....what do you guys think? Is it my motherboard? My processor? I have no clue what is going on here...why did my PC never freeze in memtest but it does whenever I'm trying to install Windows/Ubuntu (even before I hit install and it starts writing anything, I can just sit in the menu and it will freeze/black screen - doesn't matter what I'm doing, just seems like it always happens after a certain amount of time)? I think I'm just going to ship my MOBO out for RMA tomorrow if I still can't find out what the issue is. Should I ship other parts with it too just to be safe? Never had to deal with shipping back bad hardware before, so not sure what all I should do. I've spent hours toiling with this system, and I'm just eager to know what the issue could be so I can get it fixed. : /

axe0 said:

Following your description, your motherboard is failing.

MemTest86+ only makes contact to the RAM, according to what I understand nothing else, that could be the reason why Memtest86+ didn't have any problem.

That's what I was afraid of....I guess better for it to fail early while I can still RMA it instead of finding out a few months later and having to go through the manufacturer for warranty. Should I try to RMA both my MOBO and Processor to be safe, or just do the MOBO first and then processor if that doesn't solve the issue?

axe0 said:

If th CPU was giving problems, you wouldn't have freezing problems.

Well, got my new motherboard in and installed it, no dice...exact same issues. I'm really not sure if I should suspect the RAM or CPU at this point. I've tried installing Windows with just one stick of RAM in at a time and in different slots, doesn't solve anything. What would be the chances that both sticks of RAM are bad? And also, I don't get any BSOD when trying to install Win7. It just freezes or the screen goes black. When trying to install Win10, however, I get a BSOD before I can even get past the loading circle to mess with any of the installation; it's always a different error message, ranging from "CRITICAL_PROCESS_DIED" to "KMODE_EXCEPTION_NOT_HANDLED." There doesn't seem to be any pattern to what message I get, it's different every time and always happens about 30 seconds in to trying to load in to the Win10 installation. Tried using Intel's Processor Diagnostic Tool, and it freezes as soon as I boot in to it (another thing that makes me think it's the CPU). I only have 6 days left on the return period before I have to go through the manufacturer, so what should I do? This whole build has turned in to a nightmare. I honestly don't know what it could be besides the CPU at this point, unless both sticks of RAM are bad and not showing any errors when running on each stick for 20+ hours at a time on memtest....keep in mind my PC ran perfectly fine for a little over a week after putting it together, but obviously something hardware related started failing because BSODs kept increasing in frequency until I couldn't even boot in to Windows anymore. I just want to get resolved and finally be able to use the system I've put so much time and money in to, hopefully you can give me some advice on where to go from here because I'm stumped.

EDIT: Also going to throw it in there that I think it's odd I can boot in to the BIOS and do whatever I want in there for however long I want without any issues, and I can run memtest just fine on just one or all cores with no issues, yet the second I try to run any sort of OS on my system it dies. Not a HDD/SSD issue, as I've tried multiple different drives and even detached them when just trying to run an OS off of a USB.