2 Replies Latest reply on Dec 7, 2017 3:29 PM by Intel Corporation

    Dump file Error code Detailed description Request

    Jin_88

      Hi,

       

      The PC has forcibly rebooted.

       

      When I checked the dump file, code iaStorA+0x870a8 was generated.

      Please give a detailed explanation of code iaStorA+0x870a8.

       

      Below is the contents of the dump file.

       

      Best Regards

      Jin

       

       

       

       

      Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
      Copyright (c) Microsoft Corporation. All rights reserved.

       


      Loading Dump File [D:\cch\2017\supports\24.Qotom.miniPC.Troubles\1127.q220n.cs.3set.freezing\dumpfile\#1_dump\120117-4102-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 \SystemRoot\system32\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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS
      Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
      Machine Name:
      Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`032a1750
      Debug session time: Fri Dec  1 09:05:02.690 2017 (UTC + 9:00)
      System Uptime: 3 days 2:19:40.110
      *********************************************************************
      * 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 \SystemRoot\system32\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
      ..............
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

       

      Use !analyze -v to get detailed debugging information.

       

      BugCheck D1, {10, 2, 1, fffff880010bf0a8}

       

      *** WARNING: Unable to verify timestamp for mssmbios.sys
      *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
      *** WARNING: Unable to verify timestamp for iaStorA.sys
      *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
      ***** 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                                     ***
      ***                                                                   ***
      *************************************************************************
      Probably caused by : iaStorA.sys ( iaStorA+870a8 )

       

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

       

      1: kd> !analyze -v
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

       

      DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
      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 kernel debugger is available get stack backtrace.
      Arguments:
      Arg1: 0000000000000010, memory referenced
      Arg2: 0000000000000002, IRQL
      Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
      Arg4: fffff880010bf0a8, address which referenced memory

       

      Debugging Details:
      ------------------

       

      ***** 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                                     ***
      ***                                                                   ***
      *************************************************************************

       

      ADDITIONAL_DEBUG_TEXT: 
      You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

       

      MODULE_NAME: iaStorA

       

      FAULTING_MODULE: fffff8000305f000 nt

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  526ed3ee

       

      WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
      unable to get nt!MmSpecialPoolEnd
      unable to get nt!MmPagedPoolEnd
      unable to get nt!MmNonPagedPoolStart
      unable to get nt!MmSizeOfNonPagedPoolInBytes
      0000000000000010

       

      CURRENT_IRQL:  0

       

      FAULTING_IP:
      iaStorA+870a8
      fffff880`010bf0a8 8911            mov     dword ptr [rcx],edx

       

      CUSTOMER_CRASH_COUNT:  1

       

      DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

       

      BUGCHECK_STR:  0xD1

       

      LAST_CONTROL_TRANSFER:  from fffff800030cf3a9 to fffff800030cfe00

       

      STACK_TEXT: 
      fffff880`040f9c08 fffff800`030cf3a9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt+0x70e00
      fffff880`040f9c10 00000000`0000000a : 00000000`00000010 00000000`00000002 00000000`00000001 fffff880`010bf0a8 : nt+0x703a9
      fffff880`040f9c18 00000000`00000010 : 00000000`00000002 00000000`00000001 fffff880`010bf0a8 00000000`00000000 : 0xa
      fffff880`040f9c20 00000000`00000002 : 00000000`00000001 fffff880`010bf0a8 00000000`00000000 00000000`00000000 : 0x10
      fffff880`040f9c28 00000000`00000001 : fffff880`010bf0a8 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
      fffff880`040f9c30 fffff880`010bf0a8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
      fffff880`040f9c38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : iaStorA+0x870a8

       


      STACK_COMMAND:  kb

       

      FOLLOWUP_IP:
      iaStorA+870a8
      fffff880`010bf0a8 8911            mov     dword ptr [rcx],edx

       

      SYMBOL_STACK_INDEX:  6

       

      SYMBOL_NAME:  iaStorA+870a8

       

      FOLLOWUP_NAME:  MachineOwner

       

      IMAGE_NAME:  iaStorA.sys

       

      BUCKET_ID:  WRONG_SYMBOLS

       

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

       

      1: kd> lmvm iaStorA
      start             end                 module name
      fffff880`01038000 fffff880`012ee000   iaStorA  T (no symbols)          
          Loaded symbol image file: iaStorA.sys
          Image path: \SystemRoot\system32\DRIVERS\iaStorA.sys
          Image name: iaStorA.sys
          Timestamp:        Tue Oct 29 06:15:26 2013 (526ED3EE)
          CheckSum:         0009FA1B
          ImageSize:        002B6000
          Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4