Advertisement
Guest User

Untitled

a guest
Apr 8th, 2022
39
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.98 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\040822-7656-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9.  
  10. ************* Path validation summary **************
  11. Response Time (ms) Location
  12. Deferred srv*
  13. Symbol search path is: srv*
  14. Executable search path is:
  15. Windows 10 Kernel Version 19041 MP (8 procs) Free x64
  16. Product: WinNt, suite: TerminalServer SingleUserTS
  17. Machine Name:
  18. Kernel base = 0xfffff804`5fe00000 PsLoadedModuleList = 0xfffff804`60a2a270
  19. Debug session time: Fri Apr 8 13:14:18.068 2022 (UTC - 7:00)
  20. System Uptime: 7 days 18:01:49.573
  21. Loading Kernel Symbols
  22. ...............................................................
  23. ................................................................
  24. ................................................................
  25. ................................
  26. Loading User Symbols
  27. Loading unloaded module list
  28. ..................................................
  29. For analysis of this file, run !analyze -v
  30. nt!KeBugCheckEx:
  31. fffff804`601f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa86`1382f360=000000000000009f
  32. 0: kd> !analyze -v
  33. *******************************************************************************
  34. * *
  35. * Bugcheck Analysis *
  36. * *
  37. *******************************************************************************
  38.  
  39. DRIVER_POWER_STATE_FAILURE (9f)
  40. A driver has failed to complete a power IRP within a specific time.
  41. Arguments:
  42. Arg1: 0000000000000006, The device did not complete its Directed Power Transition callback successfully.
  43. Arg2: ffff9a8aad9dca70, The POP_FX_DEVICE object
  44. Arg3: 0000000000000000, If this was a Directed Power Down(1) or Power Up(0) completion
  45. Arg4: 0000000000000000
  46.  
  47. Debugging Details:
  48. ------------------
  49.  
  50.  
  51. KEY_VALUES_STRING: 1
  52.  
  53. Key : Analysis.CPU.mSec
  54. Value: 6655
  55.  
  56. Key : Analysis.DebugAnalysisManager
  57. Value: Create
  58.  
  59. Key : Analysis.Elapsed.mSec
  60. Value: 8297
  61.  
  62. Key : Analysis.Init.CPU.mSec
  63. Value: 546
  64.  
  65. Key : Analysis.Init.Elapsed.mSec
  66. Value: 5799
  67.  
  68. Key : Analysis.Memory.CommitPeak.Mb
  69. Value: 93
  70.  
  71. Key : Dump.Attributes.InsufficientDumpfileSize
  72. Value: 1
  73.  
  74. Key : Dump.Attributes.RequiredDumpfileSize
  75. Value: 0xce825070
  76.  
  77.  
  78. FILE_IN_CAB: 040822-7656-01.dmp
  79.  
  80. DUMP_FILE_ATTRIBUTES: 0xc
  81. Insufficient Dumpfile Size
  82. Kernel Generated Triage Dump
  83.  
  84. BUGCHECK_CODE: 9f
  85.  
  86. BUGCHECK_P1: 6
  87.  
  88. BUGCHECK_P2: ffff9a8aad9dca70
  89.  
  90. BUGCHECK_P3: 0
  91.  
  92. BUGCHECK_P4: 0
  93.  
  94. DRVPOWERSTATE_SUBCODE: 6
  95.  
  96. DEVICE_OBJECT: ffff9a8aac46ab70
  97.  
  98. BLACKBOXBSD: 1 (!blackboxbsd)
  99.  
  100.  
  101. BLACKBOXNTFS: 1 (!blackboxntfs)
  102.  
  103.  
  104. BLACKBOXPNP: 1 (!blackboxpnp)
  105.  
  106.  
  107. BLACKBOXWINLOGON: 1
  108.  
  109. CUSTOMER_CRASH_COUNT: 1
  110.  
  111. PROCESS_NAME: System
  112.  
  113. STACK_TEXT:
  114. fffffa86`1382f358 fffff804`6036588d : 00000000`0000009f 00000000`00000006 ffff9a8a`ad9dca70 00000000`00000000 : nt!KeBugCheckEx
  115. fffffa86`1382f360 fffff804`6036536b : ffff9a8a`ad9dca70 00000000`00000000 ffff9a8a`9d693c00 ffff9a8a`ad9dce40 : nt!PopFxEnforceDirectedPowerTransition+0xc1
  116. fffffa86`1382f3c0 fffff804`60365a52 : 00000000`00000000 00000000`00000000 fffff804`60365660 ffff9a8a`9e70c860 : nt!PopFxCompleteDirectedPowerTransition+0x16f
  117. fffffa86`1382f410 fffff804`60365671 : ffff9a8a`ad9dca70 ffff9a8a`9d693cb0 00000000`00000000 00000000`00001e00 : nt!PopFxHandleDirectedPowerTransition+0xa6
  118. fffffa86`1382f440 fffff804`600b8515 : ffff9a8a`b669e100 fffff804`6017f230 ffff9a8a`9d693cb0 ffff9a8a`00000000 : nt!PopFxDirectedPowerTransitionWorker+0x11
  119. fffffa86`1382f470 fffff804`60155855 : ffff9a8a`b669e100 00000000`00000080 ffff9a8a`9d6d1080 00000000`00000000 : nt!ExpWorkerThread+0x105
  120. fffffa86`1382f510 fffff804`601fe808 : ffffc380`b7f80180 ffff9a8a`b669e100 fffff804`60155800 00000000`00000246 : nt!PspSystemThreadStartup+0x55
  121. fffffa86`1382f560 00000000`00000000 : fffffa86`13830000 fffffa86`13829000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
  122.  
  123.  
  124. SYMBOL_NAME: nt!PopFxEnforceDirectedPowerTransition+c1
  125.  
  126. MODULE_NAME: nt
  127.  
  128. IMAGE_NAME: ntkrnlmp.exe
  129.  
  130. IMAGE_VERSION: 10.0.19041.1288
  131.  
  132. STACK_COMMAND: .cxr; .ecxr ; kb
  133.  
  134. BUCKET_ID_FUNC_OFFSET: c1
  135.  
  136. FAILURE_BUCKET_ID: 0x9F_6_nt!PopFxEnforceDirectedPowerTransition
  137.  
  138. OSPLATFORM_TYPE: x64
  139.  
  140. OSNAME: Windows 10
  141.  
  142. FAILURE_ID_HASH: {552ab33e-80a6-6879-86ff-16cacccabf6d}
  143.  
  144. Followup: MachineOwner
  145. ---------
  146.  
  147. 0: kd> !devobj ffff9a8aac46ab70 f
  148. fffff80460a259d8: Unable to get value of ObpRootDirectoryObject
  149. ffff9a8aac46ab70: Could not read device object or _DEVICE_OBJECT not found
  150. 0: kd> dt _POP_FX_DEVICE ffff9a8aac46ab70
  151. nt!_POP_FX_DEVICE
  152. +0x000 Link : _LIST_ENTRY
  153. +0x010 Irp : ????
  154. +0x018 IrpData : ????
  155. +0x020 Status : _POP_FX_DEVICE_STATUS
  156. +0x024 PowerReqCall : ??
  157. +0x028 PowerNotReqCall : ??
  158. +0x030 DevNode : ????
  159. +0x038 DpmContext : ????
  160. +0x040 Plugin : ????
  161. +0x048 PluginHandle : ????
  162. +0x050 AcpiPlugin : ????
  163. +0x058 AcpiPluginHandle : ????
  164. +0x060 DeviceObject : ????
  165. +0x068 TargetDevice : ????
  166. +0x070 Callbacks : _POP_FX_DRIVER_CALLBACKS
  167. +0x0c0 DriverContext : ????
  168. +0x0c8 AcpiLink : _LIST_ENTRY
  169. +0x0d8 DeviceId : _UNICODE_STRING
  170. +0x0e8 CommonReferenceFlags : ??
  171. +0x0f0 RemoveLock : _IO_REMOVE_LOCK
  172. +0x110 AcpiRemoveLock : _IO_REMOVE_LOCK
  173. +0x130 WorkOrder : _POP_FX_WORK_ORDER
  174. +0x168 IdleLock : ??
  175. +0x170 IdleTimer : _KTIMER
  176. +0x1b0 IdleDpc : _KDPC
  177. +0x1f0 IdleTimeout : ??
  178. +0x1f8 IdleStamp : ??
  179. +0x200 NextIrpDeviceObject : [2] ????
  180. +0x210 NextIrpPowerState : [2] _POWER_STATE
  181. +0x218 NextIrpCallerCompletion : [2] ????
  182. +0x228 NextIrpCallerContext : [2] ????
  183. +0x238 IrpCompleteEvent : _KEVENT
  184. +0x250 PowerOnDumpDeviceCallback : ????
  185. +0x258 Accounting : _POP_FX_ACCOUNTING
  186. +0x338 Flags : ??
  187. +0x33c ComponentCount : ??
  188. +0x340 Components : ????
  189. +0x348 LogEntries : ??
  190. +0x350 Log : ????
  191. +0x358 LogIndex : ??
  192. +0x360 DripsWatchdogDriverObject : ????
  193. +0x368 DripsWatchdogContext : _POP_FX_DRIPS_WATCHDOG_CONTEXT
  194. +0x390 DirectedTimeout : ??
  195. +0x398 DirectedWorkOrder : _POP_FX_WORK_ORDER
  196. +0x3d0 DirectedWorkWatchdogInfo : _POP_FX_WORK_ORDER_WATCHDOG_INFO
  197. +0x480 DirectedLock : ??
  198. +0x488 DirectedTransitionCallCount : ??
  199. +0x490 DirectedTransitionState : _POP_FX_DEVICE_DIRECTED_TRANSITION_STATE
  200. +0x4a0 PowerProfile : ????
  201. +0x4a8 FriendlyName : _UNICODE_STRING
  202. Memory read error ffff9a8aac46b010
  203.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement