Advertisement
Guest User

Untitled

a guest
Feb 6th, 2019
286
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.34 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.17763.132 X86
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [D:\Downloads\bluescreenview-x64\020719-9500-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: srv*
  10. Executable search path is:
  11. Windows 10 Kernel Version 17763 MP (16 procs) Free x64
  12. Product: WinNt, suite: TerminalServer SingleUserTS
  13. Built by: 17763.1.amd64fre.rs5_release.180914-1434
  14. Machine Name:
  15. Kernel base = 0xfffff800`51e02000 PsLoadedModuleList = 0xfffff800`5221dad0
  16. Debug session time: Wed Feb 6 23:59:34.342 2019 (UTC + 1:00)
  17. System Uptime: 0 days 2:54:12.016
  18. Loading Kernel Symbols
  19. ...............................................................
  20. ................................................................
  21. ................................................................
  22. ........
  23. Loading User Symbols
  24. Loading unloaded module list
  25. ...............
  26. *******************************************************************************
  27. * *
  28. * Bugcheck Analysis *
  29. * *
  30. *******************************************************************************
  31.  
  32. Use !analyze -v to get detailed debugging information.
  33.  
  34. BugCheck 133, {1, 1e00, fffff80052344380, 0}
  35.  
  36. *************************************************************************
  37. *** ***
  38. *** ***
  39. *** Either you specified an unqualified symbol, or your debugger ***
  40. *** doesn't have full symbol information. Unqualified symbol ***
  41. *** resolution is turned off by default. Please either specify a ***
  42. *** fully qualified symbol module!symbolname, or enable resolution ***
  43. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  44. *** enabling unqualified symbol resolution with network symbol ***
  45. *** server shares in the symbol path may cause the debugger to ***
  46. *** appear to hang for long periods of time when an incorrect ***
  47. *** symbol name is typed or the network symbol server is down. ***
  48. *** ***
  49. *** For some commands to work properly, your symbol path ***
  50. *** must point to .pdb files that have full type information. ***
  51. *** ***
  52. *** Certain .pdb files (such as the public OS symbols) do not ***
  53. *** contain the required information. Contact the group that ***
  54. *** provided you with these symbols if you need this command to ***
  55. *** work. ***
  56. *** ***
  57. *** Type referenced: TickPeriods ***
  58. *** ***
  59. *************************************************************************
  60. Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+12edb5 )
  61.  
  62. Followup: MachineOwner
  63. ---------
  64.  
  65. 7: kd> !analyze -v
  66. *******************************************************************************
  67. * *
  68. * Bugcheck Analysis *
  69. * *
  70. *******************************************************************************
  71.  
  72. DPC_WATCHDOG_VIOLATION (133)
  73. The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
  74. or above.
  75. Arguments:
  76. Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
  77. DISPATCH_LEVEL or above. The offending component can usually be
  78. identified with a stack trace.
  79. Arg2: 0000000000001e00, The watchdog period.
  80. Arg3: fffff80052344380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
  81. additional information regarding the cumulative timeout
  82. Arg4: 0000000000000000
  83.  
  84. Debugging Details:
  85. ------------------
  86.  
  87. *************************************************************************
  88. *** ***
  89. *** ***
  90. *** Either you specified an unqualified symbol, or your debugger ***
  91. *** doesn't have full symbol information. Unqualified symbol ***
  92. *** resolution is turned off by default. Please either specify a ***
  93. *** fully qualified symbol module!symbolname, or enable resolution ***
  94. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  95. *** enabling unqualified symbol resolution with network symbol ***
  96. *** server shares in the symbol path may cause the debugger to ***
  97. *** appear to hang for long periods of time when an incorrect ***
  98. *** symbol name is typed or the network symbol server is down. ***
  99. *** ***
  100. *** For some commands to work properly, your symbol path ***
  101. *** must point to .pdb files that have full type information. ***
  102. *** ***
  103. *** Certain .pdb files (such as the public OS symbols) do not ***
  104. *** contain the required information. Contact the group that ***
  105. *** provided you with these symbols if you need this command to ***
  106. *** work. ***
  107. *** ***
  108. *** Type referenced: TickPeriods ***
  109. *** ***
  110. *************************************************************************
  111.  
  112. KEY_VALUES_STRING: 1
  113.  
  114.  
  115. STACKHASH_ANALYSIS: 1
  116.  
  117. TIMELINE_ANALYSIS: 1
  118.  
  119.  
  120. DUMP_CLASS: 1
  121.  
  122. DUMP_QUALIFIER: 400
  123.  
  124. BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
  125.  
  126. DUMP_TYPE: 2
  127.  
  128. BUGCHECK_P1: 1
  129.  
  130. BUGCHECK_P2: 1e00
  131.  
  132. BUGCHECK_P3: fffff80052344380
  133.  
  134. BUGCHECK_P4: 0
  135.  
  136. DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
  137.  
  138. CPU_COUNT: 10
  139.  
  140. CPU_MHZ: e10
  141.  
  142. CPU_VENDOR: GenuineIntel
  143.  
  144. CPU_FAMILY: 6
  145.  
  146. CPU_MODEL: 9e
  147.  
  148. CPU_STEPPING: c
  149.  
  150. CUSTOMER_CRASH_COUNT: 1
  151.  
  152. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  153.  
  154. BUGCHECK_STR: 0x133
  155.  
  156. PROCESS_NAME: Corsair.Service.CpuIdRemote64.exe
  157.  
  158. CURRENT_IRQL: d
  159.  
  160. ANALYSIS_SESSION_HOST: DESKTOP-EVLPTGD
  161.  
  162. ANALYSIS_SESSION_TIME: 02-07-2019 02:53:21.0408
  163.  
  164. ANALYSIS_VERSION: 10.0.17763.132 x86fre
  165.  
  166. LAST_CONTROL_TRANSFER: from fffff800520581d5 to fffff80051fb5440
  167.  
  168. STACK_TEXT:
  169. ffffc600`9e1f1ba8 fffff800`520581d5 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`52344380 : nt!KeBugCheckEx
  170. ffffc600`9e1f1bb0 fffff800`51f262e4 : 00002243`137778a0 00000000`00000000 00000000`000a3501 ffffc600`9e1d5180 : nt!KeAccumulateTicks+0x12edb5
  171. ffffc600`9e1f1c10 fffff800`52873332 : 00000000`00000000 fffff800`528d7bd8 ffffc202`9d447090 00000000`00000002 : nt!KeClockInterruptNotify+0x604
  172. ffffc600`9e1f1f30 fffff800`51e448b5 : 00000018`55f9eb41 ffff8008`714d4f00 ffff8008`714d4fb0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf2
  173. ffffc600`9e1f1f60 fffff800`51fb6e3a : ffffc202`9d447090 ffff8008`714d4f00 00000000`00000000 ffff8008`714d4f00 : nt!KiCallInterruptServiceRoutine+0xa5
  174. ffffc600`9e1f1fb0 fffff800`51fb7387 : 00000000`ddbeef1b ffffc202`9d447090 ffff8008`714d4f00 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
  175. ffffc202`9d447010 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
  176.  
  177.  
  178. THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c
  179.  
  180. THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 06e0b5c60ca94b3ca5424fcc0f6d146bb3b24353
  181.  
  182. THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759
  183.  
  184. FOLLOWUP_IP:
  185. nt!KeAccumulateTicks+12edb5
  186. fffff800`520581d5 cc int 3
  187.  
  188. FAULT_INSTR_CODE: ab3944cc
  189.  
  190. SYMBOL_STACK_INDEX: 1
  191.  
  192. SYMBOL_NAME: nt!KeAccumulateTicks+12edb5
  193.  
  194. FOLLOWUP_NAME: MachineOwner
  195.  
  196. MODULE_NAME: nt
  197.  
  198. IMAGE_NAME: ntkrnlmp.exe
  199.  
  200. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  201.  
  202. IMAGE_VERSION: 10.0.17763.292
  203.  
  204. STACK_COMMAND: .thread ; .cxr ; kb
  205.  
  206. BUCKET_ID_FUNC_OFFSET: 12edb5
  207.  
  208. FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
  209.  
  210. BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
  211.  
  212. PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks
  213.  
  214. TARGET_TIME: 2019-02-06T22:59:34.000Z
  215.  
  216. OSBUILD: 17763
  217.  
  218. OSSERVICEPACK: 292
  219.  
  220. SERVICEPACK_NUMBER: 0
  221.  
  222. OS_REVISION: 0
  223.  
  224. SUITE_MASK: 272
  225.  
  226. PRODUCT_TYPE: 1
  227.  
  228. OSPLATFORM_TYPE: x64
  229.  
  230. OSNAME: Windows 10
  231.  
  232. OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
  233.  
  234. OS_LOCALE:
  235.  
  236. USER_LCID: 0
  237.  
  238. OSBUILD_TIMESTAMP: unknown_date
  239.  
  240. BUILDDATESTAMP_STR: 180914-1434
  241.  
  242. BUILDLAB_STR: rs5_release
  243.  
  244. BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
  245.  
  246. ANALYSIS_SESSION_ELAPSED_TIME: 1c49
  247.  
  248. ANALYSIS_SOURCE: KM
  249.  
  250. FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks
  251.  
  252. FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
  253.  
  254. Followup: MachineOwner
  255. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement