Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Crash Dump Analysis
- --------------------------------------------------------------------------------
- Crash dump directory: C:\WINDOWS\Minidump
- Crash dumps are enabled on your computer.
- On Wed 2015-11-04 18:03:35 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\110415-6421-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800DF725EA9, 0xFFFFD00190F36A90, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Wed 2015-11-04 18:03:35 GMT your computer crashed
- crash dump file: C:\WINDOWS\memory.dmp
- This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800DF725EA9, 0xFFFFD00190F36A90, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Wed 2015-11-04 17:20:40 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\110415-7750-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x7F (0x8, 0xFFFFD001442B1A30, 0xDFFFD00144362FE0, 0xFFFFF80250B55ACD)
- Error: UNEXPECTED_KERNEL_MODE_TRAP
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Tue 2015-11-03 16:52:38 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\110315-6093-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802BB0C2BD1, 0xFFFFD000231E1FC0, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Tue 2015-11-03 12:01:02 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\110315-7312-01.dmp
- This was probably caused by the following module: watchdog.sys (watchdog+0x3C3D)
- Bugcheck code: 0x119 (0xA, 0x1321CC5, 0x1321CC7, 0xFFFFE00077A9A3B0)
- Error: VIDEO_SCHEDULER_INTERNAL_ERROR
- file path: C:\WINDOWS\system32\drivers\watchdog.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: Watchdog Driver
- Bug check description: This indicates that the video scheduler has detected a fatal violation.
- 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.
- On Fri 2015-10-30 12:35:54 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\103015-5968-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x139 (0x3, 0xFFFFD00023FB1820, 0xFFFFD00023FB1778, 0x0)
- Error: KERNEL_SECURITY_CHECK_FAILURE
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: The kernel has detected the corruption of a critical data structure.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Thu 2015-10-29 21:42:22 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\102915-5906-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802406C97AE, 0xFFFFD00022CF6D30, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Thu 2015-10-29 18:14:33 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\102915-6828-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x4A (0x7FF8E9CB372A, 0x1, 0x0, 0xFFFFD0002471CB80)
- Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Thu 2015-10-29 05:32:32 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\102915-10015-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8036B7601D9, 0x0, 0xFFFFFFFFFFFFFFFF)
- Error: KMODE_EXCEPTION_NOT_HANDLED
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Thu 2015-10-29 05:31:45 GMT your computer crashed
- crash dump file: C:\WINDOWS\Minidump\102915-10906-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80085ED5680, 0xFFFFD000531A6DF0, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- file path: C:\WINDOWS\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
- This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement