Advertisement
Guest User

Untitled

a guest
Mar 20th, 2019
88
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.08 KB | None | 0 0
  1.  
  2. --------------------------------------------------------------------------------
  3. Welcome to WhoCrashed (HOME EDITION) v 6.60
  4. --------------------------------------------------------------------------------
  5.  
  6. This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
  7.  
  8. Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black 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 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.
  25.  
  26. Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
  27.  
  28. Click here for more information on the professional edition.
  29. Click here to buy the the professional edition of WhoCrashed.
  30.  
  31.  
  32. --------------------------------------------------------------------------------
  33. System Information (local)
  34. --------------------------------------------------------------------------------
  35.  
  36. Computer name: DESKTOP-4IGD3IC
  37. Windows version: Windows 10 , 10.0, build: 17763
  38. Windows dir: C:\WINDOWS
  39. Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII HERO
  40. CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel8664, level: 6
  41. 8 logical processors, active mask: 255
  42. RAM: 17119944704 bytes (15.9GB)
  43.  
  44.  
  45.  
  46.  
  47. --------------------------------------------------------------------------------
  48. Crash Dump Analysis
  49. --------------------------------------------------------------------------------
  50.  
  51. Crash dumps are enabled on your computer.
  52.  
  53. Crash dump directories:
  54. C:\WINDOWS
  55. C:\WINDOWS\Minidump
  56.  
  57. On Wed 3/20/2019 12:25:29 AM your computer crashed or a problem was reported
  58. crash dump file: C:\WINDOWS\Minidump\032019-9156-01.dmp
  59. This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
  60. Bugcheck code: 0x7F (0x8, 0xFFFF8B01CD69B050, 0xFFFFFC8C761C6000, 0xFFFFF80748A31498)
  61. Error: UNEXPECTED_KERNEL_MODE_TRAP
  62. file path: C:\WINDOWS\system32\ntoskrnl.exe
  63. product: Microsoft® Windows® Operating System
  64. company: Microsoft Corporation
  65. description: NT Kernel & System
  66. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
  67. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  68.  
  69.  
  70.  
  71. On Wed 3/20/2019 12:25:29 AM your computer crashed or a problem was reported
  72. crash dump file: C:\WINDOWS\MEMORY.DMP
  73. This was probably caused by the following module: condrv.sys (condrv+0xAD12)
  74. Bugcheck code: 0x7F (0x8, 0xFFFF8B01CD69B050, 0xFFFFFC8C761C6000, 0xFFFFF80748A31498)
  75. Error: UNEXPECTED_KERNEL_MODE_TRAP
  76. file path: C:\WINDOWS\system32\drivers\condrv.sys
  77. product: Microsoft® Windows® Operating System
  78. company: Microsoft Corporation
  79. description: Console Driver
  80. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
  81. The crash took place in a 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.
  82.  
  83.  
  84.  
  85. On Tue 3/19/2019 12:51:14 AM your computer crashed or a problem was reported
  86. crash dump file: C:\WINDOWS\Minidump\031919-9703-01.dmp
  87. This was probably caused by the following module: hal.dll (0xFFFFF80331A18536)
  88. Bugcheck code: 0x7F (0x8, 0xFFFFF80333E6EE50, 0xFFFFA781E08ADE50, 0xFFFFF80331A18536)
  89. Error: UNEXPECTED_KERNEL_MODE_TRAP
  90. file path: C:\WINDOWS\system32\hal.dll
  91. product: Microsoft® Windows® Operating System
  92. company: Microsoft Corporation
  93. description: Hardware Abstraction Layer DLL
  94. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
  95. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  96.  
  97.  
  98.  
  99. On Mon 3/18/2019 10:44:28 PM your computer crashed or a problem was reported
  100. crash dump file: C:\WINDOWS\Minidump\031819-9062-01.dmp
  101. This was probably caused by the following module: hal.dll (0xFFFFF80334487536)
  102. Bugcheck code: 0x7F (0x8, 0xFFFFD1005DACA050, 0xFFFF8A0ABFCE0EA0, 0xFFFFF80334487536)
  103. Error: UNEXPECTED_KERNEL_MODE_TRAP
  104. file path: C:\WINDOWS\system32\hal.dll
  105. product: Microsoft® Windows® Operating System
  106. company: Microsoft Corporation
  107. description: Hardware Abstraction Layer DLL
  108. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
  109. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  110.  
  111.  
  112.  
  113.  
  114.  
  115. --------------------------------------------------------------------------------
  116. Conclusion
  117. --------------------------------------------------------------------------------
  118.  
  119. 4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
  120.  
  121.  
  122. Read the topic general suggestions for troubleshooting system crashes for more information.
  123.  
  124. Note that it's not always possible to state with certainty whether a reported driver is 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