Advertisement
jlco

bsod data

Feb 24th, 2019
179
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.22 KB | None | 0 0
  1. *******************************************************************************
  2. * *
  3. * Bugcheck Analysis *
  4. * *
  5. *******************************************************************************
  6.  
  7. KERNEL_SECURITY_CHECK_FAILURE (139)
  8. A kernel component has corrupted a critical data structure. The corruption
  9. could potentially allow a malicious user to gain control of this machine.
  10. Arguments:
  11. Arg1: 0000000000000000, A stack-based buffer has been overrun.
  12. Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
  13. Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
  14. Arg4: fffff08e27ea6e00, Reserved
  15.  
  16. Debugging Details:
  17. ------------------
  18.  
  19.  
  20. KEY_VALUES_STRING: 1
  21.  
  22.  
  23. STACKHASH_ANALYSIS: 1
  24.  
  25. TIMELINE_ANALYSIS: 1
  26.  
  27.  
  28. DUMP_CLASS: 1
  29.  
  30. DUMP_QUALIFIER: 400
  31.  
  32. BUILD_VERSION_STRING: 10.0.17134.590 (WinBuild.160101.0800)
  33.  
  34. DUMP_FILE_ATTRIBUTES: 0x8
  35. Kernel Generated Triage Dump
  36.  
  37. DUMP_TYPE: 2
  38.  
  39. BUGCHECK_P1: 0
  40.  
  41. BUGCHECK_P2: 0
  42.  
  43. BUGCHECK_P3: 0
  44.  
  45. BUGCHECK_P4: fffff08e27ea6e00
  46.  
  47. TRAP_FRAME: fffff80236dae800 -- (.trap 0xfffff80236dae800)
  48. Unable to read trap frame at fffff802`36dae800
  49.  
  50. EXCEPTION_RECORD: 0000000000000001 -- (.exr 0x1)
  51. Cannot read Exception record @ 0000000000000001
  52.  
  53. CPU_COUNT: c
  54.  
  55. CPU_MHZ: d42
  56.  
  57. CPU_VENDOR: AuthenticAMD
  58.  
  59. CPU_FAMILY: 17
  60.  
  61. CPU_MODEL: 8
  62.  
  63. CPU_STEPPING: 2
  64.  
  65. CUSTOMER_CRASH_COUNT: 1
  66.  
  67. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  68.  
  69. BUGCHECK_STR: 0x139
  70.  
  71. PROCESS_NAME: System
  72.  
  73. CURRENT_IRQL: 2
  74.  
  75. ANALYSIS_SESSION_HOST: PC-JOEY
  76.  
  77. ANALYSIS_SESSION_TIME: 02-24-2019 19:25:37.0091
  78.  
  79. ANALYSIS_VERSION: 10.0.17763.132 amd64fre
  80.  
  81. LAST_CONTROL_TRANSFER: from fffff80236bb769b to fffff80236baf0c0
  82.  
  83. STACK_TEXT:
  84. fffff08e`27ea6678 fffff802`36bb769b : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
  85. fffff08e`27ea6680 fffff802`36bb796d : fffff802`36df6000 fffff802`36a05000 00058218`00953000 00000000`00000000 : nt!guard_icall_handler+0x1b
  86. fffff08e`27ea66b0 fffff802`36ac3b36 : fffff08e`27ea67e0 fffff08e`27ea6ca0 00000000`00000000 fffff08e`27ea75b8 : nt!RtlpExecuteHandlerForException+0xd
  87. fffff08e`27ea66e0 fffff802`36ac5633 : fffff08e`27ea75b8 fffff08e`27ea7300 fffff08e`27ea75b8 00000000`00000000 : nt!RtlDispatchException+0x416
  88. fffff08e`27ea6dd0 fffff802`36bbfd42 : 00000000`00000001 0f0f0f0f`0f0f0f0f fffff802`36dae800 fffff803`9c782ca2 : nt!KiDispatchException+0x1f3
  89. fffff08e`27ea7480 fffff802`36bbc49c : ffffb701`2af7ef08 fffff802`36a49ae5 00000000`00017e5e fffff802`36a4a4d2 : nt!KiExceptionDispatch+0xc2
  90. fffff08e`27ea7660 fffff802`36bb772d : fffff802`36a854a0 00000000`00000000 fffff08e`27ea7a10 fffff802`36dae840 : nt!KiGeneralProtectionFault+0x2dc
  91. fffff08e`27ea77f8 fffff802`36a854a0 : 00000000`00000000 fffff08e`27ea7a10 fffff802`36dae840 fffff802`36aa2348 : nt!guard_dispatch_icall+0x2d
  92. fffff08e`27ea7800 fffff802`36a8350e : fffff802`36db0808 00000000`00000000 fffff08e`27ea7a10 fffff803`9c783e00 : nt!PpmCheckStart+0x120
  93. fffff08e`27ea78c0 fffff802`36a44367 : 00000000`00000000 ffffde87`67f48640 ffffde87`67f48640 fffff802`36aa1e93 : nt!PpmCheckPeriodicStart+0x3e
  94. fffff08e`27ea7910 fffff802`36a439bb : 00000000`00000018 00000000`00000000 00000000`003291a2 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
  95. fffff08e`27ea7a50 fffff802`36bb27fa : ffffffff`00000000 ffffb701`2af79180 00000000`00000000 ffffb701`2af89300 : nt!KiRetireDpcList+0x1db
  96. fffff08e`27ea7c60 00000000`00000000 : fffff08e`27ea8000 fffff08e`27ea2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
  97.  
  98.  
  99. THREAD_SHA1_HASH_MOD_FUNC: c5cd3bf3d0961ae8e5d660ecda0c2c7ee3e98819
  100.  
  101. THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2696c68ae86c4041a25a774f6650237f7575da7c
  102.  
  103. THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee
  104.  
  105. FOLLOWUP_IP:
  106. nt!guard_icall_handler+1b
  107. fffff802`36bb769b 90 nop
  108.  
  109. FAULT_INSTR_CODE: ccccc390
  110.  
  111. SYMBOL_STACK_INDEX: 1
  112.  
  113. SYMBOL_NAME: nt!guard_icall_handler+1b
  114.  
  115. FOLLOWUP_NAME: MachineOwner
  116.  
  117. MODULE_NAME: nt
  118.  
  119. IMAGE_NAME: ntkrnlmp.exe
  120.  
  121. DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab
  122.  
  123. IMAGE_VERSION: 10.0.17134.590
  124.  
  125. STACK_COMMAND: .thread ; .cxr ; kb
  126.  
  127. BUCKET_ID_FUNC_OFFSET: 1b
  128.  
  129. FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler
  130.  
  131. BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler
  132.  
  133. PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler
  134.  
  135. TARGET_TIME: 2019-02-24T19:09:45.000Z
  136.  
  137. OSBUILD: 17134
  138.  
  139. OSSERVICEPACK: 590
  140.  
  141. SERVICEPACK_NUMBER: 0
  142.  
  143. OS_REVISION: 0
  144.  
  145. SUITE_MASK: 784
  146.  
  147. PRODUCT_TYPE: 1
  148.  
  149. OSPLATFORM_TYPE: x64
  150.  
  151. OSNAME: Windows 10
  152.  
  153. OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
  154.  
  155. OS_LOCALE:
  156.  
  157. USER_LCID: 0
  158.  
  159. OSBUILD_TIMESTAMP: 2019-02-05 21:25:47
  160.  
  161. BUILDDATESTAMP_STR: 160101.0800
  162.  
  163. BUILDLAB_STR: WinBuild
  164.  
  165. BUILDOSVER_STR: 10.0.17134.590
  166.  
  167. ANALYSIS_SESSION_ELAPSED_TIME: cc5
  168.  
  169. ANALYSIS_SOURCE: KM
  170.  
  171. FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_nt!guard_icall_handler
  172.  
  173. FAILURE_ID_HASH: {9ac18088-8c91-40fd-01fb-5255bc467cba}
  174.  
  175. Followup: MachineOwner
  176. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement