Bonjour à tous, j'ai depuis quelques jours des bluescreens intempestifs sur mon PC.
 
Voici les specs de ce dernier:
 
 
Intel Core i7 6700K Cadencé à 4 GHz
ASRock Z170 Extreme4  
8 Go de mémoire totale de type DDR4 à 1.20 GHz
NVIDIA GeForce GTX 970
 
Du côté de WhoCrashed, on retrouve l'erreur notée dans le titre (mais pas que) :
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Sun 06.08.2017 13:28:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080617-5890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)  
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 06.08.2017 13:28:37 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)  
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 06.08.2017 13:20:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080617-15578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 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 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 06.08.2017 12:48:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080617-6546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)  
Bugcheck code: 0xA (0x12FE8, 0x2, 0x0, 0xFFFFF800FBA92F76)
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 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 05.08.2017 16:36:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080517-16171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)  
Bugcheck code: 0xA (0xD800000000, 0x2, 0x0, 0xFFFFF801650AFD9B)
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 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.  
 
 
--------
 
J'ai déjà fait un check mémoire avec memtest sans qu'il ne détecte de problème, ainsi qu'un chkdsk et un scannow, sans pour autant trouver de problème.  
J'ai supprimé certains programmes qui auraient pu provoquer ces bluescreens, sans que ça ne change le résultat. Après avoir fait (beaucoup) de recherches, j'ai trouvé que l'erreur était probablement dûe à des drivers, notemment le driver du CPU, mais tout est à jour (depuis mesdrivers) et aucun pilote ne manque à l'appel.
 
Si quelqu'un a une idée, je suis preneur.
 
Merci.
 
 

Par ailleurs, j'ai oublié de préciser qu'une fois sur deux mon PC fait un BS pour une autre raison (irql, kmode, etc.), mais c'est marqué dans le journal de WhoCrashed. Le PC a déjà réinstallé avec les pilotes fourni avec le CD de la cm puis mis à jour avec mesdrivers, sans succès

Les diags disent que c'est un problème de pilote.
Tu réinstalles Windows et tu laisses tout d'origine et tu regardes ce que ca donne.
Ensuite tu réinstalles des pilotes au fur et à mesure si c'est nécessaire mais progressivement pour connaitre celui qui peut poser problème.
Fais aussi une mise à jour de l'UEFI.

Ok, je vais faire ça, je te tiens au courant, thx

Hello, j'ai testé la réinstallation sous W10, pour le moment ça semble tenir, je te tiens au courant de l'évolution.
 
Comme je ne suis pas habitué à ce forum, pas de nouvelles, bonnes nouvelles !