API tools faq
paste
Advertisement
Guest User

heroesbsod1

a guest
Nov 28th, 2015
241
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.53 KB | None | 0 0
raw download clone embed print report
  1. Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\112715-5359-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8.  
  9. ************* Symbol Path validation summary **************
  10. Response Time (ms) Location
  11. Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
  12. Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
  13. Executable search path is:
  14. No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
  15. Windows 10 Kernel Version 10586 MP (4 procs) Free x64
  16. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  17. Built by: 10586.11.amd64fre.th2_release.151112-1900
  18. Machine Name:
  19. Kernel base = 0xfffff802`69c1f000 PsLoadedModuleList = 0xfffff802`69efdc70
  20. Debug session time: Fri Nov 27 14:46:47.479 2015 (UTC - 5:00)
  21. System Uptime: 0 days 2:12:29.118
  22. Loading Kernel Symbols
  23. ...............................................................
  24. ................................................................
  25. ...............................
  26. Loading User Symbols
  27. Loading unloaded module list
  28. ..................
  29. *******************************************************************************
  30. * *
  31. * Bugcheck Analysis *
  32. * *
  33. *******************************************************************************
  34.  
  35. Use !analyze -v to get detailed debugging information.
  36.  
  37. BugCheck 1E, {ffffffffc0000096, fffff80269d619ac, 0, 0}
  38.  
  39. Probably caused by : ntkrnlmp.exe ( nt!KiSaveDebugRegisterState+5c )
  40.  
  41. Followup: MachineOwner
  42. ---------
  43.  
  44. 0: kd> !analyze -v
  45. *******************************************************************************
  46. * *
  47. * Bugcheck Analysis *
  48. * *
  49. *******************************************************************************
  50.  
  51. KMODE_EXCEPTION_NOT_HANDLED (1e)
  52. This is a very common bugcheck. Usually the exception address pinpoints
  53. the driver/function that caused the problem. Always note this address
  54. as well as the link date of the driver/image that contains this address.
  55. Arguments:
  56. Arg1: ffffffffc0000096, The exception code that was not handled
  57. Arg2: fffff80269d619ac, The address that the exception occurred at
  58. Arg3: 0000000000000000, Parameter 0 of the exception
  59. Arg4: 0000000000000000, Parameter 1 of the exception
  60.  
  61. Debugging Details:
  62. ------------------
  63.  
  64.  
  65. BUGCHECK_P1: ffffffffc0000096
  66.  
  67. BUGCHECK_P2: fffff80269d619ac
  68.  
  69. BUGCHECK_P3: 0
  70.  
  71. BUGCHECK_P4: 0
  72.  
  73. EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
  74.  
  75. FAULTING_IP:
  76. nt!KiSaveDebugRegisterState+5c
  77. fffff802`69d619ac 0f32 rdmsr
  78.  
  79. BUGCHECK_STR: 0x1E_c0000096
  80.  
  81. CPU_COUNT: 4
  82.  
  83. CPU_MHZ: e12
  84.  
  85. CPU_VENDOR: GenuineIntel
  86.  
  87. CPU_FAMILY: 6
  88.  
  89. CPU_MODEL: 3c
  90.  
  91. CPU_STEPPING: 3
  92.  
  93. CUSTOMER_CRASH_COUNT: 1
  94.  
  95. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  96.  
  97. PROCESS_NAME: HeroesOfTheSto
  98.  
  99. CURRENT_IRQL: 0
  100.  
  101. ANALYSIS_VERSION: 10.0.10240.9 amd64fre
  102.  
  103. LAST_CONTROL_TRANSFER: from fffff80269d923b0 to fffff80269d61460
  104.  
  105. STACK_TEXT:
  106. ffffd000`22eee098 fffff802`69d923b0 : 00000000`0000001e ffffffff`c0000096 fffff802`69d619ac 00000000`00000000 : nt!KeBugCheckEx
  107. ffffd000`22eee0a0 fffff802`69d6c0c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x225b0
  108. ffffd000`22eee780 fffff802`69d6a57d : ffffe001`e333b080 00000000`00000000 ffffd000`22eeeb00 ffffe001`e333b580 : nt!KiExceptionDispatch+0xc2
  109. ffffd000`22eee960 fffff802`69d619ac : fffff802`69d648bf ffffe001`e4391000 00000000`00000000 ffffe001`e4391080 : nt!KiGeneralProtectionFault+0xfd
  110. ffffd000`22eeeaf8 fffff802`69d648bf : ffffe001`e4391000 00000000`00000000 ffffe001`e4391080 ffffd000`22eeeb80 : nt!KiSaveDebugRegisterState+0x5c
  111. ffffd000`22eeeb00 00007ffd`1dc65c2e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x5f
  112. 00000000`03f59330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1dc65c2e
  113.  
  114.  
  115. STACK_COMMAND: kb
  116.  
  117. FOLLOWUP_IP:
  118. nt!KiSaveDebugRegisterState+5c
  119. fffff802`69d619ac 0f32 rdmsr
  120.  
  121. SYMBOL_STACK_INDEX: 4
  122.  
  123. SYMBOL_NAME: nt!KiSaveDebugRegisterState+5c
  124.  
  125. FOLLOWUP_NAME: MachineOwner
  126.  
  127. MODULE_NAME: nt
  128.  
  129. IMAGE_NAME: ntkrnlmp.exe
  130.  
  131. DEBUG_FLR_IMAGE_TIMESTAMP: 56457780
  132.  
  133. IMAGE_VERSION: 10.0.10586.11
  134.  
  135. BUCKET_ID_FUNC_OFFSET: 5c
  136.  
  137. FAILURE_BUCKET_ID: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  138.  
  139. BUCKET_ID: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  140.  
  141. PRIMARY_PROBLEM_CLASS: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  142.  
  143. ANALYSIS_SOURCE: KM
  144.  
  145. FAILURE_ID_HASH_STRING: km:0x1e_c0000096_nt!kisavedebugregisterstate
  146.  
  147. FAILURE_ID_HASH: {0bd99c55-d8f8-3ac2-60cb-53208fc267f8}
  148.  
  149. Followup: MachineOwner
  150. ---------
  151.  
  152. 0: kd> !analyze -v
  153. *******************************************************************************
  154. * *
  155. * Bugcheck Analysis *
  156. * *
  157. *******************************************************************************
  158.  
  159. KMODE_EXCEPTION_NOT_HANDLED (1e)
  160. This is a very common bugcheck. Usually the exception address pinpoints
  161. the driver/function that caused the problem. Always note this address
  162. as well as the link date of the driver/image that contains this address.
  163. Arguments:
  164. Arg1: ffffffffc0000096, The exception code that was not handled
  165. Arg2: fffff80269d619ac, The address that the exception occurred at
  166. Arg3: 0000000000000000, Parameter 0 of the exception
  167. Arg4: 0000000000000000, Parameter 1 of the exception
  168.  
  169. Debugging Details:
  170. ------------------
  171.  
  172.  
  173. BUGCHECK_P1: ffffffffc0000096
  174.  
  175. BUGCHECK_P2: fffff80269d619ac
  176.  
  177. BUGCHECK_P3: 0
  178.  
  179. BUGCHECK_P4: 0
  180.  
  181. EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
  182.  
  183. FAULTING_IP:
  184. nt!KiSaveDebugRegisterState+5c
  185. fffff802`69d619ac 0f32 rdmsr
  186.  
  187. BUGCHECK_STR: 0x1E_c0000096
  188.  
  189. CPU_COUNT: 4
  190.  
  191. CPU_MHZ: e12
  192.  
  193. CPU_VENDOR: GenuineIntel
  194.  
  195. CPU_FAMILY: 6
  196.  
  197. CPU_MODEL: 3c
  198.  
  199. CPU_STEPPING: 3
  200.  
  201. CUSTOMER_CRASH_COUNT: 1
  202.  
  203. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  204.  
  205. PROCESS_NAME: HeroesOfTheSto
  206.  
  207. CURRENT_IRQL: 0
  208.  
  209. ANALYSIS_VERSION: 10.0.10240.9 amd64fre
  210.  
  211. LAST_CONTROL_TRANSFER: from fffff80269d923b0 to fffff80269d61460
  212.  
  213. STACK_TEXT:
  214. ffffd000`22eee098 fffff802`69d923b0 : 00000000`0000001e ffffffff`c0000096 fffff802`69d619ac 00000000`00000000 : nt!KeBugCheckEx
  215. ffffd000`22eee0a0 fffff802`69d6c0c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x225b0
  216. ffffd000`22eee780 fffff802`69d6a57d : ffffe001`e333b080 00000000`00000000 ffffd000`22eeeb00 ffffe001`e333b580 : nt!KiExceptionDispatch+0xc2
  217. ffffd000`22eee960 fffff802`69d619ac : fffff802`69d648bf ffffe001`e4391000 00000000`00000000 ffffe001`e4391080 : nt!KiGeneralProtectionFault+0xfd
  218. ffffd000`22eeeaf8 fffff802`69d648bf : ffffe001`e4391000 00000000`00000000 ffffe001`e4391080 ffffd000`22eeeb80 : nt!KiSaveDebugRegisterState+0x5c
  219. ffffd000`22eeeb00 00007ffd`1dc65c2e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x5f
  220. 00000000`03f59330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1dc65c2e
  221.  
  222.  
  223. STACK_COMMAND: kb
  224.  
  225. FOLLOWUP_IP:
  226. nt!KiSaveDebugRegisterState+5c
  227. fffff802`69d619ac 0f32 rdmsr
  228.  
  229. SYMBOL_STACK_INDEX: 4
  230.  
  231. SYMBOL_NAME: nt!KiSaveDebugRegisterState+5c
  232.  
  233. FOLLOWUP_NAME: MachineOwner
  234.  
  235. MODULE_NAME: nt
  236.  
  237. IMAGE_NAME: ntkrnlmp.exe
  238.  
  239. DEBUG_FLR_IMAGE_TIMESTAMP: 56457780
  240.  
  241. IMAGE_VERSION: 10.0.10586.11
  242.  
  243. BUCKET_ID_FUNC_OFFSET: 5c
  244.  
  245. FAILURE_BUCKET_ID: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  246.  
  247. BUCKET_ID: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  248.  
  249. PRIMARY_PROBLEM_CLASS: 0x1E_c0000096_nt!KiSaveDebugRegisterState
  250.  
  251. ANALYSIS_SOURCE: KM
  252.  
  253. FAILURE_ID_HASH_STRING: km:0x1e_c0000096_nt!kisavedebugregisterstate
  254.  
  255. FAILURE_ID_HASH: {0bd99c55-d8f8-3ac2-60cb-53208fc267f8}
  256.  
  257. Followup: MachineOwner
  258. ---------
  259.  
  260. 0: kd> !analyze -v
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!