API tools faq
paste
Advertisement
Guest User

WhoCrashed Error Report

a guest
Nov 24th, 2016
86
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.73 KB | None | 0 0
raw download clone embed print report
  1. Analysis
  2. ----------------------------------------------
  3. Crash dump directory: C:\WINDOWS\Minidump
  4.  
  5. Crash dumps are enabled on your computer.
  6.  
  7. On Thu 24-Nov-16 13:34:23 your computer crashed
  8. crash dump file: C:\WINDOWS\Minidump\112416-3531-01.dmp
  9. This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
  10. Bugcheck code: 0x19 (0xE, 0xFFFFCF8A1D582080, 0x0, 0x74C5230A11CEEB26)
  11. Error: BAD_POOL_HEADER
  12. file path: C:\WINDOWS\system32\ntoskrnl.exe
  13. product: Microsoft® Windows® Operating System
  14. company: Microsoft Corporation
  15. description: NT Kernel & System
  16. Bug check description: This indicates that a pool header is corrupt.
  17. 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. This problem might also be caused because of overheating (thermal issue).
  18. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  19.  
  20.  
  21.  
  22. On Thu 24-Nov-16 13:34:23 your computer crashed
  23. crash dump file: C:\WINDOWS\memory.dmp
  24. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  25. Bugcheck code: 0x19 (0xE, 0xFFFFCF8A1D582080, 0x0, 0x74C5230A11CEEB26)
  26. Error: BAD_POOL_HEADER
  27. Bug check description: This indicates that a pool header is corrupt.
  28. 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. This problem might also be caused because of overheating (thermal issue).
  29. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  30.  
  31.  
  32.  
  33. On Wed 23-Nov-16 12:20:28 your computer crashed
  34. crash dump file: C:\WINDOWS\Minidump\112316-3390-01.dmp
  35. This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
  36. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C4933A91, 0xFFFF9F0185945DB0, 0x0)
  37. Error: SYSTEM_SERVICE_EXCEPTION
  38. file path: C:\WINDOWS\system32\ntoskrnl.exe
  39. product: Microsoft® Windows® Operating System
  40. company: Microsoft Corporation
  41. description: NT Kernel & System
  42. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  43. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  44. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  45.  
  46.  
  47.  
  48. On Wed 23-Nov-16 11:47:37 your computer crashed
  49. crash dump file: C:\WINDOWS\Minidump\112316-3421-01.dmp
  50. This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
  51. Bugcheck code: 0x19 (0xE, 0xFFFFAE84C1464D40, 0xFFFFAE84BF220C10, 0x1D247B02BFC82A5A)
  52. Error: BAD_POOL_HEADER
  53. file path: C:\WINDOWS\system32\ntoskrnl.exe
  54. product: Microsoft® Windows® Operating System
  55. company: Microsoft Corporation
  56. description: NT Kernel & System
  57. Bug check description: This indicates that a pool header is corrupt.
  58. 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. This problem might also be caused because of overheating (thermal issue).
  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. Conclusion
  63. ----------------------------------------------
  64. 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.
  65.  
  66.  
  67. Read the topic general suggestions for troubleshooting system crashes for more information.
  68.  
  69. 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!