Windows 10: BSOD (mostly Kernel_Security_Check Failure) Zipped files attached

Hi guys,
so I posted this thread on a few other forums as well but so far no one has been able to help me out.
After saving up for some time and suffering life on my terrible laptop I finally managed to get myself my own PC/Desktop. It's anew build so I ordered all the parts from aria.co.uk, made sure all the parts were compatible with each other and then built the PC. The PC boots up just fine, I installed Windows 10 via a USB and everything looked great. After using the PC for roughly half an hour I got my first Kernel_Security_Check_Failure BSOD, so I installed Driver Reviver and updated all my drivers, I then did a Hard Drive Test and Repair and did the same with my RAM. After rebooting the PC worked again for about half an hour, then I got the IRQL_Not_Less_Or_Equal BSOD, at this point I didn't know what to do any more so I rebooted, researched a bit and then got the System_Service_Exception BSOD, as you can imagine I was pretty heartbroken considering my new build which I had been waiting months to use was crashing on me. After few more attempts I'm now stuck back on the Kernel_Security_Check_Failure error. It's the only one I still get and I'm not sure what to do any more. I can boot up the PC just fine and always work for a while but it always crashes sooner or later.

Here are my specs:

- OS is Windows 10
- x64
- there was no original OS (new build)
- I bought the OS (downloaded to be specific) from retailer
- system age is under a month (literally built this PC two weeks ago)
- age of OS is the same as system
- I haven't reinstalled the OS, I have the install program on a USB and my
PC boots up just fine so there is no option to do the repair windows
function.
- CPU is AMD A10 7870K Black APU, Socket FM2+, Quad Core Processor
- Graphics Cards is Gigabyte G1 GTX 960 Windforce
- Motherboard is Gigabyte G1 Sniper A88X
- PSU is Corsair CX500M

and relevant info is attached.
Thanks for your help guys!

:)

 

BSOD Kernel_Security_Check Windows 10

My computer has been getting the BSOD with the Kernel_Security_Check warning and automatically restarting since downloading Windows 10 . Here is the link to my minidump files:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

BSOD Kernel security check failure

Hi, my laptop is running into BSOD from time to time (approx. once every 2-3 days) with a kernel_security_check error.

I ran system file check and a disk check with no error, and passed the memory test too. I am now very confused as to why the BSOD still persist.

Here is the link to my dump file: 112516-18968-01.dmp

 

Hi guys,
I'm also attaching the relevant info from the debug program.
Thanks

 

Hi GnasherKO,

Welcome to the 10forums.

May I ask from what other forums you have asked assistance? I'd like to know what has been tried.

 

Hi,
sure I posted on techsupportforum.com, however no one has replied to the post yet after 48 hours so really all I've tried are the steps from the windows and driver reviver BSOD tutorial sites, driver updates and hard drive and RAM tests.
Thanks

 

The graphics drivers are causing issues.
Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia
Code: *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 0: kd> lmvm nvlddmkm start end module name fffff801`95550000 fffff801`96037000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Mon Jul 13 18:50:59 2015 (55A3EC73) CheckSum: 00AA9850 ImageSize: 00AE7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] What hard drive test did you perform?
Code: STACK_TEXT: ffffd000`6e8f0d68 fffff801`197d9ba9 : 00000000`00000139 00000000`00000021 ffffd000`6e8f1090 ffffd000`6e8f0fe8 : nt!KeBugCheckEx ffffd000`6e8f0d70 fffff801`197d9ed0 : 00000000`00000000 00000000`00000000 ffffd000`6e8f10b8 00000000`00000001 : nt!KiBugCheckDispatch+0x69 ffffd000`6e8f0eb0 fffff801`197d90f4 : 00000000`00000000 ffffe000`c9a62bf0 00000000`00005dbc fffff801`19752be2 : nt!KiFastFailDispatch+0xd0 ffffd000`6e8f1090 fffff801`197f9ca6 : ffffd000`fffffffe ffffe000`ffffffff fffff801`199e4180 00000000`00000001 : nt!KiRaiseSecurityCheckFailure+0xf4 ffffd000`6e8f1220 fffff801`196c6059 : ffffd000`6e8f0000 ffffe000`00000000 ffffd000`6e8f1208 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1bea6 ffffd000`6e8f1270 fffff801`196c5ae8 : ffffe000`d013c010 ffffd000`6e8ed000 ffffd000`6e8ed000 fffff801`196fd2d6 : nt!KiSwapThread+0xe9 ffffd000`6e8f1320 fffff801`196c7d35 : ffffd000`6e8f14a0 00000000`00000000 ffffe000`c888ee50 00000000`05dbc000 : nt!KiCommitThreadWait+0x148 ffffd000`6e8f13b0 fffff800`e3a52c5d : ffffd000`6e8f17e8 00000000`00000000 ffffe000`c9a62a00 00000000`00000000 : nt!KeWaitForSingleObject+0x385 ffffd000`6e8f1460 fffff800`e3a50f29 : ffffc001`30b4b100 00000000`00000001 00000000`00000000 00000000`00000000 : NTFS!NtfsNonCachedIo+0x40d ffffd000`6e8f16d0 fffff800`e3a50312 : ffffd000`6e8f18a0 ffffe000`d013c010 00000000`00000000 ffffe000`00000dea : NTFS!NtfsCommonRead+0x9f9 ffffd000`6e8f1870 fffff800`e33551c4 : ffffe000`d0114b00 ffffe000`d013c010 ffffe000`d013c010 ffffe000`d013c3b0 : NTFS!NtfsFsdRead+0x1f2 ffffd000`6e8f1af0 fffff800`e3353a16 : ffffb000`5d53c000 fffffa80`0459cea0 00000000`00000001 e000c936`82b804c0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4 ffffd000`6e8f1b70 fffff801`196b2598 : ffffe000`c8b4c7a8 ffffe000`c9368070 ffffe000`cfea7110 00000000`00000000 : FLTMGR!FltpDispatch+0xb6 ffffd000`6e8f1bd0 fffff801`196b2814 : ffffe000`cfea7030 ffffe000`cfea7010 ffffe000`cfea7070 ffffd000`6e8f1c80 : nt!IoPageRead+0x258 ffffd000`6e8f1c30 fffff801`196b0ae8 : 00000000`00000002 fffff801`199c3a80 ffffe000`cfea7010 00000000`00000000 : nt!MiIssueHardFaultIo+0xbc ffffd000`6e8f1cb0 fffff801`196a023d : 00000000`c0033333 fffff801`199c3a80 ffffb000`5d53c000 fffff801`196a0347 : nt!MiIssueHardFault+0x168 ffffd000`6e8f1d90 fffff801`196b6d5e : 00000000`00000000 00000000`00000000 ffffd000`6e8f2000 ffffe000`c9359830 : nt!MmAccessFault+0x39d ffffd000`6e8f1ee0 fffff801`196b6555 : ffffe000`c8b4c080 00000000`00000001 ffffb000`55d3f000 ffffe000`cfff2018 : nt!MmCheckCachedPageStates+0x71e ffffd000`6e8f2080 fffff801`19a947e7 : 00000000`00000000 00000000`00000000 ffffd000`6e8f2101 00000000`00000001 : nt!CcMapAndRead+0xe5 ffffd000`6e8f20e0 fffff800`e3b0bf35 : ffffe000`c7287dd0 ffffe000`cfff2018 ffffe000`c9a60180 00000000`00004000 : nt!CcMapData+0x97 ffffd000`6e8f2150 fffff800`e3b0cbdd : ffffe000`c9a60180 ffffe000`cfff2018 00000000`005f0004 ffffc001`3eaa8d02 : NTFS!NtfsReadMftRecord+0xe5 ffffd000`6e8f2260 fffff800`e3b0d873 : ffffe000`cfff2018 ffffc001`32802920 ffffc001`30b4b150 00000000`00000001 : NTFS!NtfsRetrieveOtherFileName+0x10d ffffd000`6e8f2390 fffff800`e3b0fb63 : 00000000`00000000 ffffe000`c8b4adf0 ffffd000`6e8f28c0 00000000`00000000 : NTFS!NtfsQueryDirectory+0x9b3 ffffd000`6e8f2770 fffff800`e3b0fca7 : 00000000`00000000 ffffe000`d02a5010 ffffe000`d02a5001 ffffd000`6e8f28c0 : NTFS!NtfsCommonDirectoryControl+0xa3 ffffd000`6e8f27b0 fffff800`e33551c4 : ffffe000`d02a5010 ffffe000`d02a5010 ffffe000`cfff2018 ffffd000`6e8f27d8 : NTFS!NtfsFsdDirectoryControl+0xb7 ffffd000`6e8f2820 fffff800`e3353a16 : ffffe000`c87f81c0 ffffd000`6e8f2b80 00000000`00000d01 ffffe000`c75c3080 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4 ffffd000`6e8f28a0 fffff801`19aa172b : 00000000`00000001 ffffd000`6e8f2981 ffffe000`cbe6e090 ffffe000`cbe6e004 : FLTMGR!FltpDispatch+0xb6 ffffd000`6e8f2900 fffff801`19aa00ef : 00000000`00000d50 0000007d`77867000 00000000`00000000 ffffe000`c8b4c080 : nt!IopSynchronousServiceTail+0x16b ffffd000`6e8f29d0 fffff801`197d9863 : fffff6fb`401f4158 fffff680`3e82b7c0 fffff677`e6e9d7c5 00000000`00000000 : nt!NtQueryDirectoryFile+0xcf ffffd000`6e8f2a90 00007ffc`8405384a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 0000007d`7777e1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8405384a[/quote] Old drivers, check Realtek and AMD for driver updates
Code: Rtlh64 Rtlh64.sys Tue Mar 18 03:39:57 2014 (5327B1FD) // Realtek PCIe GBE Family controller driver atikmpag atikmpag.sys Fri Nov 01 17:05:58 2013 (5273D166) // AMD Video driver atikmdag atikmdag.sys Fri Nov 01 18:00:39 2013 (5273DE37) // AMD Video driver AppleCharger AppleCharger.sys Mon Oct 28 02:59:21 2013 (526DC4F9) // Remove Gigabyte software. AODDriver2 AODDriver2.sys Tue Feb 11 12:06:52 2014 (52FA044C) // Remove AMD Overdrive, known for causing BSOD's* amd_xata amd_xata.sys Tue Jul 23 10:06:39 2013 (51EE398F) // AMD driver amd_sata amd_sata.sys Tue Jul 23 10:06:27 2013 (51EE3983) // AMD driver[/quote] *Location
Code: AODDriver4.3 c:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys[/quote]

 

I ran the chkdsk scan, updating the AMD drivers now, gonna run DDU and re-install see if that helps, also gonna have a look if there are any BIOS updates for my motherboard.

 

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:











Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.

 

Right so I ran the DDU in safe mode and reinstalled my NVIDIA drivers, updated the AMD drivers adn ran the SeaTools Test, ran Fix All - Passed. When I tried using the System Specs program I can always open it but once I try editing the info to put it online the program crashes and the file disappears.

 

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

I have a slight suspicion the DDU and driver re-installs might have helped, seeing if playing some games or streaming will crash the PC (that's what generally caused it before) Running the sfc scan now, will upload the log if it comes up up with some violations.

 

Finished sfc scan and came out with no violations found. I'm going to test a few games and try to stress the PC a bit see if it crashes.

 

So the sfc scan finished and no violations have been found following the second scan. I'm going to try some games or programs to push the PC a bit and see if it crashes.

 

It would appear the issue is solved, fingers crossed it stays this way, thanks a bunch *Smile