API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Feb 6th, 2012
191
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 79.44 KB | None | 0 0
raw download clone embed print report
  1. =================================================================================================
  2. =================================================================================================
  3. =================================================================================================
  4. =================================================================================================
  5. =================================================================================================
  6. =================================================================================================
  7. =================================================================================================
  8. =================================================================================================
  9. =================================================================================================
  10. =================================================================================================
  11.  
  12.  
  13. Microsoft (R) Windows Debugger Version 6.6.0003.5
  14. Copyright (c) Microsoft Corporation. All rights reserved.
  15.  
  16.  
  17. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\012712-34803-01.dmp]
  18. Mini Kernel Dump File: Only registers and stack trace are available
  19.  
  20. Symbol search path is: *** Invalid ***
  21. ****************************************************************************
  22. * Symbol loading may be unreliable without a symbol search path. *
  23. * Use .symfix to have the debugger choose a symbol path. *
  24. * After setting your symbol path, use .reload to refresh symbol locations. *
  25. ****************************************************************************
  26. Executable search path is:
  27. *********************************************************************
  28. * Symbols can not be loaded because symbol path is not initialized. *
  29. * *
  30. * The Symbol Path can be set by: *
  31. * using the _NT_SYMBOL_PATH environment variable. *
  32. * using the -y <symbol_path> argument when starting the debugger. *
  33. * using .sympath and .sympath+ *
  34. *********************************************************************
  35. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  36. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  37. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  38. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  39. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  40. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  41. Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`03446670
  42. Debug session time: Fri Jan 27 16:37:28.188 2012 (GMT+1)
  43. System Uptime: 0 days 0:00:34.749
  44. *********************************************************************
  45. * Symbols can not be loaded because symbol path is not initialized. *
  46. * *
  47. * The Symbol Path can be set by: *
  48. * using the _NT_SYMBOL_PATH environment variable. *
  49. * using the -y <symbol_path> argument when starting the debugger. *
  50. * using .sympath and .sympath+ *
  51. *********************************************************************
  52. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  53. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  54. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  55. Loading Kernel Symbols
  56. ..........................................................................................................................................................
  57. Loading User Symbols
  58. Loading unloaded module list
  59. ......
  60. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  61. *** WARNING: Unable to verify timestamp for stdriver64.sys
  62. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  63. *******************************************************************************
  64. * *
  65. * Bugcheck Analysis *
  66. * *
  67. *******************************************************************************
  68.  
  69. Use !analyze -v to get detailed debugging information.
  70.  
  71. BugCheck 1000007E, {ffffffffc0000005, fffff880055abe87, fffff88004b1c9d8, fffff88004b1c230}
  72.  
  73. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  74.  
  75. *************************************************************************
  76. *** ***
  77. *** ***
  78. *** Your debugger is not using the correct symbols ***
  79. *** ***
  80. *** In order for this command to work properly, your symbol path ***
  81. *** must point to .pdb files that have full type information. ***
  82. *** ***
  83. *** Certain .pdb files (such as the public OS symbols) do not ***
  84. *** contain the required information. Contact the group that ***
  85. *** provided you with these symbols if you need this command to ***
  86. *** work. ***
  87. *** ***
  88. *** Type referenced: nt!_KPRCB ***
  89. *** ***
  90. *************************************************************************
  91. *************************************************************************
  92. *** ***
  93. *** ***
  94. *** Your debugger is not using the correct symbols ***
  95. *** ***
  96. *** In order for this command to work properly, your symbol path ***
  97. *** must point to .pdb files that have full type information. ***
  98. *** ***
  99. *** Certain .pdb files (such as the public OS symbols) do not ***
  100. *** contain the required information. Contact the group that ***
  101. *** provided you with these symbols if you need this command to ***
  102. *** work. ***
  103. *** ***
  104. *** Type referenced: nt!_KPRCB ***
  105. *** ***
  106. *************************************************************************
  107. Unable to load image \SystemRoot\system32\drivers\i8042prt.sys, Win32 error 2
  108. *** WARNING: Unable to verify timestamp for i8042prt.sys
  109. *** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
  110. Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 2
  111. *** WARNING: Unable to verify timestamp for Ntfs.sys
  112. *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
  113. Probably caused by : stdriver64.sys ( stdriver64+4e87 )
  114.  
  115. Followup: MachineOwner
  116. ---------
  117.  
  118.  
  119. =================================================================================================
  120. =================================================================================================
  121. =================================================================================================
  122. =================================================================================================
  123. =================================================================================================
  124. =================================================================================================
  125. =================================================================================================
  126. =================================================================================================
  127. =================================================================================================
  128. =================================================================================================
  129.  
  130.  
  131.  
  132. Microsoft (R) Windows Debugger Version 6.6.0003.5
  133. Copyright (c) Microsoft Corporation. All rights reserved.
  134.  
  135.  
  136. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020412-24788-01.dmp]
  137. Mini Kernel Dump File: Only registers and stack trace are available
  138.  
  139. Symbol search path is: *** Invalid ***
  140. ****************************************************************************
  141. * Symbol loading may be unreliable without a symbol search path. *
  142. * Use .symfix to have the debugger choose a symbol path. *
  143. * After setting your symbol path, use .reload to refresh symbol locations. *
  144. ****************************************************************************
  145. Executable search path is:
  146. *********************************************************************
  147. * Symbols can not be loaded because symbol path is not initialized. *
  148. * *
  149. * The Symbol Path can be set by: *
  150. * using the _NT_SYMBOL_PATH environment variable. *
  151. * using the -y <symbol_path> argument when starting the debugger. *
  152. * using .sympath and .sympath+ *
  153. *********************************************************************
  154. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  155. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  156. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  157. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  158. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  159. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  160. Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348e670
  161. Debug session time: Sat Feb 4 11:35:50.090 2012 (GMT+1)
  162. System Uptime: 0 days 1:57:33.650
  163. *********************************************************************
  164. * Symbols can not be loaded because symbol path is not initialized. *
  165. * *
  166. * The Symbol Path can be set by: *
  167. * using the _NT_SYMBOL_PATH environment variable. *
  168. * using the -y <symbol_path> argument when starting the debugger. *
  169. * using .sympath and .sympath+ *
  170. *********************************************************************
  171. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  172. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  173. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  174. Loading Kernel Symbols
  175. ............................................................................................................................................................
  176. Loading User Symbols
  177. Loading unloaded module list
  178. .......
  179. *******************************************************************************
  180. * *
  181. * Bugcheck Analysis *
  182. * *
  183. *******************************************************************************
  184.  
  185. Use !analyze -v to get detailed debugging information.
  186.  
  187. BugCheck 19, {22, 0, 0, 0}
  188.  
  189. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  190.  
  191. *************************************************************************
  192. *** ***
  193. *** ***
  194. *** Your debugger is not using the correct symbols ***
  195. *** ***
  196. *** In order for this command to work properly, your symbol path ***
  197. *** must point to .pdb files that have full type information. ***
  198. *** ***
  199. *** Certain .pdb files (such as the public OS symbols) do not ***
  200. *** contain the required information. Contact the group that ***
  201. *** provided you with these symbols if you need this command to ***
  202. *** work. ***
  203. *** ***
  204. *** Type referenced: nt!_KPRCB ***
  205. *** ***
  206. *************************************************************************
  207. *************************************************************************
  208. *** ***
  209. *** ***
  210. *** Your debugger is not using the correct symbols ***
  211. *** ***
  212. *** In order for this command to work properly, your symbol path ***
  213. *** must point to .pdb files that have full type information. ***
  214. *** ***
  215. *** Certain .pdb files (such as the public OS symbols) do not ***
  216. *** contain the required information. Contact the group that ***
  217. *** provided you with these symbols if you need this command to ***
  218. *** work. ***
  219. *** ***
  220. *** Type referenced: nt!_KPRCB ***
  221. *** ***
  222. *************************************************************************
  223. Unable to load image \SystemRoot\system32\drivers\viahduaa.sys, Win32 error 2
  224. *** WARNING: Unable to verify timestamp for viahduaa.sys
  225. *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
  226. *** WARNING: Unable to verify timestamp for hal.dll
  227. *** ERROR: Module load completed but symbols could not be loaded for hal.dll
  228. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  229. *** WARNING: Unable to verify timestamp for stdriver64.sys
  230. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  231. Probably caused by : viahduaa.sys ( viahduaa+184e92 )
  232.  
  233. Followup: MachineOwner
  234. ---------
  235.  
  236. =================================================================================================
  237. =================================================================================================
  238. =================================================================================================
  239. =================================================================================================
  240. =================================================================================================
  241. =================================================================================================
  242. =================================================================================================
  243. =================================================================================================
  244. =================================================================================================
  245. =================================================================================================
  246.  
  247.  
  248.  
  249.  
  250. Microsoft (R) Windows Debugger Version 6.6.0003.5
  251. Copyright (c) Microsoft Corporation. All rights reserved.
  252.  
  253.  
  254. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-23228-01.dmp]
  255. Mini Kernel Dump File: Only registers and stack trace are available
  256.  
  257. Symbol search path is: *** Invalid ***
  258. ****************************************************************************
  259. * Symbol loading may be unreliable without a symbol search path. *
  260. * Use .symfix to have the debugger choose a symbol path. *
  261. * After setting your symbol path, use .reload to refresh symbol locations. *
  262. ****************************************************************************
  263. Executable search path is:
  264. *********************************************************************
  265. * Symbols can not be loaded because symbol path is not initialized. *
  266. * *
  267. * The Symbol Path can be set by: *
  268. * using the _NT_SYMBOL_PATH environment variable. *
  269. * using the -y <symbol_path> argument when starting the debugger. *
  270. * using .sympath and .sympath+ *
  271. *********************************************************************
  272. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  273. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  274. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  275. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  276. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  277. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  278. Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`0349c670
  279. Debug session time: Mon Feb 6 19:20:53.433 2012 (GMT+1)
  280. System Uptime: 0 days 0:28:58.869
  281. *********************************************************************
  282. * Symbols can not be loaded because symbol path is not initialized. *
  283. * *
  284. * The Symbol Path can be set by: *
  285. * using the _NT_SYMBOL_PATH environment variable. *
  286. * using the -y <symbol_path> argument when starting the debugger. *
  287. * using .sympath and .sympath+ *
  288. *********************************************************************
  289. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  290. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  291. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  292. Loading Kernel Symbols
  293. ............................................................................................................................................................
  294. Loading User Symbols
  295. Loading unloaded module list
  296. .......
  297. *******************************************************************************
  298. * *
  299. * Bugcheck Analysis *
  300. * *
  301. *******************************************************************************
  302.  
  303. Use !analyze -v to get detailed debugging information.
  304.  
  305. BugCheck 19, {22, 0, 0, 0}
  306.  
  307. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  308.  
  309. *************************************************************************
  310. *** ***
  311. *** ***
  312. *** Your debugger is not using the correct symbols ***
  313. *** ***
  314. *** In order for this command to work properly, your symbol path ***
  315. *** must point to .pdb files that have full type information. ***
  316. *** ***
  317. *** Certain .pdb files (such as the public OS symbols) do not ***
  318. *** contain the required information. Contact the group that ***
  319. *** provided you with these symbols if you need this command to ***
  320. *** work. ***
  321. *** ***
  322. *** Type referenced: nt!_KPRCB ***
  323. *** ***
  324. *************************************************************************
  325. *************************************************************************
  326. *** ***
  327. *** ***
  328. *** Your debugger is not using the correct symbols ***
  329. *** ***
  330. *** In order for this command to work properly, your symbol path ***
  331. *** must point to .pdb files that have full type information. ***
  332. *** ***
  333. *** Certain .pdb files (such as the public OS symbols) do not ***
  334. *** contain the required information. Contact the group that ***
  335. *** provided you with these symbols if you need this command to ***
  336. *** work. ***
  337. *** ***
  338. *** Type referenced: nt!_KPRCB ***
  339. *** ***
  340. *************************************************************************
  341. Unable to load image \SystemRoot\system32\drivers\viahduaa.sys, Win32 error 2
  342. *** WARNING: Unable to verify timestamp for viahduaa.sys
  343. *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
  344. *** WARNING: Unable to verify timestamp for hal.dll
  345. *** ERROR: Module load completed but symbols could not be loaded for hal.dll
  346. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  347. *** WARNING: Unable to verify timestamp for stdriver64.sys
  348. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  349. Probably caused by : viahduaa.sys ( viahduaa+184e92 )
  350.  
  351. Followup: MachineOwner
  352. ---------
  353.  
  354. =================================================================================================
  355. =================================================================================================
  356. =================================================================================================
  357. =================================================================================================
  358. =================================================================================================
  359. =================================================================================================
  360. =================================================================================================
  361. =================================================================================================
  362. =================================================================================================
  363. =================================================================================================
  364.  
  365.  
  366.  
  367. Microsoft (R) Windows Debugger Version 6.6.0003.5
  368. Copyright (c) Microsoft Corporation. All rights reserved.
  369.  
  370.  
  371. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-23821-01.dmp]
  372. Mini Kernel Dump File: Only registers and stack trace are available
  373.  
  374. Symbol search path is: *** Invalid ***
  375. ****************************************************************************
  376. * Symbol loading may be unreliable without a symbol search path. *
  377. * Use .symfix to have the debugger choose a symbol path. *
  378. * After setting your symbol path, use .reload to refresh symbol locations. *
  379. ****************************************************************************
  380. Executable search path is:
  381. *********************************************************************
  382. * Symbols can not be loaded because symbol path is not initialized. *
  383. * *
  384. * The Symbol Path can be set by: *
  385. * using the _NT_SYMBOL_PATH environment variable. *
  386. * using the -y <symbol_path> argument when starting the debugger. *
  387. * using .sympath and .sympath+ *
  388. *********************************************************************
  389. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  390. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  391. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  392. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  393. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  394. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  395. Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03458670
  396. Debug session time: Mon Feb 6 20:34:52.511 2012 (GMT+1)
  397. System Uptime: 0 days 0:10:37.072
  398. *********************************************************************
  399. * Symbols can not be loaded because symbol path is not initialized. *
  400. * *
  401. * The Symbol Path can be set by: *
  402. * using the _NT_SYMBOL_PATH environment variable. *
  403. * using the -y <symbol_path> argument when starting the debugger. *
  404. * using .sympath and .sympath+ *
  405. *********************************************************************
  406. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  407. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  408. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  409. Loading Kernel Symbols
  410. .............................................................................................................................................................
  411. Loading User Symbols
  412. Loading unloaded module list
  413. .......
  414. *******************************************************************************
  415. * *
  416. * Bugcheck Analysis *
  417. * *
  418. *******************************************************************************
  419.  
  420. Use !analyze -v to get detailed debugging information.
  421.  
  422. BugCheck C2, {7, 109b, 402000c, fffffa8005816720}
  423.  
  424. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  425.  
  426. unable to get nt!MmSpecialPoolStart
  427. unable to get nt!MmSpecialPoolEnd
  428. *************************************************************************
  429. *** ***
  430. *** ***
  431. *** Your debugger is not using the correct symbols ***
  432. *** ***
  433. *** In order for this command to work properly, your symbol path ***
  434. *** must point to .pdb files that have full type information. ***
  435. *** ***
  436. *** Certain .pdb files (such as the public OS symbols) do not ***
  437. *** contain the required information. Contact the group that ***
  438. *** provided you with these symbols if you need this command to ***
  439. *** work. ***
  440. *** ***
  441. *** Type referenced: nt!_POOL_HEADER ***
  442. *** ***
  443. *************************************************************************
  444. unable to get nt!MmPoolCodeStart
  445. unable to get nt!MmPoolCodeEnd
  446. *************************************************************************
  447. *** ***
  448. *** ***
  449. *** Your debugger is not using the correct symbols ***
  450. *** ***
  451. *** In order for this command to work properly, your symbol path ***
  452. *** must point to .pdb files that have full type information. ***
  453. *** ***
  454. *** Certain .pdb files (such as the public OS symbols) do not ***
  455. *** contain the required information. Contact the group that ***
  456. *** provided you with these symbols if you need this command to ***
  457. *** work. ***
  458. *** ***
  459. *** Type referenced: nt!_POOL_HEADER ***
  460. *** ***
  461. *************************************************************************
  462. *************************************************************************
  463. *** ***
  464. *** ***
  465. *** Your debugger is not using the correct symbols ***
  466. *** ***
  467. *** In order for this command to work properly, your symbol path ***
  468. *** must point to .pdb files that have full type information. ***
  469. *** ***
  470. *** Certain .pdb files (such as the public OS symbols) do not ***
  471. *** contain the required information. Contact the group that ***
  472. *** provided you with these symbols if you need this command to ***
  473. *** work. ***
  474. *** ***
  475. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  476. *** ***
  477. *************************************************************************
  478. Cannot get _POOL_TRACKER_BIG_PAGES type size
  479. *************************************************************************
  480. *** ***
  481. *** ***
  482. *** Your debugger is not using the correct symbols ***
  483. *** ***
  484. *** In order for this command to work properly, your symbol path ***
  485. *** must point to .pdb files that have full type information. ***
  486. *** ***
  487. *** Certain .pdb files (such as the public OS symbols) do not ***
  488. *** contain the required information. Contact the group that ***
  489. *** provided you with these symbols if you need this command to ***
  490. *** work. ***
  491. *** ***
  492. *** Type referenced: nt!_KPRCB ***
  493. *** ***
  494. *************************************************************************
  495. *************************************************************************
  496. *** ***
  497. *** ***
  498. *** Your debugger is not using the correct symbols ***
  499. *** ***
  500. *** In order for this command to work properly, your symbol path ***
  501. *** must point to .pdb files that have full type information. ***
  502. *** ***
  503. *** Certain .pdb files (such as the public OS symbols) do not ***
  504. *** contain the required information. Contact the group that ***
  505. *** provided you with these symbols if you need this command to ***
  506. *** work. ***
  507. *** ***
  508. *** Type referenced: nt!_KPRCB ***
  509. *** ***
  510. *************************************************************************
  511. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  512. *** WARNING: Unable to verify timestamp for stdriver64.sys
  513. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  514. *************************************************************************
  515. *** ***
  516. *** ***
  517. *** Your debugger is not using the correct symbols ***
  518. *** ***
  519. *** In order for this command 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!_POOL_HEADER ***
  528. *** ***
  529. *************************************************************************
  530. *************************************************************************
  531. *** ***
  532. *** ***
  533. *** Your debugger is not using the correct symbols ***
  534. *** ***
  535. *** In order for this command to work properly, your symbol path ***
  536. *** must point to .pdb files that have full type information. ***
  537. *** ***
  538. *** Certain .pdb files (such as the public OS symbols) do not ***
  539. *** contain the required information. Contact the group that ***
  540. *** provided you with these symbols if you need this command to ***
  541. *** work. ***
  542. *** ***
  543. *** Type referenced: nt!_POOL_HEADER ***
  544. *** ***
  545. *************************************************************************
  546. *************************************************************************
  547. *** ***
  548. *** ***
  549. *** Your debugger is not using the correct symbols ***
  550. *** ***
  551. *** In order for this command to work properly, your symbol path ***
  552. *** must point to .pdb files that have full type information. ***
  553. *** ***
  554. *** Certain .pdb files (such as the public OS symbols) do not ***
  555. *** contain the required information. Contact the group that ***
  556. *** provided you with these symbols if you need this command to ***
  557. *** work. ***
  558. *** ***
  559. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  560. *** ***
  561. *************************************************************************
  562. Cannot get _POOL_TRACKER_BIG_PAGES type size
  563.  
  564. Followup: MachineOwner
  565. ---------
  566.  
  567. =================================================================================================
  568. =================================================================================================
  569. =================================================================================================
  570. =================================================================================================
  571. =================================================================================================
  572. =================================================================================================
  573. =================================================================================================
  574. =================================================================================================
  575. =================================================================================================
  576. =================================================================================================
  577.  
  578.  
  579.  
  580. Microsoft (R) Windows Debugger Version 6.6.0003.5
  581. Copyright (c) Microsoft Corporation. All rights reserved.
  582.  
  583.  
  584. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-24616-01.dmp]
  585. Mini Kernel Dump File: Only registers and stack trace are available
  586.  
  587. Symbol search path is: *** Invalid ***
  588. ****************************************************************************
  589. * Symbol loading may be unreliable without a symbol search path. *
  590. * Use .symfix to have the debugger choose a symbol path. *
  591. * After setting your symbol path, use .reload to refresh symbol locations. *
  592. ****************************************************************************
  593. Executable search path is:
  594. *********************************************************************
  595. * Symbols can not be loaded because symbol path is not initialized. *
  596. * *
  597. * The Symbol Path can be set by: *
  598. * using the _NT_SYMBOL_PATH environment variable. *
  599. * using the -y <symbol_path> argument when starting the debugger. *
  600. * using .sympath and .sympath+ *
  601. *********************************************************************
  602. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  603. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  604. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  605. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  606. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  607. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  608. Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03456670
  609. Debug session time: Mon Feb 6 18:03:32.927 2012 (GMT+1)
  610. System Uptime: 0 days 0:47:25.488
  611. *********************************************************************
  612. * Symbols can not be loaded because symbol path is not initialized. *
  613. * *
  614. * The Symbol Path can be set by: *
  615. * using the _NT_SYMBOL_PATH environment variable. *
  616. * using the -y <symbol_path> argument when starting the debugger. *
  617. * using .sympath and .sympath+ *
  618. *********************************************************************
  619. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  620. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  621. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  622. Loading Kernel Symbols
  623. ............................................................................................................................................................
  624. Loading User Symbols
  625. Loading unloaded module list
  626. .......
  627. *******************************************************************************
  628. * *
  629. * Bugcheck Analysis *
  630. * *
  631. *******************************************************************************
  632.  
  633. Use !analyze -v to get detailed debugging information.
  634.  
  635. BugCheck 19, {22, 0, 0, 0}
  636.  
  637. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  638.  
  639. *************************************************************************
  640. *** ***
  641. *** ***
  642. *** Your debugger is not using the correct symbols ***
  643. *** ***
  644. *** In order for this command to work properly, your symbol path ***
  645. *** must point to .pdb files that have full type information. ***
  646. *** ***
  647. *** Certain .pdb files (such as the public OS symbols) do not ***
  648. *** contain the required information. Contact the group that ***
  649. *** provided you with these symbols if you need this command to ***
  650. *** work. ***
  651. *** ***
  652. *** Type referenced: nt!_KPRCB ***
  653. *** ***
  654. *************************************************************************
  655. *************************************************************************
  656. *** ***
  657. *** ***
  658. *** Your debugger is not using the correct symbols ***
  659. *** ***
  660. *** In order for this command to work properly, your symbol path ***
  661. *** must point to .pdb files that have full type information. ***
  662. *** ***
  663. *** Certain .pdb files (such as the public OS symbols) do not ***
  664. *** contain the required information. Contact the group that ***
  665. *** provided you with these symbols if you need this command to ***
  666. *** work. ***
  667. *** ***
  668. *** Type referenced: nt!_KPRCB ***
  669. *** ***
  670. *************************************************************************
  671. Unable to load image \SystemRoot\system32\drivers\viahduaa.sys, Win32 error 2
  672. *** WARNING: Unable to verify timestamp for viahduaa.sys
  673. *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
  674. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  675. *** WARNING: Unable to verify timestamp for stdriver64.sys
  676. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  677. Probably caused by : viahduaa.sys ( viahduaa+184e92 )
  678.  
  679. Followup: MachineOwner
  680. ---------
  681.  
  682. =================================================================================================
  683. =================================================================================================
  684. =================================================================================================
  685. =================================================================================================
  686. =================================================================================================
  687. =================================================================================================
  688. =================================================================================================
  689. =================================================================================================
  690. =================================================================================================
  691. =================================================================================================
  692.  
  693.  
  694. Microsoft (R) Windows Debugger Version 6.6.0003.5
  695. Copyright (c) Microsoft Corporation. All rights reserved.
  696.  
  697.  
  698. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-25194-01.dmp]
  699. Mini Kernel Dump File: Only registers and stack trace are available
  700.  
  701. Symbol search path is: *** Invalid ***
  702. ****************************************************************************
  703. * Symbol loading may be unreliable without a symbol search path. *
  704. * Use .symfix to have the debugger choose a symbol path. *
  705. * After setting your symbol path, use .reload to refresh symbol locations. *
  706. ****************************************************************************
  707. Executable search path is:
  708. *********************************************************************
  709. * Symbols can not be loaded because symbol path is not initialized. *
  710. * *
  711. * The Symbol Path can be set by: *
  712. * using the _NT_SYMBOL_PATH environment variable. *
  713. * using the -y <symbol_path> argument when starting the debugger. *
  714. * using .sympath and .sympath+ *
  715. *********************************************************************
  716. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  717. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  718. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  719. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  720. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  721. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  722. Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a2670
  723. Debug session time: Mon Feb 6 18:48:59.445 2012 (GMT+1)
  724. System Uptime: 0 days 0:44:57.006
  725. *********************************************************************
  726. * Symbols can not be loaded because symbol path is not initialized. *
  727. * *
  728. * The Symbol Path can be set by: *
  729. * using the _NT_SYMBOL_PATH environment variable. *
  730. * using the -y <symbol_path> argument when starting the debugger. *
  731. * using .sympath and .sympath+ *
  732. *********************************************************************
  733. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  734. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  735. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  736. Loading Kernel Symbols
  737. ............................................................................................................................................................
  738. Loading User Symbols
  739. Loading unloaded module list
  740. .......
  741. *******************************************************************************
  742. * *
  743. * Bugcheck Analysis *
  744. * *
  745. *******************************************************************************
  746.  
  747. Use !analyze -v to get detailed debugging information.
  748.  
  749. BugCheck C2, {7, 109b, 4020002, fffffa8006dea260}
  750.  
  751. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  752.  
  753. unable to get nt!MmSpecialPoolStart
  754. unable to get nt!MmSpecialPoolEnd
  755. *************************************************************************
  756. *** ***
  757. *** ***
  758. *** Your debugger is not using the correct symbols ***
  759. *** ***
  760. *** In order for this command to work properly, your symbol path ***
  761. *** must point to .pdb files that have full type information. ***
  762. *** ***
  763. *** Certain .pdb files (such as the public OS symbols) do not ***
  764. *** contain the required information. Contact the group that ***
  765. *** provided you with these symbols if you need this command to ***
  766. *** work. ***
  767. *** ***
  768. *** Type referenced: nt!_POOL_HEADER ***
  769. *** ***
  770. *************************************************************************
  771. unable to get nt!MmPoolCodeStart
  772. unable to get nt!MmPoolCodeEnd
  773. *************************************************************************
  774. *** ***
  775. *** ***
  776. *** Your debugger is not using the correct symbols ***
  777. *** ***
  778. *** In order for this command to work properly, your symbol path ***
  779. *** must point to .pdb files that have full type information. ***
  780. *** ***
  781. *** Certain .pdb files (such as the public OS symbols) do not ***
  782. *** contain the required information. Contact the group that ***
  783. *** provided you with these symbols if you need this command to ***
  784. *** work. ***
  785. *** ***
  786. *** Type referenced: nt!_POOL_HEADER ***
  787. *** ***
  788. *************************************************************************
  789. *************************************************************************
  790. *** ***
  791. *** ***
  792. *** Your debugger is not using the correct symbols ***
  793. *** ***
  794. *** In order for this command to work properly, your symbol path ***
  795. *** must point to .pdb files that have full type information. ***
  796. *** ***
  797. *** Certain .pdb files (such as the public OS symbols) do not ***
  798. *** contain the required information. Contact the group that ***
  799. *** provided you with these symbols if you need this command to ***
  800. *** work. ***
  801. *** ***
  802. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  803. *** ***
  804. *************************************************************************
  805. Cannot get _POOL_TRACKER_BIG_PAGES type size
  806. *************************************************************************
  807. *** ***
  808. *** ***
  809. *** Your debugger is not using the correct symbols ***
  810. *** ***
  811. *** In order for this command to work properly, your symbol path ***
  812. *** must point to .pdb files that have full type information. ***
  813. *** ***
  814. *** Certain .pdb files (such as the public OS symbols) do not ***
  815. *** contain the required information. Contact the group that ***
  816. *** provided you with these symbols if you need this command to ***
  817. *** work. ***
  818. *** ***
  819. *** Type referenced: nt!_KPRCB ***
  820. *** ***
  821. *************************************************************************
  822. *************************************************************************
  823. *** ***
  824. *** ***
  825. *** Your debugger is not using the correct symbols ***
  826. *** ***
  827. *** In order for this command to work properly, your symbol path ***
  828. *** must point to .pdb files that have full type information. ***
  829. *** ***
  830. *** Certain .pdb files (such as the public OS symbols) do not ***
  831. *** contain the required information. Contact the group that ***
  832. *** provided you with these symbols if you need this command to ***
  833. *** work. ***
  834. *** ***
  835. *** Type referenced: nt!_KPRCB ***
  836. *** ***
  837. *************************************************************************
  838. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  839. *** WARNING: Unable to verify timestamp for stdriver64.sys
  840. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  841. *************************************************************************
  842. *** ***
  843. *** ***
  844. *** Your debugger is not using the correct symbols ***
  845. *** ***
  846. *** In order for this command to work properly, your symbol path ***
  847. *** must point to .pdb files that have full type information. ***
  848. *** ***
  849. *** Certain .pdb files (such as the public OS symbols) do not ***
  850. *** contain the required information. Contact the group that ***
  851. *** provided you with these symbols if you need this command to ***
  852. *** work. ***
  853. *** ***
  854. *** Type referenced: nt!_POOL_HEADER ***
  855. *** ***
  856. *************************************************************************
  857. *************************************************************************
  858. *** ***
  859. *** ***
  860. *** Your debugger is not using the correct symbols ***
  861. *** ***
  862. *** In order for this command to work properly, your symbol path ***
  863. *** must point to .pdb files that have full type information. ***
  864. *** ***
  865. *** Certain .pdb files (such as the public OS symbols) do not ***
  866. *** contain the required information. Contact the group that ***
  867. *** provided you with these symbols if you need this command to ***
  868. *** work. ***
  869. *** ***
  870. *** Type referenced: nt!_POOL_HEADER ***
  871. *** ***
  872. *************************************************************************
  873. *************************************************************************
  874. *** ***
  875. *** ***
  876. *** Your debugger is not using the correct symbols ***
  877. *** ***
  878. *** In order for this command to work properly, your symbol path ***
  879. *** must point to .pdb files that have full type information. ***
  880. *** ***
  881. *** Certain .pdb files (such as the public OS symbols) do not ***
  882. *** contain the required information. Contact the group that ***
  883. *** provided you with these symbols if you need this command to ***
  884. *** work. ***
  885. *** ***
  886. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  887. *** ***
  888. *************************************************************************
  889. Cannot get _POOL_TRACKER_BIG_PAGES type size
  890.  
  891. Followup: MachineOwner
  892. ---------
  893.  
  894. =================================================================================================
  895. =================================================================================================
  896. =================================================================================================
  897. =================================================================================================
  898. =================================================================================================
  899. =================================================================================================
  900. =================================================================================================
  901. =================================================================================================
  902. =================================================================================================
  903. =================================================================================================
  904.  
  905.  
  906. Microsoft (R) Windows Debugger Version 6.6.0003.5
  907. Copyright (c) Microsoft Corporation. All rights reserved.
  908.  
  909.  
  910. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-28189-01.dmp]
  911. Mini Kernel Dump File: Only registers and stack trace are available
  912.  
  913. Symbol search path is: *** Invalid ***
  914. ****************************************************************************
  915. * Symbol loading may be unreliable without a symbol search path. *
  916. * Use .symfix to have the debugger choose a symbol path. *
  917. * After setting your symbol path, use .reload to refresh symbol locations. *
  918. ****************************************************************************
  919. Executable search path is:
  920. *********************************************************************
  921. * Symbols can not be loaded because symbol path is not initialized. *
  922. * *
  923. * The Symbol Path can be set by: *
  924. * using the _NT_SYMBOL_PATH environment variable. *
  925. * using the -y <symbol_path> argument when starting the debugger. *
  926. * using .sympath and .sympath+ *
  927. *********************************************************************
  928. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  929. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  930. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  931. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  932. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  933. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  934. Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`0349e670
  935. Debug session time: Mon Feb 6 21:02:56.122 2012 (GMT+1)
  936. System Uptime: 0 days 0:27:37.683
  937. *********************************************************************
  938. * Symbols can not be loaded because symbol path is not initialized. *
  939. * *
  940. * The Symbol Path can be set by: *
  941. * using the _NT_SYMBOL_PATH environment variable. *
  942. * using the -y <symbol_path> argument when starting the debugger. *
  943. * using .sympath and .sympath+ *
  944. *********************************************************************
  945. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  946. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  947. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  948. Loading Kernel Symbols
  949. ...........................................................................................................................................................
  950. Loading User Symbols
  951. Loading unloaded module list
  952. ........
  953. *******************************************************************************
  954. * *
  955. * Bugcheck Analysis *
  956. * *
  957. *******************************************************************************
  958.  
  959. Use !analyze -v to get detailed debugging information.
  960.  
  961. BugCheck C2, {7, 109b, 513030f, fffff8a00ed444e0}
  962.  
  963. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  964.  
  965. unable to get nt!MmSpecialPoolStart
  966. unable to get nt!MmSpecialPoolEnd
  967. *************************************************************************
  968. *** ***
  969. *** ***
  970. *** Your debugger is not using the correct symbols ***
  971. *** ***
  972. *** In order for this command to work properly, your symbol path ***
  973. *** must point to .pdb files that have full type information. ***
  974. *** ***
  975. *** Certain .pdb files (such as the public OS symbols) do not ***
  976. *** contain the required information. Contact the group that ***
  977. *** provided you with these symbols if you need this command to ***
  978. *** work. ***
  979. *** ***
  980. *** Type referenced: nt!_POOL_HEADER ***
  981. *** ***
  982. *************************************************************************
  983. unable to get nt!MmPoolCodeStart
  984. unable to get nt!MmPoolCodeEnd
  985. *************************************************************************
  986. *** ***
  987. *** ***
  988. *** Your debugger is not using the correct symbols ***
  989. *** ***
  990. *** In order for this command to work properly, your symbol path ***
  991. *** must point to .pdb files that have full type information. ***
  992. *** ***
  993. *** Certain .pdb files (such as the public OS symbols) do not ***
  994. *** contain the required information. Contact the group that ***
  995. *** provided you with these symbols if you need this command to ***
  996. *** work. ***
  997. *** ***
  998. *** Type referenced: nt!_POOL_HEADER ***
  999. *** ***
  1000. *************************************************************************
  1001. *************************************************************************
  1002. *** ***
  1003. *** ***
  1004. *** Your debugger is not using the correct symbols ***
  1005. *** ***
  1006. *** In order for this command to work properly, your symbol path ***
  1007. *** must point to .pdb files that have full type information. ***
  1008. *** ***
  1009. *** Certain .pdb files (such as the public OS symbols) do not ***
  1010. *** contain the required information. Contact the group that ***
  1011. *** provided you with these symbols if you need this command to ***
  1012. *** work. ***
  1013. *** ***
  1014. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  1015. *** ***
  1016. *************************************************************************
  1017. Cannot get _POOL_TRACKER_BIG_PAGES type size
  1018. *************************************************************************
  1019. *** ***
  1020. *** ***
  1021. *** Your debugger is not using the correct symbols ***
  1022. *** ***
  1023. *** In order for this command to work properly, your symbol path ***
  1024. *** must point to .pdb files that have full type information. ***
  1025. *** ***
  1026. *** Certain .pdb files (such as the public OS symbols) do not ***
  1027. *** contain the required information. Contact the group that ***
  1028. *** provided you with these symbols if you need this command to ***
  1029. *** work. ***
  1030. *** ***
  1031. *** Type referenced: nt!_KPRCB ***
  1032. *** ***
  1033. *************************************************************************
  1034. *************************************************************************
  1035. *** ***
  1036. *** ***
  1037. *** Your debugger is not using the correct symbols ***
  1038. *** ***
  1039. *** In order for this command to work properly, your symbol path ***
  1040. *** must point to .pdb files that have full type information. ***
  1041. *** ***
  1042. *** Certain .pdb files (such as the public OS symbols) do not ***
  1043. *** contain the required information. Contact the group that ***
  1044. *** provided you with these symbols if you need this command to ***
  1045. *** work. ***
  1046. *** ***
  1047. *** Type referenced: nt!_KPRCB ***
  1048. *** ***
  1049. *************************************************************************
  1050. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  1051. *** WARNING: Unable to verify timestamp for stdriver64.sys
  1052. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  1053. *************************************************************************
  1054. *** ***
  1055. *** ***
  1056. *** Your debugger is not using the correct symbols ***
  1057. *** ***
  1058. *** In order for this command to work properly, your symbol path ***
  1059. *** must point to .pdb files that have full type information. ***
  1060. *** ***
  1061. *** Certain .pdb files (such as the public OS symbols) do not ***
  1062. *** contain the required information. Contact the group that ***
  1063. *** provided you with these symbols if you need this command to ***
  1064. *** work. ***
  1065. *** ***
  1066. *** Type referenced: nt!_POOL_HEADER ***
  1067. *** ***
  1068. *************************************************************************
  1069. *************************************************************************
  1070. *** ***
  1071. *** ***
  1072. *** Your debugger is not using the correct symbols ***
  1073. *** ***
  1074. *** In order for this command to work properly, your symbol path ***
  1075. *** must point to .pdb files that have full type information. ***
  1076. *** ***
  1077. *** Certain .pdb files (such as the public OS symbols) do not ***
  1078. *** contain the required information. Contact the group that ***
  1079. *** provided you with these symbols if you need this command to ***
  1080. *** work. ***
  1081. *** ***
  1082. *** Type referenced: nt!_POOL_HEADER ***
  1083. *** ***
  1084. *************************************************************************
  1085. *************************************************************************
  1086. *** ***
  1087. *** ***
  1088. *** Your debugger is not using the correct symbols ***
  1089. *** ***
  1090. *** In order for this command to work properly, your symbol path ***
  1091. *** must point to .pdb files that have full type information. ***
  1092. *** ***
  1093. *** Certain .pdb files (such as the public OS symbols) do not ***
  1094. *** contain the required information. Contact the group that ***
  1095. *** provided you with these symbols if you need this command to ***
  1096. *** work. ***
  1097. *** ***
  1098. *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
  1099. *** ***
  1100. *************************************************************************
  1101. Cannot get _POOL_TRACKER_BIG_PAGES type size
  1102.  
  1103. Followup: MachineOwner
  1104. ---------
  1105.  
  1106. =================================================================================================
  1107. =================================================================================================
  1108. =================================================================================================
  1109. =================================================================================================
  1110. =================================================================================================
  1111. =================================================================================================
  1112. =================================================================================================
  1113. =================================================================================================
  1114. =================================================================================================
  1115. =================================================================================================
  1116.  
  1117.  
  1118.  
  1119. Microsoft (R) Windows Debugger Version 6.6.0003.5
  1120. Copyright (c) Microsoft Corporation. All rights reserved.
  1121.  
  1122.  
  1123. Loading Dump File [C:\Users\Adam\Desktop\pliki .dmp\pliki .dmp\020612-45099-01.dmp]
  1124. Mini Kernel Dump File: Only registers and stack trace are available
  1125.  
  1126. Symbol search path is: *** Invalid ***
  1127. ****************************************************************************
  1128. * Symbol loading may be unreliable without a symbol search path. *
  1129. * Use .symfix to have the debugger choose a symbol path. *
  1130. * After setting your symbol path, use .reload to refresh symbol locations. *
  1131. ****************************************************************************
  1132. Executable search path is:
  1133. *********************************************************************
  1134. * Symbols can not be loaded because symbol path is not initialized. *
  1135. * *
  1136. * The Symbol Path can be set by: *
  1137. * using the _NT_SYMBOL_PATH environment variable. *
  1138. * using the -y <symbol_path> argument when starting the debugger. *
  1139. * using .sympath and .sympath+ *
  1140. *********************************************************************
  1141. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  1142. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  1143. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  1144. Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  1145. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  1146. Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
  1147. Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348e670
  1148. Debug session time: Mon Feb 6 22:13:21.608 2012 (GMT+1)
  1149. System Uptime: 0 days 1:09:31.169
  1150. *********************************************************************
  1151. * Symbols can not be loaded because symbol path is not initialized. *
  1152. * *
  1153. * The Symbol Path can be set by: *
  1154. * using the _NT_SYMBOL_PATH environment variable. *
  1155. * using the -y <symbol_path> argument when starting the debugger. *
  1156. * using .sympath and .sympath+ *
  1157. *********************************************************************
  1158. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
  1159. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  1160. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  1161. Loading Kernel Symbols
  1162. .........................................................................................................................................................
  1163. Loading User Symbols
  1164. Loading unloaded module list
  1165. ..........
  1166. *******************************************************************************
  1167. * *
  1168. * Bugcheck Analysis *
  1169. * *
  1170. *******************************************************************************
  1171.  
  1172. Use !analyze -v to get detailed debugging information.
  1173.  
  1174. BugCheck 19, {22, 0, 0, 0}
  1175.  
  1176. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  1177.  
  1178. *************************************************************************
  1179. *** ***
  1180. *** ***
  1181. *** Your debugger is not using the correct symbols ***
  1182. *** ***
  1183. *** In order for this command to work properly, your symbol path ***
  1184. *** must point to .pdb files that have full type information. ***
  1185. *** ***
  1186. *** Certain .pdb files (such as the public OS symbols) do not ***
  1187. *** contain the required information. Contact the group that ***
  1188. *** provided you with these symbols if you need this command to ***
  1189. *** work. ***
  1190. *** ***
  1191. *** Type referenced: nt!_KPRCB ***
  1192. *** ***
  1193. *************************************************************************
  1194. *************************************************************************
  1195. *** ***
  1196. *** ***
  1197. *** Your debugger is not using the correct symbols ***
  1198. *** ***
  1199. *** In order for this command to work properly, your symbol path ***
  1200. *** must point to .pdb files that have full type information. ***
  1201. *** ***
  1202. *** Certain .pdb files (such as the public OS symbols) do not ***
  1203. *** contain the required information. Contact the group that ***
  1204. *** provided you with these symbols if you need this command to ***
  1205. *** work. ***
  1206. *** ***
  1207. *** Type referenced: nt!_KPRCB ***
  1208. *** ***
  1209. *************************************************************************
  1210. Unable to load image \SystemRoot\system32\drivers\viahduaa.sys, Win32 error 2
  1211. *** WARNING: Unable to verify timestamp for viahduaa.sys
  1212. *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
  1213. *** WARNING: Unable to verify timestamp for hal.dll
  1214. *** ERROR: Module load completed but symbols could not be loaded for hal.dll
  1215. Unable to load image \SystemRoot\system32\DRIVERS\stdriver64.sys, Win32 error 2
  1216. *** WARNING: Unable to verify timestamp for stdriver64.sys
  1217. *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
  1218. Probably caused by : viahduaa.sys ( viahduaa+184e92 )
  1219.  
  1220. Followup: MachineOwner
  1221. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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!