API tools faq
paste
Guest User

Untitled

a guest
May 25th, 2013
233
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 35.19 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\052513-13328-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
  10. Executable search path is:
  11. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
  12. Windows 8 Kernel Version 9200 MP (4 procs) Free x64
  13. Product: WinNt, suite: TerminalServer SingleUserTS
  14. Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
  15. Machine Name:
  16. Kernel base = 0xfffff802`6b881000 PsLoadedModuleList = 0xfffff802`6bb4da20
  17. Debug session time: Sat May 25 19:06:27.976 2013 (UTC + 2:00)
  18. System Uptime: 2 days 1:53:24.710
  19. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
  20. Loading Kernel Symbols
  21. ...............................................................
  22. ................................................................
  23. ....................................................
  24. Loading User Symbols
  25. Loading unloaded module list
  26. ..................................................
  27. *******************************************************************************
  28. * *
  29. * Bugcheck Analysis *
  30. * *
  31. *******************************************************************************
  32.  
  33. Use !analyze -v to get detailed debugging information.
  34.  
  35. BugCheck 9F, {4, 12c, fffffa8009ac2900, fffff8026b71a950}
  36.  
  37. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  38.  
  39. *************************************************************************
  40. *** ***
  41. *** ***
  42. *** Either you specified an unqualified symbol, or your debugger ***
  43. *** doesn't have full symbol information. Unqualified symbol ***
  44. *** resolution is turned off by default. Please either specify a ***
  45. *** fully qualified symbol module!symbolname, or enable resolution ***
  46. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  47. *** enabling unqualified symbol resolution with network symbol ***
  48. *** server shares in the symbol path may cause the debugger to ***
  49. *** appear to hang for long periods of time when an incorrect ***
  50. *** symbol name is typed or the network symbol server is down. ***
  51. *** ***
  52. *** For some commands to work properly, your symbol path ***
  53. *** must point to .pdb files that have full type information. ***
  54. *** ***
  55. *** Certain .pdb files (such as the public OS symbols) do not ***
  56. *** contain the required information. Contact the group that ***
  57. *** provided you with these symbols if you need this command to ***
  58. *** work. ***
  59. *** ***
  60. *** Type referenced: NT!_ETHREAD ***
  61. *** ***
  62. *************************************************************************
  63. Can't retrieve thread context, Win32 error 0n30
  64. *************************************************************************
  65. *** ***
  66. *** ***
  67. *** Either you specified an unqualified symbol, or your debugger ***
  68. *** doesn't have full symbol information. Unqualified symbol ***
  69. *** resolution is turned off by default. Please either specify a ***
  70. *** fully qualified symbol module!symbolname, or enable resolution ***
  71. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  72. *** enabling unqualified symbol resolution with network symbol ***
  73. *** server shares in the symbol path may cause the debugger to ***
  74. *** appear to hang for long periods of time when an incorrect ***
  75. *** symbol name is typed or the network symbol server is down. ***
  76. *** ***
  77. *** For some commands to work properly, your symbol path ***
  78. *** must point to .pdb files that have full type information. ***
  79. *** ***
  80. *** Certain .pdb files (such as the public OS symbols) do not ***
  81. *** contain the required information. Contact the group that ***
  82. *** provided you with these symbols if you need this command to ***
  83. *** work. ***
  84. *** ***
  85. *** Type referenced: nt!_ETHREAD ***
  86. *** ***
  87. *************************************************************************
  88. *************************************************************************
  89. *** ***
  90. *** ***
  91. *** Either you specified an unqualified symbol, or your debugger ***
  92. *** doesn't have full symbol information. Unqualified symbol ***
  93. *** resolution is turned off by default. Please either specify a ***
  94. *** fully qualified symbol module!symbolname, or enable resolution ***
  95. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  96. *** enabling unqualified symbol resolution with network symbol ***
  97. *** server shares in the symbol path may cause the debugger to ***
  98. *** appear to hang for long periods of time when an incorrect ***
  99. *** symbol name is typed or the network symbol server is down. ***
  100. *** ***
  101. *** For some commands to work properly, your symbol path ***
  102. *** must point to .pdb files that have full type information. ***
  103. *** ***
  104. *** Certain .pdb files (such as the public OS symbols) do not ***
  105. *** contain the required information. Contact the group that ***
  106. *** provided you with these symbols if you need this command to ***
  107. *** work. ***
  108. *** ***
  109. *** Type referenced: nt!_TRIAGE_9F_PNP ***
  110. *** ***
  111. *************************************************************************
  112. *************************************************************************
  113. *** ***
  114. *** ***
  115. *** Either you specified an unqualified symbol, or your debugger ***
  116. *** doesn't have full symbol information. Unqualified symbol ***
  117. *** resolution is turned off by default. Please either specify a ***
  118. *** fully qualified symbol module!symbolname, or enable resolution ***
  119. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  120. *** enabling unqualified symbol resolution with network symbol ***
  121. *** server shares in the symbol path may cause the debugger to ***
  122. *** appear to hang for long periods of time when an incorrect ***
  123. *** symbol name is typed or the network symbol server is down. ***
  124. *** ***
  125. *** For some commands to work properly, your symbol path ***
  126. *** must point to .pdb files that have full type information. ***
  127. *** ***
  128. *** Certain .pdb files (such as the public OS symbols) do not ***
  129. *** contain the required information. Contact the group that ***
  130. *** provided you with these symbols if you need this command to ***
  131. *** work. ***
  132. *** ***
  133. *** Type referenced: nt!_KPRCB ***
  134. *** ***
  135. *************************************************************************
  136. *************************************************************************
  137. *** ***
  138. *** ***
  139. *** Either you specified an unqualified symbol, or your debugger ***
  140. *** doesn't have full symbol information. Unqualified symbol ***
  141. *** resolution is turned off by default. Please either specify a ***
  142. *** fully qualified symbol module!symbolname, or enable resolution ***
  143. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  144. *** enabling unqualified symbol resolution with network symbol ***
  145. *** server shares in the symbol path may cause the debugger to ***
  146. *** appear to hang for long periods of time when an incorrect ***
  147. *** symbol name is typed or the network symbol server is down. ***
  148. *** ***
  149. *** For some commands to work properly, your symbol path ***
  150. *** must point to .pdb files that have full type information. ***
  151. *** ***
  152. *** Certain .pdb files (such as the public OS symbols) do not ***
  153. *** contain the required information. Contact the group that ***
  154. *** provided you with these symbols if you need this command to ***
  155. *** work. ***
  156. *** ***
  157. *** Type referenced: nt!_MMPTE ***
  158. *** ***
  159. *************************************************************************
  160. *************************************************************************
  161. *** ***
  162. *** ***
  163. *** Either you specified an unqualified symbol, or your debugger ***
  164. *** doesn't have full symbol information. Unqualified symbol ***
  165. *** resolution is turned off by default. Please either specify a ***
  166. *** fully qualified symbol module!symbolname, or enable resolution ***
  167. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  168. *** enabling unqualified symbol resolution with network symbol ***
  169. *** server shares in the symbol path may cause the debugger to ***
  170. *** appear to hang for long periods of time when an incorrect ***
  171. *** symbol name is typed or the network symbol server is down. ***
  172. *** ***
  173. *** For some commands to work properly, your symbol path ***
  174. *** must point to .pdb files that have full type information. ***
  175. *** ***
  176. *** Certain .pdb files (such as the public OS symbols) do not ***
  177. *** contain the required information. Contact the group that ***
  178. *** provided you with these symbols if you need this command to ***
  179. *** work. ***
  180. *** ***
  181. *** Type referenced: nt!_MMPTE ***
  182. *** ***
  183. *************************************************************************
  184. *************************************************************************
  185. *** ***
  186. *** ***
  187. *** Either you specified an unqualified symbol, or your debugger ***
  188. *** doesn't have full symbol information. Unqualified symbol ***
  189. *** resolution is turned off by default. Please either specify a ***
  190. *** fully qualified symbol module!symbolname, or enable resolution ***
  191. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  192. *** enabling unqualified symbol resolution with network symbol ***
  193. *** server shares in the symbol path may cause the debugger to ***
  194. *** appear to hang for long periods of time when an incorrect ***
  195. *** symbol name is typed or the network symbol server is down. ***
  196. *** ***
  197. *** For some commands to work properly, your symbol path ***
  198. *** must point to .pdb files that have full type information. ***
  199. *** ***
  200. *** Certain .pdb files (such as the public OS symbols) do not ***
  201. *** contain the required information. Contact the group that ***
  202. *** provided you with these symbols if you need this command to ***
  203. *** work. ***
  204. *** ***
  205. *** Type referenced: nt!_KPRCB ***
  206. *** ***
  207. *************************************************************************
  208. *************************************************************************
  209. *** ***
  210. *** ***
  211. *** Either you specified an unqualified symbol, or your debugger ***
  212. *** doesn't have full symbol information. Unqualified symbol ***
  213. *** resolution is turned off by default. Please either specify a ***
  214. *** fully qualified symbol module!symbolname, or enable resolution ***
  215. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  216. *** enabling unqualified symbol resolution with network symbol ***
  217. *** server shares in the symbol path may cause the debugger to ***
  218. *** appear to hang for long periods of time when an incorrect ***
  219. *** symbol name is typed or the network symbol server is down. ***
  220. *** ***
  221. *** For some commands to work properly, your symbol path ***
  222. *** must point to .pdb files that have full type information. ***
  223. *** ***
  224. *** Certain .pdb files (such as the public OS symbols) do not ***
  225. *** contain the required information. Contact the group that ***
  226. *** provided you with these symbols if you need this command to ***
  227. *** work. ***
  228. *** ***
  229. *** Type referenced: nt!_KPRCB ***
  230. *** ***
  231. *************************************************************************
  232. Probably caused by : ntkrnlmp.exe
  233.  
  234. Followup: MachineOwner
  235. ---------
  236.  
  237. 0: kd> !analyze -v
  238. *******************************************************************************
  239. * *
  240. * Bugcheck Analysis *
  241. * *
  242. *******************************************************************************
  243.  
  244. DRIVER_POWER_STATE_FAILURE (9f)
  245. A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
  246. Arguments:
  247. Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
  248. subsystem.
  249. Arg2: 000000000000012c, Timeout in seconds.
  250. Arg3: fffffa8009ac2900, The thread currently holding on to the Pnp lock.
  251. Arg4: fffff8026b71a950, nt!TRIAGE_9F_PNP on Win7
  252.  
  253. Debugging Details:
  254. ------------------
  255.  
  256. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  257.  
  258. *************************************************************************
  259. *** ***
  260. *** ***
  261. *** Either you specified an unqualified symbol, or your debugger ***
  262. *** doesn't have full symbol information. Unqualified symbol ***
  263. *** resolution is turned off by default. Please either specify a ***
  264. *** fully qualified symbol module!symbolname, or enable resolution ***
  265. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  266. *** enabling unqualified symbol resolution with network symbol ***
  267. *** server shares in the symbol path may cause the debugger to ***
  268. *** appear to hang for long periods of time when an incorrect ***
  269. *** symbol name is typed or the network symbol server is down. ***
  270. *** ***
  271. *** For some commands to work properly, your symbol path ***
  272. *** must point to .pdb files that have full type information. ***
  273. *** ***
  274. *** Certain .pdb files (such as the public OS symbols) do not ***
  275. *** contain the required information. Contact the group that ***
  276. *** provided you with these symbols if you need this command to ***
  277. *** work. ***
  278. *** ***
  279. *** Type referenced: NT!_ETHREAD ***
  280. *** ***
  281. *************************************************************************
  282. Can't retrieve thread context, Win32 error 0n30
  283. *************************************************************************
  284. *** ***
  285. *** ***
  286. *** Either you specified an unqualified symbol, or your debugger ***
  287. *** doesn't have full symbol information. Unqualified symbol ***
  288. *** resolution is turned off by default. Please either specify a ***
  289. *** fully qualified symbol module!symbolname, or enable resolution ***
  290. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  291. *** enabling unqualified symbol resolution with network symbol ***
  292. *** server shares in the symbol path may cause the debugger to ***
  293. *** appear to hang for long periods of time when an incorrect ***
  294. *** symbol name is typed or the network symbol server is down. ***
  295. *** ***
  296. *** For some commands to work properly, your symbol path ***
  297. *** must point to .pdb files that have full type information. ***
  298. *** ***
  299. *** Certain .pdb files (such as the public OS symbols) do not ***
  300. *** contain the required information. Contact the group that ***
  301. *** provided you with these symbols if you need this command to ***
  302. *** work. ***
  303. *** ***
  304. *** Type referenced: nt!_ETHREAD ***
  305. *** ***
  306. *************************************************************************
  307. *************************************************************************
  308. *** ***
  309. *** ***
  310. *** Either you specified an unqualified symbol, or your debugger ***
  311. *** doesn't have full symbol information. Unqualified symbol ***
  312. *** resolution is turned off by default. Please either specify a ***
  313. *** fully qualified symbol module!symbolname, or enable resolution ***
  314. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  315. *** enabling unqualified symbol resolution with network symbol ***
  316. *** server shares in the symbol path may cause the debugger to ***
  317. *** appear to hang for long periods of time when an incorrect ***
  318. *** symbol name is typed or the network symbol server is down. ***
  319. *** ***
  320. *** For some commands to work properly, your symbol path ***
  321. *** must point to .pdb files that have full type information. ***
  322. *** ***
  323. *** Certain .pdb files (such as the public OS symbols) do not ***
  324. *** contain the required information. Contact the group that ***
  325. *** provided you with these symbols if you need this command to ***
  326. *** work. ***
  327. *** ***
  328. *** Type referenced: nt!_TRIAGE_9F_PNP ***
  329. *** ***
  330. *************************************************************************
  331. *************************************************************************
  332. *** ***
  333. *** ***
  334. *** Either you specified an unqualified symbol, or your debugger ***
  335. *** doesn't have full symbol information. Unqualified symbol ***
  336. *** resolution is turned off by default. Please either specify a ***
  337. *** fully qualified symbol module!symbolname, or enable resolution ***
  338. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  339. *** enabling unqualified symbol resolution with network symbol ***
  340. *** server shares in the symbol path may cause the debugger to ***
  341. *** appear to hang for long periods of time when an incorrect ***
  342. *** symbol name is typed or the network symbol server is down. ***
  343. *** ***
  344. *** For some commands to work properly, your symbol path ***
  345. *** must point to .pdb files that have full type information. ***
  346. *** ***
  347. *** Certain .pdb files (such as the public OS symbols) do not ***
  348. *** contain the required information. Contact the group that ***
  349. *** provided you with these symbols if you need this command to ***
  350. *** work. ***
  351. *** ***
  352. *** Type referenced: nt!_KPRCB ***
  353. *** ***
  354. *************************************************************************
  355. *************************************************************************
  356. *** ***
  357. *** ***
  358. *** Either you specified an unqualified symbol, or your debugger ***
  359. *** doesn't have full symbol information. Unqualified symbol ***
  360. *** resolution is turned off by default. Please either specify a ***
  361. *** fully qualified symbol module!symbolname, or enable resolution ***
  362. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  363. *** enabling unqualified symbol resolution with network symbol ***
  364. *** server shares in the symbol path may cause the debugger to ***
  365. *** appear to hang for long periods of time when an incorrect ***
  366. *** symbol name is typed or the network symbol server is down. ***
  367. *** ***
  368. *** For some commands to work properly, your symbol path ***
  369. *** must point to .pdb files that have full type information. ***
  370. *** ***
  371. *** Certain .pdb files (such as the public OS symbols) do not ***
  372. *** contain the required information. Contact the group that ***
  373. *** provided you with these symbols if you need this command to ***
  374. *** work. ***
  375. *** ***
  376. *** Type referenced: nt!_MMPTE ***
  377. *** ***
  378. *************************************************************************
  379. *************************************************************************
  380. *** ***
  381. *** ***
  382. *** Either you specified an unqualified symbol, or your debugger ***
  383. *** doesn't have full symbol information. Unqualified symbol ***
  384. *** resolution is turned off by default. Please either specify a ***
  385. *** fully qualified symbol module!symbolname, or enable resolution ***
  386. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  387. *** enabling unqualified symbol resolution with network symbol ***
  388. *** server shares in the symbol path may cause the debugger to ***
  389. *** appear to hang for long periods of time when an incorrect ***
  390. *** symbol name is typed or the network symbol server is down. ***
  391. *** ***
  392. *** For some commands to work properly, your symbol path ***
  393. *** must point to .pdb files that have full type information. ***
  394. *** ***
  395. *** Certain .pdb files (such as the public OS symbols) do not ***
  396. *** contain the required information. Contact the group that ***
  397. *** provided you with these symbols if you need this command to ***
  398. *** work. ***
  399. *** ***
  400. *** Type referenced: nt!_MMPTE ***
  401. *** ***
  402. *************************************************************************
  403. *************************************************************************
  404. *** ***
  405. *** ***
  406. *** Either you specified an unqualified symbol, or your debugger ***
  407. *** doesn't have full symbol information. Unqualified symbol ***
  408. *** resolution is turned off by default. Please either specify a ***
  409. *** fully qualified symbol module!symbolname, or enable resolution ***
  410. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  411. *** enabling unqualified symbol resolution with network symbol ***
  412. *** server shares in the symbol path may cause the debugger to ***
  413. *** appear to hang for long periods of time when an incorrect ***
  414. *** symbol name is typed or the network symbol server is down. ***
  415. *** ***
  416. *** For some commands to work properly, your symbol path ***
  417. *** must point to .pdb files that have full type information. ***
  418. *** ***
  419. *** Certain .pdb files (such as the public OS symbols) do not ***
  420. *** contain the required information. Contact the group that ***
  421. *** provided you with these symbols if you need this command to ***
  422. *** work. ***
  423. *** ***
  424. *** Type referenced: nt!_KPRCB ***
  425. *** ***
  426. *************************************************************************
  427. *************************************************************************
  428. *** ***
  429. *** ***
  430. *** Either you specified an unqualified symbol, or your debugger ***
  431. *** doesn't have full symbol information. Unqualified symbol ***
  432. *** resolution is turned off by default. Please either specify a ***
  433. *** fully qualified symbol module!symbolname, or enable resolution ***
  434. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  435. *** enabling unqualified symbol resolution with network symbol ***
  436. *** server shares in the symbol path may cause the debugger to ***
  437. *** appear to hang for long periods of time when an incorrect ***
  438. *** symbol name is typed or the network symbol server is down. ***
  439. *** ***
  440. *** For some commands to work properly, your symbol path ***
  441. *** must point to .pdb files that have full type information. ***
  442. *** ***
  443. *** Certain .pdb files (such as the public OS symbols) do not ***
  444. *** contain the required information. Contact the group that ***
  445. *** provided you with these symbols if you need this command to ***
  446. *** work. ***
  447. *** ***
  448. *** Type referenced: nt!_KPRCB ***
  449. *** ***
  450. *************************************************************************
  451.  
  452. ADDITIONAL_DEBUG_TEXT:
  453. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  454.  
  455. MODULE_NAME: nt
  456.  
  457. FAULTING_MODULE: fffff8026b881000 nt
  458.  
  459. DEBUG_FLR_IMAGE_TIMESTAMP: 5165e551
  460.  
  461. DRVPOWERSTATE_SUBCODE: 4
  462.  
  463. CUSTOMER_CRASH_COUNT: 1
  464.  
  465. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  466.  
  467. BUGCHECK_STR: 0x9F
  468.  
  469. CURRENT_IRQL: 0
  470.  
  471. STACK_TEXT:
  472. fffff880`1aba9fd0 fffff802`6b91e7cb : 00000000`00000001 00000000`00000000 ffffffff`00000003 00000000`00000008 : nt!KiCpuId+0xa6
  473. fffff880`1abaa110 fffff802`6b9029a8 : fffffa80`09ac2900 fffff880`1abaa5b8 00000000`00000000 00000000`00000000 : nt!KeWaitForMutexObject+0x137b
  474. fffff880`1abaa1d0 fffff880`181f547c : fffffa80`03e0c098 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x1c8
  475. fffff880`1abaa250 fffff880`181f5089 : 00000000`00000000 ffffffff`ff63c000 ffff5357`a23454ae fffff8a0`00000010 : mslldp!lldpWaitForValueToZero+0x30
  476. fffff880`1abaa280 fffff880`181f3094 : fffffa80`03e0c000 00000000`00000000 fffffa80`093ea010 00000000`00000000 : mslldp!lldpWaitForTxCompletion+0x5d
  477. fffff880`1abaa2c0 fffff880`01ce446e : 00000000`0000000f fffffa80`0437ac30 00000000`00000008 fffffa80`06e95b30 : mslldp!lldpProtNetPnPEvent+0x31c
  478. fffff880`1abaa2f0 fffff880`01ce4543 : fffffa80`093ea010 fffffa80`06e95b30 fffff880`1abaa470 fffff880`1abaa5b8 : ndis!ndisInvokeNetPnPEvent+0x42
  479. fffff880`1abaa330 fffff880`01d17988 : fffffa80`0437ac30 fffffa80`046fd1a0 fffff880`1abaa478 fffff802`6bb07110 : ndis!ndisDeliverNetPnPEventSynchronously+0x47
  480. fffff880`1abaa370 fffff880`01d178d0 : fffffa80`0437ac30 fffff880`1abaa4e0 00000000`00000008 fffffa80`046fd1a0 : ndis!ndisPnPNotifyBinding+0x84
  481. fffff880`1abaa3e0 fffff880`01ce4c70 : 00000000`00000000 fffff880`1abaa5d0 00000000`00000000 00000000`00000000 : ndis!ndisPnPNotifyAllTransports+0x3b0
  482. fffff880`1abaa580 fffff880`01d20af7 : fffffa80`046fd1a0 fffffa80`0a8c93a8 fffffa80`0b3a61e0 fffffa80`0a8c9230 : ndis!ndisPauseMiniportStack+0x94
  483. fffff880`1abaa610 fffff880`01d0539c : fffffa80`046fd1a0 fffffa80`046fd1a0 fffffa80`0ae58bf0 fffffa80`046fd050 : ndis!ndisPnPRemoveDevice+0x1f7
  484. fffff880`1abaa7a0 fffff880`01d22330 : fffffa80`0ae58bf0 fffffa80`046fd050 00000000`00000000 fffffa80`046fd100 : ndis!ndisPnPRemoveDeviceEx+0x84
  485. fffff880`1abaa7d0 fffff880`01d14887 : fffffa80`0ae58bf0 fffff880`1abaa860 fffffa80`046fd1a0 00000000`00000000 : ndis!ndisPnPIrpRemoveDevice+0xd8
  486. fffff880`1abaa830 fffff802`6bc6d99f : fffffa80`046fd001 fffffa80`046fd050 00000000`00000001 fffff802`6bb79180 : ndis!ndisPnPDispatch+0x2f8a7
  487. fffff880`1abaa890 fffff802`6bd8ada9 : 00000000`00000002 fffff880`1abaa959 fffffa80`03b8fc30 fffffa80`03b81e30 : nt!ExAllocateCacheAwareRundownProtection+0x1287
  488. fffff880`1abaa900 fffff802`6b9c9e70 : fffff8a0`0ece4010 00000000`00000000 fffffa80`03b8fc30 00000000`00000000 : nt!IoDeleteController+0x1a59
  489. fffff880`1abaa9c0 fffff802`6bd8a86e : fffffa80`03b81e30 fffffa80`03b8fc30 00000000`00000016 fffff8a0`00985501 : nt!PoFxStartDevicePowerManagement+0xafc
  490. fffff880`1abaaa10 fffff802`6bd8a798 : 00000000`00000000 00000000`00000000 fffff8a0`00985590 fffffa80`03b8fc30 : nt!IoDeleteController+0x151e
  491. fffff880`1abaaa50 fffff802`6be701bd : 00000000`00000000 fffff880`1abaabb0 fffff8a0`0b9b38d0 00000000`00000000 : nt!IoDeleteController+0x1448
  492. fffff880`1abaaab0 fffff802`6bc18319 : fffff880`00000000 00000000`00000000 fffff8a0`0f859400 fffff8a0`00000000 : nt!PcwUnregister+0x3d2cd
  493. fffff880`1abaac20 fffff802`6bc7b3e6 : fffff8a0`0ece4010 00000000`00000000 00000000`00000001 0000018d`7222f100 : nt!IoWMIRegistrationControl+0x36d
  494. fffff880`1abaac60 fffff802`6b9192b1 : fffffa80`09ac2900 fffff8a0`0b9b38d0 fffff802`6bc7b0fc fffffa80`0414c400 : nt!MmLockPagableDataSection+0x486
  495. fffff880`1abaacc0 fffff802`6b8ae045 : 00000000`00000000 00000000`00000080 fffff802`6b919170 fffffa80`09ac2900 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x181
  496. fffff880`1abaad50 fffff802`6b962766 : fffff880`02ecf180 fffffa80`09ac2900 fffffa80`0a717240 fffffa80`03b73040 : nt!RtlTimeFieldsToTime+0x291
  497. fffff880`1abaada0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlImageNtHeader+0x39e
  498.  
  499.  
  500. STACK_COMMAND: .bugcheck ; kb
  501.  
  502. FOLLOWUP_NAME: MachineOwner
  503.  
  504. IMAGE_NAME: ntkrnlmp.exe
  505.  
  506. BUCKET_ID: WRONG_SYMBOLS
  507.  
  508. Followup: MachineOwner
  509. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!