API tools faq
paste
Advertisement
Guest User

WhoCrashed

a guest
Feb 2nd, 2017
239
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.74 KB | None | 0 0
raw download clone embed print report
  1. System Information (local)
  2. --------------------------------------------------------------------------------
  3.  
  4. Computer name: TAGANS-PC
  5. Windows version: Windows 10 , 10.0, build: 14393
  6. Windows dir: C:\WINDOWS
  7. Hardware: MS-7641, MSI, 760GM-P23(FX) (MS-7641)
  8. CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
  9. 6 logical processors, active mask: 63
  10. RAM: 8589070336 bytes total
  11.  
  12.  
  13.  
  14.  
  15. --------------------------------------------------------------------------------
  16. Crash Dump Analysis
  17. --------------------------------------------------------------------------------
  18.  
  19. Crash dump directory: C:\WINDOWS\Minidump
  20.  
  21. Crash dumps are enabled on your computer.
  22.  
  23. On Wed 2/1/2017 11:38:15 PM your computer crashed
  24. crash dump file: C:\WINDOWS\Minidump\020117-48578-01.dmp
  25. This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
  26. Bugcheck code: 0xA (0x21CA173D, 0xFF, 0xAD, 0xFFFFF80001BC28C1)
  27. Error: IRQL_NOT_LESS_OR_EQUAL
  28. file path: C:\WINDOWS\system32\ntoskrnl.exe
  29. product: Microsoft® Windows® Operating System
  30. company: Microsoft Corporation
  31. description: NT Kernel & System
  32. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  33. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  34. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  35.  
  36.  
  37.  
  38. On Wed 2/1/2017 11:38:15 PM your computer crashed
  39. crash dump file: C:\WINDOWS\memory.dmp
  40. This was probably caused by the following module: amdppm.sys (amdppm+0x5D82)
  41. Bugcheck code: 0xA (0x21CA173D, 0xFF, 0xAD, 0xFFFFF80001BC28C1)
  42. Error: IRQL_NOT_LESS_OR_EQUAL
  43. file path: C:\WINDOWS\system32\drivers\amdppm.sys
  44. product: Microsoft® Windows® Operating System
  45. company: Microsoft Corporation
  46. description: Processor Device Driver
  47. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  48. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  49. 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.
  50.  
  51.  
  52.  
  53. On Wed 2/1/2017 7:38:53 PM your computer crashed
  54. crash dump file: C:\WINDOWS\Minidump\020117-30765-01.dmp
  55. This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1AC797)
  56. Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8021491C797, 0x0, 0x801)
  57. Error: KMODE_EXCEPTION_NOT_HANDLED
  58. file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
  59. product: NVIDIA Windows Kernel Mode Driver, Version 368.81
  60. company: NVIDIA Corporation
  61. description: NVIDIA Windows Kernel Mode Driver, Version 368.81
  62. Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
  63. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  64. 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.81 , NVIDIA Corporation).
  65. Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED
  66.  
  67.  
  68.  
  69. On Wed 2/1/2017 7:25:24 PM your computer crashed
  70. crash dump file: C:\WINDOWS\Minidump\020117-40921-01.dmp
  71. This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
  72. Bugcheck code: 0x124 (0x0, 0xFFFF928C2FA9E758, 0x0, 0x0)
  73. Error: WHEA_UNCORRECTABLE_ERROR
  74. file path: C:\WINDOWS\system32\ntoskrnl.exe
  75. product: Microsoft® Windows® Operating System
  76. company: Microsoft Corporation
  77. description: NT Kernel & System
  78. 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).
  79. This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
  80. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  81.  
  82.  
  83.  
  84. On Wed 2/1/2017 6:59:54 PM your computer crashed
  85. crash dump file: C:\WINDOWS\Minidump\020117-38500-01.dmp
  86. This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
  87. Bugcheck code: 0x124 (0x0, 0xFFFFA503C4EC2038, 0x0, 0x0)
  88. Error: WHEA_UNCORRECTABLE_ERROR
  89. file path: C:\WINDOWS\system32\ntoskrnl.exe
  90. product: Microsoft® Windows® Operating System
  91. company: Microsoft Corporation
  92. description: NT Kernel & System
  93. 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).
  94. This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
  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.  
  100.  
  101. --------------------------------------------------------------------------------
  102. Conclusion
  103. --------------------------------------------------------------------------------
  104.  
  105. 12 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
  106.  
  107. nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.81 , NVIDIA Corporation)
  108.  
  109. If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
  110.  
  111.  
  112. Read the topic general suggestions for troubleshooting system crashes for more information.
  113.  
  114. 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
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!