API tools faq
paste
Advertisement
Guest User

BSOD

a guest
Nov 28th, 2013
51
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.49 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\112313-77906-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  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. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  25. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  26. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  27. Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
  28. Product: WinNt, suite: TerminalServer SingleUserTS
  29. Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
  30. Machine Name:
  31. Kernel base = 0xfffff800`03662000 PsLoadedModuleList = 0xfffff800`038a5670
  32. Debug session time: Sat Nov 23 17:08:41.947 2013 (UTC - 5:00)
  33. System Uptime: 0 days 0:40:14.498
  34. *********************************************************************
  35. * Symbols can not be loaded because symbol path is not initialized. *
  36. * *
  37. * The Symbol Path can be set by: *
  38. * using the _NT_SYMBOL_PATH environment variable. *
  39. * using the -y <symbol_path> argument when starting the debugger. *
  40. * using .sympath and .sympath+ *
  41. *********************************************************************
  42. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  43. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  44. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  45. Loading Kernel Symbols
  46. ...............................................................
  47. ................................................................
  48. ................................................................
  49. ...................................
  50. Loading User Symbols
  51. Loading unloaded module list
  52. ........
  53.  
  54. ************* Symbol Loading Error Summary **************
  55. Module name Error
  56. ntoskrnl The system cannot find the file specified
  57.  
  58. 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.
  59. You should also verify that your symbol search path (.sympath) is correct.
  60. *******************************************************************************
  61. * *
  62. * Bugcheck Analysis *
  63. * *
  64. *******************************************************************************
  65.  
  66. Use !analyze -v to get detailed debugging information.
  67.  
  68. BugCheck D1, {48, e, 1, fffff88006cf0d9b}
  69.  
  70. *** WARNING: Unable to verify timestamp for mssmbios.sys
  71. *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
  72. *** WARNING: Unable to verify timestamp for nvlddmkm.sys
  73. *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
  74. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  75.  
  76. *************************************************************************
  77. *** ***
  78. *** ***
  79. *** Either you specified an unqualified symbol, or your debugger ***
  80. *** doesn't have full symbol information. Unqualified symbol ***
  81. *** resolution is turned off by default. Please either specify a ***
  82. *** fully qualified symbol module!symbolname, or enable resolution ***
  83. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  84. *** enabling unqualified symbol resolution with network symbol ***
  85. *** server shares in the symbol path may cause the debugger to ***
  86. *** appear to hang for long periods of time when an incorrect ***
  87. *** symbol name is typed or the network symbol server is down. ***
  88. *** ***
  89. *** For some commands to work properly, your symbol path ***
  90. *** must point to .pdb files that have full type information. ***
  91. *** ***
  92. *** Certain .pdb files (such as the public OS symbols) do not ***
  93. *** contain the required information. Contact the group that ***
  94. *** provided you with these symbols if you need this command to ***
  95. *** work. ***
  96. *** ***
  97. *** Type referenced: nt!_KPRCB ***
  98. *** ***
  99. *************************************************************************
  100. *************************************************************************
  101. *** ***
  102. *** ***
  103. *** Either you specified an unqualified symbol, or your debugger ***
  104. *** doesn't have full symbol information. Unqualified symbol ***
  105. *** resolution is turned off by default. Please either specify a ***
  106. *** fully qualified symbol module!symbolname, or enable resolution ***
  107. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  108. *** enabling unqualified symbol resolution with network symbol ***
  109. *** server shares in the symbol path may cause the debugger to ***
  110. *** appear to hang for long periods of time when an incorrect ***
  111. *** symbol name is typed or the network symbol server is down. ***
  112. *** ***
  113. *** For some commands to work properly, your symbol path ***
  114. *** must point to .pdb files that have full type information. ***
  115. *** ***
  116. *** Certain .pdb files (such as the public OS symbols) do not ***
  117. *** contain the required information. Contact the group that ***
  118. *** provided you with these symbols if you need this command to ***
  119. *** work. ***
  120. *** ***
  121. *** Type referenced: nt!_KPRCB ***
  122. *** ***
  123. *************************************************************************
  124. *************************************************************************
  125. *** ***
  126. *** ***
  127. *** Either you specified an unqualified symbol, or your debugger ***
  128. *** doesn't have full symbol information. Unqualified symbol ***
  129. *** resolution is turned off by default. Please either specify a ***
  130. *** fully qualified symbol module!symbolname, or enable resolution ***
  131. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  132. *** enabling unqualified symbol resolution with network symbol ***
  133. *** server shares in the symbol path may cause the debugger to ***
  134. *** appear to hang for long periods of time when an incorrect ***
  135. *** symbol name is typed or the network symbol server is down. ***
  136. *** ***
  137. *** For some commands to work properly, your symbol path ***
  138. *** must point to .pdb files that have full type information. ***
  139. *** ***
  140. *** Certain .pdb files (such as the public OS symbols) do not ***
  141. *** contain the required information. Contact the group that ***
  142. *** provided you with these symbols if you need this command to ***
  143. *** work. ***
  144. *** ***
  145. *** Type referenced: nt!_KPRCB ***
  146. *** ***
  147. *************************************************************************
  148. Probably caused by : nvlddmkm.sys ( nvlddmkm+209d9b )
  149.  
  150. Followup: MachineOwner
  151. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!