Guest User

Crash Dump

a guest
Nov 19th, 2013
74
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.79 KB | None | 0 0
  1. Crash Dump Analysis
  2. --------------------------------------------------------------------------------
  3.  
  4. Crash dump directory: C:\Windows\Minidump
  5.  
  6. Crash dumps are enabled on your computer.
  7.  
  8. On Thu 16/05/2013 17:28:00 GMT your computer crashed
  9. crash dump file: C:\Windows\Minidump\051613-18236-01.dmp
  10. This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
  11. Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AE5A840, 0xFFFFFA800AE5AB20, 0xFFFFF80002D99350)
  12. Error: CRITICAL_OBJECT_TERMINATION
  13. file path: C:\Windows\system32\ntoskrnl.exe
  14. product: Microsoft® Windows® Operating System
  15. company: Microsoft Corporation
  16. description: NT Kernel & System
  17. Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
  18. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
  19. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  20.  
  21.  
  22.  
  23. On Thu 16/05/2013 17:28:00 GMT your computer crashed
  24. crash dump file: C:\Windows\memory.dmp
  25. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  26. Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AE5A840, 0xFFFFFA800AE5AB20, 0xFFFFF80002D99350)
  27. Error: CRITICAL_OBJECT_TERMINATION
  28. Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
  29. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
  30. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Add Comment
Please, Sign In to add comment