Crash Dump

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-OK7J4TD
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., STRIX Z270F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34295488512 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 03/06/2018 18:29:07 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+0x111C8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800D95BE47D, 0xFFFFCB8E2765D940, 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 18:21:09 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: 0x3B (0xC0000005, 0xFFFFE335D0FFC884, 0xFFFFDF8938D1EDE0, 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 Sun 03/06/2018 18:15:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltSendMessage+0x338)
Bugcheck code: 0xA (0xFFFFF801D14FEA58, 0x2, 0x0, 0xFFFFF801910F5B47)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 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 17:55:53 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+0xC50ED)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803AE7C35F0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_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 indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 17:00:53 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: 0x3B (0xC0000005, 0xFFFFF802FF4C5EAA, 0xFFFFD98AB984EAA0, 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 Sun 03/06/2018 16:00:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-11765-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8068FD706D8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8068FD706D8, 0xFFFFC783E6FD0F18, 0xFFFFC783E6FD0760)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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 16:00:32 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 (0xFFFFF8068FD706D8)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8068FD706D8, 0xFFFFC783E6FD0F18, 0xFFFFC783E6FD0760)
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 Sun 03/06/2018 15:58:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-12343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8035CAFF98E, 0xFFFFF3086643E350, 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 14:33:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-12296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80143C3CEAA, 0xFFFFFE0BCAA8E7E0, 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 04:55:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060318-10468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801E1C28EAA, 0xFFFFE10C67C962E0, 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 Sat 02/06/2018 19:08:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060218-11921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x19 (0x22, 0x800000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 02/06/2018 18:56:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060218-11328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x15D470)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803ACB62470, 0xFFFFF4806191A818, 0xFFFFF4806191A060)
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 Sat 02/06/2018 18:15:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060218-10312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFBAC398BF9F6F, 0xFFFF8000759AED00, 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.