Advertisement
comniemeer

Untitled

May 16th, 2014
296
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.27 KB | None | 0 0
  1. Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\MEMORY.DMP]
  6. Kernel Bitmap Dump File: Only kernel address space is available
  7.  
  8. Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 8 Kernel Version 9600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
  13. Machine Name:
  14. Kernel base = 0xfffff802`25472000 PsLoadedModuleList = 0xfffff802`2573c2d0
  15. Debug session time: Fri May 16 23:22:07.811 2014 (UTC + 2:00)
  16. System Uptime: 1 days 1:05:43.212
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ..............................................................
  21. Loading User Symbols
  22.  
  23. Loading unloaded module list
  24. .....................
  25. *******************************************************************************
  26. * *
  27. * Bugcheck Analysis *
  28. * *
  29. *******************************************************************************
  30.  
  31. Use !analyze -v to get detailed debugging information.
  32.  
  33. BugCheck 9F, {3, ffffe001a5ef98e0, ffffd001033fc930, ffffe001a99a3470}
  34.  
  35. Probably caused by : usbccgp.sys
  36.  
  37. Followup: MachineOwner
  38. ---------
  39.  
  40. 2: kd> !analyze –v
  41. *******************************************************************************
  42. * *
  43. * Bugcheck Analysis *
  44. * *
  45. *******************************************************************************
  46.  
  47. Use !analyze -v to get detailed debugging information.
  48.  
  49. BugCheck 9F, {3, ffffe001a5ef98e0, ffffd001033fc930, ffffe001a99a3470}
  50.  
  51. Probably caused by : usbccgp.sys
  52.  
  53. Followup: MachineOwner
  54. ---------
  55.  
  56. 2: kd> !analyze -v
  57. *******************************************************************************
  58. * *
  59. * Bugcheck Analysis *
  60. * *
  61. *******************************************************************************
  62.  
  63. DRIVER_POWER_STATE_FAILURE (9f)
  64. A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
  65. Arguments:
  66. Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
  67. Arg2: ffffe001a5ef98e0, Physical Device Object of the stack
  68. Arg3: ffffd001033fc930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
  69. Arg4: ffffe001a99a3470, The blocked IRP
  70.  
  71. Debugging Details:
  72. ------------------
  73.  
  74.  
  75. DRVPOWERSTATE_SUBCODE: 3
  76.  
  77. IMAGE_NAME: usbccgp.sys
  78.  
  79. DEBUG_FLR_IMAGE_TIMESTAMP: 52678625
  80.  
  81. MODULE_NAME: usbccgp
  82.  
  83. FAULTING_MODULE: fffff801ef9bf000 usbccgp
  84.  
  85. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  86.  
  87. BUGCHECK_STR: 0x9F
  88.  
  89. PROCESS_NAME: System
  90.  
  91. CURRENT_IRQL: 2
  92.  
  93. STACK_TEXT:
  94. ffffd001`033fc8f8 fffff802`2566ec1e : 00000000`0000009f 00000000`00000003 ffffe001`a5ef98e0 ffffd001`033fc930 : nt!KeBugCheckEx
  95. ffffd001`033fc900 fffff802`2566eb3e : ffffe001`abceda00 ffffe000`ffffffff ffffe001`abceda40 fffff802`254cf240 : nt!PopIrpWatchdogBugcheck+0xde
  96. ffffd001`033fc960 fffff802`254cb810 : 00000000`00000000 ffffd001`033fcab0 ffffe001`abceda38 fffff802`00000002 : nt!PopIrpWatchdog+0x32
  97. ffffd001`033fc9b0 fffff802`255c9aea : ffffd001`033e7180 ffffd001`033e7180 ffffd001`033f33c0 ffffe001`a182e080 : nt!KiRetireDpcList+0x4f0
  98. ffffd001`033fcc60 00000000`00000000 : ffffd001`033fd000 ffffd001`033f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
  99.  
  100.  
  101. STACK_COMMAND: kb
  102.  
  103. FOLLOWUP_NAME: MachineOwner
  104.  
  105. FAILURE_BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  106.  
  107. BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  108.  
  109. Followup: MachineOwner
  110. ---------
  111.  
  112. 2: kd> !analyze -v
  113. *******************************************************************************
  114. * *
  115. * Bugcheck Analysis *
  116. * *
  117. *******************************************************************************
  118.  
  119. DRIVER_POWER_STATE_FAILURE (9f)
  120. A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
  121. Arguments:
  122. Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
  123. Arg2: ffffe001a5ef98e0, Physical Device Object of the stack
  124. Arg3: ffffd001033fc930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
  125. Arg4: ffffe001a99a3470, The blocked IRP
  126.  
  127. Debugging Details:
  128. ------------------
  129.  
  130.  
  131. DRVPOWERSTATE_SUBCODE: 3
  132.  
  133. IMAGE_NAME: usbccgp.sys
  134.  
  135. DEBUG_FLR_IMAGE_TIMESTAMP: 52678625
  136.  
  137. MODULE_NAME: usbccgp
  138.  
  139. FAULTING_MODULE: fffff801ef9bf000 usbccgp
  140.  
  141. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  142.  
  143. BUGCHECK_STR: 0x9F
  144.  
  145. PROCESS_NAME: System
  146.  
  147. CURRENT_IRQL: 2
  148.  
  149. STACK_TEXT:
  150. ffffd001`033fc8f8 fffff802`2566ec1e : 00000000`0000009f 00000000`00000003 ffffe001`a5ef98e0 ffffd001`033fc930 : nt!KeBugCheckEx
  151. ffffd001`033fc900 fffff802`2566eb3e : ffffe001`abceda00 ffffe000`ffffffff ffffe001`abceda40 fffff802`254cf240 : nt!PopIrpWatchdogBugcheck+0xde
  152. ffffd001`033fc960 fffff802`254cb810 : 00000000`00000000 ffffd001`033fcab0 ffffe001`abceda38 fffff802`00000002 : nt!PopIrpWatchdog+0x32
  153. ffffd001`033fc9b0 fffff802`255c9aea : ffffd001`033e7180 ffffd001`033e7180 ffffd001`033f33c0 ffffe001`a182e080 : nt!KiRetireDpcList+0x4f0
  154. ffffd001`033fcc60 00000000`00000000 : ffffd001`033fd000 ffffd001`033f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
  155.  
  156.  
  157. STACK_COMMAND: kb
  158.  
  159. FOLLOWUP_NAME: MachineOwner
  160.  
  161. FAILURE_BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  162.  
  163. BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  164.  
  165. Followup: MachineOwner
  166. ---------
  167.  
  168. 2: kd> !analyze -v
  169. *******************************************************************************
  170. * *
  171. * Bugcheck Analysis *
  172. * *
  173. *******************************************************************************
  174.  
  175. DRIVER_POWER_STATE_FAILURE (9f)
  176. A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
  177. Arguments:
  178. Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
  179. Arg2: ffffe001a5ef98e0, Physical Device Object of the stack
  180. Arg3: ffffd001033fc930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
  181. Arg4: ffffe001a99a3470, The blocked IRP
  182.  
  183. Debugging Details:
  184. ------------------
  185.  
  186.  
  187. DRVPOWERSTATE_SUBCODE: 3
  188.  
  189. IMAGE_NAME: usbccgp.sys
  190.  
  191. DEBUG_FLR_IMAGE_TIMESTAMP: 52678625
  192.  
  193. MODULE_NAME: usbccgp
  194.  
  195. FAULTING_MODULE: fffff801ef9bf000 usbccgp
  196.  
  197. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  198.  
  199. BUGCHECK_STR: 0x9F
  200.  
  201. PROCESS_NAME: System
  202.  
  203. CURRENT_IRQL: 2
  204.  
  205. STACK_TEXT:
  206. ffffd001`033fc8f8 fffff802`2566ec1e : 00000000`0000009f 00000000`00000003 ffffe001`a5ef98e0 ffffd001`033fc930 : nt!KeBugCheckEx
  207. ffffd001`033fc900 fffff802`2566eb3e : ffffe001`abceda00 ffffe000`ffffffff ffffe001`abceda40 fffff802`254cf240 : nt!PopIrpWatchdogBugcheck+0xde
  208. ffffd001`033fc960 fffff802`254cb810 : 00000000`00000000 ffffd001`033fcab0 ffffe001`abceda38 fffff802`00000002 : nt!PopIrpWatchdog+0x32
  209. ffffd001`033fc9b0 fffff802`255c9aea : ffffd001`033e7180 ffffd001`033e7180 ffffd001`033f33c0 ffffe001`a182e080 : nt!KiRetireDpcList+0x4f0
  210. ffffd001`033fcc60 00000000`00000000 : ffffd001`033fd000 ffffd001`033f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
  211.  
  212.  
  213. STACK_COMMAND: kb
  214.  
  215. FOLLOWUP_NAME: MachineOwner
  216.  
  217. FAILURE_BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  218.  
  219. BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  220.  
  221. Followup: MachineOwner
  222. ---------
  223.  
  224. 2: kd> !analyze -v
  225. *******************************************************************************
  226. * *
  227. * Bugcheck Analysis *
  228. * *
  229. *******************************************************************************
  230.  
  231. DRIVER_POWER_STATE_FAILURE (9f)
  232. A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
  233. Arguments:
  234. Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
  235. Arg2: ffffe001a5ef98e0, Physical Device Object of the stack
  236. Arg3: ffffd001033fc930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
  237. Arg4: ffffe001a99a3470, The blocked IRP
  238.  
  239. Debugging Details:
  240. ------------------
  241.  
  242.  
  243. DRVPOWERSTATE_SUBCODE: 3
  244.  
  245. IMAGE_NAME: usbccgp.sys
  246.  
  247. DEBUG_FLR_IMAGE_TIMESTAMP: 52678625
  248.  
  249. MODULE_NAME: usbccgp
  250.  
  251. FAULTING_MODULE: fffff801ef9bf000 usbccgp
  252.  
  253. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  254.  
  255. BUGCHECK_STR: 0x9F
  256.  
  257. PROCESS_NAME: System
  258.  
  259. CURRENT_IRQL: 2
  260.  
  261. STACK_TEXT:
  262. ffffd001`033fc8f8 fffff802`2566ec1e : 00000000`0000009f 00000000`00000003 ffffe001`a5ef98e0 ffffd001`033fc930 : nt!KeBugCheckEx
  263. ffffd001`033fc900 fffff802`2566eb3e : ffffe001`abceda00 ffffe000`ffffffff ffffe001`abceda40 fffff802`254cf240 : nt!PopIrpWatchdogBugcheck+0xde
  264. ffffd001`033fc960 fffff802`254cb810 : 00000000`00000000 ffffd001`033fcab0 ffffe001`abceda38 fffff802`00000002 : nt!PopIrpWatchdog+0x32
  265. ffffd001`033fc9b0 fffff802`255c9aea : ffffd001`033e7180 ffffd001`033e7180 ffffd001`033f33c0 ffffe001`a182e080 : nt!KiRetireDpcList+0x4f0
  266. ffffd001`033fcc60 00000000`00000000 : ffffd001`033fd000 ffffd001`033f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
  267.  
  268.  
  269. STACK_COMMAND: kb
  270.  
  271. FOLLOWUP_NAME: MachineOwner
  272.  
  273. FAILURE_BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  274.  
  275. BUCKET_ID: 0x9F_3_usbaudio_IMAGE_usbccgp.sys
  276.  
  277. Followup: MachineOwner
  278. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement