J'ai un nouveau PC depuis la mi décembre et j'ai depuis le début un problème récurrent de Plantage BSOD.
J'avais déjà cherché de l'aide sur un forum d'aide de Microsoft un peu avant Noël, mais malgré l'aide de la personne qui s'occupait de mon cas, nous n'avons pas réussi à corriger le problème et j'ai fini par faire une clean reinstall de Windows 10.
Suite à quoi j'ai été tranquille jusqu'à il y a quelques jours où j'ai à nouveau eu un BSOD, et ce matin où j'en ai eu plusieurs (3-4 d'affilé). J'ai vu qu'il y avait une màj Windows, que j'ai faite, et là ça remarche apparemment correctement, mais un nouveau crash peut arriver d'un moment à l'autre !
Les crashs récents sont majoritairement arrivés au démarrage de l'ordinateur. Je joue également beaucoup (des jeux assez récents et plutôt gourmands en ressources) mais je n'ai jamais eu de problème lors de mes sessions de jeu, quelles que soient leurs longueurs.
J'avais également, lors des premiers problèmes avant Noël, utilisé l'outil de diagnostic de RAM de Windows car les codes d'erreur semblaient mettre en avant un problème lié à la mémoire. Mais aucun souci matériel n'avait été détecté.
Je vous mets ci-dessous le rapport de WhoCrashed que je viens d'effectuer :
Home Edition Notice
--------------------------------------------------------------------------------
Code : Tout sélectionner
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-K5D1SSQ
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: ASRock, AB350 Pro4
CPU: AuthenticAMD AMD Ryzen 5 1500X Quad-Core Processor AMD586, level: 23
8 logical processors, active mask: 255
RAM: 17109446656 bytes (15,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 09/01/2019 12:23:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010919-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x1A (0x61941, 0x7FFC1BE27E30, 0x1D, 0xFFFFFC8640EEDB00)
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.
On Wed 09/01/2019 12:23:16 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!memset+0x1C788)
Bugcheck code: 0x1A (0x61941, 0x7FFC1BE27E30, 0x1D, 0xFFFFFC8640EEDB00)
Error: MEMORY_MANAGEMENT
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.
On Wed 09/01/2019 11:57:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010919-6140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8026BE487B2, 0x17B, 0x0)
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 Wed 09/01/2019 11:54:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010919-6890-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF807BDEAF27B)
Bugcheck code: 0x50 (0xFFFF82809BF4AF64, 0x0, 0xFFFFF807BDEAF27B, 0xC)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
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 Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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.
Operating System
Windows 10 Famille 64-bit
CPU
AMD Ryzen 5 1500X 23 °C
14nm Technology
RAM
16,0 Go Dual-Channel Unknown @ 1064MHz (15-15-15-36)
Motherboard
ASRock AB350 Pro4 (AM4) 25 °C
Graphics
S24D300 (1920x1080@60Hz)
2047MB NVIDIA GeForce GTX 1060 6GB (ASUStek Computer Inc) 35 °C
Storage
232GB Samsung SSD 860 EVO 250GB (SATA (SSD)) 27 °C
929GB Microsoft Storage Space Device (TMax (SSD))
Optical Drives
ASUS DRW-24D5MT
Audio
Périphérique High Definition Audio
Voilà et merci d'avance !