[spoiler][quote=""]
System Information (local)
Computer name: DESKTOP-9CF5E8S
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:WINDOWS
Hardware: ASUSTeK COMPUTER INC., Z170 PRO GAMING
CPU: GenuineIntel Intel® Core™ i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34274955264 bytes total
Crash Dump Analysis
Crash dump directory: C:WINDOWSMinidump
Crash dumps are enabled on your computer.
On Mon 24-10-16 16:52:34 your computer crashed
crash dump file: C:WINDOWSMinidump102416-4796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x109 (0xA3A017D91A3D763B, 0x0, 0x208FEB171918338E, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
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 24-10-16 16:52:34 your computer crashed
crash dump file: C:WINDOWSmemory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A017D91A3D763B, 0x0, 0x208FEB171918338E, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
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 24-10-16 07:15:08 your computer crashed
crash dump file: C:WINDOWSMinidump102416-4921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800DE7E3E27, 0xFFFF81002E7A62E8, 0xFFFF81002E7A5B10)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:WINDOWSsystem32ntoskrnl.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 Mon 24-10-16 06:16:11 your computer crashed
crash dump file: C:WINDOWSMinidump102416-4890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1247C5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801765B77C5, 0xFFFF8381BDA57658, 0xFFFF8381BDA56E80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:WINDOWSsystem32ntoskrnl.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 Mon 24-10-16 05:40:08 your computer crashed
crash dump file: C:WINDOWSMinidump102416-4625-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x1A (0x5002, 0xFFFFE3134B5EE1A0, 0x8772, 0x80000E59FFFFFFFE)
Error: MEMORY_MANAGEMENT
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/quote]
[/spoiler]
Voici le rapport WhoCrashed. Rien n’est très clair pour moi là dedans
Merci pour ta réponse