kapitanluffy

Untitled

Oct 8th, 2019
275
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 113.99 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Users\Ramona\Downloads\100919-6890-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: srv*
  10. Executable search path is:
  11. Windows 10 Kernel Version 18362 MP (8 procs) Free x64
  12. Product: WinNt, suite: TerminalServer SingleUserTS
  13. Built by: 18362.10000.amd64fre.19h1_release_svc_19h2_rel.190621-1123
  14. Machine Name:
  15. Kernel base = 0xfffff800`3f400000 PsLoadedModuleList = 0xfffff800`3f847490
  16. Debug session time: Wed Oct 9 00:49:15.359 2019 (UTC + 8:00)
  17. System Uptime: 0 days 10:18:17.987
  18. Loading Kernel Symbols
  19. .
  20.  
  21. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  22. Run !sym noisy before .reload to track down problems loading symbols.
  23.  
  24. ..............................................................
  25. ................................................................
  26. ................................................................
  27. .................................
  28. Loading User Symbols
  29. Loading unloaded module list
  30. .........................
  31.  
  32. ************* Symbol Loading Error Summary **************
  33. Module name Error
  34. ntkrnlmp The system cannot find the file specified
  35.  
  36. You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
  37. You should also verify that your symbol search path (.sympath) is correct.
  38. For analysis of this file, run !analyze -v
  39. nt!KeBugCheckEx:
  40. fffff800`3f5c10a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8508`95b331c0=0000000000000050
  41. 2: kd> !analyze -v
  42. *******************************************************************************
  43. * *
  44. * Bugcheck Analysis *
  45. * *
  46. *******************************************************************************
  47.  
  48. PAGE_FAULT_IN_NONPAGED_AREA (50)
  49. Invalid system memory was referenced. This cannot be protected by try-except.
  50. Typically the address is just plain bad or it is pointing at freed memory.
  51. Arguments:
  52. Arg1: ffffae80006f56d8, memory referenced.
  53. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
  54. Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
  55. address.
  56. Arg4: 0000000000000006, (reserved)
  57.  
  58. Debugging Details:
  59. ------------------
  60.  
  61. *** WARNING: Unable to verify timestamp for bcmwl63a.sys
  62. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  63.  
  64. *************************************************************************
  65. *** ***
  66. *** ***
  67. *** Either you specified an unqualified symbol, or your debugger ***
  68. *** doesn't have full symbol information. Unqualified symbol ***
  69. *** resolution is turned off by default. Please either specify a ***
  70. *** fully qualified symbol module!symbolname, or enable resolution ***
  71. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  72. *** enabling unqualified symbol resolution with network symbol ***
  73. *** server shares in the symbol path may cause the debugger to ***
  74. *** appear to hang for long periods of time when an incorrect ***
  75. *** symbol name is typed or the network symbol server is down. ***
  76. *** ***
  77. *** For some commands to work properly, your symbol path ***
  78. *** must point to .pdb files that have full type information. ***
  79. *** ***
  80. *** Certain .pdb files (such as the public OS symbols) do not ***
  81. *** contain the required information. Contact the group that ***
  82. *** provided you with these symbols if you need this command to ***
  83. *** work. ***
  84. *** ***
  85. *** Type referenced: nt!_EPROCESS ***
  86. *** ***
  87. *************************************************************************
  88. *************************************************************************
  89. *** ***
  90. *** ***
  91. *** Either you specified an unqualified symbol, or your debugger ***
  92. *** doesn't have full symbol information. Unqualified symbol ***
  93. *** resolution is turned off by default. Please either specify a ***
  94. *** fully qualified symbol module!symbolname, or enable resolution ***
  95. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  96. *** enabling unqualified symbol resolution with network symbol ***
  97. *** server shares in the symbol path may cause the debugger to ***
  98. *** appear to hang for long periods of time when an incorrect ***
  99. *** symbol name is typed or the network symbol server is down. ***
  100. *** ***
  101. *** For some commands to work properly, your symbol path ***
  102. *** must point to .pdb files that have full type information. ***
  103. *** ***
  104. *** Certain .pdb files (such as the public OS symbols) do not ***
  105. *** contain the required information. Contact the group that ***
  106. *** provided you with these symbols if you need this command to ***
  107. *** work. ***
  108. *** ***
  109. *** Type referenced: nt!_KPRCB ***
  110. *** ***
  111. *************************************************************************
  112. *************************************************************************
  113. *** ***
  114. *** ***
  115. *** Either you specified an unqualified symbol, or your debugger ***
  116. *** doesn't have full symbol information. Unqualified symbol ***
  117. *** resolution is turned off by default. Please either specify a ***
  118. *** fully qualified symbol module!symbolname, or enable resolution ***
  119. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  120. *** enabling unqualified symbol resolution with network symbol ***
  121. *** server shares in the symbol path may cause the debugger to ***
  122. *** appear to hang for long periods of time when an incorrect ***
  123. *** symbol name is typed or the network symbol server is down. ***
  124. *** ***
  125. *** For some commands to work properly, your symbol path ***
  126. *** must point to .pdb files that have full type information. ***
  127. *** ***
  128. *** Certain .pdb files (such as the public OS symbols) do not ***
  129. *** contain the required information. Contact the group that ***
  130. *** provided you with these symbols if you need this command to ***
  131. *** work. ***
  132. *** ***
  133. *** Type referenced: nt!_KPRCB ***
  134. *** ***
  135. *************************************************************************
  136. *************************************************************************
  137. *** ***
  138. *** ***
  139. *** Either you specified an unqualified symbol, or your debugger ***
  140. *** doesn't have full symbol information. Unqualified symbol ***
  141. *** resolution is turned off by default. Please either specify a ***
  142. *** fully qualified symbol module!symbolname, or enable resolution ***
  143. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  144. *** enabling unqualified symbol resolution with network symbol ***
  145. *** server shares in the symbol path may cause the debugger to ***
  146. *** appear to hang for long periods of time when an incorrect ***
  147. *** symbol name is typed or the network symbol server is down. ***
  148. *** ***
  149. *** For some commands to work properly, your symbol path ***
  150. *** must point to .pdb files that have full type information. ***
  151. *** ***
  152. *** Certain .pdb files (such as the public OS symbols) do not ***
  153. *** contain the required information. Contact the group that ***
  154. *** provided you with these symbols if you need this command to ***
  155. *** work. ***
  156. *** ***
  157. *** Type referenced: nt!_KPRCB ***
  158. *** ***
  159. *************************************************************************
  160. *************************************************************************
  161. *** ***
  162. *** ***
  163. *** Either you specified an unqualified symbol, or your debugger ***
  164. *** doesn't have full symbol information. Unqualified symbol ***
  165. *** resolution is turned off by default. Please either specify a ***
  166. *** fully qualified symbol module!symbolname, or enable resolution ***
  167. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  168. *** enabling unqualified symbol resolution with network symbol ***
  169. *** server shares in the symbol path may cause the debugger to ***
  170. *** appear to hang for long periods of time when an incorrect ***
  171. *** symbol name is typed or the network symbol server is down. ***
  172. *** ***
  173. *** For some commands to work properly, your symbol path ***
  174. *** must point to .pdb files that have full type information. ***
  175. *** ***
  176. *** Certain .pdb files (such as the public OS symbols) do not ***
  177. *** contain the required information. Contact the group that ***
  178. *** provided you with these symbols if you need this command to ***
  179. *** work. ***
  180. *** ***
  181. *** Type referenced: nt!_KPRCB ***
  182. *** ***
  183. *************************************************************************
  184. *************************************************************************
  185. *** ***
  186. *** ***
  187. *** Either you specified an unqualified symbol, or your debugger ***
  188. *** doesn't have full symbol information. Unqualified symbol ***
  189. *** resolution is turned off by default. Please either specify a ***
  190. *** fully qualified symbol module!symbolname, or enable resolution ***
  191. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  192. *** enabling unqualified symbol resolution with network symbol ***
  193. *** server shares in the symbol path may cause the debugger to ***
  194. *** appear to hang for long periods of time when an incorrect ***
  195. *** symbol name is typed or the network symbol server is down. ***
  196. *** ***
  197. *** For some commands to work properly, your symbol path ***
  198. *** must point to .pdb files that have full type information. ***
  199. *** ***
  200. *** Certain .pdb files (such as the public OS symbols) do not ***
  201. *** contain the required information. Contact the group that ***
  202. *** provided you with these symbols if you need this command to ***
  203. *** work. ***
  204. *** ***
  205. *** Type referenced: nt!_KTHREAD ***
  206. *** ***
  207. *************************************************************************
  208. *************************************************************************
  209. *** ***
  210. *** ***
  211. *** Either you specified an unqualified symbol, or your debugger ***
  212. *** doesn't have full symbol information. Unqualified symbol ***
  213. *** resolution is turned off by default. Please either specify a ***
  214. *** fully qualified symbol module!symbolname, or enable resolution ***
  215. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  216. *** enabling unqualified symbol resolution with network symbol ***
  217. *** server shares in the symbol path may cause the debugger to ***
  218. *** appear to hang for long periods of time when an incorrect ***
  219. *** symbol name is typed or the network symbol server is down. ***
  220. *** ***
  221. *** For some commands to work properly, your symbol path ***
  222. *** must point to .pdb files that have full type information. ***
  223. *** ***
  224. *** Certain .pdb files (such as the public OS symbols) do not ***
  225. *** contain the required information. Contact the group that ***
  226. *** provided you with these symbols if you need this command to ***
  227. *** work. ***
  228. *** ***
  229. *** Type referenced: nt!_MI_SYSTEM_INFORMATION ***
  230. *** ***
  231. *************************************************************************
  232. *************************************************************************
  233. *** ***
  234. *** ***
  235. *** Either you specified an unqualified symbol, or your debugger ***
  236. *** doesn't have full symbol information. Unqualified symbol ***
  237. *** resolution is turned off by default. Please either specify a ***
  238. *** fully qualified symbol module!symbolname, or enable resolution ***
  239. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  240. *** enabling unqualified symbol resolution with network symbol ***
  241. *** server shares in the symbol path may cause the debugger to ***
  242. *** appear to hang for long periods of time when an incorrect ***
  243. *** symbol name is typed or the network symbol server is down. ***
  244. *** ***
  245. *** For some commands to work properly, your symbol path ***
  246. *** must point to .pdb files that have full type information. ***
  247. *** ***
  248. *** Certain .pdb files (such as the public OS symbols) do not ***
  249. *** contain the required information. Contact the group that ***
  250. *** provided you with these symbols if you need this command to ***
  251. *** work. ***
  252. *** ***
  253. *** Type referenced: nt!_MI_SYSTEM_INFORMATION ***
  254. *** ***
  255. *************************************************************************
  256. *************************************************************************
  257. *** ***
  258. *** ***
  259. *** Either you specified an unqualified symbol, or your debugger ***
  260. *** doesn't have full symbol information. Unqualified symbol ***
  261. *** resolution is turned off by default. Please either specify a ***
  262. *** fully qualified symbol module!symbolname, or enable resolution ***
  263. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  264. *** enabling unqualified symbol resolution with network symbol ***
  265. *** server shares in the symbol path may cause the debugger to ***
  266. *** appear to hang for long periods of time when an incorrect ***
  267. *** symbol name is typed or the network symbol server is down. ***
  268. *** ***
  269. *** For some commands to work properly, your symbol path ***
  270. *** must point to .pdb files that have full type information. ***
  271. *** ***
  272. *** Certain .pdb files (such as the public OS symbols) do not ***
  273. *** contain the required information. Contact the group that ***
  274. *** provided you with these symbols if you need this command to ***
  275. *** work. ***
  276. *** ***
  277. *** Type referenced: nt!_MMPTE ***
  278. *** ***
  279. *************************************************************************
  280. *************************************************************************
  281. *** ***
  282. *** ***
  283. *** Either you specified an unqualified symbol, or your debugger ***
  284. *** doesn't have full symbol information. Unqualified symbol ***
  285. *** resolution is turned off by default. Please either specify a ***
  286. *** fully qualified symbol module!symbolname, or enable resolution ***
  287. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  288. *** enabling unqualified symbol resolution with network symbol ***
  289. *** server shares in the symbol path may cause the debugger to ***
  290. *** appear to hang for long periods of time when an incorrect ***
  291. *** symbol name is typed or the network symbol server is down. ***
  292. *** ***
  293. *** For some commands to work properly, your symbol path ***
  294. *** must point to .pdb files that have full type information. ***
  295. *** ***
  296. *** Certain .pdb files (such as the public OS symbols) do not ***
  297. *** contain the required information. Contact the group that ***
  298. *** provided you with these symbols if you need this command to ***
  299. *** work. ***
  300. *** ***
  301. *** Type referenced: nt!_MMPTE ***
  302. *** ***
  303. *************************************************************************
  304. *** WARNING: Unable to verify checksum for win32k.sys
  305. *************************************************************************
  306. *** ***
  307. *** ***
  308. *** Either you specified an unqualified symbol, or your debugger ***
  309. *** doesn't have full symbol information. Unqualified symbol ***
  310. *** resolution is turned off by default. Please either specify a ***
  311. *** fully qualified symbol module!symbolname, or enable resolution ***
  312. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  313. *** enabling unqualified symbol resolution with network symbol ***
  314. *** server shares in the symbol path may cause the debugger to ***
  315. *** appear to hang for long periods of time when an incorrect ***
  316. *** symbol name is typed or the network symbol server is down. ***
  317. *** ***
  318. *** For some commands to work properly, your symbol path ***
  319. *** must point to .pdb files that have full type information. ***
  320. *** ***
  321. *** Certain .pdb files (such as the public OS symbols) do not ***
  322. *** contain the required information. Contact the group that ***
  323. *** provided you with these symbols if you need this command to ***
  324. *** work. ***
  325. *** ***
  326. *** Type referenced: nt!_MMPTE ***
  327. *** ***
  328. *************************************************************************
  329. *************************************************************************
  330. *** ***
  331. *** ***
  332. *** Either you specified an unqualified symbol, or your debugger ***
  333. *** doesn't have full symbol information. Unqualified symbol ***
  334. *** resolution is turned off by default. Please either specify a ***
  335. *** fully qualified symbol module!symbolname, or enable resolution ***
  336. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  337. *** enabling unqualified symbol resolution with network symbol ***
  338. *** server shares in the symbol path may cause the debugger to ***
  339. *** appear to hang for long periods of time when an incorrect ***
  340. *** symbol name is typed or the network symbol server is down. ***
  341. *** ***
  342. *** For some commands to work properly, your symbol path ***
  343. *** must point to .pdb files that have full type information. ***
  344. *** ***
  345. *** Certain .pdb files (such as the public OS symbols) do not ***
  346. *** contain the required information. Contact the group that ***
  347. *** provided you with these symbols if you need this command to ***
  348. *** work. ***
  349. *** ***
  350. *** Type referenced: nt!_MMPTE ***
  351. *** ***
  352. *************************************************************************
  353. *************************************************************************
  354. *** ***
  355. *** ***
  356. *** Either you specified an unqualified symbol, or your debugger ***
  357. *** doesn't have full symbol information. Unqualified symbol ***
  358. *** resolution is turned off by default. Please either specify a ***
  359. *** fully qualified symbol module!symbolname, or enable resolution ***
  360. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  361. *** enabling unqualified symbol resolution with network symbol ***
  362. *** server shares in the symbol path may cause the debugger to ***
  363. *** appear to hang for long periods of time when an incorrect ***
  364. *** symbol name is typed or the network symbol server is down. ***
  365. *** ***
  366. *** For some commands to work properly, your symbol path ***
  367. *** must point to .pdb files that have full type information. ***
  368. *** ***
  369. *** Certain .pdb files (such as the public OS symbols) do not ***
  370. *** contain the required information. Contact the group that ***
  371. *** provided you with these symbols if you need this command to ***
  372. *** work. ***
  373. *** ***
  374. *** Type referenced: nt!_MMPTE ***
  375. *** ***
  376. *************************************************************************
  377. *************************************************************************
  378. *** ***
  379. *** ***
  380. *** Either you specified an unqualified symbol, or your debugger ***
  381. *** doesn't have full symbol information. Unqualified symbol ***
  382. *** resolution is turned off by default. Please either specify a ***
  383. *** fully qualified symbol module!symbolname, or enable resolution ***
  384. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  385. *** enabling unqualified symbol resolution with network symbol ***
  386. *** server shares in the symbol path may cause the debugger to ***
  387. *** appear to hang for long periods of time when an incorrect ***
  388. *** symbol name is typed or the network symbol server is down. ***
  389. *** ***
  390. *** For some commands to work properly, your symbol path ***
  391. *** must point to .pdb files that have full type information. ***
  392. *** ***
  393. *** Certain .pdb files (such as the public OS symbols) do not ***
  394. *** contain the required information. Contact the group that ***
  395. *** provided you with these symbols if you need this command to ***
  396. *** work. ***
  397. *** ***
  398. *** Type referenced: nt!_MMPTE ***
  399. *** ***
  400. *************************************************************************
  401. *************************************************************************
  402. *** ***
  403. *** ***
  404. *** Either you specified an unqualified symbol, or your debugger ***
  405. *** doesn't have full symbol information. Unqualified symbol ***
  406. *** resolution is turned off by default. Please either specify a ***
  407. *** fully qualified symbol module!symbolname, or enable resolution ***
  408. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  409. *** enabling unqualified symbol resolution with network symbol ***
  410. *** server shares in the symbol path may cause the debugger to ***
  411. *** appear to hang for long periods of time when an incorrect ***
  412. *** symbol name is typed or the network symbol server is down. ***
  413. *** ***
  414. *** For some commands to work properly, your symbol path ***
  415. *** must point to .pdb files that have full type information. ***
  416. *** ***
  417. *** Certain .pdb files (such as the public OS symbols) do not ***
  418. *** contain the required information. Contact the group that ***
  419. *** provided you with these symbols if you need this command to ***
  420. *** work. ***
  421. *** ***
  422. *** Type referenced: nt!_MMPTE ***
  423. *** ***
  424. *************************************************************************
  425. *************************************************************************
  426. *** ***
  427. *** ***
  428. *** Either you specified an unqualified symbol, or your debugger ***
  429. *** doesn't have full symbol information. Unqualified symbol ***
  430. *** resolution is turned off by default. Please either specify a ***
  431. *** fully qualified symbol module!symbolname, or enable resolution ***
  432. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  433. *** enabling unqualified symbol resolution with network symbol ***
  434. *** server shares in the symbol path may cause the debugger to ***
  435. *** appear to hang for long periods of time when an incorrect ***
  436. *** symbol name is typed or the network symbol server is down. ***
  437. *** ***
  438. *** For some commands to work properly, your symbol path ***
  439. *** must point to .pdb files that have full type information. ***
  440. *** ***
  441. *** Certain .pdb files (such as the public OS symbols) do not ***
  442. *** contain the required information. Contact the group that ***
  443. *** provided you with these symbols if you need this command to ***
  444. *** work. ***
  445. *** ***
  446. *** Type referenced: nt!_MMPTE ***
  447. *** ***
  448. *************************************************************************
  449. *************************************************************************
  450. *** ***
  451. *** ***
  452. *** Either you specified an unqualified symbol, or your debugger ***
  453. *** doesn't have full symbol information. Unqualified symbol ***
  454. *** resolution is turned off by default. Please either specify a ***
  455. *** fully qualified symbol module!symbolname, or enable resolution ***
  456. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  457. *** enabling unqualified symbol resolution with network symbol ***
  458. *** server shares in the symbol path may cause the debugger to ***
  459. *** appear to hang for long periods of time when an incorrect ***
  460. *** symbol name is typed or the network symbol server is down. ***
  461. *** ***
  462. *** For some commands to work properly, your symbol path ***
  463. *** must point to .pdb files that have full type information. ***
  464. *** ***
  465. *** Certain .pdb files (such as the public OS symbols) do not ***
  466. *** contain the required information. Contact the group that ***
  467. *** provided you with these symbols if you need this command to ***
  468. *** work. ***
  469. *** ***
  470. *** Type referenced: nt!_MMPTE ***
  471. *** ***
  472. *************************************************************************
  473. *************************************************************************
  474. *** ***
  475. *** ***
  476. *** Either you specified an unqualified symbol, or your debugger ***
  477. *** doesn't have full symbol information. Unqualified symbol ***
  478. *** resolution is turned off by default. Please either specify a ***
  479. *** fully qualified symbol module!symbolname, or enable resolution ***
  480. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  481. *** enabling unqualified symbol resolution with network symbol ***
  482. *** server shares in the symbol path may cause the debugger to ***
  483. *** appear to hang for long periods of time when an incorrect ***
  484. *** symbol name is typed or the network symbol server is down. ***
  485. *** ***
  486. *** For some commands to work properly, your symbol path ***
  487. *** must point to .pdb files that have full type information. ***
  488. *** ***
  489. *** Certain .pdb files (such as the public OS symbols) do not ***
  490. *** contain the required information. Contact the group that ***
  491. *** provided you with these symbols if you need this command to ***
  492. *** work. ***
  493. *** ***
  494. *** Type referenced: nt!_MMPTE ***
  495. *** ***
  496. *************************************************************************
  497. *************************************************************************
  498. *** ***
  499. *** ***
  500. *** Either you specified an unqualified symbol, or your debugger ***
  501. *** doesn't have full symbol information. Unqualified symbol ***
  502. *** resolution is turned off by default. Please either specify a ***
  503. *** fully qualified symbol module!symbolname, or enable resolution ***
  504. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  505. *** enabling unqualified symbol resolution with network symbol ***
  506. *** server shares in the symbol path may cause the debugger to ***
  507. *** appear to hang for long periods of time when an incorrect ***
  508. *** symbol name is typed or the network symbol server is down. ***
  509. *** ***
  510. *** For some commands to work properly, your symbol path ***
  511. *** must point to .pdb files that have full type information. ***
  512. *** ***
  513. *** Certain .pdb files (such as the public OS symbols) do not ***
  514. *** contain the required information. Contact the group that ***
  515. *** provided you with these symbols if you need this command to ***
  516. *** work. ***
  517. *** ***
  518. *** Type referenced: nt!_MMPTE ***
  519. *** ***
  520. *************************************************************************
  521. *************************************************************************
  522. *** ***
  523. *** ***
  524. *** Either you specified an unqualified symbol, or your debugger ***
  525. *** doesn't have full symbol information. Unqualified symbol ***
  526. *** resolution is turned off by default. Please either specify a ***
  527. *** fully qualified symbol module!symbolname, or enable resolution ***
  528. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  529. *** enabling unqualified symbol resolution with network symbol ***
  530. *** server shares in the symbol path may cause the debugger to ***
  531. *** appear to hang for long periods of time when an incorrect ***
  532. *** symbol name is typed or the network symbol server is down. ***
  533. *** ***
  534. *** For some commands to work properly, your symbol path ***
  535. *** must point to .pdb files that have full type information. ***
  536. *** ***
  537. *** Certain .pdb files (such as the public OS symbols) do not ***
  538. *** contain the required information. Contact the group that ***
  539. *** provided you with these symbols if you need this command to ***
  540. *** work. ***
  541. *** ***
  542. *** Type referenced: nt!_MMPTE ***
  543. *** ***
  544. *************************************************************************
  545. *************************************************************************
  546. *** ***
  547. *** ***
  548. *** Either you specified an unqualified symbol, or your debugger ***
  549. *** doesn't have full symbol information. Unqualified symbol ***
  550. *** resolution is turned off by default. Please either specify a ***
  551. *** fully qualified symbol module!symbolname, or enable resolution ***
  552. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  553. *** enabling unqualified symbol resolution with network symbol ***
  554. *** server shares in the symbol path may cause the debugger to ***
  555. *** appear to hang for long periods of time when an incorrect ***
  556. *** symbol name is typed or the network symbol server is down. ***
  557. *** ***
  558. *** For some commands to work properly, your symbol path ***
  559. *** must point to .pdb files that have full type information. ***
  560. *** ***
  561. *** Certain .pdb files (such as the public OS symbols) do not ***
  562. *** contain the required information. Contact the group that ***
  563. *** provided you with these symbols if you need this command to ***
  564. *** work. ***
  565. *** ***
  566. *** Type referenced: nt!_MMPTE ***
  567. *** ***
  568. *************************************************************************
  569. *************************************************************************
  570. *** ***
  571. *** ***
  572. *** Either you specified an unqualified symbol, or your debugger ***
  573. *** doesn't have full symbol information. Unqualified symbol ***
  574. *** resolution is turned off by default. Please either specify a ***
  575. *** fully qualified symbol module!symbolname, or enable resolution ***
  576. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  577. *** enabling unqualified symbol resolution with network symbol ***
  578. *** server shares in the symbol path may cause the debugger to ***
  579. *** appear to hang for long periods of time when an incorrect ***
  580. *** symbol name is typed or the network symbol server is down. ***
  581. *** ***
  582. *** For some commands to work properly, your symbol path ***
  583. *** must point to .pdb files that have full type information. ***
  584. *** ***
  585. *** Certain .pdb files (such as the public OS symbols) do not ***
  586. *** contain the required information. Contact the group that ***
  587. *** provided you with these symbols if you need this command to ***
  588. *** work. ***
  589. *** ***
  590. *** Type referenced: nt!_MMPTE ***
  591. *** ***
  592. *************************************************************************
  593. *************************************************************************
  594. *** ***
  595. *** ***
  596. *** Either you specified an unqualified symbol, or your debugger ***
  597. *** doesn't have full symbol information. Unqualified symbol ***
  598. *** resolution is turned off by default. Please either specify a ***
  599. *** fully qualified symbol module!symbolname, or enable resolution ***
  600. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  601. *** enabling unqualified symbol resolution with network symbol ***
  602. *** server shares in the symbol path may cause the debugger to ***
  603. *** appear to hang for long periods of time when an incorrect ***
  604. *** symbol name is typed or the network symbol server is down. ***
  605. *** ***
  606. *** For some commands to work properly, your symbol path ***
  607. *** must point to .pdb files that have full type information. ***
  608. *** ***
  609. *** Certain .pdb files (such as the public OS symbols) do not ***
  610. *** contain the required information. Contact the group that ***
  611. *** provided you with these symbols if you need this command to ***
  612. *** work. ***
  613. *** ***
  614. *** Type referenced: nt!_MMPTE ***
  615. *** ***
  616. *************************************************************************
  617. *************************************************************************
  618. *** ***
  619. *** ***
  620. *** Either you specified an unqualified symbol, or your debugger ***
  621. *** doesn't have full symbol information. Unqualified symbol ***
  622. *** resolution is turned off by default. Please either specify a ***
  623. *** fully qualified symbol module!symbolname, or enable resolution ***
  624. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  625. *** enabling unqualified symbol resolution with network symbol ***
  626. *** server shares in the symbol path may cause the debugger to ***
  627. *** appear to hang for long periods of time when an incorrect ***
  628. *** symbol name is typed or the network symbol server is down. ***
  629. *** ***
  630. *** For some commands to work properly, your symbol path ***
  631. *** must point to .pdb files that have full type information. ***
  632. *** ***
  633. *** Certain .pdb files (such as the public OS symbols) do not ***
  634. *** contain the required information. Contact the group that ***
  635. *** provided you with these symbols if you need this command to ***
  636. *** work. ***
  637. *** ***
  638. *** Type referenced: nt!_MMPTE ***
  639. *** ***
  640. *************************************************************************
  641. *************************************************************************
  642. *** ***
  643. *** ***
  644. *** Either you specified an unqualified symbol, or your debugger ***
  645. *** doesn't have full symbol information. Unqualified symbol ***
  646. *** resolution is turned off by default. Please either specify a ***
  647. *** fully qualified symbol module!symbolname, or enable resolution ***
  648. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  649. *** enabling unqualified symbol resolution with network symbol ***
  650. *** server shares in the symbol path may cause the debugger to ***
  651. *** appear to hang for long periods of time when an incorrect ***
  652. *** symbol name is typed or the network symbol server is down. ***
  653. *** ***
  654. *** For some commands to work properly, your symbol path ***
  655. *** must point to .pdb files that have full type information. ***
  656. *** ***
  657. *** Certain .pdb files (such as the public OS symbols) do not ***
  658. *** contain the required information. Contact the group that ***
  659. *** provided you with these symbols if you need this command to ***
  660. *** work. ***
  661. *** ***
  662. *** Type referenced: nt!_MMPTE ***
  663. *** ***
  664. *************************************************************************
  665. *************************************************************************
  666. *** ***
  667. *** ***
  668. *** Either you specified an unqualified symbol, or your debugger ***
  669. *** doesn't have full symbol information. Unqualified symbol ***
  670. *** resolution is turned off by default. Please either specify a ***
  671. *** fully qualified symbol module!symbolname, or enable resolution ***
  672. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  673. *** enabling unqualified symbol resolution with network symbol ***
  674. *** server shares in the symbol path may cause the debugger to ***
  675. *** appear to hang for long periods of time when an incorrect ***
  676. *** symbol name is typed or the network symbol server is down. ***
  677. *** ***
  678. *** For some commands to work properly, your symbol path ***
  679. *** must point to .pdb files that have full type information. ***
  680. *** ***
  681. *** Certain .pdb files (such as the public OS symbols) do not ***
  682. *** contain the required information. Contact the group that ***
  683. *** provided you with these symbols if you need this command to ***
  684. *** work. ***
  685. *** ***
  686. *** Type referenced: nt!_MMPTE ***
  687. *** ***
  688. *************************************************************************
  689. *************************************************************************
  690. *** ***
  691. *** ***
  692. *** Either you specified an unqualified symbol, or your debugger ***
  693. *** doesn't have full symbol information. Unqualified symbol ***
  694. *** resolution is turned off by default. Please either specify a ***
  695. *** fully qualified symbol module!symbolname, or enable resolution ***
  696. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  697. *** enabling unqualified symbol resolution with network symbol ***
  698. *** server shares in the symbol path may cause the debugger to ***
  699. *** appear to hang for long periods of time when an incorrect ***
  700. *** symbol name is typed or the network symbol server is down. ***
  701. *** ***
  702. *** For some commands to work properly, your symbol path ***
  703. *** must point to .pdb files that have full type information. ***
  704. *** ***
  705. *** Certain .pdb files (such as the public OS symbols) do not ***
  706. *** contain the required information. Contact the group that ***
  707. *** provided you with these symbols if you need this command to ***
  708. *** work. ***
  709. *** ***
  710. *** Type referenced: nt!_MMPTE ***
  711. *** ***
  712. *************************************************************************
  713. *************************************************************************
  714. *** ***
  715. *** ***
  716. *** Either you specified an unqualified symbol, or your debugger ***
  717. *** doesn't have full symbol information. Unqualified symbol ***
  718. *** resolution is turned off by default. Please either specify a ***
  719. *** fully qualified symbol module!symbolname, or enable resolution ***
  720. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  721. *** enabling unqualified symbol resolution with network symbol ***
  722. *** server shares in the symbol path may cause the debugger to ***
  723. *** appear to hang for long periods of time when an incorrect ***
  724. *** symbol name is typed or the network symbol server is down. ***
  725. *** ***
  726. *** For some commands to work properly, your symbol path ***
  727. *** must point to .pdb files that have full type information. ***
  728. *** ***
  729. *** Certain .pdb files (such as the public OS symbols) do not ***
  730. *** contain the required information. Contact the group that ***
  731. *** provided you with these symbols if you need this command to ***
  732. *** work. ***
  733. *** ***
  734. *** Type referenced: nt!_MMPTE ***
  735. *** ***
  736. *************************************************************************
  737. *************************************************************************
  738. *** ***
  739. *** ***
  740. *** Either you specified an unqualified symbol, or your debugger ***
  741. *** doesn't have full symbol information. Unqualified symbol ***
  742. *** resolution is turned off by default. Please either specify a ***
  743. *** fully qualified symbol module!symbolname, or enable resolution ***
  744. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  745. *** enabling unqualified symbol resolution with network symbol ***
  746. *** server shares in the symbol path may cause the debugger to ***
  747. *** appear to hang for long periods of time when an incorrect ***
  748. *** symbol name is typed or the network symbol server is down. ***
  749. *** ***
  750. *** For some commands to work properly, your symbol path ***
  751. *** must point to .pdb files that have full type information. ***
  752. *** ***
  753. *** Certain .pdb files (such as the public OS symbols) do not ***
  754. *** contain the required information. Contact the group that ***
  755. *** provided you with these symbols if you need this command to ***
  756. *** work. ***
  757. *** ***
  758. *** Type referenced: nt!_MMPTE ***
  759. *** ***
  760. *************************************************************************
  761. *************************************************************************
  762. *** ***
  763. *** ***
  764. *** Either you specified an unqualified symbol, or your debugger ***
  765. *** doesn't have full symbol information. Unqualified symbol ***
  766. *** resolution is turned off by default. Please either specify a ***
  767. *** fully qualified symbol module!symbolname, or enable resolution ***
  768. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  769. *** enabling unqualified symbol resolution with network symbol ***
  770. *** server shares in the symbol path may cause the debugger to ***
  771. *** appear to hang for long periods of time when an incorrect ***
  772. *** symbol name is typed or the network symbol server is down. ***
  773. *** ***
  774. *** For some commands to work properly, your symbol path ***
  775. *** must point to .pdb files that have full type information. ***
  776. *** ***
  777. *** Certain .pdb files (such as the public OS symbols) do not ***
  778. *** contain the required information. Contact the group that ***
  779. *** provided you with these symbols if you need this command to ***
  780. *** work. ***
  781. *** ***
  782. *** Type referenced: nt!_MMPTE ***
  783. *** ***
  784. *************************************************************************
  785. *************************************************************************
  786. *** ***
  787. *** ***
  788. *** Either you specified an unqualified symbol, or your debugger ***
  789. *** doesn't have full symbol information. Unqualified symbol ***
  790. *** resolution is turned off by default. Please either specify a ***
  791. *** fully qualified symbol module!symbolname, or enable resolution ***
  792. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  793. *** enabling unqualified symbol resolution with network symbol ***
  794. *** server shares in the symbol path may cause the debugger to ***
  795. *** appear to hang for long periods of time when an incorrect ***
  796. *** symbol name is typed or the network symbol server is down. ***
  797. *** ***
  798. *** For some commands to work properly, your symbol path ***
  799. *** must point to .pdb files that have full type information. ***
  800. *** ***
  801. *** Certain .pdb files (such as the public OS symbols) do not ***
  802. *** contain the required information. Contact the group that ***
  803. *** provided you with these symbols if you need this command to ***
  804. *** work. ***
  805. *** ***
  806. *** Type referenced: nt!_MMPTE ***
  807. *** ***
  808. *************************************************************************
  809. *************************************************************************
  810. *** ***
  811. *** ***
  812. *** Either you specified an unqualified symbol, or your debugger ***
  813. *** doesn't have full symbol information. Unqualified symbol ***
  814. *** resolution is turned off by default. Please either specify a ***
  815. *** fully qualified symbol module!symbolname, or enable resolution ***
  816. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  817. *** enabling unqualified symbol resolution with network symbol ***
  818. *** server shares in the symbol path may cause the debugger to ***
  819. *** appear to hang for long periods of time when an incorrect ***
  820. *** symbol name is typed or the network symbol server is down. ***
  821. *** ***
  822. *** For some commands to work properly, your symbol path ***
  823. *** must point to .pdb files that have full type information. ***
  824. *** ***
  825. *** Certain .pdb files (such as the public OS symbols) do not ***
  826. *** contain the required information. Contact the group that ***
  827. *** provided you with these symbols if you need this command to ***
  828. *** work. ***
  829. *** ***
  830. *** Type referenced: nt!_MMPTE ***
  831. *** ***
  832. *************************************************************************
  833. *************************************************************************
  834. *** ***
  835. *** ***
  836. *** Either you specified an unqualified symbol, or your debugger ***
  837. *** doesn't have full symbol information. Unqualified symbol ***
  838. *** resolution is turned off by default. Please either specify a ***
  839. *** fully qualified symbol module!symbolname, or enable resolution ***
  840. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  841. *** enabling unqualified symbol resolution with network symbol ***
  842. *** server shares in the symbol path may cause the debugger to ***
  843. *** appear to hang for long periods of time when an incorrect ***
  844. *** symbol name is typed or the network symbol server is down. ***
  845. *** ***
  846. *** For some commands 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!_MMPTE ***
  855. *** ***
  856. *************************************************************************
  857. *************************************************************************
  858. *** ***
  859. *** ***
  860. *** Either you specified an unqualified symbol, or your debugger ***
  861. *** doesn't have full symbol information. Unqualified symbol ***
  862. *** resolution is turned off by default. Please either specify a ***
  863. *** fully qualified symbol module!symbolname, or enable resolution ***
  864. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  865. *** enabling unqualified symbol resolution with network symbol ***
  866. *** server shares in the symbol path may cause the debugger to ***
  867. *** appear to hang for long periods of time when an incorrect ***
  868. *** symbol name is typed or the network symbol server is down. ***
  869. *** ***
  870. *** For some commands to work properly, your symbol path ***
  871. *** must point to .pdb files that have full type information. ***
  872. *** ***
  873. *** Certain .pdb files (such as the public OS symbols) do not ***
  874. *** contain the required information. Contact the group that ***
  875. *** provided you with these symbols if you need this command to ***
  876. *** work. ***
  877. *** ***
  878. *** Type referenced: nt!_MMPTE ***
  879. *** ***
  880. *************************************************************************
  881. *************************************************************************
  882. *** ***
  883. *** ***
  884. *** Either you specified an unqualified symbol, or your debugger ***
  885. *** doesn't have full symbol information. Unqualified symbol ***
  886. *** resolution is turned off by default. Please either specify a ***
  887. *** fully qualified symbol module!symbolname, or enable resolution ***
  888. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  889. *** enabling unqualified symbol resolution with network symbol ***
  890. *** server shares in the symbol path may cause the debugger to ***
  891. *** appear to hang for long periods of time when an incorrect ***
  892. *** symbol name is typed or the network symbol server is down. ***
  893. *** ***
  894. *** For some commands to work properly, your symbol path ***
  895. *** must point to .pdb files that have full type information. ***
  896. *** ***
  897. *** Certain .pdb files (such as the public OS symbols) do not ***
  898. *** contain the required information. Contact the group that ***
  899. *** provided you with these symbols if you need this command to ***
  900. *** work. ***
  901. *** ***
  902. *** Type referenced: nt!_MMPTE ***
  903. *** ***
  904. *************************************************************************
  905. *************************************************************************
  906. *** ***
  907. *** ***
  908. *** Either you specified an unqualified symbol, or your debugger ***
  909. *** doesn't have full symbol information. Unqualified symbol ***
  910. *** resolution is turned off by default. Please either specify a ***
  911. *** fully qualified symbol module!symbolname, or enable resolution ***
  912. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  913. *** enabling unqualified symbol resolution with network symbol ***
  914. *** server shares in the symbol path may cause the debugger to ***
  915. *** appear to hang for long periods of time when an incorrect ***
  916. *** symbol name is typed or the network symbol server is down. ***
  917. *** ***
  918. *** For some commands to work properly, your symbol path ***
  919. *** must point to .pdb files that have full type information. ***
  920. *** ***
  921. *** Certain .pdb files (such as the public OS symbols) do not ***
  922. *** contain the required information. Contact the group that ***
  923. *** provided you with these symbols if you need this command to ***
  924. *** work. ***
  925. *** ***
  926. *** Type referenced: nt!_MMPTE ***
  927. *** ***
  928. *************************************************************************
  929. *************************************************************************
  930. *** ***
  931. *** ***
  932. *** Either you specified an unqualified symbol, or your debugger ***
  933. *** doesn't have full symbol information. Unqualified symbol ***
  934. *** resolution is turned off by default. Please either specify a ***
  935. *** fully qualified symbol module!symbolname, or enable resolution ***
  936. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  937. *** enabling unqualified symbol resolution with network symbol ***
  938. *** server shares in the symbol path may cause the debugger to ***
  939. *** appear to hang for long periods of time when an incorrect ***
  940. *** symbol name is typed or the network symbol server is down. ***
  941. *** ***
  942. *** For some commands to work properly, your symbol path ***
  943. *** must point to .pdb files that have full type information. ***
  944. *** ***
  945. *** Certain .pdb files (such as the public OS symbols) do not ***
  946. *** contain the required information. Contact the group that ***
  947. *** provided you with these symbols if you need this command to ***
  948. *** work. ***
  949. *** ***
  950. *** Type referenced: nt!_MMPTE ***
  951. *** ***
  952. *************************************************************************
  953. *************************************************************************
  954. *** ***
  955. *** ***
  956. *** Either you specified an unqualified symbol, or your debugger ***
  957. *** doesn't have full symbol information. Unqualified symbol ***
  958. *** resolution is turned off by default. Please either specify a ***
  959. *** fully qualified symbol module!symbolname, or enable resolution ***
  960. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  961. *** enabling unqualified symbol resolution with network symbol ***
  962. *** server shares in the symbol path may cause the debugger to ***
  963. *** appear to hang for long periods of time when an incorrect ***
  964. *** symbol name is typed or the network symbol server is down. ***
  965. *** ***
  966. *** For some commands to work properly, your symbol path ***
  967. *** must point to .pdb files that have full type information. ***
  968. *** ***
  969. *** Certain .pdb files (such as the public OS symbols) do not ***
  970. *** contain the required information. Contact the group that ***
  971. *** provided you with these symbols if you need this command to ***
  972. *** work. ***
  973. *** ***
  974. *** Type referenced: nt!_MMPTE ***
  975. *** ***
  976. *************************************************************************
  977. *************************************************************************
  978. *** ***
  979. *** ***
  980. *** Either you specified an unqualified symbol, or your debugger ***
  981. *** doesn't have full symbol information. Unqualified symbol ***
  982. *** resolution is turned off by default. Please either specify a ***
  983. *** fully qualified symbol module!symbolname, or enable resolution ***
  984. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  985. *** enabling unqualified symbol resolution with network symbol ***
  986. *** server shares in the symbol path may cause the debugger to ***
  987. *** appear to hang for long periods of time when an incorrect ***
  988. *** symbol name is typed or the network symbol server is down. ***
  989. *** ***
  990. *** For some commands 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!_MMPTE ***
  999. *** ***
  1000. *************************************************************************
  1001. *************************************************************************
  1002. *** ***
  1003. *** ***
  1004. *** Either you specified an unqualified symbol, or your debugger ***
  1005. *** doesn't have full symbol information. Unqualified symbol ***
  1006. *** resolution is turned off by default. Please either specify a ***
  1007. *** fully qualified symbol module!symbolname, or enable resolution ***
  1008. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1009. *** enabling unqualified symbol resolution with network symbol ***
  1010. *** server shares in the symbol path may cause the debugger to ***
  1011. *** appear to hang for long periods of time when an incorrect ***
  1012. *** symbol name is typed or the network symbol server is down. ***
  1013. *** ***
  1014. *** For some commands to work properly, your symbol path ***
  1015. *** must point to .pdb files that have full type information. ***
  1016. *** ***
  1017. *** Certain .pdb files (such as the public OS symbols) do not ***
  1018. *** contain the required information. Contact the group that ***
  1019. *** provided you with these symbols if you need this command to ***
  1020. *** work. ***
  1021. *** ***
  1022. *** Type referenced: nt!_MMPTE ***
  1023. *** ***
  1024. *************************************************************************
  1025. *************************************************************************
  1026. *** ***
  1027. *** ***
  1028. *** Either you specified an unqualified symbol, or your debugger ***
  1029. *** doesn't have full symbol information. Unqualified symbol ***
  1030. *** resolution is turned off by default. Please either specify a ***
  1031. *** fully qualified symbol module!symbolname, or enable resolution ***
  1032. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1033. *** enabling unqualified symbol resolution with network symbol ***
  1034. *** server shares in the symbol path may cause the debugger to ***
  1035. *** appear to hang for long periods of time when an incorrect ***
  1036. *** symbol name is typed or the network symbol server is down. ***
  1037. *** ***
  1038. *** For some commands to work properly, your symbol path ***
  1039. *** must point to .pdb files that have full type information. ***
  1040. *** ***
  1041. *** Certain .pdb files (such as the public OS symbols) do not ***
  1042. *** contain the required information. Contact the group that ***
  1043. *** provided you with these symbols if you need this command to ***
  1044. *** work. ***
  1045. *** ***
  1046. *** Type referenced: nt!_MMPTE ***
  1047. *** ***
  1048. *************************************************************************
  1049. *************************************************************************
  1050. *** ***
  1051. *** ***
  1052. *** Either you specified an unqualified symbol, or your debugger ***
  1053. *** doesn't have full symbol information. Unqualified symbol ***
  1054. *** resolution is turned off by default. Please either specify a ***
  1055. *** fully qualified symbol module!symbolname, or enable resolution ***
  1056. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1057. *** enabling unqualified symbol resolution with network symbol ***
  1058. *** server shares in the symbol path may cause the debugger to ***
  1059. *** appear to hang for long periods of time when an incorrect ***
  1060. *** symbol name is typed or the network symbol server is down. ***
  1061. *** ***
  1062. *** For some commands to work properly, your symbol path ***
  1063. *** must point to .pdb files that have full type information. ***
  1064. *** ***
  1065. *** Certain .pdb files (such as the public OS symbols) do not ***
  1066. *** contain the required information. Contact the group that ***
  1067. *** provided you with these symbols if you need this command to ***
  1068. *** work. ***
  1069. *** ***
  1070. *** Type referenced: nt!_MMPTE ***
  1071. *** ***
  1072. *************************************************************************
  1073. *************************************************************************
  1074. *** ***
  1075. *** ***
  1076. *** Either you specified an unqualified symbol, or your debugger ***
  1077. *** doesn't have full symbol information. Unqualified symbol ***
  1078. *** resolution is turned off by default. Please either specify a ***
  1079. *** fully qualified symbol module!symbolname, or enable resolution ***
  1080. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1081. *** enabling unqualified symbol resolution with network symbol ***
  1082. *** server shares in the symbol path may cause the debugger to ***
  1083. *** appear to hang for long periods of time when an incorrect ***
  1084. *** symbol name is typed or the network symbol server is down. ***
  1085. *** ***
  1086. *** For some commands to work properly, your symbol path ***
  1087. *** must point to .pdb files that have full type information. ***
  1088. *** ***
  1089. *** Certain .pdb files (such as the public OS symbols) do not ***
  1090. *** contain the required information. Contact the group that ***
  1091. *** provided you with these symbols if you need this command to ***
  1092. *** work. ***
  1093. *** ***
  1094. *** Type referenced: nt!_MMPTE ***
  1095. *** ***
  1096. *************************************************************************
  1097. *************************************************************************
  1098. *** ***
  1099. *** ***
  1100. *** Either you specified an unqualified symbol, or your debugger ***
  1101. *** doesn't have full symbol information. Unqualified symbol ***
  1102. *** resolution is turned off by default. Please either specify a ***
  1103. *** fully qualified symbol module!symbolname, or enable resolution ***
  1104. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1105. *** enabling unqualified symbol resolution with network symbol ***
  1106. *** server shares in the symbol path may cause the debugger to ***
  1107. *** appear to hang for long periods of time when an incorrect ***
  1108. *** symbol name is typed or the network symbol server is down. ***
  1109. *** ***
  1110. *** For some commands to work properly, your symbol path ***
  1111. *** must point to .pdb files that have full type information. ***
  1112. *** ***
  1113. *** Certain .pdb files (such as the public OS symbols) do not ***
  1114. *** contain the required information. Contact the group that ***
  1115. *** provided you with these symbols if you need this command to ***
  1116. *** work. ***
  1117. *** ***
  1118. *** Type referenced: nt!_MMPTE ***
  1119. *** ***
  1120. *************************************************************************
  1121. *************************************************************************
  1122. *** ***
  1123. *** ***
  1124. *** Either you specified an unqualified symbol, or your debugger ***
  1125. *** doesn't have full symbol information. Unqualified symbol ***
  1126. *** resolution is turned off by default. Please either specify a ***
  1127. *** fully qualified symbol module!symbolname, or enable resolution ***
  1128. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1129. *** enabling unqualified symbol resolution with network symbol ***
  1130. *** server shares in the symbol path may cause the debugger to ***
  1131. *** appear to hang for long periods of time when an incorrect ***
  1132. *** symbol name is typed or the network symbol server is down. ***
  1133. *** ***
  1134. *** For some commands to work properly, your symbol path ***
  1135. *** must point to .pdb files that have full type information. ***
  1136. *** ***
  1137. *** Certain .pdb files (such as the public OS symbols) do not ***
  1138. *** contain the required information. Contact the group that ***
  1139. *** provided you with these symbols if you need this command to ***
  1140. *** work. ***
  1141. *** ***
  1142. *** Type referenced: nt!_MMPTE ***
  1143. *** ***
  1144. *************************************************************************
  1145. *************************************************************************
  1146. *** ***
  1147. *** ***
  1148. *** Either you specified an unqualified symbol, or your debugger ***
  1149. *** doesn't have full symbol information. Unqualified symbol ***
  1150. *** resolution is turned off by default. Please either specify a ***
  1151. *** fully qualified symbol module!symbolname, or enable resolution ***
  1152. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1153. *** enabling unqualified symbol resolution with network symbol ***
  1154. *** server shares in the symbol path may cause the debugger to ***
  1155. *** appear to hang for long periods of time when an incorrect ***
  1156. *** symbol name is typed or the network symbol server is down. ***
  1157. *** ***
  1158. *** For some commands to work properly, your symbol path ***
  1159. *** must point to .pdb files that have full type information. ***
  1160. *** ***
  1161. *** Certain .pdb files (such as the public OS symbols) do not ***
  1162. *** contain the required information. Contact the group that ***
  1163. *** provided you with these symbols if you need this command to ***
  1164. *** work. ***
  1165. *** ***
  1166. *** Type referenced: nt!_MMPTE ***
  1167. *** ***
  1168. *************************************************************************
  1169. *************************************************************************
  1170. *** ***
  1171. *** ***
  1172. *** Either you specified an unqualified symbol, or your debugger ***
  1173. *** doesn't have full symbol information. Unqualified symbol ***
  1174. *** resolution is turned off by default. Please either specify a ***
  1175. *** fully qualified symbol module!symbolname, or enable resolution ***
  1176. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1177. *** enabling unqualified symbol resolution with network symbol ***
  1178. *** server shares in the symbol path may cause the debugger to ***
  1179. *** appear to hang for long periods of time when an incorrect ***
  1180. *** symbol name is typed or the network symbol server is down. ***
  1181. *** ***
  1182. *** For some commands to work properly, your symbol path ***
  1183. *** must point to .pdb files that have full type information. ***
  1184. *** ***
  1185. *** Certain .pdb files (such as the public OS symbols) do not ***
  1186. *** contain the required information. Contact the group that ***
  1187. *** provided you with these symbols if you need this command to ***
  1188. *** work. ***
  1189. *** ***
  1190. *** Type referenced: nt!_MMPTE ***
  1191. *** ***
  1192. *************************************************************************
  1193. *************************************************************************
  1194. *** ***
  1195. *** ***
  1196. *** Either you specified an unqualified symbol, or your debugger ***
  1197. *** doesn't have full symbol information. Unqualified symbol ***
  1198. *** resolution is turned off by default. Please either specify a ***
  1199. *** fully qualified symbol module!symbolname, or enable resolution ***
  1200. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1201. *** enabling unqualified symbol resolution with network symbol ***
  1202. *** server shares in the symbol path may cause the debugger to ***
  1203. *** appear to hang for long periods of time when an incorrect ***
  1204. *** symbol name is typed or the network symbol server is down. ***
  1205. *** ***
  1206. *** For some commands to work properly, your symbol path ***
  1207. *** must point to .pdb files that have full type information. ***
  1208. *** ***
  1209. *** Certain .pdb files (such as the public OS symbols) do not ***
  1210. *** contain the required information. Contact the group that ***
  1211. *** provided you with these symbols if you need this command to ***
  1212. *** work. ***
  1213. *** ***
  1214. *** Type referenced: nt!_MMPTE ***
  1215. *** ***
  1216. *************************************************************************
  1217. *************************************************************************
  1218. *** ***
  1219. *** ***
  1220. *** Either you specified an unqualified symbol, or your debugger ***
  1221. *** doesn't have full symbol information. Unqualified symbol ***
  1222. *** resolution is turned off by default. Please either specify a ***
  1223. *** fully qualified symbol module!symbolname, or enable resolution ***
  1224. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1225. *** enabling unqualified symbol resolution with network symbol ***
  1226. *** server shares in the symbol path may cause the debugger to ***
  1227. *** appear to hang for long periods of time when an incorrect ***
  1228. *** symbol name is typed or the network symbol server is down. ***
  1229. *** ***
  1230. *** For some commands to work properly, your symbol path ***
  1231. *** must point to .pdb files that have full type information. ***
  1232. *** ***
  1233. *** Certain .pdb files (such as the public OS symbols) do not ***
  1234. *** contain the required information. Contact the group that ***
  1235. *** provided you with these symbols if you need this command to ***
  1236. *** work. ***
  1237. *** ***
  1238. *** Type referenced: nt!_MMPTE ***
  1239. *** ***
  1240. *************************************************************************
  1241. *************************************************************************
  1242. *** ***
  1243. *** ***
  1244. *** Either you specified an unqualified symbol, or your debugger ***
  1245. *** doesn't have full symbol information. Unqualified symbol ***
  1246. *** resolution is turned off by default. Please either specify a ***
  1247. *** fully qualified symbol module!symbolname, or enable resolution ***
  1248. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1249. *** enabling unqualified symbol resolution with network symbol ***
  1250. *** server shares in the symbol path may cause the debugger to ***
  1251. *** appear to hang for long periods of time when an incorrect ***
  1252. *** symbol name is typed or the network symbol server is down. ***
  1253. *** ***
  1254. *** For some commands to work properly, your symbol path ***
  1255. *** must point to .pdb files that have full type information. ***
  1256. *** ***
  1257. *** Certain .pdb files (such as the public OS symbols) do not ***
  1258. *** contain the required information. Contact the group that ***
  1259. *** provided you with these symbols if you need this command to ***
  1260. *** work. ***
  1261. *** ***
  1262. *** Type referenced: nt!_MMPTE ***
  1263. *** ***
  1264. *************************************************************************
  1265. *************************************************************************
  1266. *** ***
  1267. *** ***
  1268. *** Either you specified an unqualified symbol, or your debugger ***
  1269. *** doesn't have full symbol information. Unqualified symbol ***
  1270. *** resolution is turned off by default. Please either specify a ***
  1271. *** fully qualified symbol module!symbolname, or enable resolution ***
  1272. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1273. *** enabling unqualified symbol resolution with network symbol ***
  1274. *** server shares in the symbol path may cause the debugger to ***
  1275. *** appear to hang for long periods of time when an incorrect ***
  1276. *** symbol name is typed or the network symbol server is down. ***
  1277. *** ***
  1278. *** For some commands to work properly, your symbol path ***
  1279. *** must point to .pdb files that have full type information. ***
  1280. *** ***
  1281. *** Certain .pdb files (such as the public OS symbols) do not ***
  1282. *** contain the required information. Contact the group that ***
  1283. *** provided you with these symbols if you need this command to ***
  1284. *** work. ***
  1285. *** ***
  1286. *** Type referenced: nt!_MMPTE ***
  1287. *** ***
  1288. *************************************************************************
  1289. *************************************************************************
  1290. *** ***
  1291. *** ***
  1292. *** Either you specified an unqualified symbol, or your debugger ***
  1293. *** doesn't have full symbol information. Unqualified symbol ***
  1294. *** resolution is turned off by default. Please either specify a ***
  1295. *** fully qualified symbol module!symbolname, or enable resolution ***
  1296. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1297. *** enabling unqualified symbol resolution with network symbol ***
  1298. *** server shares in the symbol path may cause the debugger to ***
  1299. *** appear to hang for long periods of time when an incorrect ***
  1300. *** symbol name is typed or the network symbol server is down. ***
  1301. *** ***
  1302. *** For some commands to work properly, your symbol path ***
  1303. *** must point to .pdb files that have full type information. ***
  1304. *** ***
  1305. *** Certain .pdb files (such as the public OS symbols) do not ***
  1306. *** contain the required information. Contact the group that ***
  1307. *** provided you with these symbols if you need this command to ***
  1308. *** work. ***
  1309. *** ***
  1310. *** Type referenced: nt!_MMPTE ***
  1311. *** ***
  1312. *************************************************************************
  1313. *************************************************************************
  1314. *** ***
  1315. *** ***
  1316. *** Either you specified an unqualified symbol, or your debugger ***
  1317. *** doesn't have full symbol information. Unqualified symbol ***
  1318. *** resolution is turned off by default. Please either specify a ***
  1319. *** fully qualified symbol module!symbolname, or enable resolution ***
  1320. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1321. *** enabling unqualified symbol resolution with network symbol ***
  1322. *** server shares in the symbol path may cause the debugger to ***
  1323. *** appear to hang for long periods of time when an incorrect ***
  1324. *** symbol name is typed or the network symbol server is down. ***
  1325. *** ***
  1326. *** For some commands to work properly, your symbol path ***
  1327. *** must point to .pdb files that have full type information. ***
  1328. *** ***
  1329. *** Certain .pdb files (such as the public OS symbols) do not ***
  1330. *** contain the required information. Contact the group that ***
  1331. *** provided you with these symbols if you need this command to ***
  1332. *** work. ***
  1333. *** ***
  1334. *** Type referenced: nt!_MMPTE ***
  1335. *** ***
  1336. *************************************************************************
  1337. *************************************************************************
  1338. *** ***
  1339. *** ***
  1340. *** Either you specified an unqualified symbol, or your debugger ***
  1341. *** doesn't have full symbol information. Unqualified symbol ***
  1342. *** resolution is turned off by default. Please either specify a ***
  1343. *** fully qualified symbol module!symbolname, or enable resolution ***
  1344. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1345. *** enabling unqualified symbol resolution with network symbol ***
  1346. *** server shares in the symbol path may cause the debugger to ***
  1347. *** appear to hang for long periods of time when an incorrect ***
  1348. *** symbol name is typed or the network symbol server is down. ***
  1349. *** ***
  1350. *** For some commands to work properly, your symbol path ***
  1351. *** must point to .pdb files that have full type information. ***
  1352. *** ***
  1353. *** Certain .pdb files (such as the public OS symbols) do not ***
  1354. *** contain the required information. Contact the group that ***
  1355. *** provided you with these symbols if you need this command to ***
  1356. *** work. ***
  1357. *** ***
  1358. *** Type referenced: nt!_MMPTE ***
  1359. *** ***
  1360. *************************************************************************
  1361. *************************************************************************
  1362. *** ***
  1363. *** ***
  1364. *** Either you specified an unqualified symbol, or your debugger ***
  1365. *** doesn't have full symbol information. Unqualified symbol ***
  1366. *** resolution is turned off by default. Please either specify a ***
  1367. *** fully qualified symbol module!symbolname, or enable resolution ***
  1368. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1369. *** enabling unqualified symbol resolution with network symbol ***
  1370. *** server shares in the symbol path may cause the debugger to ***
  1371. *** appear to hang for long periods of time when an incorrect ***
  1372. *** symbol name is typed or the network symbol server is down. ***
  1373. *** ***
  1374. *** For some commands to work properly, your symbol path ***
  1375. *** must point to .pdb files that have full type information. ***
  1376. *** ***
  1377. *** Certain .pdb files (such as the public OS symbols) do not ***
  1378. *** contain the required information. Contact the group that ***
  1379. *** provided you with these symbols if you need this command to ***
  1380. *** work. ***
  1381. *** ***
  1382. *** Type referenced: nt!_MMPTE ***
  1383. *** ***
  1384. *************************************************************************
  1385. *************************************************************************
  1386. *** ***
  1387. *** ***
  1388. *** Either you specified an unqualified symbol, or your debugger ***
  1389. *** doesn't have full symbol information. Unqualified symbol ***
  1390. *** resolution is turned off by default. Please either specify a ***
  1391. *** fully qualified symbol module!symbolname, or enable resolution ***
  1392. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1393. *** enabling unqualified symbol resolution with network symbol ***
  1394. *** server shares in the symbol path may cause the debugger to ***
  1395. *** appear to hang for long periods of time when an incorrect ***
  1396. *** symbol name is typed or the network symbol server is down. ***
  1397. *** ***
  1398. *** For some commands to work properly, your symbol path ***
  1399. *** must point to .pdb files that have full type information. ***
  1400. *** ***
  1401. *** Certain .pdb files (such as the public OS symbols) do not ***
  1402. *** contain the required information. Contact the group that ***
  1403. *** provided you with these symbols if you need this command to ***
  1404. *** work. ***
  1405. *** ***
  1406. *** Type referenced: nt!_MMPTE ***
  1407. *** ***
  1408. *************************************************************************
  1409. *************************************************************************
  1410. *** ***
  1411. *** ***
  1412. *** Either you specified an unqualified symbol, or your debugger ***
  1413. *** doesn't have full symbol information. Unqualified symbol ***
  1414. *** resolution is turned off by default. Please either specify a ***
  1415. *** fully qualified symbol module!symbolname, or enable resolution ***
  1416. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1417. *** enabling unqualified symbol resolution with network symbol ***
  1418. *** server shares in the symbol path may cause the debugger to ***
  1419. *** appear to hang for long periods of time when an incorrect ***
  1420. *** symbol name is typed or the network symbol server is down. ***
  1421. *** ***
  1422. *** For some commands to work properly, your symbol path ***
  1423. *** must point to .pdb files that have full type information. ***
  1424. *** ***
  1425. *** Certain .pdb files (such as the public OS symbols) do not ***
  1426. *** contain the required information. Contact the group that ***
  1427. *** provided you with these symbols if you need this command to ***
  1428. *** work. ***
  1429. *** ***
  1430. *** Type referenced: nt!_MMPTE ***
  1431. *** ***
  1432. *************************************************************************
  1433. *************************************************************************
  1434. *** ***
  1435. *** ***
  1436. *** Either you specified an unqualified symbol, or your debugger ***
  1437. *** doesn't have full symbol information. Unqualified symbol ***
  1438. *** resolution is turned off by default. Please either specify a ***
  1439. *** fully qualified symbol module!symbolname, or enable resolution ***
  1440. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1441. *** enabling unqualified symbol resolution with network symbol ***
  1442. *** server shares in the symbol path may cause the debugger to ***
  1443. *** appear to hang for long periods of time when an incorrect ***
  1444. *** symbol name is typed or the network symbol server is down. ***
  1445. *** ***
  1446. *** For some commands to work properly, your symbol path ***
  1447. *** must point to .pdb files that have full type information. ***
  1448. *** ***
  1449. *** Certain .pdb files (such as the public OS symbols) do not ***
  1450. *** contain the required information. Contact the group that ***
  1451. *** provided you with these symbols if you need this command to ***
  1452. *** work. ***
  1453. *** ***
  1454. *** Type referenced: nt!_KPRCB ***
  1455. *** ***
  1456. *************************************************************************
  1457. *************************************************************************
  1458. *** ***
  1459. *** ***
  1460. *** Either you specified an unqualified symbol, or your debugger ***
  1461. *** doesn't have full symbol information. Unqualified symbol ***
  1462. *** resolution is turned off by default. Please either specify a ***
  1463. *** fully qualified symbol module!symbolname, or enable resolution ***
  1464. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1465. *** enabling unqualified symbol resolution with network symbol ***
  1466. *** server shares in the symbol path may cause the debugger to ***
  1467. *** appear to hang for long periods of time when an incorrect ***
  1468. *** symbol name is typed or the network symbol server is down. ***
  1469. *** ***
  1470. *** For some commands to work properly, your symbol path ***
  1471. *** must point to .pdb files that have full type information. ***
  1472. *** ***
  1473. *** Certain .pdb files (such as the public OS symbols) do not ***
  1474. *** contain the required information. Contact the group that ***
  1475. *** provided you with these symbols if you need this command to ***
  1476. *** work. ***
  1477. *** ***
  1478. *** Type referenced: nt!_KPRCB ***
  1479. *** ***
  1480. *************************************************************************
  1481.  
  1482. KEY_VALUES_STRING: 1
  1483.  
  1484. Key : Analysis.CPU.Sec
  1485. Value: 1
  1486.  
  1487. Key : Analysis.DebugAnalysisProvider.CPP
  1488. Value: Create: 8007007e on BILLY
  1489.  
  1490. Key : Analysis.DebugData
  1491. Value: CreateObject
  1492.  
  1493. Key : Analysis.DebugModel
  1494. Value: CreateObject
  1495.  
  1496. Key : Analysis.Elapsed.Sec
  1497. Value: 228
  1498.  
  1499. Key : Analysis.Memory.CommitPeak.Mb
  1500. Value: 65
  1501.  
  1502. Key : Analysis.System
  1503. Value: CreateObject
  1504.  
  1505.  
  1506. ADDITIONAL_DEBUG_TEXT:
  1507. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  1508.  
  1509. WRONG_SYMBOLS_TIMESTAMP: e98009eb
  1510.  
  1511. WRONG_SYMBOLS_SIZE: ab5000
  1512.  
  1513. FAULTING_MODULE: fffff8003f400000 nt
  1514.  
  1515. BUGCHECK_CODE: 50
  1516.  
  1517. BUGCHECK_P1: ffffae80006f56d8
  1518.  
  1519. BUGCHECK_P2: 0
  1520.  
  1521. BUGCHECK_P3: 0
  1522.  
  1523. BUGCHECK_P4: 6
  1524.  
  1525. READ_ADDRESS: *************************************************************************
  1526. *** ***
  1527. *** ***
  1528. *** Either you specified an unqualified symbol, or your debugger ***
  1529. *** doesn't have full symbol information. Unqualified symbol ***
  1530. *** resolution is turned off by default. Please either specify a ***
  1531. *** fully qualified symbol module!symbolname, or enable resolution ***
  1532. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1533. *** enabling unqualified symbol resolution with network symbol ***
  1534. *** server shares in the symbol path may cause the debugger to ***
  1535. *** appear to hang for long periods of time when an incorrect ***
  1536. *** symbol name is typed or the network symbol server is down. ***
  1537. *** ***
  1538. *** For some commands to work properly, your symbol path ***
  1539. *** must point to .pdb files that have full type information. ***
  1540. *** ***
  1541. *** Certain .pdb files (such as the public OS symbols) do not ***
  1542. *** contain the required information. Contact the group that ***
  1543. *** provided you with these symbols if you need this command to ***
  1544. *** work. ***
  1545. *** ***
  1546. *** Type referenced: nt!_MMPFN ***
  1547. *** ***
  1548. *************************************************************************
  1549. *************************************************************************
  1550. *** ***
  1551. *** ***
  1552. *** Either you specified an unqualified symbol, or your debugger ***
  1553. *** doesn't have full symbol information. Unqualified symbol ***
  1554. *** resolution is turned off by default. Please either specify a ***
  1555. *** fully qualified symbol module!symbolname, or enable resolution ***
  1556. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  1557. *** enabling unqualified symbol resolution with network symbol ***
  1558. *** server shares in the symbol path may cause the debugger to ***
  1559. *** appear to hang for long periods of time when an incorrect ***
  1560. *** symbol name is typed or the network symbol server is down. ***
  1561. *** ***
  1562. *** For some commands to work properly, your symbol path ***
  1563. *** must point to .pdb files that have full type information. ***
  1564. *** ***
  1565. *** Certain .pdb files (such as the public OS symbols) do not ***
  1566. *** contain the required information. Contact the group that ***
  1567. *** provided you with these symbols if you need this command to ***
  1568. *** work. ***
  1569. *** ***
  1570. *** Type referenced: nt!_MMPTE ***
  1571. *** ***
  1572. *************************************************************************
  1573. Unable to get size of nt!_MMPTE - probably bad symbols
  1574. ffffae80006f56d8
  1575.  
  1576. MM_INTERNAL_CODE: 6
  1577.  
  1578. CUSTOMER_CRASH_COUNT: 1
  1579.  
  1580. STACK_TEXT:
  1581. ffff8508`95b331b8 fffff800`3f62d3e0 : 00000000`00000050 ffffae80`006f56d8 00000000`00000000 ffffaed7`6ba00018 : nt!KeBugCheckEx
  1582. ffff8508`95b331c0 fffff800`3f473b8c : ffffaeff`ffffffff 00000000`00000000 ffffae80`00000000 fffff800`46d06038 : nt!memset+0x59260
  1583. ffff8508`95b33310 fffff800`3f472ebe : 00000000`02000103 00000000`00000000 00000000`00000001 ffffae80`006f56d8 : nt!SeAccessCheckWithHint+0x2fac
  1584. ffff8508`95b333c0 fffff800`3f5cf120 : 00000000`00000170 00000000`00000032 ffffe00b`3c890030 000001ff`000001a4 : nt!SeAccessCheckWithHint+0x22de
  1585. ffff8508`95b33560 fffff800`3f46e5e0 : fffff800`3f4ef848 00000000`206c644d fffff800`3f76e06d ffffe00b`00000200 : nt!setjmpex+0x43c0
  1586. ffff8508`95b336f8 fffff800`3f4ef848 : 00000000`206c644d fffff800`3f76e06d ffffe00b`00000200 00000000`00000000 : nt!IoGetStackLimits+0x2fc0
  1587. ffff8508`95b33700 fffff800`41a52992 : ffffe00b`45b6cf10 00000000`00000000 ffffae80`00a08e10 ffffe00b`3c890000 : nt!MmBuildMdlForNonPagedPool+0x1e8
  1588. ffff8508`95b337b0 fffff800`3b68e64f : 00000000`626e5910 ffffe00b`45b6cf10 ffffe00b`411b9800 ffffe00b`4ac5e040 : ndis!NdisAllocateMdl+0x42
  1589. ffff8508`95b337f0 00000000`626e5910 : ffffe00b`45b6cf10 ffffe00b`411b9800 ffffe00b`4ac5e040 00000000`00000044 : bcmwl63a+0x8e64f
  1590. ffff8508`95b337f8 ffffe00b`45b6cf10 : ffffe00b`411b9800 ffffe00b`4ac5e040 00000000`00000044 fffff800`3b670a6c : 0x626e5910
  1591. ffff8508`95b33800 ffffe00b`411b9800 : ffffe00b`4ac5e040 00000000`00000044 fffff800`3b670a6c ffffe00b`518c31d0 : 0xffffe00b`45b6cf10
  1592. ffff8508`95b33808 ffffe00b`4ac5e040 : 00000000`00000044 fffff800`3b670a6c ffffe00b`518c31d0 ffffe00b`411c1f80 : 0xffffe00b`411b9800
  1593. ffff8508`95b33810 00000000`00000044 : fffff800`3b670a6c ffffe00b`518c31d0 ffffe00b`411c1f80 00000000`00000022 : 0xffffe00b`4ac5e040
  1594. ffff8508`95b33818 fffff800`3b670a6c : ffffe00b`518c31d0 ffffe00b`411c1f80 00000000`00000022 ffffe00b`518c31d0 : 0x44
  1595. ffff8508`95b33820 ffffe00b`518c31d0 : ffffe00b`411c1f80 00000000`00000022 ffffe00b`518c31d0 00000000`00000000 : bcmwl63a+0x70a6c
  1596. ffff8508`95b33828 ffffe00b`411c1f80 : 00000000`00000022 ffffe00b`518c31d0 00000000`00000000 ffffe00b`44ac1600 : 0xffffe00b`518c31d0
  1597. ffff8508`95b33830 00000000`00000022 : ffffe00b`518c31d0 00000000`00000000 ffffe00b`44ac1600 00000000`10003240 : 0xffffe00b`411c1f80
  1598. ffff8508`95b33838 ffffe00b`518c31d0 : 00000000`00000000 ffffe00b`44ac1600 00000000`10003240 fffff800`3f5c7e26 : 0x22
  1599. ffff8508`95b33840 00000000`00000000 : ffffe00b`44ac1600 00000000`10003240 fffff800`3f5c7e26 00000000`00000000 : 0xffffe00b`518c31d0
  1600.  
  1601.  
  1602. STACK_COMMAND: .thread ; .cxr ; kb
  1603.  
  1604. EXCEPTION_CODE_STR: E98009EB
  1605.  
  1606. EXCEPTION_STR: WRONG_SYMBOLS
  1607.  
  1608. PROCESS_NAME: ntoskrnl.wrong.symbols.exe
  1609.  
  1610. IMAGE_NAME: ntoskrnl.wrong.symbols.exe
  1611.  
  1612. MODULE_NAME: nt_wrong_symbols
  1613.  
  1614. SYMBOL_NAME: nt_wrong_symbols!E98009EBAB5000
  1615.  
  1616. FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_18362.10000.amd64fre.19h1_release_svc_19h2_rel.190621-1123_TIMESTAMP_940220-053435_E98009EB_nt_wrong_symbols!E98009EBAB5000
  1617.  
  1618. OSPLATFORM_TYPE: x64
  1619.  
  1620. OSNAME: Windows 10
  1621.  
  1622. FAILURE_ID_HASH: {2a70a753-d8cb-6556-8b86-9d16c4278dcf}
  1623.  
  1624. Followup: MachineOwner
  1625. ---------
Advertisement
Add Comment
Please, Sign In to add comment