API tools faq
paste
Advertisement
Guest User

Blad

a guest
Nov 2nd, 2012
88
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.62 KB | None | 0 0
raw download clone embed print report
  1.  
  2. --------------------------------------------------------------------------------
  3. Welcome to WhoCrashed (HOME EDITION) v 4.00
  4. --------------------------------------------------------------------------------
  5.  
  6. This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
  7.  
  8. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
  9.  
  10. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
  11.  
  12. To obtain technical support visit www.resplendence.com/support
  13.  
  14. Click here to check if you have the latest version or if an update is available.
  15.  
  16. Just click the Analyze button for a comprehensible report ...
  17.  
  18.  
  19.  
  20. --------------------------------------------------------------------------------
  21. Home Edition Notice
  22. --------------------------------------------------------------------------------
  23.  
  24. This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
  25.  
  26. Click here for more information on the professional edition.
  27. Click here to buy the the professional edition of WhoCrashed.
  28.  
  29.  
  30. --------------------------------------------------------------------------------
  31. System Information (local)
  32. --------------------------------------------------------------------------------
  33.  
  34. computer name: SZWEDOMAN-KOMP
  35. windows version: Windows 7 , 6.1, build: 7600
  36. windows dir: C:\Windows
  37. CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AMD586, level: 15
  38. 2 logical processors, active mask: 3
  39. RAM: 4294500352 total
  40. VM: 2147352576, free: 1979555840
  41.  
  42.  
  43.  
  44.  
  45. --------------------------------------------------------------------------------
  46. Crash Dump Analysis
  47. --------------------------------------------------------------------------------
  48.  
  49. Crash dump directory: C:\Windows\Minidump
  50.  
  51. Crash dumps are enabled on your computer.
  52.  
  53. On Fri 2012-11-02 17:30:19 GMT your computer crashed
  54. crash dump file: C:\Windows\Minidump\110212-48157-01.dmp
  55. This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
  56. Bugcheck code: 0x18 (0x0, 0xFFFFFA8005DE5990, 0x2, 0xCCE09B4145A91125)
  57. Error: REFERENCE_BY_POINTER
  58. file path: C:\Windows\system32\ntoskrnl.exe
  59. product: Microsoft® Windows® Operating System
  60. company: Microsoft Corporation
  61. description: NT Kernel & System
  62. Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
  63. 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.
  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 Fri 2012-11-02 17:30:19 GMT your computer crashed
  69. crash dump file: C:\Windows\memory.dmp
  70. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  71. Bugcheck code: 0x18 (0x0, 0xFFFFFA8005DE5990, 0x2, 0xCCE09B4145A91125)
  72. Error: REFERENCE_BY_POINTER
  73. Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
  74. 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.
  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 Fri 2012-11-02 11:46:58 GMT your computer crashed
  80. crash dump file: C:\Windows\Minidump\110212-20748-01.dmp
  81. This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
  82. Bugcheck code: 0xC2 (0xB, 0xFFFFFA8005FD0330, 0x101F76B3, 0xFFFFFA8005FD0940)
  83. Error: BAD_POOL_CALLER
  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 the current thread is making a bad pool request.
  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 Fri 2012-11-02 11:30:54 GMT your computer crashed
  95. crash dump file: C:\Windows\Minidump\110212-32479-01.dmp
  96. This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
  97. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED0C22, 0xFFFFF8800B744110, 0x0)
  98. Error: SYSTEM_SERVICE_EXCEPTION
  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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  104. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  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 Fri 2012-11-02 11:07:06 GMT your computer crashed
  110. crash dump file: C:\Windows\Minidump\110212-21075-01.dmp
  111. This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
  112. Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002F1FD90, 0x0, 0x0)
  113. Error: KMODE_EXCEPTION_NOT_HANDLED
  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 kernel-mode program generated an exception which the error handler did not catch.
  119. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  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 Thu 2012-11-01 09:27:53 GMT your computer crashed
  125. crash dump file: C:\Windows\Minidump\110112-20982-01.dmp
  126. This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
  127. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002CC9ED, 0xFFFFF8800950A140, 0x0)
  128. Error: SYSTEM_SERVICE_EXCEPTION
  129. file path: C:\Windows\system32\win32k.sys
  130. product: System operacyjny Microsoft® Windows®
  131. company: Microsoft Corporation
  132. description: Współużytkowany sterownik Win32
  133. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  136.  
  137.  
  138.  
  139. On Tue 2012-10-16 22:37:06 GMT your computer crashed
  140. crash dump file: C:\Windows\Minidump\101712-23634-01.dmp
  141. This was probably caused by the following module: win32k.sys (0xFFFFF960002AC69D)
  142. Bugcheck code: 0x50 (0xFFFFF900C0807CF0, 0x0, 0xFFFFF960002AC69D, 0x0)
  143. Error: PAGE_FAULT_IN_NONPAGED_AREA
  144. file path: C:\Windows\system32\win32k.sys
  145. product: System operacyjny Microsoft® Windows®
  146. company: Microsoft Corporation
  147. description: Współużytkowany sterownik Win32
  148. Bug check description: This indicates that invalid system memory has been referenced.
  149. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  150. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  151.  
  152.  
  153.  
  154. On Mon 2012-09-17 19:31:09 GMT your computer crashed
  155. crash dump file: C:\Windows\Minidump\091712-20904-01.dmp
  156. This was probably caused by the following module: win32k.sys (win32k+0x1D3453)
  157. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000203453, 0xFFFFF880092D27B0, 0x0)
  158. Error: SYSTEM_SERVICE_EXCEPTION
  159. file path: C:\Windows\system32\win32k.sys
  160. product: System operacyjny Microsoft® Windows®
  161. company: Microsoft Corporation
  162. description: Współużytkowany sterownik Win32
  163. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  164. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  165. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  166.  
  167.  
  168.  
  169. On Thu 2012-08-30 21:29:34 GMT your computer crashed
  170. crash dump file: C:\Windows\Minidump\083012-38859-01.dmp
  171. This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
  172. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002DC9ED, 0xFFFFF880095EA140, 0x0)
  173. Error: SYSTEM_SERVICE_EXCEPTION
  174. file path: C:\Windows\system32\win32k.sys
  175. product: System operacyjny Microsoft® Windows®
  176. company: Microsoft Corporation
  177. description: Współużytkowany sterownik Win32
  178. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  181.  
  182.  
  183.  
  184.  
  185. --------------------------------------------------------------------------------
  186. Conclusion
  187. --------------------------------------------------------------------------------
  188.  
  189. 9 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
  190.  
  191.  
  192. Read the topic general suggestions for troubleshooting system crashes for more information.
  193.  
  194. 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!