BSODs all week long KERNEL SECURITY CHECK FAILURE

bjkash · 31 Aug 2016

Hi guys,
Last week I upgraded my CPU and cooler. I made sure everything was compatible and it was and works great. However, after the first boot, I installed the drivers and new Windows updates and started getting BSODs. The main one seems to be KERNEL_SECURITY_CHECK_FAILURE but I have been getting a couple of different ones now and again. I can game for hours and then it can crash suddenly when loading google chrome for example.
I have tried literally everything I can think of and followed various tutorials. I've clean booted Windows 10 twice, ran disk checks, RAM checks, checked CPU temp (which is fine btw) and checked for faulty drivers and more. I'm really stuck now and would greatly appreciate the help! :)

batlhilz · 31 Aug 2016

"Display Tab 2: There is a problem with AMD Radeon(TM) R7 Graphics device. For more information, search for 'graphics device driver error code 22' "

the error itself translates to ->
This device is turned off.

and here's how to turn it on:

Open Start, enter (or type) Device Manager, and select Device Manager from the list of results.
Near the top, select Action > Enable Device, and then follow the instructions.

did you get the dxdiag log AFTER the problem occured? get a new one AFTER a reboot.

bjkash · 31 Aug 2016

Thanks for the quick reply! I got it after the problem but the crash was about 10 minutes before. The problem is I have a dedicated graphics card, a Radeon R9 280 which is obviously better than intergrated R7 graphics. I thought that there may have been a conflict between the two causing this issue, so I disabled the intergrated graphics so it just ran off my dedicated GPU.

batlhilz · 31 Aug 2016

you got quite amount of warnings for your

Card name: AMD Radeon R9 200 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6810)

so it looks like its really driver based issue. tested the DDU? run it in safemode, remove all the drivers and get the newest ones for the AMD website?

bjkash · 31 Aug 2016

I'll try that! I'll get back to you.

bjkash · 31 Aug 2016

I've uninstalled and reinstalled the drivers and had no crashes as of yet! Fingers crossed that's the end of the nightmare, if so I can't thank you enough.
UPDATE: Spoke way too soon, 5 minutes after this post I got 8 consecutive crashes when configuring windows updates.

axe0 · 31 Aug 2016

Did any crash occur before installing these programs listed below?

Please remove following programs and see if you have a restore point for reverting the changes these programs have made

Code:

Start Menu\Programs\Advanced SystemCare	Public:Start Menu\Programs\Advanced SystemCare	Public
Start Menu\Programs\Driver Booster 3	Public:Start Menu\Programs\Driver Booster 3	Public
Start Menu\Programs\IObit Uninstaller	Public:Start Menu\Programs\IObit Uninstaller	Public
Start Menu\Programs\Smart Defrag	Public:Start Menu\Programs\Smart Defrag	Public

Simply speaking, IObit has a bad reputation where the programs are quite unstable.
It is important that you uninstall these programs and revert back the changes, it does often occur that a system becomes unbootable after using these programs or programs from other companies that are similar to IObit.

The 0x7F, the one you've had the most, is a double fault crash. A double fault could occur when the CPU is handling an exception (by trying to call the exception handler) when another exception occurs. A double fault is mostly caused by a stack overflow or hardware. As there is no stack overflow present + driver verifier is unable to find any driver (or a minidump isn't good enough to provide us information about what driver is being called by the I/O manager) there is a possibility that we're dealing with a hardware problem.

Please upload the kernel dump, C:\Windows\Memory.dmp, to a 3rd party uploader (onedrive, google drive, dropbox, etc) and post a share link in your next reply.

Please provide at least the following information about the hardware tests you performed.
1. Upload the chkdsk log

Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
2. How did you check your RAM? What program and what requirement did you use to ensure the test is conclusive in case of 3rd party programs.

Please fill in your system specs

Please 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 including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

How to fill in your system specs:

bjkash · 31 Aug 2016

Thanks for your in depth reply. I did experience these crashes before installing any of the iObit software, but I will uninstall soon to check just in case. I have put the PC under have use for just over 3 hours since the crash happened and it hasn't crashed since. I used Windows Memory Diagnostic to check the RAM and no problems appeared. I have updated the system specs and will upload the files for you. The memory dump is currently uploading to DropBox and I will add once it's finished.
Dropbox - MEMORY.DMP

axe0 · 31 Aug 2016

What device is referred to?

Code:

TimeCreated : 31/08/2016 15:00:35
Message     : 
              
              Checking file system on \\?\Volume{f4fa9261-0000-0000-0000-100000000000}
              The type of the file system is FAT32.
              
              
              One of your disks needs to be checked for consistency. You
              may cancel the disk check, but it is strongly recommended
              that you continue.
              Windows will now check the disk.                         
              Volume Serial Number is 268D-527D
              
              Windows has scanned the file system and found no problems.
              No further action is required.
              
                  100663296 bytes total disk space.
                     479232 bytes in 9 hidden files.
                      46080 bytes in 42 folders.
                   18475008 bytes in 88 files.
                   81661952 bytes available on disk.
              
                       1024 bytes in each allocation unit.
                      98304 total allocation units on disk.
                      79748 allocation units available on disk.

That's too bad, the last dump appears to be the corrupted dump, I hope you haven't disabled driver verifier?

Code:

WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Unable to read NT module Base Name string at ae09eb8d`320004c0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_ae09eb8d`320004c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_ae09eb8d`320004c0
Debugger can not determine kernel base address
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.82.amd64fre.rs1_release.160805-1735
Machine Name:
Kernel base = 0xfffff803`85a11000 PsLoadedModuleList = 0xfffff803`85d16060
Debug session time: Wed Aug 31 16:10:25.754 2016 (UTC + 2:00)
System Uptime: 0 days 0:03:12.843
Unable to read NT module Base Name string at ae09eb8d`320004c0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_ae09eb8d`320004c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_ae09eb8d`320004c0
Debugger can not determine kernel base address
Loading Kernel Symbols
Unable to read NT module Base Name string at ae09eb8d`320004c0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at ae09eb8d`320004c0 - NTSTATUS 0xC0000141

bjkash · 31 Aug 2016

That would be referring to my hard drive or a partition of it maybe?
And no I used driver verifier yesterday so I'm not sure why it would be missing.