Bonjour,
Voici le rapport WHOSCRASHED :
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-0G72RIS
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: MS-7B86, Micro-Star International Co., Ltd, B450 GAMING PLUS (MS-7B86)
CPU: AuthenticAMD AMD Ryzen 7 2700 Eight-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 34308100096 bytes (32,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 22/08/2019 11:04:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082219-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
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 kernel mode heap manager has detected corruption in a heap.
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 22/08/2019 11:04: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!RtlTraceDatabaseValidate+0x5C48)
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
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 18/08/2019 18:45:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xDE (0x2, 0xFFFF8402CB1C5D38, 0xFFFF8402CB1C6480, 0x3EBD818C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
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 Sun 18/08/2019 17:38:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x4E (0x99, 0x1E1282, 0x2, 0x60003100031D281)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 18/08/2019 15:38:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-7171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xDE (0x2, 0xFFFFDD05733A7D38, 0xFFFFDD05733A7D78, 0x3F2F798C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
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 Sun 18/08/2019 15:33:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x1A (0x402, 0xFFFF8C0936E8CD38, 0x67A3FB8C0, 0xFFFF8C0939C6F1F8)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 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.
J'ai installé les derniers pilotes a jour pour la suite MSI.
Merci pour vos réponses les gars.