Guest User

WhoCrashed

a guest
Jan 29th, 2019
25
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.  
  2. --------------------------------------------------------------------------------
  3. Welcome to WhoCrashed (HOME EDITION) v 6.50
  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-DUQ*****
  37. Windows version: Windows 10 , 10.0, build: 17763
  38. Windows dir: C:\Windows
  39. Hardware: ASUSTeK COMPUTER INC., TUF X470-PLUS GAMING
  40. CPU: AuthenticAMD AMD Ryzen 7 2700 Eight-Core Processor AMD586, level: 23
  41. 16 logical processors, active mask: 65535
  42. RAM: 17111154688 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 Tue 29.01.2019 19:34:37 your computer crashed or a problem was reported
  58. crash dump file: C:\Windows\Minidump\012919-7734-01.dmp
  59. This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
  60. Bugcheck code: 0xA0 (0x608, 0xFFFFB603903A5648, 0x0, 0x0)
  61. Error: INTERNAL_POWER_ERROR
  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 power policy manager experienced a fatal error.
  67. This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
  68. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  69.  
  70.  
  71.  
  72. On Tue 29.01.2019 19:34:37 your computer crashed or a problem was reported
  73. crash dump file: C:\Windows\MEMORY.DMP
  74. This was probably caused by the following module: ntkrnlmp.exe (nt!PoFxSetComponentWake+0x14C)
  75. Bugcheck code: 0xA0 (0x608, 0xFFFFB603903A5648, 0x0, 0x0)
  76. Error: INTERNAL_POWER_ERROR
  77. Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
  78. This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
  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.  
  84.  
  85. --------------------------------------------------------------------------------
  86. Conclusion
  87. --------------------------------------------------------------------------------
  88.  
  89. 2 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.
  90.  
  91.  
  92. Read the topic general suggestions for troubleshooting system crashes for more information.
  93.  
  94. 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.
RAW Paste Data