API tools faq
paste
Guest User

csm_uefi_asus_debug.txt

a guest
Oct 20th, 2019
409
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 19.23 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 (Sun Oct 20 13:09:13.578 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`01800000 PsLoadedModuleList = 0xfffff800`019d5100
  29. System Uptime: not available
  30.  
  31.  
  32. Intel Storage Driver Ver: 11.2.0.1006
  33.  
  34. KDTARGET: Refreshing KD connection
  35.  
  36. *** Fatal System Error: 0x0000000a
  37. (0xFFFFFADFCB40202A,0x0000000000000002,0x0000000000000000,0xFFFFF800018E2CAE)
  38.  
  39. Break instruction exception - code 80000003 (first chance)
  40.  
  41. A fatal system error has occurred.
  42. Debugger entered on first try; Bugcheck callbacks have not been invoked.
  43.  
  44. A fatal system error has occurred.
  45.  
  46. *********************************************************************
  47. * Symbols can not be loaded because symbol path is not initialized. *
  48. * *
  49. * The Symbol Path can be set by: *
  50. * using the _NT_SYMBOL_PATH environment variable. *
  51. * using the -y <symbol_path> argument when starting the debugger. *
  52. * using .sympath and .sympath+ *
  53. *********************************************************************
  54. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
  55. *******************************************************************************
  56. * *
  57. * Bugcheck Analysis *
  58. * *
  59. *******************************************************************************
  60.  
  61. Use !analyze -v to get detailed debugging information.
  62.  
  63. BugCheck A, {fffffadfcb40202a, 2, 0, fffff800018e2cae}
  64.  
  65. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
  66. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  67.  
  68. *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
  69. *************************************************************************
  70. *** ***
  71. *** ***
  72. *** Your debugger is not using the correct symbols ***
  73. *** ***
  74. *** In order for this command to work properly, your symbol path ***
  75. *** must point to .pdb files that have full type information. ***
  76. *** ***
  77. *** Certain .pdb files (such as the public OS symbols) do not ***
  78. *** contain the required information. Contact the group that ***
  79. *** provided you with these symbols if you need this command to ***
  80. *** work. ***
  81. *** ***
  82. *** Type referenced: nt!_KPRCB ***
  83. *** ***
  84. *************************************************************************
  85. *** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
  86. *** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
  87. *************************************************************************
  88. *** ***
  89. *** ***
  90. *** Your debugger is not using the correct symbols ***
  91. *** ***
  92. *** In order for this command to work properly, your symbol path ***
  93. *** must point to .pdb files that have full type information. ***
  94. *** ***
  95. *** Certain .pdb files (such as the public OS symbols) do not ***
  96. *** contain the required information. Contact the group that ***
  97. *** provided you with these symbols if you need this command to ***
  98. *** work. ***
  99. *** ***
  100. *** Type referenced: nt!_KPRCB ***
  101. *** ***
  102. *************************************************************************
  103. *************************************************************************
  104. *** ***
  105. *** ***
  106. *** Your debugger is not using the correct symbols ***
  107. *** ***
  108. *** In order for this command to work properly, your symbol path ***
  109. *** must point to .pdb files that have full type information. ***
  110. *** ***
  111. *** Certain .pdb files (such as the public OS symbols) do not ***
  112. *** contain the required information. Contact the group that ***
  113. *** provided you with these symbols if you need this command to ***
  114. *** work. ***
  115. *** ***
  116. *** Type referenced: nt!_KPRCB ***
  117. *** ***
  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. *********************************************************************
  128. * Symbols can not be loaded because symbol path is not initialized. *
  129. * *
  130. * The Symbol Path can be set by: *
  131. * using the _NT_SYMBOL_PATH environment variable. *
  132. * using the -y <symbol_path> argument when starting the debugger. *
  133. * using .sympath and .sympath+ *
  134. *********************************************************************
  135. Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e )
  136.  
  137. Followup: MachineOwner
  138. ---------
  139.  
  140. nt!DbgBreakPointWithStatus:
  141. fffff800`01826db0 cc int 3
  142. 0: kd> !analyze -v
  143. *******************************************************************************
  144. * *
  145. * Bugcheck Analysis *
  146. * *
  147. *******************************************************************************
  148.  
  149. IRQL_NOT_LESS_OR_EQUAL (a)
  150. An attempt was made to access a pageable (or completely invalid) address at an
  151. interrupt request level (IRQL) that is too high. This is usually
  152. caused by drivers using improper addresses.
  153. If a kernel debugger is available get the stack backtrace.
  154. Arguments:
  155. Arg1: fffffadfcb40202a, memory referenced
  156. Arg2: 0000000000000002, IRQL
  157. Arg3: 0000000000000000, bitfield :
  158. bit 0 : value 0 = read operation, 1 = write operation
  159. bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
  160. Arg4: fffff800018e2cae, address which referenced memory
  161.  
  162. Debugging Details:
  163. ------------------
  164.  
  165. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  166.  
  167. *************************************************************************
  168. *** ***
  169. *** ***
  170. *** Your debugger is not using the correct symbols ***
  171. *** ***
  172. *** In order for this command to work properly, your symbol path ***
  173. *** must point to .pdb files that have full type information. ***
  174. *** ***
  175. *** Certain .pdb files (such as the public OS symbols) do not ***
  176. *** contain the required information. Contact the group that ***
  177. *** provided you with these symbols if you need this command to ***
  178. *** work. ***
  179. *** ***
  180. *** Type referenced: nt!_KPRCB ***
  181. *** ***
  182. *************************************************************************
  183. *************************************************************************
  184. *** ***
  185. *** ***
  186. *** Your debugger is not using the correct symbols ***
  187. *** ***
  188. *** In order for this command to work properly, your symbol path ***
  189. *** must point to .pdb files that have full type information. ***
  190. *** ***
  191. *** Certain .pdb files (such as the public OS symbols) do not ***
  192. *** contain the required information. Contact the group that ***
  193. *** provided you with these symbols if you need this command to ***
  194. *** work. ***
  195. *** ***
  196. *** Type referenced: nt!_KPRCB ***
  197. *** ***
  198. *************************************************************************
  199. *************************************************************************
  200. *** ***
  201. *** ***
  202. *** Your debugger is not using the correct symbols ***
  203. *** ***
  204. *** In order for this command to work properly, your symbol path ***
  205. *** must point to .pdb files that have full type information. ***
  206. *** ***
  207. *** Certain .pdb files (such as the public OS symbols) do not ***
  208. *** contain the required information. Contact the group that ***
  209. *** provided you with these symbols if you need this command to ***
  210. *** work. ***
  211. *** ***
  212. *** Type referenced: nt!_KPRCB ***
  213. *** ***
  214. *************************************************************************
  215. *********************************************************************
  216. * Symbols can not be loaded because symbol path is not initialized. *
  217. * *
  218. * The Symbol Path can be set by: *
  219. * using the _NT_SYMBOL_PATH environment variable. *
  220. * using the -y <symbol_path> argument when starting the debugger. *
  221. * using .sympath and .sympath+ *
  222. *********************************************************************
  223. *********************************************************************
  224. * Symbols can not be loaded because symbol path is not initialized. *
  225. * *
  226. * The Symbol Path can be set by: *
  227. * using the _NT_SYMBOL_PATH environment variable. *
  228. * using the -y <symbol_path> argument when starting the debugger. *
  229. * using .sympath and .sympath+ *
  230. *********************************************************************
  231.  
  232. ADDITIONAL_DEBUG_TEXT:
  233. Use '!findthebuild' command to search for the target build information.
  234. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  235.  
  236. FAULTING_MODULE: fffff80001800000 nt
  237.  
  238. DEBUG_FLR_IMAGE_TIMESTAMP: 45d69799
  239.  
  240. READ_ADDRESS: unable to get nt!MmSpecialPoolStart
  241. unable to get nt!MmSpecialPoolEnd
  242. unable to get nt!MmPoolCodeStart
  243. unable to get nt!MmPoolCodeEnd
  244. fffffadfcb40202a
  245.  
  246. CURRENT_IRQL: 0
  247.  
  248. FAULTING_IP:
  249. nt!MmMapIoSpace+46e
  250. fffff800`018e2cae 668b4e1a mov cx,word ptr [rsi+1Ah]
  251.  
  252. DEFAULT_BUCKET_ID: DRIVER_FAULT
  253.  
  254. BUGCHECK_STR: 0xA
  255.  
  256. LAST_CONTROL_TRANSFER: from fffff800018d673e to fffff80001826db0
  257.  
  258. STACK_TEXT:
  259. fffffadf`ca789098 fffff800`018d673e : 00000000`00000000 00000000`00000000 fffffadf`cb40202a fffff800`0185669e : nt!DbgBreakPointWithStatus
  260. fffffadf`ca7890a0 fffff800`018d7d0e : fffff800`00000003 00000000`0000000a fffffadf`cb40202a 00000000`00000002 : nt!KeDisconnectInterrupt+0x48e
  261. fffffadf`ca789100 fffff800`0182ea54 : 00000000`00000300 fffffa80`000a8008 fffff980`00000002 00000000`00000002 : nt!KeDisconnectInterrupt+0x1a5e
  262. fffffadf`ca789740 fffff800`0182e674 : 00000000`0000000a fffffadf`cb40202a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx+0x104
  263. fffffadf`ca789780 fffff800`0182d607 : 00000000`00000011 fffff800`01a9534b fffffadf`00000000 fffffadf`d1f13010 : nt!ZwUnloadKey+0x2314
  264. fffffadf`ca789900 fffff800`018e2cae : 00000000`0000087b 00000000`00000000 fffffadf`cb400000 00000000`00000000 : nt!ZwUnloadKey+0x12a7
  265. fffffadf`ca789a90 fffffadf`c938d13e : fffffadf`00000001 00000000`00100000 fffffadf`00000000 fffffa80`00cd7000 : nt!MmMapIoSpace+0x46e
  266. fffffadf`ca789b60 fffffadf`c93978b3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VIDEOPRT!VideoPortSetTrappedEmulatorPorts+0x5e
  267. fffffadf`ca789ba0 fffff800`01a837c9 : fffffadf`cf36a070 fffffadf`d181c650 fffffadf`cf36a070 fffff800`01a83170 : VIDEOPRT!VideoPortCreateEvent+0xf73
  268. fffffadf`ca789cc0 fffff800`01a81164 : fffffadf`cf36a070 fffffadf`cf36a020 fffffadf`ca789ff0 00000000`00000000 : nt!ObDeleteCapturedInsertInfo+0x8c9
  269. fffffadf`ca789e70 fffff800`01a85887 : 00000000`00000000 fffffadf`ca789fe0 00000000`00000240 00000000`00000000 : nt!NtQuerySystemInformation+0x3b4
  270. fffffadf`ca789f80 fffff800`01a92e4d : 00000000`00000001 fffffadf`ca78a4e0 00000000`00000001 fffff800`018241ce : nt!ObOpenObjectByName+0x167
  271. fffffadf`ca78a170 fffff800`01a99ef7 : fffffa80`0082beb0 fffff800`0183c37e fffffa80`0082be80 00000000`000001e0 : nt!CcFastCopyRead+0x7ed
  272. fffffadf`ca78a300 fffff800`01a958f9 : 00000000`00000000 fffffa80`00000c40 fffffadf`cecf5c20 fffffadf`cecf4bf0 : nt!IoCreateFile+0xe7
  273. fffffadf`ca78a3e0 fffff800`0182e3fd : fffffadf`cecf4bf0 fffffadf`ca78a4e0 00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x49
  274. fffffadf`ca78a460 fffff800`0182e8c0 : fffff800`01a7ec67 00000000`00000000 000007ff`7c5c9620 00000000`00000000 : nt!ZwUnloadKey+0x209d
  275. fffffadf`ca78a668 fffff800`01a7ec67 : 00000000`00000000 000007ff`7c5c9620 00000000`00000000 00000000`00000001 : nt!ZwUnloadKey+0x2560
  276. fffffadf`ca78a670 fffff97f`ff008587 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IoGetDeviceObjectPointer+0x57
  277. fffffadf`ca78a700 fffff97f`ff00334d : 00000000`00000001 00000000`00000000 00000000`00000003 00000000`00000001 : win32k!EngFindImageProcAddress+0x487
  278. fffffadf`ca78a900 fffff97f`ff008d8c : fffffadf`ca78aa38 00000000`00000000 00000000`01bc8000 00000000`00000000 : win32k!EngDeleteSafeSemaphore+0x126d
  279. fffffadf`ca78a970 fffff97f`ff00bb28 : 00000000`01bc8000 00000000`00000000 00000000`00000003 00000000`00000000 : win32k!EngFindImageProcAddress+0xc8c
  280. fffffadf`ca78a9e0 fffff97f`ff00b646 : 00000000`0000006c fffffadf`ca78acf0 00000000`00000003 00000000`00000068 : win32k!EngFindImageProcAddress+0x3a28
  281. fffffadf`ca78ac20 fffff800`0182e3fd : fffffadf`000001e0 00000000`00000001 fffffadf`cecf4bf0 00000000`00000020 : win32k!EngFindImageProcAddress+0x3546
  282. fffffadf`ca78ac70 000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0 00000000`001657f0 00000000`00000003 : nt!ZwUnloadKey+0x209d
  283. 00000000`0015fbc8 000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0 00000000`00000003 00000000`00000000 : 0x7ff`7c7de86a
  284. 00000000`0015fbd0 00000000`001657f0 : 00000000`001657f0 00000000`00000003 00000000`00000000 00000000`00000000 : 0x7ff`7c7deaa9
  285. 00000000`0015fbd8 00000000`001657f0 : 00000000`00000003 00000000`00000000 00000000`00000000 00000000`00000003 : 0x1657f0
  286. 00000000`0015fbe0 00000000`00000003 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`001657f0 : 0x1657f0
  287. 00000000`0015fbe8 00000000`00000000 : 00000000`00000000 00000000`00000003 00000000`001657f0 00000000`77efa1ee : 0x3
  288.  
  289.  
  290. STACK_COMMAND: kb
  291.  
  292. FOLLOWUP_IP:
  293. VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e
  294. fffffadf`c938d13e 4c8bcb mov r9,rbx
  295.  
  296. SYMBOL_STACK_INDEX: 7
  297.  
  298. SYMBOL_NAME: VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e
  299.  
  300. FOLLOWUP_NAME: MachineOwner
  301.  
  302. MODULE_NAME: VIDEOPRT
  303.  
  304. IMAGE_NAME: VIDEOPRT.SYS
  305.  
  306. BUCKET_ID: WRONG_SYMBOLS
  307.  
  308. Followup: MachineOwner
  309. ---------
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!