API tools faq
paste
Guest User

setup_longhorn_server_16497_x86_ASUS_7E.txt

a guest
Nov 11th, 2019
132
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.13 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5. Opened \\.\com1
  6. Waiting to reconnect...
  7. Connected to Windows Server 2008/Windows Vista 6001 x86 compatible target at (Mon Nov 11 19:23:28.078 2019 (GMT+1)), ptr64 FALSE
  8. Kernel Debugger connection established.
  9. Symbol search path is: *** Invalid ***
  10. ****************************************************************************
  11. * Symbol loading may be unreliable without a symbol search path. *
  12. * Use .symfix to have the debugger choose a symbol path. *
  13. * After setting your symbol path, use .reload to refresh symbol locations. *
  14. ****************************************************************************
  15. Executable search path is:
  16. *********************************************************************
  17. * Symbols can not be loaded because symbol path is not initialized. *
  18. * *
  19. * The Symbol Path can be set by: *
  20. * using the _NT_SYMBOL_PATH environment variable. *
  21. * using the -y <symbol_path> argument when starting the debugger. *
  22. * using .sympath and .sympath+ *
  23. *********************************************************************
  24. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
  25. Windows Server 2008/Windows Vista Kernel Version 6001 MP (1 procs) Free x86 compatible
  26. Built by: 6001.16497.x86fre.longhorn_beta3.070330-1720
  27. Machine Name:
  28. Kernel base = 0x88c00000 PsLoadedModuleList = 0x88d0f1f0
  29. System Uptime: not available
  30.  
  31. *** Fatal System Error: 0x0000007e
  32. (0xC0000005,0x88FBF1B4,0x86F44AD4,0x86F447D0)
  33.  
  34. Break instruction exception - code 80000003 (first chance)
  35.  
  36. A fatal system error has occurred.
  37. Debugger entered on first try; Bugcheck callbacks have not been invoked.
  38.  
  39. A fatal system error has occurred.
  40.  
  41. *********************************************************************
  42. * Symbols can not be loaded because symbol path is not initialized. *
  43. * *
  44. * The Symbol Path can be set by: *
  45. * using the _NT_SYMBOL_PATH environment variable. *
  46. * using the -y <symbol_path> argument when starting the debugger. *
  47. * using .sympath and .sympath+ *
  48. *********************************************************************
  49. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
  50. *******************************************************************************
  51. * *
  52. * Bugcheck Analysis *
  53. * *
  54. *******************************************************************************
  55.  
  56. Use !analyze -v to get detailed debugging information.
  57.  
  58. BugCheck 7E, {c0000005, 88fbf1b4, 86f44ad4, 86f447d0}
  59.  
  60. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  61.  
  62. *** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -
  63. *************************************************************************
  64. *** ***
  65. *** ***
  66. *** Your debugger is not using the correct symbols ***
  67. *** ***
  68. *** In order for this command to work properly, your symbol path ***
  69. *** must point to .pdb files that have full type information. ***
  70. *** ***
  71. *** Certain .pdb files (such as the public OS symbols) do not ***
  72. *** contain the required information. Contact the group that ***
  73. *** provided you with these symbols if you need this command to ***
  74. *** work. ***
  75. *** ***
  76. *** Type referenced: nt!_KPRCB ***
  77. *** ***
  78. *************************************************************************
  79. *************************************************************************
  80. *** ***
  81. *** ***
  82. *** Your debugger is not using the correct symbols ***
  83. *** ***
  84. *** In order for this command to work properly, your symbol path ***
  85. *** must point to .pdb files that have full type information. ***
  86. *** ***
  87. *** Certain .pdb files (such as the public OS symbols) do not ***
  88. *** contain the required information. Contact the group that ***
  89. *** provided you with these symbols if you need this command to ***
  90. *** work. ***
  91. *** ***
  92. *** Type referenced: nt!_KPRCB ***
  93. *** ***
  94. *************************************************************************
  95. *************************************************************************
  96. *** ***
  97. *** ***
  98. *** Your debugger is not using the correct symbols ***
  99. *** ***
  100. *** In order for this command to work properly, your symbol path ***
  101. *** must point to .pdb files that have full type information. ***
  102. *** ***
  103. *** Certain .pdb files (such as the public OS symbols) do not ***
  104. *** contain the required information. Contact the group that ***
  105. *** provided you with these symbols if you need this command to ***
  106. *** work. ***
  107. *** ***
  108. *** Type referenced: nt!_KPRCB ***
  109. *** ***
  110. *************************************************************************
  111. *********************************************************************
  112. * Symbols can not be loaded because symbol path is not initialized. *
  113. * *
  114. * The Symbol Path can be set by: *
  115. * using the _NT_SYMBOL_PATH environment variable. *
  116. * using the -y <symbol_path> argument when starting the debugger. *
  117. * using .sympath and .sympath+ *
  118. *********************************************************************
  119. *********************************************************************
  120. * Symbols can not be loaded because symbol path is not initialized. *
  121. * *
  122. * The Symbol Path can be set by: *
  123. * using the _NT_SYMBOL_PATH environment variable. *
  124. * using the -y <symbol_path> argument when starting the debugger. *
  125. * using .sympath and .sympath+ *
  126. *********************************************************************
  127. Probably caused by : ntkrpamp.exe ( nt!TmInitSystem+4bda )
  128.  
  129. Followup: MachineOwner
  130. ---------
  131.  
  132. nt!DbgBreakPointWithStatus+0x4:
  133. 88c459c8 cc int 3
  134. 0: kd> !analyze -v
  135. *******************************************************************************
  136. * *
  137. * Bugcheck Analysis *
  138. * *
  139. *******************************************************************************
  140.  
  141. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
  142. This is a very common bugcheck. Usually the exception address pinpoints
  143. the driver/function that caused the problem. Always note this address
  144. as well as the link date of the driver/image that contains this address.
  145. Arguments:
  146. Arg1: c0000005, The exception code that was not handled
  147. Arg2: 88fbf1b4, The address that the exception occurred at
  148. Arg3: 86f44ad4, Exception Record Address
  149. Arg4: 86f447d0, Context Record Address
  150.  
  151. Debugging Details:
  152. ------------------
  153.  
  154. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  155.  
  156. *************************************************************************
  157. *** ***
  158. *** ***
  159. *** Your debugger is not using the correct symbols ***
  160. *** ***
  161. *** In order for this command to work properly, your symbol path ***
  162. *** must point to .pdb files that have full type information. ***
  163. *** ***
  164. *** Certain .pdb files (such as the public OS symbols) do not ***
  165. *** contain the required information. Contact the group that ***
  166. *** provided you with these symbols if you need this command to ***
  167. *** work. ***
  168. *** ***
  169. *** Type referenced: nt!_KPRCB ***
  170. *** ***
  171. *************************************************************************
  172. *************************************************************************
  173. *** ***
  174. *** ***
  175. *** Your debugger is not using the correct symbols ***
  176. *** ***
  177. *** In order for this command to work properly, your symbol path ***
  178. *** must point to .pdb files that have full type information. ***
  179. *** ***
  180. *** Certain .pdb files (such as the public OS symbols) do not ***
  181. *** contain the required information. Contact the group that ***
  182. *** provided you with these symbols if you need this command to ***
  183. *** work. ***
  184. *** ***
  185. *** Type referenced: nt!_KPRCB ***
  186. *** ***
  187. *************************************************************************
  188. *************************************************************************
  189. *** ***
  190. *** ***
  191. *** Your debugger is not using the correct symbols ***
  192. *** ***
  193. *** In order for this command to work properly, your symbol path ***
  194. *** must point to .pdb files that have full type information. ***
  195. *** ***
  196. *** Certain .pdb files (such as the public OS symbols) do not ***
  197. *** contain the required information. Contact the group that ***
  198. *** provided you with these symbols if you need this command to ***
  199. *** work. ***
  200. *** ***
  201. *** Type referenced: nt!_KPRCB ***
  202. *** ***
  203. *************************************************************************
  204. *********************************************************************
  205. * Symbols can not be loaded because symbol path is not initialized. *
  206. * *
  207. * The Symbol Path can be set by: *
  208. * using the _NT_SYMBOL_PATH environment variable. *
  209. * using the -y <symbol_path> argument when starting the debugger. *
  210. * using .sympath and .sympath+ *
  211. *********************************************************************
  212. *********************************************************************
  213. * Symbols can not be loaded because symbol path is not initialized. *
  214. * *
  215. * The Symbol Path can be set by: *
  216. * using the _NT_SYMBOL_PATH environment variable. *
  217. * using the -y <symbol_path> argument when starting the debugger. *
  218. * using .sympath and .sympath+ *
  219. *********************************************************************
  220.  
  221. ADDITIONAL_DEBUG_TEXT:
  222. Use '!findthebuild' command to search for the target build information.
  223. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  224.  
  225. MODULE_NAME: nt
  226.  
  227. FAULTING_MODULE: 88c00000 nt
  228.  
  229. DEBUG_FLR_IMAGE_TIMESTAMP: 460dcf29
  230.  
  231. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
  232.  
  233. FAULTING_IP:
  234. hal!WRITE_PORT_BUFFER_ULONG+28
  235. 88fbf1b4 0f30 wrmsr
  236.  
  237. EXCEPTION_RECORD: 86f44ad4 -- (.exr 0xffffffff86f44ad4)
  238. ExceptionAddress: 88fbf1b4 (hal!WRITE_PORT_BUFFER_ULONG+0x00000028)
  239. ExceptionCode: c0000005 (Access violation)
  240. ExceptionFlags: 00000000
  241. NumberParameters: 0
  242.  
  243. CONTEXT: 86f447d0 -- (.cxr 0xffffffff86f447d0)
  244. eax=40000000 ebx=00000000 ecx=00000288 edx=00000000 esi=00000288 edi=00000002
  245. eip=88fbf1b4 esp=86f44b9c ebp=86f44bb4 iopl=0 nv up ei ng nz ac po cy
  246. cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210293
  247. hal!WRITE_PORT_BUFFER_ULONG+0x28:
  248. 88fbf1b4 0f30 wrmsr
  249. Resetting default scope
  250.  
  251. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  252.  
  253. BUGCHECK_STR: 0x7E
  254.  
  255. CURRENT_IRQL: 0
  256.  
  257. LAST_CONTROL_TRANSFER: from 88fb0c34 to 88fbf1b4
  258.  
  259. STACK_TEXT:
  260. WARNING: Stack unwind information not available. Following frames may be wrong.
  261. 86f44bb4 88fb0c34 82034444 00000001 00000000 hal!WRITE_PORT_BUFFER_ULONG+0x28
  262. 86f44bcc 88fc7cf8 82034444 82034444 86f44bec hal!HalBugCheckSystem+0x5d0
  263. 86f44bdc 88fc7e78 00000000 82034444 86f44bfc hal!KdComPortInUse+0x4920
  264. 86f44bec 88fc7ecb 00000000 82034444 86f44c28 hal!KdComPortInUse+0x4aa0
  265. 86f44bfc 88f4d732 00000000 82034444 00000000 hal!KdComPortInUse+0x4af3
  266. 86f44c28 88f4d48a 82034238 00000000 885ea114 nt!TmInitSystem+0x4bda
  267. 86f44c8c 88f50d47 885e72a8 81e8f0a0 81e8fd78 nt!TmInitSystem+0x4932
  268. 86f44d74 88d51fd0 86f44dc0 88df131c 885e72a8 nt!TmInitSystem+0x81ef
  269. 86f44d7c 88df131c 885e72a8 68750c1d 00000000 nt!IoConnectInterruptEx+0x294
  270. 86f44dc0 88ca821e 88d51fc3 885e72a8 00000000 nt!IoFreeMiniCompletionPacket+0x14f7
  271. 00000000 00000000 00000000 00000000 00000000 nt!PsGetCurrentThreadTeb+0x3be
  272.  
  273.  
  274. FOLLOWUP_IP:
  275. nt!TmInitSystem+4bda
  276. 88f4d732 3bc3 cmp eax,ebx
  277.  
  278. SYMBOL_STACK_INDEX: 5
  279.  
  280. SYMBOL_NAME: nt!TmInitSystem+4bda
  281.  
  282. FOLLOWUP_NAME: MachineOwner
  283.  
  284. IMAGE_NAME: ntkrpamp.exe
  285.  
  286. STACK_COMMAND: .cxr 0xffffffff86f447d0 ; kb
  287.  
  288. BUCKET_ID: WRONG_SYMBOLS
  289.  
  290. Followup: MachineOwner
  291. ---------
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!