Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- On Mon 04/06/2018 19:23:34 your computer crashed or a problem was reported
- crash dump file: C:\Windows\Minidump\060418-11656-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8004B8547D5, 0xFFFF8F8FB0086760, 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 Mon 04/06/2018 19:14:23 your computer crashed or a problem was reported
- crash dump file: C:\Windows\Minidump\060418-10375-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
- Bugcheck code: 0x154 (0xFFFF8E0BC2A8D000, 0xFFFF8A8169A56690, 0x1, 0x0)
- Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
- 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 Mon 04/06/2018 19:14:23 your computer crashed or a problem was reported
- crash dump file: C:\Windows\MEMORY.DMP
- This was probably caused by the following module: ntkrnlmp.exe (nt!SeConvertSidToStringSid+0x191A)
- Bugcheck code: 0x154 (0xFFFF8E0BC2A8D000, 0xFFFF8A8169A56690, 0x1, 0x0)
- Error: UNEXPECTED_STORE_EXCEPTION
- Bug check description: This indicates that the store component caught an unexpected exception.
- 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 Mon 04/06/2018 19:42:10 your computer crashed or a problem was reported
- crash dump file: C:\Windows\MEMORY.DMP
- This was probably caused by the following module: ntfs.sys (Ntfs+0x98B8)
- Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8013947BA62, 0xFFFF928DE1B39998, 0xFFFF928DE1B391E0)
- Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- file path: C:\WINDOWS\system32\drivers\ntfs.sys
- product: Système d’exploitation Microsoft® Windows®
- company: Microsoft Corporation
- description: Pilote du système de fichiers NT
- Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
- The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
- On Mon 04/06/2018 19:31:19 your computer crashed or a problem was reported
- crash dump file: C:\Windows\Minidump\060418-11593-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x272A62)
- Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8020DB16A62, 0xFFFF8D03420B6A88, 0xFFFF8D03420B62D0)
- Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
- 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 system thread 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 Sun 03/06/2018 21:31:56 your computer crashed or a problem was reported
- crash dump file: C:\Windows\MEMORY.DMP
- This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x87E9)
- Bugcheck code: 0x7F (0x8, 0xFFFFC38197CE0050, 0xFFFFC38197CE7F80, 0xFFFFF801AC7B2610)
- Error: UNEXPECTED_KERNEL_MODE_TRAP
- Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sun 03/06/2018 21:16:17 your computer crashed or a problem was reported
- crash dump file: C:\Windows\Minidump\060318-11843-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024CEFF318, 0xFFFFF3098B4FDEF0, 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 Sun 03/06/2018 21:16:17 your computer crashed or a problem was reported
- crash dump file: C:\Windows\MEMORY.DMP
- This was probably caused by the following module: ntfs.sys (Ntfs+0x14525)
- Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024CEFF318, 0xFFFFF3098B4FDEF0, 0x0)
- Error: SYSTEM_SERVICE_EXCEPTION
- file path: C:\WINDOWS\system32\drivers\ntfs.sys
- product: Système d’exploitation Microsoft® Windows®
- company: Microsoft Corporation
- description: Pilote du système de fichiers NT
- 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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
- On Sun 03/06/2018 20:44:11 your computer crashed or a problem was reported
- crash dump file: C:\Windows\Minidump\060318-11593-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
- Bugcheck code: 0x18 (0xFFFFC1027D2DDBE0, 0xFFFFC1028C69E170, 0x1, 0x800000000000000)
- Error: REFERENCE_BY_POINTER
- 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 the reference count of an object is illegal for the current state of the object.
- This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Sun 03/06/2018 20:44:11 your computer crashed or a problem was reported
- crash dump file: C:\Windows\MEMORY.DMP
- This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x24D46)
- Bugcheck code: 0x18 (0xFFFFC1027D2DDBE0, 0xFFFFC1028C69E170, 0x1, 0x800000000000000)
- Error: REFERENCE_BY_POINTER
- Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
- This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
- 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