API tools faq
paste
Advertisement
Guest User

Crashes

a guest
Nov 8th, 2016
79
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.74 KB | None | 0 0
raw download clone embed print report
  1. On Tue 08/11/2016 18:31:16 your computer crashed
  2. crash dump file: C:\WINDOWS\Minidump\110816-30546-01.dmp
  3. This was probably caused by the following module: fltmgr.sys (FLTMGR+0x5856)
  4. Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80ABEAD5856, 0xFFFFC8817FF90C70, 0x0)
  5. Error: SYSTEM_SERVICE_EXCEPTION
  6. file path: C:\WINDOWS\system32\drivers\fltmgr.sys
  7. product: Microsoft® Windows® Operating System
  8. company: Microsoft Corporation
  9. description: Microsoft Filesystem Filter Manager
  10. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  11. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  12. 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.
  13.  
  14.  
  15. On Tue 08/11/2016 18:31:16 your computer crashed
  16. crash dump file: C:\WINDOWS\memory.dmp
  17. This was probably caused by the following module: fltmgr.sys (FLTMGR!FltIsCallbackDataDirty+0x966)
  18. Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80ABEAD5856, 0xFFFFC8817FF90C70, 0x0)
  19. Error: SYSTEM_SERVICE_EXCEPTION
  20. file path: C:\WINDOWS\system32\drivers\fltmgr.sys
  21. product: Microsoft® Windows® Operating System
  22. company: Microsoft Corporation
  23. description: Microsoft Filesystem Filter Manager
  24. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  25. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  26. 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.
  27.  
  28.  
  29. On Mon 07/11/2016 17:24:45 your computer crashed
  30. crash dump file: C:\WINDOWS\Minidump\110716-30250-01.dmp
  31. This was probably caused by the following module: usbxhci.sys (0xFFFFF80DB6A029A4)
  32. Bugcheck code: 0xD1 (0xFFFF8303CED35091, 0x2, 0x0, 0xFFFFF80DB6A029A4)
  33. Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  34. file path: C:\WINDOWS\system32\drivers\usbxhci.sys
  35. product: Microsoft® Windows® Operating System
  36. company: Microsoft Corporation
  37. description: USB XHCI Driver
  38. Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
  39. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  40. 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.
  41.  
  42.  
  43.  
  44. On Fri 04/11/2016 22:50:55 your computer crashed
  45. crash dump file: C:\WINDOWS\Minidump\110416-67984-01.dmp
  46. This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x471A0)
  47. Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF805C41071A0, 0xFFFFA0817D557018, 0xFFFFA0817D556840)
  48. Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  49. file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
  50. product: Microsoft® Windows® Operating System
  51. company: Microsoft Corporation
  52. description: DirectX Graphics MMS
  53. Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
  54. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  55. 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.
  56.  
  57.  
  58.  
  59. On Fri 04/11/2016 04:12:13 your computer crashed
  60. crash dump file: C:\WINDOWS\Minidump\110416-78968-01.dmp
  61. This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x36300)
  62. Bugcheck code: 0x19 (0xE, 0xFFFFF80082936300, 0xFFFFF80082912890, 0x21156DCC58065FED)
  63. Error: BAD_POOL_HEADER
  64. file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
  65. product: Microsoft® Windows® Operating System
  66. company: Microsoft Corporation
  67. description: DirectX Graphics Kernel
  68. Bug check description: This indicates that a pool header is corrupt.
  69. 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).
  70. 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.
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!