Kernel Security Check Failuire Please Help!

Page 1 of 2 12 LastLast

  1. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
       New #1

    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
      My Computer
    Quote Quote

  3. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
    Thread Starter
       New #2

    etc.


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

  4. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
    Thread Starter
       New #3

    Bump


    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
---------
      My Computer
    Quote Quote

  6. derekimo
    Posts : 1,092
    Win 10 Pro x64
       New #4

    BSOD - Posting Instructions - Windows 10 Forums

    Look at step three here,

    WinDBG - Install Configure - Windows 10 Forums

    To set the correct symbol path.
      My Computer
    Quote Quote

  7. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
    Thread Starter
       New #5

    Set 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*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    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
    ---------
      My Computer
    Quote Quote

  8. essenbe
    Posts : 12,801
    Windows 11 Pro
       New #6

    Please upload the BSOD Posting instructions BSOD - Posting Instructions - Windows 10 Forums. Upload them here. This will tell you how Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.
      My Computer
    Quote Quote

  9. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
    Thread Starter
       New #7

    Here is the file that you asked for


    Attachment 40965
      My Computer
    Quote Quote

  10. essenbe
    Posts : 12,801
    Windows 11 Pro
       New #8

    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:
    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
    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
      My Computer
    Quote Quote

  12. essenbe
    Posts : 12,801
    Windows 11 Pro
       New #9

    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:
      My Computer
    Quote Quote

  13. Whats Gucci
    Posts : 49
    Windows 10 Pro x64bit
    Thread Starter
       New #10

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

 

  Related Discussions
kernel security check failure
in BSOD Crashes and Debugging

Hi all, I have a new laptop and my intel driver utility said there where new chipset drivers available, when i try to install them i get a blue screen and says "kernel security check failure". No matter how many times i try to install it i always...
kernel security check failure
in BSOD Crashes and Debugging

MSI GE62 6QC 030uk KERNEL_SECURITY_CHECK_FAILURE I've seen this BSOD a few times on this laptop. It's probably a driver issue but identifying which ones are causing the issues would be greatly appreciated. And before you ask about the Intel...
Hi all, I bought a new computer a month ago, and am having BSOD each day. It's a Kernel Security Check Failure, and when i look in the event watcher, i can see a kernel-power critical error. 57819 Thanks for your help !
kernel security check failure
in BSOD Crashes and Debugging

i get this error all the time for no definitive reason at all. the machine has only been built for a few months. i just clean installed win 10. did memchck, called microsoft they did a few things and it didn't fix my problem. quite frustrating...
kernel security check failure
in BSOD Crashes and Debugging

upgraded to windows 10 not long ago like less then a month and it worked perfectly fine and today i got blue screen saying kernel security check failure it happend twice already i hope you guys can help me :) thank you
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 19:05.
Find Us




Windows 10 Forums