Bonjour à tous,
Depuis quelques semaines, je rencontre un problème avec des BSOD qui surviennent de façon totalement aléatoire, parfois après 3-4 heures, parfois plus. Ces écrans bleus surviennent parfois en jeu, d'autres fois sur youtube ou sur internet, ou même sans aucune raison (j'ai laissé mon ordinateur allumé cette nuit pour tester, sans aucune activité, et un crash a eu lieu vers 7 heure ce matin).
Je précises que j'ai reformaté le week-end dernier mais que rien n'y fait. Après quelques recherches, il semblerait que ces problèmes soit liés à des drivers. J'ai essayé de tout réinstaller, analyse malware-bytes, fait un memtest en 8 passes pendant environ 6h, changé de carte graphique et même de processeur, rien n'y fait. Je précise également que je n'avais pas ces problèmes lorsque j'étais sous Windows 7, ils sont apparus quelques temps après la mise à jour sur Windows 10. J'ai installé Win10 vers mi-février cette année et les problèmes sont arrivés début mars.
Ma configuration étant la suivante :
Processeur : Intel Core i5-4590 @ 3.30GHz
Carte graphique : NVIDIA GeForce GTX 770
Carte mère : MSI Z87-G45 Gaming
RAM : GSkill - 1600MHz - 16Go
Voici les rapports de crashs effectués grâce à WhoCrashed :
On Mon 18/04/2016 07:03:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041816-3750-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80241C7B54E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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/04/2016 17:57:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041716-3921-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000!FxObject::RemoveChildObjectInternal+0x27)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8033E2375D9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 a standard 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.
On Sat 16/04/2016 13:59:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041616-3953-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8020EDC56B8, 0xFFFFD000222C49C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Sat 16/04/2016 00:11:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041616-3765-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8027E64FFAA, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
--------------------------------------------------------------------------------
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.
Merci d'avance pour votre aide !
