Guest User

MGA minidump

a guest
Apr 21st, 2012
159
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 37.74 KB | None | 0 0
  1. Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\041912-9703-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: *** Invalid ***
  9. ****************************************************************************
  10. * Symbol loading may be unreliable without a symbol search path. *
  11. * Use .symfix to have the debugger choose a symbol path. *
  12. * After setting your symbol path, use .reload to refresh symbol locations. *
  13. ****************************************************************************
  14. Executable search path is:
  15. *********************************************************************
  16. * Symbols can not be loaded because symbol path is not initialized. *
  17. * *
  18. * The Symbol Path can be set by: *
  19. * using the _NT_SYMBOL_PATH environment variable. *
  20. * using the -y <symbol_path> argument when starting the debugger. *
  21. * using .sympath and .sympath+ *
  22. *********************************************************************
  23. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  24. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  25. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  26. Windows 8 Kernel Version 8250 MP (4 procs) Free x64
  27. Product: WinNt, suite: TerminalServer SingleUserTS
  28. Built by: 8250.128.amd64fre.winmain_win8beta_se.120330-1316
  29. Machine Name:
  30. Kernel base = 0xfffff800`8c278000 PsLoadedModuleList = 0xfffff800`8c51ed80
  31. Debug session time: Thu Apr 19 11:07:31.007 2012 (UTC - 7:00)
  32. System Uptime: 0 days 12:11:15.922
  33. *********************************************************************
  34. * Symbols can not be loaded because symbol path is not initialized. *
  35. * *
  36. * The Symbol Path can be set by: *
  37. * using the _NT_SYMBOL_PATH environment variable. *
  38. * using the -y <symbol_path> argument when starting the debugger. *
  39. * using .sympath and .sympath+ *
  40. *********************************************************************
  41. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  42. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  43. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  44. Loading Kernel Symbols
  45. ...............................................................
  46. ................................................................
  47. ............................
  48. Loading User Symbols
  49. Loading unloaded module list
  50. ..................................................
  51. TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
  52. TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
  53. *******************************************************************************
  54. * *
  55. * Bugcheck Analysis *
  56. * *
  57. *******************************************************************************
  58.  
  59. Use !analyze -v to get detailed debugging information.
  60.  
  61. BugCheck 101, {30, 0, fffff880009c0180, 1}
  62.  
  63. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  64.  
  65. *************************************************************************
  66. *** ***
  67. *** ***
  68. *** Either you specified an unqualified symbol, or your debugger ***
  69. *** doesn't have full symbol information. Unqualified symbol ***
  70. *** resolution is turned off by default. Please either specify a ***
  71. *** fully qualified symbol module!symbolname, or enable resolution ***
  72. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  73. *** enabling unqualified symbol resolution with network symbol ***
  74. *** server shares in the symbol path may cause the debugger to ***
  75. *** appear to hang for long periods of time when an incorrect ***
  76. *** symbol name is typed or the network symbol server is down. ***
  77. *** ***
  78. *** For some commands to work properly, your symbol path ***
  79. *** must point to .pdb files that have full type information. ***
  80. *** ***
  81. *** Certain .pdb files (such as the public OS symbols) do not ***
  82. *** contain the required information. Contact the group that ***
  83. *** provided you with these symbols if you need this command to ***
  84. *** work. ***
  85. *** ***
  86. *** Type referenced: nt!_KPRCB ***
  87. *** ***
  88. *************************************************************************
  89. *************************************************************************
  90. *** ***
  91. *** ***
  92. *** Either you specified an unqualified symbol, or your debugger ***
  93. *** doesn't have full symbol information. Unqualified symbol ***
  94. *** resolution is turned off by default. Please either specify a ***
  95. *** fully qualified symbol module!symbolname, or enable resolution ***
  96. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  97. *** enabling unqualified symbol resolution with network symbol ***
  98. *** server shares in the symbol path may cause the debugger to ***
  99. *** appear to hang for long periods of time when an incorrect ***
  100. *** symbol name is typed or the network symbol server is down. ***
  101. *** ***
  102. *** For some commands to work properly, your symbol path ***
  103. *** must point to .pdb files that have full type information. ***
  104. *** ***
  105. *** Certain .pdb files (such as the public OS symbols) do not ***
  106. *** contain the required information. Contact the group that ***
  107. *** provided you with these symbols if you need this command to ***
  108. *** work. ***
  109. *** ***
  110. *** Type referenced: nt!KPRCB ***
  111. *** ***
  112. *************************************************************************
  113. *************************************************************************
  114. *** ***
  115. *** ***
  116. *** Either you specified an unqualified symbol, or your debugger ***
  117. *** doesn't have full symbol information. Unqualified symbol ***
  118. *** resolution is turned off by default. Please either specify a ***
  119. *** fully qualified symbol module!symbolname, or enable resolution ***
  120. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  121. *** enabling unqualified symbol resolution with network symbol ***
  122. *** server shares in the symbol path may cause the debugger to ***
  123. *** appear to hang for long periods of time when an incorrect ***
  124. *** symbol name is typed or the network symbol server is down. ***
  125. *** ***
  126. *** For some commands to work properly, your symbol path ***
  127. *** must point to .pdb files that have full type information. ***
  128. *** ***
  129. *** Certain .pdb files (such as the public OS symbols) do not ***
  130. *** contain the required information. Contact the group that ***
  131. *** provided you with these symbols if you need this command to ***
  132. *** work. ***
  133. *** ***
  134. *** Type referenced: nt!_KPRCB ***
  135. *** ***
  136. *************************************************************************
  137. *************************************************************************
  138. *** ***
  139. *** ***
  140. *** Either you specified an unqualified symbol, or your debugger ***
  141. *** doesn't have full symbol information. Unqualified symbol ***
  142. *** resolution is turned off by default. Please either specify a ***
  143. *** fully qualified symbol module!symbolname, or enable resolution ***
  144. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  145. *** enabling unqualified symbol resolution with network symbol ***
  146. *** server shares in the symbol path may cause the debugger to ***
  147. *** appear to hang for long periods of time when an incorrect ***
  148. *** symbol name is typed or the network symbol server is down. ***
  149. *** ***
  150. *** For some commands to work properly, your symbol path ***
  151. *** must point to .pdb files that have full type information. ***
  152. *** ***
  153. *** Certain .pdb files (such as the public OS symbols) do not ***
  154. *** contain the required information. Contact the group that ***
  155. *** provided you with these symbols if you need this command to ***
  156. *** work. ***
  157. *** ***
  158. *** Type referenced: nt!KPRCB ***
  159. *** ***
  160. *************************************************************************
  161. *************************************************************************
  162. *** ***
  163. *** ***
  164. *** Either you specified an unqualified symbol, or your debugger ***
  165. *** doesn't have full symbol information. Unqualified symbol ***
  166. *** resolution is turned off by default. Please either specify a ***
  167. *** fully qualified symbol module!symbolname, or enable resolution ***
  168. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  169. *** enabling unqualified symbol resolution with network symbol ***
  170. *** server shares in the symbol path may cause the debugger to ***
  171. *** appear to hang for long periods of time when an incorrect ***
  172. *** symbol name is typed or the network symbol server is down. ***
  173. *** ***
  174. *** For some commands to work properly, your symbol path ***
  175. *** must point to .pdb files that have full type information. ***
  176. *** ***
  177. *** Certain .pdb files (such as the public OS symbols) do not ***
  178. *** contain the required information. Contact the group that ***
  179. *** provided you with these symbols if you need this command to ***
  180. *** work. ***
  181. *** ***
  182. *** Type referenced: nt!_KPRCB ***
  183. *** ***
  184. *************************************************************************
  185. *************************************************************************
  186. *** ***
  187. *** ***
  188. *** Either you specified an unqualified symbol, or your debugger ***
  189. *** doesn't have full symbol information. Unqualified symbol ***
  190. *** resolution is turned off by default. Please either specify a ***
  191. *** fully qualified symbol module!symbolname, or enable resolution ***
  192. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  193. *** enabling unqualified symbol resolution with network symbol ***
  194. *** server shares in the symbol path may cause the debugger to ***
  195. *** appear to hang for long periods of time when an incorrect ***
  196. *** symbol name is typed or the network symbol server is down. ***
  197. *** ***
  198. *** For some commands to work properly, your symbol path ***
  199. *** must point to .pdb files that have full type information. ***
  200. *** ***
  201. *** Certain .pdb files (such as the public OS symbols) do not ***
  202. *** contain the required information. Contact the group that ***
  203. *** provided you with these symbols if you need this command to ***
  204. *** work. ***
  205. *** ***
  206. *** Type referenced: nt!_KPRCB ***
  207. *** ***
  208. *************************************************************************
  209. TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
  210. *************************************************************************
  211. *** ***
  212. *** ***
  213. *** Either you specified an unqualified symbol, or your debugger ***
  214. *** doesn't have full symbol information. Unqualified symbol ***
  215. *** resolution is turned off by default. Please either specify a ***
  216. *** fully qualified symbol module!symbolname, or enable resolution ***
  217. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  218. *** enabling unqualified symbol resolution with network symbol ***
  219. *** server shares in the symbol path may cause the debugger to ***
  220. *** appear to hang for long periods of time when an incorrect ***
  221. *** symbol name is typed or the network symbol server is down. ***
  222. *** ***
  223. *** For some commands to work properly, your symbol path ***
  224. *** must point to .pdb files that have full type information. ***
  225. *** ***
  226. *** Certain .pdb files (such as the public OS symbols) do not ***
  227. *** contain the required information. Contact the group that ***
  228. *** provided you with these symbols if you need this command to ***
  229. *** work. ***
  230. *** ***
  231. *** Type referenced: nt!_KPRCB ***
  232. *** ***
  233. *************************************************************************
  234. *************************************************************************
  235. *** ***
  236. *** ***
  237. *** Either you specified an unqualified symbol, or your debugger ***
  238. *** doesn't have full symbol information. Unqualified symbol ***
  239. *** resolution is turned off by default. Please either specify a ***
  240. *** fully qualified symbol module!symbolname, or enable resolution ***
  241. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  242. *** enabling unqualified symbol resolution with network symbol ***
  243. *** server shares in the symbol path may cause the debugger to ***
  244. *** appear to hang for long periods of time when an incorrect ***
  245. *** symbol name is typed or the network symbol server is down. ***
  246. *** ***
  247. *** For some commands to work properly, your symbol path ***
  248. *** must point to .pdb files that have full type information. ***
  249. *** ***
  250. *** Certain .pdb files (such as the public OS symbols) do not ***
  251. *** contain the required information. Contact the group that ***
  252. *** provided you with these symbols if you need this command to ***
  253. *** work. ***
  254. *** ***
  255. *** Type referenced: nt!_KPRCB ***
  256. *** ***
  257. *************************************************************************
  258. Probably caused by : ntoskrnl.exe
  259.  
  260. Followup: MachineOwner
  261. ---------
  262.  
  263. 0: kd> .exepath
  264. Executable image search path is: <empty>
  265. Expanded Executable image search path is: <empty>
  266. 0: kd> .symfix
  267. 0: kd> !analyze -v
  268. *******************************************************************************
  269. * *
  270. * Bugcheck Analysis *
  271. * *
  272. *******************************************************************************
  273.  
  274. CLOCK_WATCHDOG_TIMEOUT (101)
  275. An expected clock interrupt was not received on a secondary processor in an
  276. MP system within the allocated interval. This indicates that the specified
  277. processor is hung and not processing interrupts.
  278. Arguments:
  279. Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
  280. Arg2: 0000000000000000, 0.
  281. Arg3: fffff880009c0180, The PRCB address of the hung processor.
  282. Arg4: 0000000000000001, 0.
  283.  
  284. Debugging Details:
  285. ------------------
  286.  
  287. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  288.  
  289. *************************************************************************
  290. *** ***
  291. *** ***
  292. *** Either you specified an unqualified symbol, or your debugger ***
  293. *** doesn't have full symbol information. Unqualified symbol ***
  294. *** resolution is turned off by default. Please either specify a ***
  295. *** fully qualified symbol module!symbolname, or enable resolution ***
  296. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  297. *** enabling unqualified symbol resolution with network symbol ***
  298. *** server shares in the symbol path may cause the debugger to ***
  299. *** appear to hang for long periods of time when an incorrect ***
  300. *** symbol name is typed or the network symbol server is down. ***
  301. *** ***
  302. *** For some commands to work properly, your symbol path ***
  303. *** must point to .pdb files that have full type information. ***
  304. *** ***
  305. *** Certain .pdb files (such as the public OS symbols) do not ***
  306. *** contain the required information. Contact the group that ***
  307. *** provided you with these symbols if you need this command to ***
  308. *** work. ***
  309. *** ***
  310. *** Type referenced: nt!_KPRCB ***
  311. *** ***
  312. *************************************************************************
  313. *************************************************************************
  314. *** ***
  315. *** ***
  316. *** Either you specified an unqualified symbol, or your debugger ***
  317. *** doesn't have full symbol information. Unqualified symbol ***
  318. *** resolution is turned off by default. Please either specify a ***
  319. *** fully qualified symbol module!symbolname, or enable resolution ***
  320. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  321. *** enabling unqualified symbol resolution with network symbol ***
  322. *** server shares in the symbol path may cause the debugger to ***
  323. *** appear to hang for long periods of time when an incorrect ***
  324. *** symbol name is typed or the network symbol server is down. ***
  325. *** ***
  326. *** For some commands to work properly, your symbol path ***
  327. *** must point to .pdb files that have full type information. ***
  328. *** ***
  329. *** Certain .pdb files (such as the public OS symbols) do not ***
  330. *** contain the required information. Contact the group that ***
  331. *** provided you with these symbols if you need this command to ***
  332. *** work. ***
  333. *** ***
  334. *** Type referenced: nt!KPRCB ***
  335. *** ***
  336. *************************************************************************
  337. *************************************************************************
  338. *** ***
  339. *** ***
  340. *** Either you specified an unqualified symbol, or your debugger ***
  341. *** doesn't have full symbol information. Unqualified symbol ***
  342. *** resolution is turned off by default. Please either specify a ***
  343. *** fully qualified symbol module!symbolname, or enable resolution ***
  344. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  345. *** enabling unqualified symbol resolution with network symbol ***
  346. *** server shares in the symbol path may cause the debugger to ***
  347. *** appear to hang for long periods of time when an incorrect ***
  348. *** symbol name is typed or the network symbol server is down. ***
  349. *** ***
  350. *** For some commands to work properly, your symbol path ***
  351. *** must point to .pdb files that have full type information. ***
  352. *** ***
  353. *** Certain .pdb files (such as the public OS symbols) do not ***
  354. *** contain the required information. Contact the group that ***
  355. *** provided you with these symbols if you need this command to ***
  356. *** work. ***
  357. *** ***
  358. *** Type referenced: nt!_KPRCB ***
  359. *** ***
  360. *************************************************************************
  361. *************************************************************************
  362. *** ***
  363. *** ***
  364. *** Either you specified an unqualified symbol, or your debugger ***
  365. *** doesn't have full symbol information. Unqualified symbol ***
  366. *** resolution is turned off by default. Please either specify a ***
  367. *** fully qualified symbol module!symbolname, or enable resolution ***
  368. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  369. *** enabling unqualified symbol resolution with network symbol ***
  370. *** server shares in the symbol path may cause the debugger to ***
  371. *** appear to hang for long periods of time when an incorrect ***
  372. *** symbol name is typed or the network symbol server is down. ***
  373. *** ***
  374. *** For some commands to work properly, your symbol path ***
  375. *** must point to .pdb files that have full type information. ***
  376. *** ***
  377. *** Certain .pdb files (such as the public OS symbols) do not ***
  378. *** contain the required information. Contact the group that ***
  379. *** provided you with these symbols if you need this command to ***
  380. *** work. ***
  381. *** ***
  382. *** Type referenced: nt!KPRCB ***
  383. *** ***
  384. *************************************************************************
  385. *************************************************************************
  386. *** ***
  387. *** ***
  388. *** Either you specified an unqualified symbol, or your debugger ***
  389. *** doesn't have full symbol information. Unqualified symbol ***
  390. *** resolution is turned off by default. Please either specify a ***
  391. *** fully qualified symbol module!symbolname, or enable resolution ***
  392. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  393. *** enabling unqualified symbol resolution with network symbol ***
  394. *** server shares in the symbol path may cause the debugger to ***
  395. *** appear to hang for long periods of time when an incorrect ***
  396. *** symbol name is typed or the network symbol server is down. ***
  397. *** ***
  398. *** For some commands to work properly, your symbol path ***
  399. *** must point to .pdb files that have full type information. ***
  400. *** ***
  401. *** Certain .pdb files (such as the public OS symbols) do not ***
  402. *** contain the required information. Contact the group that ***
  403. *** provided you with these symbols if you need this command to ***
  404. *** work. ***
  405. *** ***
  406. *** Type referenced: nt!_KPRCB ***
  407. *** ***
  408. *************************************************************************
  409. *************************************************************************
  410. *** ***
  411. *** ***
  412. *** Either you specified an unqualified symbol, or your debugger ***
  413. *** doesn't have full symbol information. Unqualified symbol ***
  414. *** resolution is turned off by default. Please either specify a ***
  415. *** fully qualified symbol module!symbolname, or enable resolution ***
  416. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  417. *** enabling unqualified symbol resolution with network symbol ***
  418. *** server shares in the symbol path may cause the debugger to ***
  419. *** appear to hang for long periods of time when an incorrect ***
  420. *** symbol name is typed or the network symbol server is down. ***
  421. *** ***
  422. *** For some commands to work properly, your symbol path ***
  423. *** must point to .pdb files that have full type information. ***
  424. *** ***
  425. *** Certain .pdb files (such as the public OS symbols) do not ***
  426. *** contain the required information. Contact the group that ***
  427. *** provided you with these symbols if you need this command to ***
  428. *** work. ***
  429. *** ***
  430. *** Type referenced: nt!_KPRCB ***
  431. *** ***
  432. *************************************************************************
  433. *************************************************************************
  434. *** ***
  435. *** ***
  436. *** Either you specified an unqualified symbol, or your debugger ***
  437. *** doesn't have full symbol information. Unqualified symbol ***
  438. *** resolution is turned off by default. Please either specify a ***
  439. *** fully qualified symbol module!symbolname, or enable resolution ***
  440. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  441. *** enabling unqualified symbol resolution with network symbol ***
  442. *** server shares in the symbol path may cause the debugger to ***
  443. *** appear to hang for long periods of time when an incorrect ***
  444. *** symbol name is typed or the network symbol server is down. ***
  445. *** ***
  446. *** For some commands to work properly, your symbol path ***
  447. *** must point to .pdb files that have full type information. ***
  448. *** ***
  449. *** Certain .pdb files (such as the public OS symbols) do not ***
  450. *** contain the required information. Contact the group that ***
  451. *** provided you with these symbols if you need this command to ***
  452. *** work. ***
  453. *** ***
  454. *** Type referenced: nt!_MMPTE ***
  455. *** ***
  456. *************************************************************************
  457. *************************************************************************
  458. *** ***
  459. *** ***
  460. *** Either you specified an unqualified symbol, or your debugger ***
  461. *** doesn't have full symbol information. Unqualified symbol ***
  462. *** resolution is turned off by default. Please either specify a ***
  463. *** fully qualified symbol module!symbolname, or enable resolution ***
  464. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  465. *** enabling unqualified symbol resolution with network symbol ***
  466. *** server shares in the symbol path may cause the debugger to ***
  467. *** appear to hang for long periods of time when an incorrect ***
  468. *** symbol name is typed or the network symbol server is down. ***
  469. *** ***
  470. *** For some commands to work properly, your symbol path ***
  471. *** must point to .pdb files that have full type information. ***
  472. *** ***
  473. *** Certain .pdb files (such as the public OS symbols) do not ***
  474. *** contain the required information. Contact the group that ***
  475. *** provided you with these symbols if you need this command to ***
  476. *** work. ***
  477. *** ***
  478. *** Type referenced: nt!_MMPTE ***
  479. *** ***
  480. *************************************************************************
  481. TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
  482. *************************************************************************
  483. *** ***
  484. *** ***
  485. *** Either you specified an unqualified symbol, or your debugger ***
  486. *** doesn't have full symbol information. Unqualified symbol ***
  487. *** resolution is turned off by default. Please either specify a ***
  488. *** fully qualified symbol module!symbolname, or enable resolution ***
  489. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  490. *** enabling unqualified symbol resolution with network symbol ***
  491. *** server shares in the symbol path may cause the debugger to ***
  492. *** appear to hang for long periods of time when an incorrect ***
  493. *** symbol name is typed or the network symbol server is down. ***
  494. *** ***
  495. *** For some commands to work properly, your symbol path ***
  496. *** must point to .pdb files that have full type information. ***
  497. *** ***
  498. *** Certain .pdb files (such as the public OS symbols) do not ***
  499. *** contain the required information. Contact the group that ***
  500. *** provided you with these symbols if you need this command to ***
  501. *** work. ***
  502. *** ***
  503. *** Type referenced: nt!_KPRCB ***
  504. *** ***
  505. *************************************************************************
  506. *************************************************************************
  507. *** ***
  508. *** ***
  509. *** Either you specified an unqualified symbol, or your debugger ***
  510. *** doesn't have full symbol information. Unqualified symbol ***
  511. *** resolution is turned off by default. Please either specify a ***
  512. *** fully qualified symbol module!symbolname, or enable resolution ***
  513. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  514. *** enabling unqualified symbol resolution with network symbol ***
  515. *** server shares in the symbol path may cause the debugger to ***
  516. *** appear to hang for long periods of time when an incorrect ***
  517. *** symbol name is typed or the network symbol server is down. ***
  518. *** ***
  519. *** For some commands to work properly, your symbol path ***
  520. *** must point to .pdb files that have full type information. ***
  521. *** ***
  522. *** Certain .pdb files (such as the public OS symbols) do not ***
  523. *** contain the required information. Contact the group that ***
  524. *** provided you with these symbols if you need this command to ***
  525. *** work. ***
  526. *** ***
  527. *** Type referenced: nt!_KPRCB ***
  528. *** ***
  529. *************************************************************************
  530.  
  531. ADDITIONAL_DEBUG_TEXT:
  532. Use '!findthebuild' command to search for the target build information.
  533. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  534.  
  535. MODULE_NAME: nt
  536.  
  537. FAULTING_MODULE: fffff8008c278000 nt
  538.  
  539. DEBUG_FLR_IMAGE_TIMESTAMP: 4f7658cb
  540.  
  541. BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
  542.  
  543. CUSTOMER_CRASH_COUNT: 1
  544.  
  545. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  546.  
  547. CURRENT_IRQL: 0
  548.  
  549. STACK_TEXT:
  550. fffff880`027781f8 fffff800`8c43947e : 00000000`00000101 00000000`00000030 00000000`00000000 fffff880`009c0180 : nt+0x19e140
  551. fffff880`02778200 00000000`00000101 : 00000000`00000030 00000000`00000000 fffff880`009c0180 00000000`00000001 : nt+0x1c147e
  552. fffff880`02778208 00000000`00000030 : 00000000`00000000 fffff880`009c0180 00000000`00000001 fffff800`8c2261cb : 0x101
  553. fffff880`02778210 00000000`00000000 : fffff880`009c0180 00000000`00000001 fffff800`8c2261cb 00000000`00000000 : 0x30
  554.  
  555.  
  556. STACK_COMMAND: .bugcheck ; kb
  557.  
  558. FOLLOWUP_NAME: MachineOwner
  559.  
  560. IMAGE_NAME: ntoskrnl.exe
  561.  
  562. BUCKET_ID: WRONG_SYMBOLS
  563.  
  564. Followup: MachineOwner
  565. ---------
Add Comment
Please, Sign In to add comment