Voici le rapport de mes crashs: On Tue 06/02/2018 17:08:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-33718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0xBE (0xFFFFF40E1FAD1318, 0x8A000000DDD00021, 0xFFFFB583F38688F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 06/02/2018 12:55:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-42546-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80B9071FFFC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80B9071FFFC, 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 Tue 06/02/2018 11:50:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-17156-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF800B4635243)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B4635243, 0xFFFF86001EE3D820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 06/02/2018 11:50:04 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 (0xFFFFF800B4635243)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B4635243, 0xFFFF86001EE3D820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 06/02/2018 10:57:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-37031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF803F05978C8, 0xFFFFF803F08B5380, 0xCCCC9942B60CBEFD)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 06/02/2018 10:50:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-57500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802DE2ED7A0, 0xFFFF998218D162E0, 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.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\020618-26281-01.dmp
C:\WINDOWS\Minidump\020618-33140-01.dmp
C:\WINDOWS\Minidump\020618-35015-01.dmp
C:\WINDOWS\Minidump\020618-42406-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. Only 6 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
On Tue 06/02/2018 17:08:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-33718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0xBE (0xFFFFF40E1FAD1318, 0x8A000000DDD00021, 0xFFFFB583F38688F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 06/02/2018 12:55:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-42546-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80B9071FFFC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80B9071FFFC, 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 Tue 06/02/2018 11:50:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-17156-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF800B4635243)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B4635243, 0xFFFF86001EE3D820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 06/02/2018 11:50:04 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 (0xFFFFF800B4635243)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B4635243, 0xFFFF86001EE3D820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 06/02/2018 10:57:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-37031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF803F05978C8, 0xFFFFF803F08B5380, 0xCCCC9942B60CBEFD)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 06/02/2018 10:50:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-57500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802DE2ED7A0, 0xFFFF998218D162E0, 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.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\020618-26281-01.dmp
C:\WINDOWS\Minidump\020618-33140-01.dmp
C:\WINDOWS\Minidump\020618-35015-01.dmp
C:\WINDOWS\Minidump\020618-42406-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. Only 6 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
