API tools faq
paste
Advertisement
jrgoncal

WhoCrashed report

jrgoncal
Mar 4th, 2014
4,078
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.56 KB | None | 0 0
raw download clone embed print report
  1. System Information (local)
  2. --------------------------------------------------------------------------------
  3.  
  4. computer name: BIGDADDY-PC
  5. windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  6. windows dir: C:\Windows
  7. Hardware: DX4831, Gateway, H57M01
  8. CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
  9. 4 logical processors, active mask: 15
  10. RAM: 5292261376 total
  11. VM: 2147352576, free: 1936515072
  12.  
  13.  
  14.  
  15.  
  16. --------------------------------------------------------------------------------
  17. Crash Dump Analysis
  18. --------------------------------------------------------------------------------
  19.  
  20. Crash dump directory: C:\Windows\Minidump
  21.  
  22. Crash dumps are enabled on your computer.
  23.  
  24. On Sun 3/2/2014 5:16:23 PM GMT your computer crashed
  25. crash dump file: C:\Windows\Minidump\030214-18532-01.dmp
  26. This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
  27. Bugcheck code: 0xD1 (0xFFFFFF0002E3868C, 0x2, 0x8, 0xFFFFFF0002E3868C)
  28. Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  29. file path: C:\Windows\system32\ntoskrnl.exe
  30. product: Microsoft® Windows® Operating System
  31. company: Microsoft Corporation
  32. description: NT Kernel & System
  33. Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
  34. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  35. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  36.  
  37.  
  38.  
  39. On Thu 6/6/2013 12:38:52 AM GMT your computer crashed
  40. crash dump file: C:\Windows\Minidump\060513-19921-01.dmp
  41. This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
  42. Bugcheck code: 0x124 (0x0, 0xFFFFFA8004F31038, 0x0, 0x0)
  43. Error: WHEA_UNCORRECTABLE_ERROR
  44. file path: C:\Windows\system32\ntoskrnl.exe
  45. product: Microsoft® Windows® Operating System
  46. company: Microsoft Corporation
  47. description: NT Kernel & System
  48. Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
  49. This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
  50. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  51.  
  52.  
  53.  
  54. On Sat 3/9/2013 5:44:55 AM GMT your computer crashed
  55. crash dump file: C:\Windows\Minidump\030913-18673-01.dmp
  56. This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
  57. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8006CCE078, 0x0)
  58. Error: KERNEL_DATA_INPAGE_ERROR
  59. file path: C:\Windows\system32\ntoskrnl.exe
  60. product: Microsoft® Windows® Operating System
  61. company: Microsoft Corporation
  62. description: NT Kernel & System
  63. Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  64. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  65.  
  66.  
  67.  
  68. On Sun 3/3/2013 4:57:20 AM GMT your computer crashed
  69. crash dump file: C:\Windows\Minidump\030313-20139-01.dmp
  70. This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
  71. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C445FE, 0xFFFFF880077B9E40, 0x0)
  72. Error: SYSTEM_SERVICE_EXCEPTION
  73. file path: C:\Windows\system32\ntoskrnl.exe
  74. product: Microsoft® Windows® Operating System
  75. company: Microsoft Corporation
  76. description: NT Kernel & System
  77. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  78. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  79. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  80.  
  81.  
  82.  
  83. On Sat 2/23/2013 4:17:19 AM GMT your computer crashed
  84. crash dump file: C:\Windows\Minidump\022213-21434-01.dmp
  85. This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
  86. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80068C5078, 0x0)
  87. Error: KERNEL_DATA_INPAGE_ERROR
  88. file path: C:\Windows\system32\ntoskrnl.exe
  89. product: Microsoft® Windows® Operating System
  90. company: Microsoft Corporation
  91. description: NT Kernel & System
  92. Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  93. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  94.  
  95.  
  96.  
  97. On Thu 2/7/2013 6:57:31 PM GMT your computer crashed
  98. crash dump file: C:\Windows\Minidump\020713-26613-01.dmp
  99. This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
  100. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800551D698, 0x0)
  101. Error: KERNEL_DATA_INPAGE_ERROR
  102. file path: C:\Windows\system32\ntoskrnl.exe
  103. product: Microsoft® Windows® Operating System
  104. company: Microsoft Corporation
  105. description: NT Kernel & System
  106. Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  107. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  108.  
  109.  
  110.  
  111. On Wed 2/6/2013 5:31:31 AM GMT your computer crashed
  112. crash dump file: C:\Windows\Minidump\020613-19812-01.dmp
  113. This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
  114. Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006F03B30, 0xFFFFFA8006F03E10, 0xFFFFF80002FD7D50)
  115. Error: CRITICAL_OBJECT_TERMINATION
  116. file path: C:\Windows\system32\ntoskrnl.exe
  117. product: Microsoft® Windows® Operating System
  118. company: Microsoft Corporation
  119. description: NT Kernel & System
  120. Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
  121. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
  122. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  123.  
  124.  
  125.  
  126. On Sun 2/3/2013 3:32:11 AM GMT your computer crashed
  127. crash dump file: C:\Windows\Minidump\020213-20794-01.dmp
  128. This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
  129. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8006F0F078, 0x0)
  130. Error: KERNEL_DATA_INPAGE_ERROR
  131. file path: C:\Windows\system32\ntoskrnl.exe
  132. product: Microsoft® Windows® Operating System
  133. company: Microsoft Corporation
  134. description: NT Kernel & System
  135. Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  136. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  137.  
  138.  
  139.  
  140. On Sun 1/20/2013 1:46:16 AM GMT your computer crashed
  141. crash dump file: C:\Windows\Minidump\011913-35193-01.dmp
  142. This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
  143. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80068767C8, 0x0)
  144. Error: KERNEL_DATA_INPAGE_ERROR
  145. file path: C:\Windows\system32\ntoskrnl.exe
  146. product: Microsoft® Windows® Operating System
  147. company: Microsoft Corporation
  148. description: NT Kernel & System
  149. Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  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 Wed 1/9/2013 2:02:52 AM GMT your computer crashed
  155. crash dump file: C:\Windows\Minidump\010813-19016-01.dmp
  156. This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
  157. Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8006FE7078, 0x0)
  158. Error: KERNEL_DATA_INPAGE_ERROR
  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 bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
  164. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  165.  
  166.  
  167.  
  168.  
  169. --------------------------------------------------------------------------------
  170. Conclusion
  171. --------------------------------------------------------------------------------
  172.  
  173. 24 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
  174.  
  175.  
  176. Read the topic general suggestions for troubleshooting system crashes for more information.
  177.  
  178. 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.
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!