title: How to read a Windows 10 BSOD mini dump analysis
body: <p>I'm hoping someone here can help.</p>
  
  <p>I have a new Windows 10 machine (all parts by EVGA).</p>
  
  <p>I get random BSOD, so I've grabbed a mini dump, installed the SDK and looked into it. I just don't understand what it is reporting.</p>
  
  <p>Can someone point me in the direction of a guide, or decode this mini dump.
  Note : Each dump looks very similar. e.g. almost the same report from 'irp'</p>
  
  <p>Here is the dump....</p>
  
  <blockquote>
    <p>Microsoft (R) Windows Debugger Version 10.0.10586.567 X86
    Copyright (c) Microsoft Corporation. All rights reserved.</p>
    
    <p>Loading Dump File [C:\Windows\Minidump\033016-4718-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available</p>
    
    <p>Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 10586 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
    Machine Name:
    Kernel base = 0xfffff801<code>8d674000 PsLoadedModuleList = 0xfffff801</code>8d952cd0
    Debug session time: Wed Mar 30 18:15:33.639 2016 (UTC + 1:00)
    System Uptime: 0 days 2:47:26.264
    Loading Kernel Symbols
    .</p>
    
    <p>Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.</p>
    
    <p>..............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    .............</p>
    
    <hr>
    
    <ul>
    <li>*</li>
    <li>Bugcheck Analysis                                    *</li>
    <li>*
    
    <hr></li>
    </ul>
    
    <p>Use !analyze -v to get detailed debugging information.</p>
    
    <p>BugCheck 9F, {3, ffffe000935ea880, fffff8018f25a890, ffffe00092718bd0}</p>
    
    <p>Probably caused by : ACPI.sys</p>
    
    <h2>Followup:     MachineOwner</h2>
    
    <p>0: kd> !analyze -v </p>
    
    <hr>
  </blockquote>
  
  <ul>
  <li>*</li>
  <li>Bugcheck Analysis                                    *</li>
  <li>*
  
  <hr></li>
  </ul>
  
  <blockquote>
    <p>DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000935ea880, Physical Device Object of the stack
    Arg3: fffff8018f25a890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00092718bd0, The blocked IRP</p>
    
    <h2>Debugging Details:</h2>
    
    <p>DUMP_CLASS: 1</p>
    
    <p>DUMP_QUALIFIER: 400</p>
    
    <p>BUILD_VERSION_STRING:  10586.162.amd64fre.th2_release_sec.160223-1728</p>
    
    <p>SYSTEM_MANUFACTURER:  EVGA INTERNATIONAL CO.,LTD</p>
    
    <p>SYSTEM_PRODUCT_NAME:  Default string</p>
    
    <p>SYSTEM_SKU:  Default string</p>
    
    <p>SYSTEM_VERSION:  Default string</p>
    
    <p>BIOS_VENDOR:  American Megatrends Inc.</p>
    
    <p>BIOS_VERSION:  1.07</p>
    
    <p>BIOS_DATE:  01/04/2016</p>
    
    <p>BASEBOARD_MANUFACTURER:  EVGA INTERNATIONAL CO.,LTD</p>
    
    <p>BASEBOARD_PRODUCT:  111-SS-E172</p>
    
    <p>BASEBOARD_VERSION:  1.0</p>
    
    <p>DUMP_TYPE:  2</p>
    
    <p>DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump</p>
    
    <p>BUGCHECK_P1: 3</p>
    
    <p>BUGCHECK_P2: ffffe000935ea880</p>
    
    <p>BUGCHECK_P3: fffff8018f25a890</p>
    
    <p>BUGCHECK_P4: ffffe00092718bd0</p>
    
    <p>DRVPOWERSTATE_SUBCODE:  3</p>
    
    <p>IMAGE_NAME:  ACPI.sys</p>
    
    <p>DEBUG_FLR_IMAGE_TIMESTAMP:  56cbf9c9</p>
    
    <p>MODULE_NAME: ACPI</p>
    
    <p>FAULTING_MODULE: fffff800d5de0000 ACPI</p>
    
    <p>CPU_COUNT: 8</p>
    
    <p>CPU_MHZ: d50</p>
    
    <p>CPU_VENDOR:  GenuineIntel</p>
    
    <p>CPU_FAMILY: 6</p>
    
    <p>CPU_MODEL: 5e</p>
    
    <p>CPU_STEPPING: 3</p>
    
    <p>CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 33'00000000 (cache) 33'00000000 (init)</p>
    
    <p>CUSTOMER_CRASH_COUNT:  1</p>
    
    <p>DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT</p>
    
    <p>BUGCHECK_STR:  0x9F</p>
    
    <p>PROCESS_NAME:  System</p>
    
    <p>CURRENT_IRQL:  2</p>
    
    <p>ANALYSIS_SESSION_HOST:  Q-PC</p>
    
    <p>ANALYSIS_SESSION_TIME:  03-30-2016 20:04:47.0460</p>
    
    <p>ANALYSIS_VERSION: 10.0.10586.567 x86fre</p>
    
    <p>STACK_TEXT:<br>
    fffff801<code>8f25a858 fffff801</code>8d854e42 : 00000000<code>0000009f 00000000</code>00000003 ffffe000<code>935ea880 fffff801</code>8f25a890 : nt!KeBugCheckEx
    fffff801<code>8f25a860 fffff801</code>8d854d62 : ffffe000<code>96133010 fffff801</code>8f252070 00000000<code>00000000 fffff801</code>8d73e0a6 : nt!PopIrpWatchdogBugcheck+0xde
    fffff801<code>8f25a8c0 fffff801</code>8d6e22c6 : ffffe000<code>96133048 fffff801</code>8f25aa10 00000000<code>00000001 00000000</code>00000002 : nt!PopIrpWatchdog+0x32
    fffff801<code>8f25a910 fffff801</code>8d7b951a : 00000000<code>00000000 fffff801</code>8d991180 fffff801<code>8da07740 ffffe000</code>96723800 : nt!KiRetireDpcList+0x5f6
    fffff801<code>8f25ab60 00000000</code>00000000 : fffff801<code>8f25b000 fffff801</code>8f254000 00000000<code>00000000 00000000</code>00000000 : nt!KiIdleLoop+0x5a</p>
    
    <p>STACK_COMMAND:  kb</p>
    
    <p>THREAD_SHA1_HASH_MOD_FUNC:  81a7ba75a791115b4f55c8910c64a260d525502e</p>
    
    <p>THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  936d5c51c0ad2157bf4c85af575dd55cea2c0947</p>
    
    <p>THREAD_SHA1_HASH_MOD:  f08ac56120cad14894587db086f77ce277bfae84</p>
    
    <p>FOLLOWUP_NAME:  MachineOwner</p>
    
    <p>IMAGE_VERSION:  10.0.10586.122</p>
    
    <p>FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys</p>
    
    <p>BUCKET_ID:  0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys</p>
    
    <p>PRIMARY_PROBLEM_CLASS:  0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys</p>
    
    <p>TARGET_TIME:  2016-03-30T17:15:33.000Z</p>
    
    <p>OSBUILD:  10586</p>
    
    <p>OSSERVICEPACK:  0</p>
    
    <p>SERVICEPACK_NUMBER: 0</p>
    
    <p>OS_REVISION: 0</p>
    
    <p>SUITE_MASK:  272</p>
    
    <p>PRODUCT_TYPE:  1</p>
    
    <p>OSPLATFORM_TYPE:  x64</p>
    
    <p>OSNAME:  Windows 10</p>
    
    <p>OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS</p>
    
    <p>OS_LOCALE:  </p>
    
    <p>USER_LCID:  0</p>
    
    <p>OSBUILD_TIMESTAMP:  2016-02-24 05:48:00</p>
    
    <p>BUILDDATESTAMP_STR:  160223-1728</p>
    
    <p>BUILDLAB_STR:  th2_release_sec</p>
    
    <p>BUILDOSVER_STR:  10.0.10586.162.amd64fre.th2_release_sec.160223-1728</p>
    
    <p>ANALYSIS_SESSION_ELAPSED_TIME: 3d7</p>
    
    <p>ANALYSIS_SOURCE:  KM</p>
    
    <p>FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_i8042prt_image_acpi.sys</p>
    
    <p>FAILURE_ID_HASH:  {22a3ff34-49ca-8d37-715b-ae023b6cc9fb}</p>
    
    <h2>Followup:     MachineOwner</h2>
    
    <p>0: kd> !irp ffffe00092718bd0
    Irp is active with 8 stacks 6 is current (= 0xffffe00092718e08)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    </p>
  </blockquote>
  
  <pre><code>        Args: 00000000 00000000 00000000 00000000
  </code></pre>
  
  <p>[N/A(0), N/A(0)]
              0  0 00000000 00000000 00000000-00000000    </p>
  
  <pre><code>        Args: 00000000 00000000 00000000 00000000
  </code></pre>
  
  <p>[N/A(0), N/A(0)]
              0  0 00000000 00000000 00000000-00000000    </p>
  
  <blockquote>
  <pre><code>        Args: 00000000 00000000 00000000 00000000
  </code></pre>
    
    <p>[N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    </p>
  </blockquote>
  
  <pre><code>        Args: 00000000 00000000 00000000 00000000
  </code></pre>
  
  <p>[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
              0  0 ffffe000935ea880 00000000 fffff800d6a81ec0-00000000<br>
             \Driver\ACPI i8042prt!I8xPowerUpToD0Complete
              Args: 00000000 00000000 00000000 00000002</p>
  
  <blockquote>
    <p>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffe00093f936f0 00000000 fffff800d6ab1060-00000000 Success Error Cancel pending
               \Driver\i8042prt kbdclass!KeyboardClassPowerComplete
                Args: 00051100 00000001 00000001 00000002
     [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffe00093dc95f0 00000000 fffff8018d7840b8-ffffe00096133010 Success Error Cancel pending
               \Driver\kbdclass nt!PopRequestCompletion
                Args: 00051100 00000001 00000001 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffffe00096133010    </p>
  
  <pre><code>        Args: 00000000 00000000 00000000 00000000
  </code></pre>
  </blockquote>
  
  <hr>
  
  <p>I'm also adding a BlueScreen screen shot, incase that helps.</p>
  
  <p><a href="https://i.stack.imgur.com/jAkcu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/jAkcu.png" alt="bluescreen"></a></p>
  
  <hr>
  
  <p>Now adding output from some extra commands after Martins comments...</p>
  
  <pre><code>0: kd&gt; !devstack ffffe000935ea880
    !DevObj           !DrvObj            !DevExt           ObjectName
    ffffe00093dc95f0  \Driver\kbdclass   ffffe00093dc9740  InfoMask field not found for _OBJECT_HEADER at ffffe00093dc95c0
  
    ffffe00093f936f0  \Driver\i8042prt   ffffe00093f93840  InfoMask field not found for _OBJECT_HEADER at ffffe00093f936c0
  
  &gt; ffffe000935ea880  \Driver\ACPI       ffffe000923fa8d0  Cannot read info offset from nt!ObpInfoMaskToOffset
  
  !DevNode ffffe000935d6af0 :
    DeviceInst is "ACPI\PNP0303\0"
    ServiceName is "i8042prt"
  
  
  
  
  !process 0 7
  **** NT ACTIVE PROCESS DUMP ****
  GetPointerFromAddress: unable to read from fffff8018d9f3200
  Error in reading nt!_EPROCESS at 0000000000000000
  
  
  
  
  0: kd&gt; !poaction
  PopAction: fffff8018d94efe0
    State..........: 0 - Idle
    Updates........: 0 
    Action.........: None
    Lightest State.: Unspecified
    Flags..........: 10000003 QueryApps|UIAllowed
    Irp minor......: ??
    System State...: Unspecified
    Hiber Context..: 0000000000000000
  
  Allocated power irps (PopIrpList - fffff8018d94f4f0)
    IRP: ffffe00092718bd0 (set/D0,), PDO: ffffe000935ea880, CURRENT: ffffe00093f936f0
    IRP: ffffe000971aa990
  
  Irp worker threads (PopIrpThreadList - fffff8018d94e100)
    THREAD: ffffe00091515040 (static)
    THREAD: ffffe00091501800 (static)
  
  Error resolving nt!_POP_CURRENT_BROADCAST...
  </code></pre>
  
  <hr>
  
  <p>Summary: Error was caused by my 10 year old Razor mouse with Windows 10.
  The driver when entering power save state was freaking out and causing the blue screen.</p>
  
  <p>I purchased a new mouse, removed the driver &amp; 2 months in no more BSOD.</p>