Bonjour,
 
Mon ordinateur crashe avec des BSOD réguliers, sans qu'il ne semble y avoir une activité particulière qui cause le problème.
 
J'ai fait tourner memtest86+ pendant environ 15 heures, soit 7 passes, aucune erreur détectée. J'ai poussé le CPU pendant environ 10 heures sur OCCT, aucun problème. De même pour le GPU, aucun souci. Tous mes drivers sont à jour. J'ai déjà procédé à une réinstallation de Windows, sans changement.
 
Que pourrais-je faire pour identifier et résoudre le problème?
 
Merci d'avance!
 
Voici le rapport WhoCrashed:
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: DESKTOP-FPR6P06
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: MS-7B79, Micro-Star International Co., Ltd., X470 GAMING PLUS (MS-7B79)
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: 17125851136 bytes total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Sun 17/06/2018 15:14:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061718-14546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)  
Bugcheck code: 0xA (0xDEBAD08D, 0xFF, 0xFF, 0xFFFFF802EAA9F97E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 17/06/2018 15:14:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!HalQueryRealTimeClock+0x873)  
Bugcheck code: 0xA (0xDEBAD08D, 0xFF, 0xFF, 0xFFFFF802EAA9F97E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 17/06/2018 14:56:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061718-14500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800AAFB1027, 0xFFFFF902999E2890, 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 17/06/2018 14:07:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061718-14406-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80249BBB027, 0xFFFFBE8EF1D00620, 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 17/06/2018 13:48:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061718-14328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)  
Bugcheck code: 0xF7 (0xC3820B4EB61A, 0xC3820B4EB61B, 0xFFFF3C7DF4B149E4, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 overrun a stack-based buffer.  
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 17/06/2018 08:42:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061718-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)  
Bugcheck code: 0xA (0xFFFFB686CB869000, 0x2, 0x0, 0xFFFFF8035C75A48E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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.  
 
 
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.