API tools faq
paste
Guest User

Whocrashed crash dump analysis

a guest
Jan 22nd, 2013
84
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.61 KB | None | 0 0
raw download clone embed print report
  1. System Information (local)
  2. --------------------------------------------------------------------------------
  3.  
  4. computer name: USER-PC
  5. windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  6. windows dir: C:\Windows
  7. CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6
  8. 4 logical processors, active mask: 15
  9. RAM: 8513904640 total
  10. VM: 2147352576, free: 1965506560
  11.  
  12.  
  13.  
  14.  
  15. --------------------------------------------------------------------------------
  16. Crash Dump Analysis
  17. --------------------------------------------------------------------------------
  18.  
  19. Crash dump directory: C:\Windows\Minidump
  20.  
  21. Crash dumps are enabled on your computer.
  22.  
  23. On Tue 22/01/2013 5:08:09 PM GMT your computer crashed
  24. crash dump file: C:\Windows\Minidump\012313-20732-01.dmp
  25. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  26. Bugcheck code: 0xA (0xFFFFF6FC40E50A60, 0x2, 0x0, 0xFFFFF80003D138C2)
  27. Error: IRQL_NOT_LESS_OR_EQUAL
  28. file path: C:\Windows\system32\ntoskrnl.exe
  29. product: Microsoft® Windows® Operating System
  30. company: Microsoft Corporation
  31. description: NT Kernel & System
  32. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  33. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  34. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  35.  
  36.  
  37.  
  38. On Tue 22/01/2013 5:08:09 PM GMT your computer crashed
  39. crash dump file: C:\Windows\memory.dmp
  40. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  41. Bugcheck code: 0xA (0xFFFFF6FC40E50A60, 0x2, 0x0, 0xFFFFF80003D138C2)
  42. Error: IRQL_NOT_LESS_OR_EQUAL
  43. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  44. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  45. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  46.  
  47.  
  48.  
  49. On Tue 22/01/2013 1:35:57 PM GMT your computer crashed
  50. crash dump file: C:\Windows\Minidump\012213-29109-01.dmp
  51. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  52. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 0x0)
  53. Error: MEMORY_MANAGEMENT
  54. file path: C:\Windows\system32\ntoskrnl.exe
  55. product: Microsoft® Windows® Operating System
  56. company: Microsoft Corporation
  57. description: NT Kernel & System
  58. Bug check description: This indicates that a severe memory management error occurred.
  59. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  60. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  61.  
  62.  
  63.  
  64. On Mon 21/01/2013 4:10:23 PM GMT your computer crashed
  65. crash dump file: C:\Windows\Minidump\012213-27783-01.dmp
  66. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  67. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 0x0)
  68. Error: MEMORY_MANAGEMENT
  69. file path: C:\Windows\system32\ntoskrnl.exe
  70. product: Microsoft® Windows® Operating System
  71. company: Microsoft Corporation
  72. description: NT Kernel & System
  73. Bug check description: This indicates that a severe memory management error occurred.
  74. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  75. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  76.  
  77.  
  78.  
  79. On Mon 21/01/2013 7:52:00 AM GMT your computer crashed
  80. crash dump file: C:\Windows\Minidump\012113-17893-01.dmp
  81. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  82. Bugcheck code: 0x50 (0xFFFFF700018CA238, 0x0, 0xFFFFF80003C97C43, 0x2)
  83. Error: PAGE_FAULT_IN_NONPAGED_AREA
  84. file path: C:\Windows\system32\ntoskrnl.exe
  85. product: Microsoft® Windows® Operating System
  86. company: Microsoft Corporation
  87. description: NT Kernel & System
  88. Bug check description: This indicates that invalid system memory has been referenced.
  89. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  90. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  91.  
  92.  
  93.  
  94. On Mon 21/01/2013 6:54:08 AM GMT your computer crashed
  95. crash dump file: C:\Windows\Minidump\012113-20888-01.dmp
  96. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  97. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 0x0)
  98. Error: MEMORY_MANAGEMENT
  99. file path: C:\Windows\system32\ntoskrnl.exe
  100. product: Microsoft® Windows® Operating System
  101. company: Microsoft Corporation
  102. description: NT Kernel & System
  103. Bug check description: This indicates that a severe memory management error occurred.
  104. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  105. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  106.  
  107.  
  108.  
  109. On Sun 20/01/2013 4:47:04 PM GMT your computer crashed
  110. crash dump file: C:\Windows\Minidump\012113-20560-01.dmp
  111. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  112. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 0x0)
  113. Error: MEMORY_MANAGEMENT
  114. file path: C:\Windows\system32\ntoskrnl.exe
  115. product: Microsoft® Windows® Operating System
  116. company: Microsoft Corporation
  117. description: NT Kernel & System
  118. Bug check description: This indicates that a severe memory management error occurred.
  119. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  120. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  121.  
  122.  
  123.  
  124. On Sun 20/01/2013 1:14:40 PM GMT your computer crashed
  125. crash dump file: C:\Windows\Minidump\012013-19141-01.dmp
  126. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  127. Bugcheck code: 0x50 (0xFFFFFA000737B4D0, 0x0, 0xFFFFF80003D05E2A, 0x7)
  128. Error: PAGE_FAULT_IN_NONPAGED_AREA
  129. file path: C:\Windows\system32\ntoskrnl.exe
  130. product: Microsoft® Windows® Operating System
  131. company: Microsoft Corporation
  132. description: NT Kernel & System
  133. Bug check description: This indicates that invalid system memory has been referenced.
  134. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  135. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  136.  
  137.  
  138.  
  139. On Sun 20/01/2013 12:07:47 PM GMT your computer crashed
  140. crash dump file: C:\Windows\Minidump\012013-22744-01.dmp
  141. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  142. Bugcheck code: 0x19 (0x3, 0xFFFFFA80066920D0, 0xFFFFFA80066920D0, 0xFFDFFA80066920D0)
  143. Error: BAD_POOL_HEADER
  144. file path: C:\Windows\system32\ntoskrnl.exe
  145. product: Microsoft® Windows® Operating System
  146. company: Microsoft Corporation
  147. description: NT Kernel & System
  148. Bug check description: This indicates that a pool header is corrupt.
  149. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  150. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  151.  
  152.  
  153.  
  154. On Sat 19/01/2013 7:51:50 AM GMT your computer crashed
  155. crash dump file: C:\Windows\Minidump\011913-20545-01.dmp
  156. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  157. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 0x0)
  158. Error: MEMORY_MANAGEMENT
  159. file path: C:\Windows\system32\ntoskrnl.exe
  160. product: Microsoft® Windows® Operating System
  161. company: Microsoft Corporation
  162. description: NT Kernel & System
  163. Bug check description: This indicates that a severe memory management error occurred.
  164. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  165. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  166.  
  167.  
  168.  
  169. On Sat 19/01/2013 2:41:16 AM GMT your computer crashed
  170. crash dump file: C:\Windows\Minidump\011913-22323-01.dmp
  171. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  172. Bugcheck code: 0x50 (0xFFFFF8A00F60E000, 0x0, 0xFFFFF80003F16B9B, 0x2)
  173. Error: PAGE_FAULT_IN_NONPAGED_AREA
  174. file path: C:\Windows\system32\ntoskrnl.exe
  175. product: Microsoft® Windows® Operating System
  176. company: Microsoft Corporation
  177. description: NT Kernel & System
  178. Bug check description: This indicates that invalid system memory has been referenced.
  179. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  180. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  181.  
  182.  
  183.  
  184. On Thu 17/01/2013 2:31:34 PM GMT your computer crashed
  185. crash dump file: C:\Windows\Minidump\011813-21590-01.dmp
  186. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  187. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 0x0)
  188. Error: MEMORY_MANAGEMENT
  189. file path: C:\Windows\system32\ntoskrnl.exe
  190. product: Microsoft® Windows® Operating System
  191. company: Microsoft Corporation
  192. description: NT Kernel & System
  193. Bug check description: This indicates that a severe memory management error occurred.
  194. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  195. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  196.  
  197.  
  198.  
  199. On Thu 17/01/2013 2:05:57 AM GMT your computer crashed
  200. crash dump file: C:\Windows\Minidump\011713-21746-01.dmp
  201. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  202. Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003CD2F90)
  203. Error: UNEXPECTED_KERNEL_MODE_TRAP
  204. file path: C:\Windows\system32\ntoskrnl.exe
  205. product: Microsoft® Windows® Operating System
  206. company: Microsoft Corporation
  207. description: NT Kernel & System
  208. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
  209. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  210.  
  211.  
  212.  
  213. On Mon 14/01/2013 4:29:36 AM GMT your computer crashed
  214. crash dump file: C:\Windows\Minidump\011413-56519-01.dmp
  215. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  216. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 0x0)
  217. Error: MEMORY_MANAGEMENT
  218. file path: C:\Windows\system32\ntoskrnl.exe
  219. product: Microsoft® Windows® Operating System
  220. company: Microsoft Corporation
  221. description: NT Kernel & System
  222. Bug check description: This indicates that a severe memory management error occurred.
  223. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  224. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  225.  
  226.  
  227.  
  228. On Sun 13/01/2013 2:47:02 PM GMT your computer crashed
  229. crash dump file: C:\Windows\Minidump\011413-25958-01.dmp
  230. This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
  231. Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 0x0)
  232. Error: MEMORY_MANAGEMENT
  233. file path: C:\Windows\system32\ntoskrnl.exe
  234. product: Microsoft® Windows® Operating System
  235. company: Microsoft Corporation
  236. description: NT Kernel & System
  237. Bug check description: This indicates that a severe memory management error occurred.
  238. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  239. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  240.  
  241.  
  242.  
  243.  
  244. --------------------------------------------------------------------------------
  245. Conclusion
  246. --------------------------------------------------------------------------------
  247.  
  248. 51 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
  249.  
  250.  
  251. Read the topic general suggestions for troubleshooting system crashes for more information.
  252.  
  253. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Add Comment
Please, Sign In to add comment
Public Pastes
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!