API tools faq
paste
Advertisement
Guest User

legacy_asus_debug.txt

a guest
Oct 26th, 2019
331
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.35 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 2003 3790 x64 target at (Sat Oct 26 11:04:17.250 2019 (GMT+2)), ptr64 TRUE
  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 ntkrnlmp.exe -
  25. Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
  26. Built by: 3790.srv03_sp2_rtm.070216-1710
  27. Machine Name:
  28. Kernel base = 0xfffff800`01400000 PsLoadedModuleList = 0xfffff800`015d5100
  29. System Uptime: not available
  30.  
  31. *** Fatal System Error: 0x000000a5
  32. (0x0000000000000002,0xFFFFFADFD02F5790,0xFFFFFA80008CA010,0xFFFFFADFD03D7A3C)
  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 ntkrnlmp.exe -
  50. *******************************************************************************
  51. * *
  52. * Bugcheck Analysis *
  53. * *
  54. *******************************************************************************
  55.  
  56. Use !analyze -v to get detailed debugging information.
  57.  
  58. BugCheck A5, {2, fffffadfd02f5790, fffffa80008ca010, fffffadfd03d7a3c}
  59.  
  60. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  61.  
  62. *************************************************************************
  63. *** ***
  64. *** ***
  65. *** Your debugger is not using the correct symbols ***
  66. *** ***
  67. *** In order for this command to work properly, your symbol path ***
  68. *** must point to .pdb files that have full type information. ***
  69. *** ***
  70. *** Certain .pdb files (such as the public OS symbols) do not ***
  71. *** contain the required information. Contact the group that ***
  72. *** provided you with these symbols if you need this command to ***
  73. *** work. ***
  74. *** ***
  75. *** Type referenced: nt!_KPRCB ***
  76. *** ***
  77. *************************************************************************
  78. *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
  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 : ACPI.sys ( ACPI+16cd6 )
  128.  
  129. Followup: MachineOwner
  130. ---------
  131.  
  132. nt!DbgBreakPointWithStatus:
  133. fffff800`01426db0 cc int 3
  134. 0: kd> ! analyze -v
  135. *******************************************************************************
  136. * *
  137. * Bugcheck Analysis *
  138. * *
  139. *******************************************************************************
  140.  
  141. ACPI_BIOS_ERROR (a5)
  142. The ACPI Bios in the system is not fully compliant with the ACPI specification.
  143. The first value indicates where the incompatibility lies:
  144. This bug check covers a great variety of ACPI problems. If a kernel debugger
  145. is attached, use "!analyze -v". This command will analyze the precise problem,
  146. and display whatever information is most useful for debugging the specific
  147. error.
  148. Arguments:
  149. Arg1: 0000000000000002, ACPI_ROOT_PCI_RESOURCE_FAILURE
  150. ACPI could not process the resource list for the PCI root buses
  151. Arg2: fffffadfd02f5790, The ACPI Extension for the PCI bus.
  152. Arg3: fffffa80008ca010,
  153. Arg4: fffffadfd03d7a3c
  154.  
  155. Debugging Details:
  156. ------------------
  157.  
  158. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  159.  
  160. *************************************************************************
  161. *** ***
  162. *** ***
  163. *** Your debugger is not using the correct symbols ***
  164. *** ***
  165. *** In order for this command to work properly, your symbol path ***
  166. *** must point to .pdb files that have full type information. ***
  167. *** ***
  168. *** Certain .pdb files (such as the public OS symbols) do not ***
  169. *** contain the required information. Contact the group that ***
  170. *** provided you with these symbols if you need this command to ***
  171. *** work. ***
  172. *** ***
  173. *** Type referenced: nt!_KPRCB ***
  174. *** ***
  175. *************************************************************************
  176. *************************************************************************
  177. *** ***
  178. *** ***
  179. *** Your debugger is not using the correct symbols ***
  180. *** ***
  181. *** In order for this command to work properly, your symbol path ***
  182. *** must point to .pdb files that have full type information. ***
  183. *** ***
  184. *** Certain .pdb files (such as the public OS symbols) do not ***
  185. *** contain the required information. Contact the group that ***
  186. *** provided you with these symbols if you need this command to ***
  187. *** work. ***
  188. *** ***
  189. *** Type referenced: nt!_KPRCB ***
  190. *** ***
  191. *************************************************************************
  192. *************************************************************************
  193. *** ***
  194. *** ***
  195. *** Your debugger is not using the correct symbols ***
  196. *** ***
  197. *** In order for this command 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. * Symbols can not be loaded because symbol path is not initialized. *
  210. * *
  211. * The Symbol Path can be set by: *
  212. * using the _NT_SYMBOL_PATH environment variable. *
  213. * using the -y <symbol_path> argument when starting the debugger. *
  214. * using .sympath and .sympath+ *
  215. *********************************************************************
  216. *********************************************************************
  217. * Symbols can not be loaded because symbol path is not initialized. *
  218. * *
  219. * The Symbol Path can be set by: *
  220. * using the _NT_SYMBOL_PATH environment variable. *
  221. * using the -y <symbol_path> argument when starting the debugger. *
  222. * using .sympath and .sympath+ *
  223. *********************************************************************
  224.  
  225. ADDITIONAL_DEBUG_TEXT:
  226. Use '!findthebuild' command to search for the target build information.
  227. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  228.  
  229. MODULE_NAME: ACPI
  230.  
  231. FAULTING_MODULE: fffff80001400000 nt
  232.  
  233. DEBUG_FLR_IMAGE_TIMESTAMP: 45d694b4
  234.  
  235. ACPI_EXTENSION: fffffadfd02f5790 -- (!acpikd.acpiext fffffadfd02f5790)
  236.  
  237. ACPI_RESCONFLICT: fffffa80008ca010 -- (!acpiresconflict fffffa80008ca010 fffffadfd03d7a3c)
  238. Number of arguments found = 1. 2 arguments expected
  239. Usage: acpiresconflict [DeviceExtension] [IoResList] [e820Info]
  240.  
  241.  
  242. DEFAULT_BUCKET_ID: DRIVER_FAULT
  243.  
  244. BUGCHECK_STR: 0xA5
  245.  
  246. CURRENT_IRQL: 0
  247.  
  248. LAST_CONTROL_TRANSFER: from fffff800014d673e to fffff80001426db0
  249.  
  250. STACK_TEXT:
  251. fffffadf`ca80e418 fffff800`014d673e : 00000000`00000000 00000000`00000000 00000000`00000002 fffff800`0145669e : nt!DbgBreakPointWithStatus
  252. fffffadf`ca80e420 fffff800`014d7d0e : fffff800`00000003 00000000`000000a5 00000000`00000002 fffffadf`d02f5790 : nt!KeDisconnectInterrupt+0x48e
  253. fffffadf`ca80e480 fffff800`0142ea54 : fffffadf`c9e6e300 00000000`00000031 0000fadf`c9e6e46e 00000000`00000000 : nt!KeDisconnectInterrupt+0x1a5e
  254. fffffadf`ca80eac0 fffffadf`c9e4fcd6 : 00000000`000000a5 00000000`00000002 fffffadf`d02f5790 fffffa80`008ca010 : nt!KeBugCheckEx+0x104
  255. fffffadf`ca80eb00 fffffadf`c9e77ecc : fffffadf`d02f5790 fffffa80`008ca010 00000000`00000000 fffffadf`d02f5660 : ACPI+0x16cd6
  256. fffffadf`ca80eb80 fffffadf`c9e4596d : fffffadf`d02f5660 fffffadf`ca80ed28 fffffadf`d0070370 fffffadf`c9e77d20 : ACPI+0x3eecc
  257. fffffadf`ca80ec00 fffff800`0173ed04 : fffffadf`d03d91b0 fffffadf`d02f5660 fffffadf`d0070370 fffffadf`ca80ed10 : ACPI+0xc96d
  258. fffffadf`ca80ec70 fffff800`01731abb : fffffadf`d03d91b0 00000000`00000000 ffffffff`80000078 00000000`00000000 : nt!IoReportResourceUsage+0x14fb4
  259. fffffadf`ca80ece0 fffff800`01733093 : fffffadf`ca80ee20 00000000`00000002 fffffadf`d03d91b0 fffffa80`008b2110 : nt!IoReportResourceUsage+0x7d6b
  260. fffffadf`ca80eda0 fffff800`0173591b : fffffadf`d0179870 fffffadf`d03d91b0 00000000`00000000 fffffadf`d03d91b0 : nt!IoReportResourceUsage+0x9343
  261. fffffadf`ca80f140 fffff800`014cc809 : fffffadf`d0300320 fffff800`0085a8b0 fffffadf`d02fe460 fffffadf`d0300320 : nt!IoReportResourceUsage+0xbbcb
  262. fffffadf`ca80f4d0 fffff800`018329f7 : ffffffff`00000000 fffffadf`d0300320 fffff800`0085a8b0 fffffadf`d02fe490 : nt!IoTranslateBusAddress+0x1559
  263. fffffadf`ca80f560 fffff800`0182a14d : 00000000`00000000 00000000`0000fffc 00000000`00000000 00000000`0000fffc : nt!IoReportHalResourceUsage+0x2ca7
  264. fffffadf`ca80f8c0 fffff800`01828144 : fffff800`00858400 fffff800`00858400 00000000`00000003 fffffadf`d02db010 : nt!NlsMbOemCodePageTag+0x1c08d
  265. fffffadf`ca80fa50 fffff800`0170dc29 : fffffadf`d04dbbf0 fffffadf`d02dcbf0 00000000`00000080 fffffadf`d02dcbf0 : nt!NlsMbOemCodePageTag+0x1a084
  266. fffffadf`ca80fd40 fffff800`0164b972 : 6cde5f83`502367bc f3be6142`dda09cbb f104e220`0c5f3ec1 4e5f9c97`f130c41f : nt!IoVerifyPartitionTable+0x2409
  267. fffffadf`ca80fd70 fffff800`014202d6 : fffff800`015b1180 fffffadf`d02dcbf0 fffff800`015b5500 fffff800`008161e8 : nt!PsCreateSystemThread+0xa2
  268. fffffadf`ca80fdd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeQueryPriorityThread+0xa56
  269.  
  270.  
  271. STACK_COMMAND: kb
  272.  
  273. FOLLOWUP_IP:
  274. ACPI+16cd6
  275. fffffadf`c9e4fcd6 cc int 3
  276.  
  277. SYMBOL_STACK_INDEX: 4
  278.  
  279. SYMBOL_NAME: ACPI+16cd6
  280.  
  281. FOLLOWUP_NAME: MachineOwner
  282.  
  283. IMAGE_NAME: ACPI.sys
  284.  
  285. BUCKET_ID: WRONG_SYMBOLS
  286.  
  287. Followup: MachineOwner
  288. ---------
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!