Windows 10: Kernel Security Check Failuire Please Help!

Keep getting these bsod error messages called Kernel_security_check_failure then my computer restarts it happens almost two to three times a day! Please help.

System Specs:
Cpu:AMD A10-7870k R7, 12 compute cores 4C+8G 3.90Ghz
Gpu:Radeon R7 Graphics
Ram:16GB
System type:64 bit Windows 10 Professional system

Dump File For BSOD:Attachment 40939

:)

 

Kernel Security Check Failuire Please Help!

Hello Lego,

Thank you for posting your query in Microsoft Community.

Regrets the inconvenience you have epxeircned.

Did you see any Windows Update Installed recently?

The KERNEL_SECURITY_CHECK_FAILURE bug indicates that the kernel has detected the corruption of a critical data structure.
Blue screen error, or stop code, will make your computer shut down abruptly to protect itself from data loss.

It’s not always obvious what may have caused a blue screen. On older PCs, it may be that hardware is malfunctioning. Many blue screen errors can be resolved by making sure that Windows is up to date. In the search box on the taskbar, enter
Windows Update, select Windows Update. On the Windows Update page, select
Check for updates.

If the problem started recently, you can restore Windows back to an earlier point in time, called a restore point. System Restore doesn’t change your personal files, but it might remove recently installed apps and drivers.

Note: Windows automatically creates a restore point when you install desktop apps and new Windows updates, if the last restore point is older than 7 days. You can also create a restore point manually at any time.

To restore your PC to an earlier point in time

* Press Windows Key + R to open run command

* Type rstrui and hit Enter key.

* Select Recommended Restore or any other restore point and click
Next

* Follow the instructions to restore your PC to earlier.

Keep us posted for any concerns with windows, we're glad to assist you.

 

Kernel Security Check Failuire Please Help!

Keep getting these bsod error messages called Kernel_security_check_failure then my computer restarts it happens almost two to three times a day! Please help.

System Specs:

Cpu:AMD A10-7870k R7, 12 compute cores 4C+8G 3.90Ghz

Gpu:Radeon R7 Graphics

Ram:16GB

System type:64 bit Windows 10 Professional system

Dump File For BSOD:100315-13140-01.zip

 

Already ran a hard disk verifier and used command prompt to check system for any errors both found nothing wrong

 

I used windbg to read my dump files and they all point out to ntoskrnl.wrong.symbols.exe being the cause
Code: Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100315-29093-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 10 Kernel Version 10240 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff801`55a8a000 PsLoadedModuleList = 0xfffff801`55daf010 Debug session time: Sat Oct 3 18:05:29.263 2015 (UTC - 7:00) System Uptime: 0 days 0:39:11.417 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ......... ************* Symbol Loading Error Summary ************** Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {1008, ffffe001cef5ea30, 2467f8, 4} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KTHREAD *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!55FA569B852000 ) Followup: MachineOwner ---------[/quote]

 

BSOD - Posting Instructions - Windows 10 Forums

Look at step three here,

WinDBG - Install Configure - Windows 10 Forums

To set the correct symbol path.

 

after setting the correct symbol path in windbg
Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\100315-29093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available




************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*Symbol information
Symbol search path is: SRV*C:\SymCache*Symbol information
Executable search path is:
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
Windows 10 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16515.amd64fre.th1.150916-2039
Machine Name:
Kernel base = 0xfffff801`55a8a000 PsLoadedModuleList = 0xfffff801`55daf010
Debug session time: Sat Oct 3 18:05:29.263 2015 (UTC - 7:00)
System Uptime: 0 days 0:39:11.417
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck C4, {1008, ffffe001cef5ea30, 2467f8, 4}


Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )


Followup: MachineOwner
---------

 

Please upload the BSOD Posting instructions Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

 

Here's what I can get, so far,

Code: DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 0000000000001008, Acquiring lock using mismatched API for this lock type. Arg2: ffffe001cef5ea30, Lock address. Arg3: 00000000002467f8, Verifier internal data. Arg4: 0000000000000004, Verifier internal data. Debugging Details:[/quote] I'm getting a lot of errors from UE4_Shooter Game

Code: Problem signature: P1: UE4-ShooterGame P2: 4.5.1.0 P3: 56046786 P4: ShooterGame.exe P5: 4.5.1.0 P6: 00000000 P7: c0000005 P8: 00007FFAA3FDA374 P9: !-lowmemory -sm4 -nomansky!AssertLog="" P10: UE4!C:/Program Files (x86)/Steam/steamapps/common/ARK/ShooterGame/Binaries/Win64/!Game!0[/quote] It may be worth a try to uninstall the game and see if you still have the problem. I would also like you to complete filling out your system specs.

Please go to your last post and in the bottom left corner click 'My System Specs'. there is a link there to update your system specs, click it and fill them all out in as much detail as possible. Please list Manufacturer and Model, and list Desktop or Laptop. If it is an OEM, please list the Manufacturer and Model number. Please be sure to list your Hard Drives, PSU and CPU cooler. If you would like to know what we would like, please click 'My System Specs' at the bottom left of this post and see mine.

For right now, disable Driver Verifier https://www.tenforums.com/tutorials/5...dows-10-a.html

 

This is what the rest of the dumps are

Code: KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000021, An invalid exception chain was detected. Arg2: ffffd0002a2b4520, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffd0002a2b4478, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details:[/quote]

 

That shooter game is ark survival evolved a game that i had removed

 

Check your date and time in the OS and in BIOS. I am seeing that game showing errors on 10/4/2015.

 

both my bios and my os say the current date and time for me also added more computer specs some missing could it be a problem with my ram timing? Can you find out if my mother board can handle 2133MHz 16gb ddr3 ram

 

At this point, everything is possible. I'm wondering about your hard drive right now. Right now your error codes are consistent except for 1, which is not usually the case with ram. What I did see, won't mean anything to you and is not blame, but just some of the sequence of events leading up to the crash.

Code: ffffd001`f5360a10 fffff801`347c172c NTFS!TxfSetupTxfRmcbForFcb+0x38ffffd001`f5360a18 fffff801`34799c9d NTFS!NtfsUpdateFcbInfoFromDisk+0x42d ffffd001`f5360a20 fffff801`3478bb55 NTFS!NtfsOpenSubdirectory+0x1a5 ffffd001`f5360a28 fffff801`34792338 NTFS!NtfsCommonCreate+0xad8 ffffd001`f5360a30 fffff801`3479182d NTFS!NtfsCommonCreateCallout+0x1d ffffd001`f5360a38 fffff801`55bdada7 nt!KxSwitchKernelStackCallout+0x27 ffffd001`f5360a40 fffff801`55bdad6d nt!KiSwitchKernelStackContinue ffffd001`f5360a48 fffff801`55b06564 nt!KiExpandKernelStackAndCalloutOnStackSegment+0x134 ffffd001`f5360ac0 fffff801`347c172c NTFS!TxfSetupTxfRmcbForFcb+0x38 ffffd001`f5360ac8 ffffcf81`f2c9ab40 ffffd001`f5360ad0 ffffcf82`57d76a00 ffffd001`f5360ad8 fffff801`347c172c NTFS!TxfSetupTxfRmcbForFcb+0x38 ffffd001`f5360ae0 ffffb001`cc571400 ffffd001`f5360ae8 ffffe001`cef5d100 ffffd001`f5360af0 ffffd001`f5360b80 ffffd001`f5360af8 fffff801`55be13eb nt!KiPageFault+0x26b ffffd001`f5360b00 00050000`00000005 ffffd001`f5360b08 00000000`00004001 ffffd001`f5360b10 ffffb001`cc5714f8 ffffd001`f5360b18 00000000`00000000 ffffd001`f5360b20 ffffcf82`57d76a00 ffffd001`f5360b28 fffff801`34799c9d NTFS!NtfsUpdateFcbInfoFromDisk+0x42d[/quote] All of the ones named NTFS is the file system Windows uses, which makes me wonder about the hard drive having problems. I may be all wrong too. But, I would run Western Digital's Data Lifeguard for DOS WD Support
. Run the short and the long test, and run Check Disk on it too, Disk Cleanup - Open and Use in Windows 10 - Windows 10 Forums.