Windows 8 and 8.1 Forums


BSOD - Kernal Security Check Failure, Windows 8.1

  1. #1


    Posts : 2
    Windows 8.1

    BSOD - Kernal Security Check Failure, Windows 8.1


    I can't seem to figure out the pattern here with programs/actions despite the consistent crashing. Any help is appreciated. Thanks

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    Almost all BSOD (8) of your 10 Dumpfiles is a BugCheck 139, {3, ffffd0002077b6d0, ffffd0002077b628, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 ) ,
    (1) BSOD is BugCheck A, {ffffcf8003b16f98, 2, 1, fffff80255133a39}

    Probably caused by : ntkrnlmp.exe ( nt!KiProcessThreadWaitList+b9 )
    and (1) BSOD is
    BugCheck 1000007E, {ffffffffc0000005, fffff80002b79c38, ffffd0003839b208, ffffd0003839aa10}

    Probably caused by : AsusTP.sys

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd0002072aa20, ffffd0002072a978, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
    Followup: MachineOwner
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd0002072aa20, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd0002072a978, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    ------------------
    
    TRAP_FRAME:  ffffd0002072aa20 -- (.trap 0xffffd0002072aa20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe0000046e8b0 rbx=0000000000000000 rcx=0000000000000003
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8014600095a rsp=ffffd0002072abb0 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000002 r10=ffffd000206f9180
    r11=ffffd0002072abe0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po cy
    nt! ?? ::FNODOBFM::`string'+0x2b7ba:
    fffff801`4600095a cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd0002072a978 -- (.exr 0xffffd0002072a978)
    ExceptionAddress: fffff8014600095a (nt! ?? ::FNODOBFM::`string'+0x000000000002b7ba)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  explorer.exe
    CURRENT_IRQL:  2
    ERROR_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen.
    EXCEPTION_PARAMETER1:  0000000000000003
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    DPC_STACK_BASE:  FFFFD0002072AFB0
    LAST_CONTROL_TRANSFER:  from fffff80145fd07e9 to fffff80145fc4ca0
    STACK_TEXT:  
    ffffd000`2072a6f8 fffff801`45fd07e9 : 00000000`00000139 00000000`00000003 ffffd000`2072aa20 ffffd000`2072a978 : nt!KeBugCheckEx
    ffffd000`2072a700 fffff801`45fd0b10 : ffffd000`20780180 ffffd000`206f9180 fffff801`46116100 fffff801`45e0e627 : nt!KiBugCheckDispatch+0x69
    ffffd000`2072a840 fffff801`45fcfd34 : ffffd000`2072aa38 00000000`00000000 fffffff6`00000002 00000001`ffffffff : nt!KiFastFailDispatch+0xd0
    ffffd000`2072aa20 fffff801`4600095a : 00000000`00000000 ffffd000`206f9180 ffffe000`033ea9f0 00000000`00000008 : nt!KiRaiseSecurityCheckFailure+0xf4
    ffffd000`2072abb0 fffff801`45f24fe3 : ffffe000`05d32400 ffffd000`00000001 ffffd000`2072ac89 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x2b7ba
    ffffd000`2072ac10 fffff801`45f25478 : ffffe000`080b0a0b ffffd000`2072ad79 ffffe000`05c1c068 fffff801`46168ec0 : nt!KiProcessExpiredTimerList+0x257
    ffffd000`2072acf0 fffff801`45f81478 : ffffd000`206f9180 00000000`0023ae8a ffffd000`0002f552 ffffd000`0002f56a : nt!KiExpireTimerTable+0x218
    ffffd000`2072ad90 fffff801`45ed1abc : ffffe000`0ac41080 ffffd000`206f9180 00000000`00000008 0000000b`748c71db : nt!KiTimerExpiration+0x148
    ffffd000`2072ae40 fffff801`45fc7dd5 : 80000000`00ac0121 ffffd000`206f9180 ffffd000`35638440 ffffe000`00400300 : nt!KiRetireDpcList+0x19c
    ffffd000`2072afb0 fffff801`45fc7bd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd000`35638380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiFastFailDispatch+d0
    fffff801`45fd0b10 c644242000      mov     byte ptr [rsp+20h],0
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  nt!KiFastFailDispatch+d0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c
    IMAGE_VERSION:  6.3.9600.16452
    BUCKET_ID_FUNC_OFFSET:  d0
    FAILURE_BUCKET_ID:  0x139_3_nt!KiFastFailDispatch
    BUCKET_ID:  0x139_3_nt!KiFastFailDispatch
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x139_3_nt!kifastfaildispatch
    FAILURE_ID_HASH:  {36173680-6f08-995f-065a-3d368c996911}
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {ffffcf8003b16f98, 2, 1, fffff80255133a39}
    Probably caused by : ntkrnlmp.exe ( nt!KiProcessThreadWaitList+b9 )
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffffcf8003b16f98, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80255133a39, address which referenced memory
    Debugging Details:
    ------------------
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff802553d3150
    GetUlongFromAddress: unable to read from fffff802553d3208
    Unable to get PFN database address fffff802553d3100
     ffffcf8003b16f98 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KiProcessThreadWaitList+b9
    fffff802`55133a39 f00fba2f07      lock bts dword ptr [rdi],7
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  AV
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    DPC_STACK_BASE:  FFFFD000205AAFB0
    TRAP_FRAME:  ffffd000205a36d0 -- (.trap 0xffffd000205a36d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=08e45efc80f80000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80255133a39 rsp=ffffd000205a3860 rbp=0000000000000000
     r8=0000000000000100  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiProcessThreadWaitList+0xb9:
    fffff802`55133a39 f00fba2f07      lock bts dword ptr [rdi],7 ds:00000000`00000000=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff802551df7e9 to fffff802551d3ca0
    STACK_TEXT:  
    ffffd000`205a3588 fffff802`551df7e9 : 00000000`0000000a ffffcf80`03b16f98 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`205a3590 fffff802`551de03a : 00000000`00000001 ffffe000`06d7e1c0 fffffff6`00000000 ffffd000`205a36d0 : nt!KiBugCheckDispatch+0x69
    ffffd000`205a36d0 fffff802`55133a39 : 00000000`00000000 ffffd000`20579180 ffffe000`058f2b40 ffffd000`205a3939 : nt!KiPageFault+0x23a
    ffffd000`205a3860 fffff802`55133fe3 : ffffe000`05e86b00 00000000`00000001 ffffd000`205a3939 00000000`00000002 : nt!KiProcessThreadWaitList+0xb9
    ffffd000`205a38c0 fffff802`55134478 : 00000000`00000000 ffffe000`05cfb250 ffffd000`20579180 fffff802`553772c0 : nt!KiProcessExpiredTimerList+0x257
    ffffd000`205a39a0 fffff802`55190478 : ffffd000`20579180 00000000`0023ae85 00000000`00011cf2 00000000`00011d0a : nt!KiExpireTimerTable+0x218
    ffffd000`205a3a40 fffff802`550e0abc : ffffe000`00000000 00001f80`00000001 00000004`73ca7602 00000000`00000002 : nt!KiTimerExpiration+0x148
    ffffd000`205a3af0 fffff802`551d77ea : ffffd000`20579180 ffffd000`20579180 00000000`00000000 ffffd000`20585240 : nt!KiRetireDpcList+0x19c
    ffffd000`205a3c60 00000000`00000000 : ffffd000`205a4000 ffffd000`2059e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiProcessThreadWaitList+b9
    fffff802`55133a39 f00fba2f07      lock bts dword ptr [rdi],7
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KiProcessThreadWaitList+b9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c
    IMAGE_VERSION:  6.3.9600.16452
    BUCKET_ID_FUNC_OFFSET:  b9
    FAILURE_BUCKET_ID:  AV_VRF_nt!KiProcessThreadWaitList
    BUCKET_ID:  AV_VRF_nt!KiProcessThreadWaitList
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:av_vrf_nt!kiprocessthreadwaitlist
    FAILURE_ID_HASH:  {4c242e02-1262-7f60-009a-dfe44df4757f}
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff80002b79c38, ffffd0003839b208, ffffd0003839aa10}
    Probably caused by : AsusTP.sys ( AsusTP+1c38 )
    Followup: MachineOwner
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002b79c38, The address that the exception occurred at
    Arg3: ffffd0003839b208, Exception Record Address
    Arg4: ffffd0003839aa10, Context Record Address
    Debugging Details:
    ------------------
    
    DUMP_FILE_ATTRIBUTES: 0xc
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    FAULTING_IP: 
    AsusTP+1c38
    fffff800`02b79c38 c783282d020005000000 mov dword ptr [rbx+22D28h],5
    EXCEPTION_RECORD:  ffffd0003839b208 -- (.exr 0xffffd0003839b208)
    ExceptionAddress: fffff80002b79c38 (AsusTP+0x0000000000001c38)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000000022d28
    Attempt to write to address 0000000000022d28
    CONTEXT:  ffffd0003839aa10 -- (.cxr 0xffffd0003839aa10;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffd0003839b458
    rdx=0000000000000000 rsi=0000000000000000 rdi=ffffe00004a731d4
    rip=fffff80002b79c38 rsp=ffffd0003839b440 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000000 r10=fffff8018e397520
    r11=ffffd0003839b400 r12=0000000000000003 r13=ffffd0003839b4b0
    r14=00000000000000e6 r15=fffff8018deaf100
    iopl=0         nv up ei pl nz ac po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010217
    AsusTP+0x1c38:
    fffff800`02b79c38 c783282d020005000000 mov dword ptr [rbx+22D28h],5 ds:002b:00000000`00022d28=????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffd0003839b458
    rdx=0000000000000000 rsi=0000000000000000 rdi=ffffe00004a731d4
    rip=fffff80002b79c38 rsp=ffffd0003839b440 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000000 r10=fffff8018e397520
    r11=ffffd0003839b400 r12=0000000000000003 r13=ffffd0003839b4b0
    r14=00000000000000e6 r15=fffff8018deaf100
    iopl=0         nv up ei pl nz ac po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010217
    AsusTP+0x1c38:
    fffff800`02b79c38 c783282d020005000000 mov dword ptr [rbx+22D28h],5 ds:002b:00000000`00022d28=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    EXCEPTION_PARAMETER1:  0000000000000001
    EXCEPTION_PARAMETER2:  0000000000022d28
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8018df5d150
    GetUlongFromAddress: unable to read from fffff8018df5d208
     0000000000022d28 Nonpaged pool
    FOLLOWUP_IP: 
    AsusTP+1c38
    fffff800`02b79c38 c783282d020005000000 mov dword ptr [rbx+22D28h],5
    BUGCHECK_STR:  AV
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002b79c38
    STACK_TEXT:  
    ffffd000`3839b440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : AsusTP+0x1c38
    
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  AsusTP+1c38
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AsusTP
    IMAGE_NAME:  AsusTP.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  508ec9ba
    STACK_COMMAND:  .cxr 0xffffd0003839aa10 ; kb
    FAILURE_BUCKET_ID:  AV_AsusTP+1c38
    BUCKET_ID:  AV_AsusTP+1c38
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:av_asustp+1c38
    FAILURE_ID_HASH:  {48828ea3-34a3-2f8f-2a7d-2cff9a4f5485}
    Followup: MachineOwner
    
    


    Analyse:
    When a Windows/system driver like ntkrnlmp.exe is blamed when experiencing a BSOD
    it's most likely not the problem. Most of the time further analysis is needed to determine the actual cause
    .

    While trying to solve your BSOD stop overclocking.
    CPUID: "Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz"
    MaxSpeed: 1900
    CurrentSpeed: 2395

    Your running 2 diffferent memory modules Elpida 4gb and Samsung 2gb, did you check the compatibility of this memory?

    Please update all your drivers to windows 8.1 from this page ASUSTeK Computer Inc. -Support- Drivers and Download K56CA

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the systemunbootable! :

    Note: If you updated all your drivers from your mainboard first, some may already be updated.

    ASMMAP64 fffff800`033f8000 fffff800`03400000 Thu Jul 02 11:13:26 2009 (4a4c7a36) 0000ceab ASMMAP64.sys
    Driver Description: LENOVO ATK Hotkey ATK0101 ACPI UTILITY (also found in Asus systems)
    Driver Update Site: Lenovo Support - Home (US)

    atkwmiacpi64 fffff800`01e36000 fffff800`01e3f000 Wed Sep 07 03:44:52 2011 (4e66cc94) 000056b5 atkwmiacpi64.sys

    Driver Description: ATK WMIACPI Utility
    Driver Update Site: http://support.asus.com/download/download.aspx

    AiCharger fffff800`024d4000 fffff800`024d6880 Fri Sep 23 04:04:40 2011 (4e7be938) 0000a877 AiCharger.sys
    Driver Description: Asus Charger Driver
    Likely BSOD cause - haven't seen recently (15Jan2013)
    Driver Update Site: ASUSTeK Computer Inc. -Support- Drivers and Download P6T

    excsd fffff800`00606000 fffff800`006c2000 Fri Mar 30 21:52:41 2012 (4f760f09) 00021f23 excsd.sys
    Driver Description: Diskeeper Corporation driver
    Driver Update Site: Support: Condusiv Online Support: Pre-Sales Questions
    Downloads: My Condusiv account - Access purchased software and resources for customers
    excfs fffff800`01be5000 fffff800`01bee000 Fri Mar 30 21:53:05 2012 (4f760f21) 0000e23a excfs.sys
    Driver Description: Diskeeper Corporation driver
    Driver Update Site: Support: Condusiv Online Support: Pre-Sales Questions
    Downloads: My Condusiv account - Access purchased software and resources for customers

    GEARAspiWDM fffff800`02b7a000 fffff800`02b80c00 Thu May 03 21:56:17 2012 (4fa2e2e1) 00008963 GEARAspiWDM.sys

    Driver Description: CD-ROM Class Filter Driver by Gear Software.
    Also comes with iTunes
    Driver Update Site: http://www.gearsoftware.com

    AsHIDSwitch64 fffff800`02bf7000 fffff800`02c00000 Thu May 31 04:38:32 2012 (4fc6d9a8) 0001072e AsHIDSwitch64.sys

    Driver Description: HID driver for ASUS Wireless Radio Control
    Driver Update Site: http://www.service.asus.com/#!downloads/c1wax

    RtsBaStor fffff800`02019000 fffff800`02065000 Wed Jun 13 12:09:02 2012 (4fd866be) 00055a2e RtsBaStor.sys

    Driver Description: Realtek Pcie CardReader Driver for 2K/XP/Vista/Win7
    Driver Update Site: Realtek

    IntcDAud fffff800`0326c000 fffff800`032c4000 Tue Jun 19 16:40:51 2012 (4fe08f73) 00056d76 IntcDAud.sys
    Driver Description: Intel Graphics Media Accelerator HD Driver
    Driver Update Site: http://downloadcenter.intel.com/

    HECIx64 fffff800`0255e000 fffff800`02571000 Tue Jul 03 00:14:58 2012 (4ff21d62) 00015752 HECIx64.sys
    Driver Description: Intel Management Engine Interface
    Driver Update Site: http://downloadcenter.intel.com/Default.aspx

    iaStorA fffff800`00883000 fffff800`00b4d000 Mon Jul 09 22:42:33 2012 (4ffb4239) 000ab20a iaStorA.sys
    dump_iaStorA fffff800`018cb000 fffff800`01b95000 Mon Jul 09 22:42:33 2012 (4ffb4239) 000ab20a dump_iaStorA.sys

    Driver Description: Intel RST (Rapid Storage Technology) driver
    Driver Update Site: http://downloadcenter.intel.com/Default.aspx

    irstrtdv fffff800`029e5000 fffff800`029f5000 Fri Jul 13 01:58:02 2012 (4fff648a) 0000f237 irstrtdv.sys
    Driver Description: Intel(R) Rapid Start Storage Technology driver
    Driver Update Site:
    http://downloadcenter.intel.com/defa...+dnlds_drivers
    Intel® Rapid Storage Technology (Intel® RST) — Version 9.6 does not start immediately after boot on Windows 7*

    DptfManager fffff800`00c00000 fffff800`00c5c000 Sat Jul 14 01:46:44 2012 (5000b364) 00064593 DptfManager.sys
    DptfDevDram fffff800`02bb0000 fffff800`02bcf000 Sat Jul 14 01:47:22 2012 (5000b38a) 0002494f DptfDevDram.sys
    DptfDevGen fffff800`02b65000 fffff800`02b7a000 Sat Jul 14 01:47:46 2012 (5000b3a2) 00016111 DptfDevGen.sys
    DptfDevFan fffff800`02b55000 fffff800`02b65000 Sat Jul 14 01:48:07 2012 (5000b3b7) 000133d7 DptfDevFan.sys
    DptfDevPch fffff800`02b81000 fffff800`02b9d000 Sat Jul 14 01:48:46 2012 (5000b3de) 00023b10 DptfDevPch.sys
    DptfDevProc fffff800`02498000 fffff800`024d4000 Sat Jul 14 01:49:52 2012 (5000b420) 0003c213 DptfDevProc.sys

    Driver Description: Intel(R) Dynamic Platform & Thermal Framework, Networkprocessor

    kbfiltr fffff800`02b3d000 fffff800`02b45000 Thu Aug 02 05:22:22 2012 (5019f26e) 0000b40b kbfiltr.sys
    Driver Description: Dritek Keyboard Filter Driver
    Driver Update Site: OEM none at http://www.dritek.com.tw/download_en.htm

    RTKVHD64 fffff800`02e1a000 fffff800`03202080 Tue Aug 07 12:49:39 2012 (5020f2c3) 003f6091 RTKVHD64.sys
    Driver Description: Realtek High Definition Audio Function Driver
    Driver Update Site: Realtek

    AsusTP fffff800`02ad7000 fffff800`02b2d000 Mon Oct 29 19:23:54 2012 (508ec9ba) 00012f87 AsusTP.sys

    Driver Description: Asis transformer pad filter driver
    Driver Update Site: Eee Pad | Transformer Prime

    athw8x fffff800`02647000 fffff800`029d0000 Thu Jan 17 10:15:39 2013 (50f7c13b) 00386204 athw8x.sys
    Driver Description: Atheros Wireless LAN Driver
    Driver Update Site: ATHEROS drivers for Microsoft Windows (Atheros?????)

    Rt630x64 fffff800`02a24000 fffff800`02ab8000 Fri May 10 11:59:08 2013 (518cc4ec) 0009d8fe Rt630x64.sys
    Driver Description: Realtek PCI/PCIe Adapters
    Driver Update Site: Realtek

    iwdbus fffff800`02600000 fffff800`0260c000 Thu Jul 25 03:06:12 2013 (51f07a04) 0000ce8f iwdbus.sys
    Driver Description: Intel WIDI Bus Enumerator driver
    Related to Intel Widi - Wireless Display
    Driver Update Site: http://downloadcenter.intel.com/Sear...ord=%22widi%22








      My System SpecsSystem Spec

  3. #3


    Posts : 2
    Windows 8.1


    Thanks for your detailed response. I'll work on updating the drivers.

    While I don't know a huge amount about altering my computer, I don't recall changing the settings for overclocking. Unless this is a side effect of something else I did (i.e. program install), I'm not sure how it got this way. Is this something I should change back manually?

    In response to the memory compatibility, the computer came that way from Best Buy but I wouldn't use that as a guarantee it's compatible.

    Lastly, I regularly use windows update. I'm guessing it's not effective at catching everything?
      My System SpecsSystem Spec

  4. #4


    Posts : 660
    windows 8.1


    ]Thanks for your detailed response. I'll work on updating the drivers.

    While I don't know a huge amount about altering my computer, I don't recall changing the settings for overclocking. Unless this is a side effect of something else I did (i.e. program install), I'm not sure how it got this way. Is this something I should change back manually?
    It is also possible that the processor was running in Turbomode at that moment, first let's concentrate on updating drivers.

    In response to the memory compatibility, the computer came that way from Best Buy but I wouldn't use that as a guarantee it's compatible.
    Same first concentrate on updating drivers

    Lastly, I regularly use windows update. I'm guessing it's not effective at catching everything?
    No, it is good practice to update your ( especcialy thirdparty ) drivers manually from 1. OEM driverssite Asus 2 From manufactures sites.
      My System SpecsSystem Spec

BSOD - Kernal Security Check Failure, Windows 8.1
Related Threads
Hi, Any help would be much appreciated. Have been having problems with BSOD, mostly with kernal security check failure, but sometimes other messages whilst playing games. Please find attached report from sf debug tool. Thanks, Alex
On new 8.1 pro PC with windows media center feature added and a tv signal scan started the machines bsod with error. Windows 8.1 pro has been fully reinstalled but same issue. Before re installing 8.1 pro a crash happened when playing media files from a usb. see uploaded file can you help? All...
BSOD Randomly- Kernal Security Check Failure in BSOD Crashes and Debugging
Attachments down below.
My brother screwed up my PC a while back; so I had to format the drive and wipe everything from the PC (all drives) I got it working by reinstalling Windows 8; I recently just upgraded (free) to Win 8.1 and I get a BSoD when playing high graphic intensity games With an error Message "Kernal...
Solved Random BSOD Kernal security check failed in BSOD Crashes and Debugging
Hello all I am getting a random BSOD and I can't pinpoint the cause. It seems to be completely at random. Attached files. Any help appreciated
Kernal Security Check Failure in BSOD Crashes and Debugging
Hey Guys, From time to time i get a bluescreen saying something about Kernal Security Check Failure :(. As i do not know that much of computers i tought I would ask here. (files are in the attachment). Any help would be much appreciated thanks, PieJie
After upgrading from 4gb OEM RAM to 8gb Corsair CMSO8GX3M2A1333C9 I get BSOD with kernel_security_check_failure message just as Windows attempts to load. This happens with memory sticks in either slot. Testing memory with Memtest continually hangs on test #2. Memory was tested with Memtest in...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook