Advertisement
Akrozia

BSOD WhoCrashed

Dec 24th, 2013
85
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.12 KB | None | 0 0
  1. --------------------------------------------------------------------------------
  2. Welcome to WhoCrashed (HOME EDITION) v 5.00
  3. --------------------------------------------------------------------------------
  4.  
  5. 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.
  6.  
  7. 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.
  8.  
  9. 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.
  10.  
  11. To obtain technical support visit www.resplendence.com/support
  12.  
  13. Click here to check if you have the latest version or if an update is available.
  14.  
  15. Just click the Analyze button for a comprehensible report ...
  16.  
  17.  
  18.  
  19. --------------------------------------------------------------------------------
  20. Home Edition Notice
  21. --------------------------------------------------------------------------------
  22.  
  23. 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 allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
  24.  
  25. Click here for more information on the professional edition.
  26. Click here to buy the the professional edition of WhoCrashed.
  27.  
  28.  
  29. --------------------------------------------------------------------------------
  30. System Information (local)
  31. --------------------------------------------------------------------------------
  32.  
  33. computer name: KHAAL
  34. windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  35. windows dir: C:\Windows
  36. Hardware: ASUSTeK Computer INC., P7P55D
  37. CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz Intel586, level: 6
  38. 4 logical processors, active mask: 15
  39. RAM: 4292927488 total
  40. VM: 2147352576, free: 1940303872
  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 Tue 24/12/2013 21:46:11 GMT your computer crashed
  54. crash dump file: C:\Windows\memory.dmp
  55. This was probably caused by the following module: ntkrnlmp.exe (nt!RtlRemoveEntryHashTable+0x93D)
  56. Bugcheck code: 0x116 (0xFFFFFA8003F51170, 0xFFFFF8800FA1B2BC, 0xFFFFFFFFC000009A, 0x4)
  57. Error: VIDEO_TDR_ERROR
  58. Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
  59. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  60.  
  61.  
  62.  
  63. On Tue 24/12/2013 13:54:01 GMT your computer crashed
  64. crash dump file: C:\Windows\Minidump\122413-16676-01.dmp
  65. This was probably caused by the following module: unknown_module_00000000`000000e2.sys (Unloaded_Unknown_Module_00000000`000000e2+0x29D9A5)
  66. Bugcheck code: 0x116 (0xFFFFFA8007C574E0, 0xFFFFF8800FA422BC, 0xFFFFFFFFC000009A, 0x4)
  67. Error: VIDEO_TDR_ERROR
  68. Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
  69. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`000000e2.sys .
  70. Google query: unknown_module_00000000`000000e2.sys VIDEO_TDR_ERROR
  71.  
  72.  
  73.  
  74. On Mon 23/12/2013 14:46:29 GMT your computer crashed
  75. crash dump file: C:\Windows\Minidump\122313-18033-01.dmp
  76. This was probably caused by the following module: ntoskrnl.exe (nt+0x7E709)
  77. Bugcheck code: 0x116 (0xFFFFFA80045244E0, 0xFFFFF8800FA472BC, 0xFFFFFFFFC000009A, 0x4)
  78. Error: VIDEO_TDR_ERROR
  79. file path: C:\Windows\system32\ntoskrnl.exe
  80. product: Microsoft® Windows® Operating System
  81. company: Microsoft Corporation
  82. description: NT Kernel & System
  83. Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
  84. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  85.  
  86.  
  87.  
  88. On Mon 23/12/2013 14:15:57 GMT your computer crashed
  89. crash dump file: C:\Windows\Minidump\122313-16614-01.dmp
  90. This was probably caused by the following module: ntoskrnl.exe (nt+0x7E709)
  91. Bugcheck code: 0x116 (0xFFFFFA80074ED010, 0xFFFFF8800FA662BC, 0xFFFFFFFFC000009A, 0x4)
  92. Error: VIDEO_TDR_ERROR
  93. file path: C:\Windows\system32\ntoskrnl.exe
  94. product: Microsoft® Windows® Operating System
  95. company: Microsoft Corporation
  96. description: NT Kernel & System
  97. Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
  98. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  99.  
  100.  
  101.  
  102.  
  103. --------------------------------------------------------------------------------
  104. Conclusion
  105. --------------------------------------------------------------------------------
  106.  
  107. 4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
  108.  
  109. unknown_module_00000000`000000e2.sys
  110.  
  111. If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
  112.  
  113.  
  114. Read the topic general suggestions for troubleshooting system crashes for more information.
  115.  
  116. 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