Datasmurf

20171207-minidump_a

Dec 7th, 2017
117
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.09 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.16299.15 X86
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\120717-8096-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
  12. Product: WinNt, suite: TerminalServer SingleUserTS
  13. Built by: 7601.23915.x86fre.win7sp1_ldr.170913-0600
  14. Machine Name:
  15. Kernel base = 0x8364e000 PsLoadedModuleList = 0x8379ae30
  16. Debug session time: Thu Dec 7 21:39:19.501 2017 (UTC + 1:00)
  17. System Uptime: 0 days 0:09:19.344
  18. Loading Kernel Symbols
  19. ...............................................................
  20. ................................................................
  21. ................................................................
  22. ...
  23. Loading User Symbols
  24. Loading unloaded module list
  25. .......
  26. *******************************************************************************
  27. * *
  28. * Bugcheck Analysis *
  29. * *
  30. *******************************************************************************
  31.  
  32. Use !analyze -v to get detailed debugging information.
  33.  
  34. BugCheck 7A, {20, c000009d, 890cebdc, 0}
  35.  
  36. Probably caused by : memory_corruption ( nt!MiWriteComplete+22d )
  37.  
  38. Followup: MachineOwner
  39. ---------
  40.  
  41. 4: kd> !analyze -v
  42. *******************************************************************************
  43. * *
  44. * Bugcheck Analysis *
  45. * *
  46. *******************************************************************************
  47.  
  48. KERNEL_DATA_INPAGE_ERROR (7a)
  49. The requested page of kernel data could not be read in. Typically caused by
  50. a bad block in the paging file or disk controller error. Also see
  51. KERNEL_STACK_INPAGE_ERROR.
  52. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
  53. it means the disk subsystem has experienced a failure.
  54. If the error status is 0xC000009A, then it means the request failed because
  55. a filesystem failed to make forward progress.
  56. Arguments:
  57. Arg1: 00000020, lock type that was held (value 1,2,3, or PTE address)
  58. Arg2: c000009d, error status (normally i/o status code)
  59. Arg3: 890cebdc, current process (virtual address for lock type 3, or PTE)
  60. Arg4: 00000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
  61.  
  62. Debugging Details:
  63. ------------------
  64.  
  65.  
  66. DUMP_CLASS: 1
  67.  
  68. DUMP_QUALIFIER: 400
  69.  
  70. BUILD_VERSION_STRING: 7601.23915.x86fre.win7sp1_ldr.170913-0600
  71.  
  72. SYSTEM_MANUFACTURER: System manufacturer
  73.  
  74. SYSTEM_PRODUCT_NAME: System Product Name
  75.  
  76. SYSTEM_SKU: To be filled by O.E.M.
  77.  
  78. SYSTEM_VERSION: System Version
  79.  
  80. BIOS_VENDOR: American Megatrends Inc.
  81.  
  82. BIOS_VERSION: 1904
  83.  
  84. BIOS_DATE: 08/09/2011
  85.  
  86. BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
  87.  
  88. BASEBOARD_PRODUCT: SABERTOOTH P67
  89.  
  90. BASEBOARD_VERSION: Rev 1.xx
  91.  
  92. DUMP_TYPE: 2
  93.  
  94. BUGCHECK_P1: 20
  95.  
  96. BUGCHECK_P2: ffffffffc000009d
  97.  
  98. BUGCHECK_P3: ffffffff890cebdc
  99.  
  100. BUGCHECK_P4: 0
  101.  
  102. ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
  103.  
  104. DISK_HARDWARE_ERROR: There was error with disk hardware
  105.  
  106. BUGCHECK_STR: 0x7a_c000009d
  107.  
  108. CPU_COUNT: 8
  109.  
  110. CPU_MHZ: dae
  111.  
  112. CPU_VENDOR: GenuineIntel
  113.  
  114. CPU_FAMILY: 6
  115.  
  116. CPU_MODEL: 2a
  117.  
  118. CPU_STEPPING: 7
  119.  
  120. CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 1A'00000000 (cache) 1A'00000000 (init)
  121.  
  122. CUSTOMER_CRASH_COUNT: 1
  123.  
  124. DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  125.  
  126. PROCESS_NAME: System
  127.  
  128. CURRENT_IRQL: 1
  129.  
  130. ANALYSIS_SESSION_HOST: JAN-PC
  131.  
  132. ANALYSIS_SESSION_TIME: 12-07-2017 21:43:06.0166
  133.  
  134. ANALYSIS_VERSION: 10.0.16299.15 x86fre
  135.  
  136. LAST_CONTROL_TRANSFER: from 83682643 to 836c3106
  137.  
  138. STACK_TEXT:
  139. 8fa83b04 83682643 890ceba0 890ceba8 00000000 nt!MiWriteComplete+0x22d
  140. 8fa83b24 836fffe6 8bbdfe68 8fa83b50 8fa83b5c nt!IopCompletePageWrite+0x4d
  141. 8fa83b74 836ccfa5 00000000 00000000 00000000 nt!KiDeliverApc+0x111
  142. 8fa83bb8 836cbe17 865940e0 86594020 8379a390 nt!KiSwapThread+0x24e
  143. 8fa83be0 836f7b06 86594020 865940e0 00000000 nt!KiCommitThreadWait+0x1df
  144. 8fa83c24 83680b91 00000000 00000000 86594020 nt!KeWaitForGate+0x158
  145. 8fa83c50 8385b63d 00000000 a3ec6d47 00000000 nt!MiModifiedPageWriter+0x39
  146. 8fa83c90 836ffab9 83680b58 00000000 00000000 nt!PspSystemThreadStartup+0x9e
  147. 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
  148.  
  149.  
  150. THREAD_SHA1_HASH_MOD_FUNC: d78d17a4230e9eacdc178f31aba1263613c19840
  151.  
  152. THREAD_SHA1_HASH_MOD_FUNC_OFFSET: afc82d4f9093586885e38fa0d3d00fd4addecacc
  153.  
  154. THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe
  155.  
  156. FOLLOWUP_IP:
  157. nt!MiWriteComplete+22d
  158. 836c3106 cc int 3
  159.  
  160. FAULT_INSTR_CODE: 2444c7cc
  161.  
  162. SYMBOL_STACK_INDEX: 0
  163.  
  164. SYMBOL_NAME: nt!MiWriteComplete+22d
  165.  
  166. FOLLOWUP_NAME: MachineOwner
  167.  
  168. MODULE_NAME: nt
  169.  
  170. DEBUG_FLR_IMAGE_TIMESTAMP: 59b9451d
  171.  
  172. IMAGE_VERSION: 6.1.7601.23915
  173.  
  174. STACK_COMMAND: .thread ; .cxr ; kb
  175.  
  176. IMAGE_NAME: memory_corruption
  177.  
  178. FAILURE_BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d
  179.  
  180. BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d
  181.  
  182. PRIMARY_PROBLEM_CLASS: 0x7a_c000009d_nt!MiWriteComplete+22d
  183.  
  184. TARGET_TIME: 2017-12-07T20:39:19.000Z
  185.  
  186. OSBUILD: 7601
  187.  
  188. OSSERVICEPACK: 1000
  189.  
  190. SERVICEPACK_NUMBER: 0
  191.  
  192. OS_REVISION: 0
  193.  
  194. SUITE_MASK: 272
  195.  
  196. PRODUCT_TYPE: 1
  197.  
  198. OSPLATFORM_TYPE: x86
  199.  
  200. OSNAME: Windows 7
  201.  
  202. OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
  203.  
  204. OS_LOCALE:
  205.  
  206. USER_LCID: 0
  207.  
  208. OSBUILD_TIMESTAMP: 2017-09-13 16:47:57
  209.  
  210. BUILDDATESTAMP_STR: 170913-0600
  211.  
  212. BUILDLAB_STR: win7sp1_ldr
  213.  
  214. BUILDOSVER_STR: 6.1.7601.23915.x86fre.win7sp1_ldr.170913-0600
  215.  
  216. ANALYSIS_SESSION_ELAPSED_TIME: 637
  217.  
  218. ANALYSIS_SOURCE: KM
  219.  
  220. FAILURE_ID_HASH_STRING: km:0x7a_c000009d_nt!miwritecomplete+22d
  221.  
  222. FAILURE_ID_HASH: {280ce060-8b00-c306-3e98-579e06913606}
  223.  
  224. Followup: MachineOwner
  225. ---------
Add Comment
Please, Sign In to add comment