Bonjour à tous !  
 
Voila !  j'ai un gros soucis avec ma machine et je n'arrive pas à savoir d'où ça vient !
 
Alors que tout allait bien depuis 1 ans 1/2, des BSOD se sont mis à apparaître sans modification de hardware.  
Dans un premier temps, un pote informaticien m'a testé le pc et m'a dit qu'il n'y avait aucun soucis au niveau de la RAM ni de la CM ni des Drivers et que cela venait certainement de mon Alim.
 
J'ai donc commandé une nouvelle alim et cela n'a rien changé au problème.
 
Les BSOD apparaissaient alors à n'importe quel moment de la journée par forcément lorsque j'étais en jeu ou sur des applications nécessitant beaucoup de ressources.
 
Je me suis donc décidé à réinstaller windows 7 et mes drivers proprement.
 
Hors, les BSOD se sont mis a devenir plus récurrents notamment lors du démarrage de windows une fois arrivé sur le desktop.
 
J'ai testé la ram via MemtestX86 et effectivement il y avait un soucis sur une barrette de RAM.
 
J'ai testé les RAM séparément et j'ai enlevé la RAM défaillante.
 
J'ai refais un test sur la barrette restante et tout était OK, sauf que ça n'a pas résolu le problème... J'ai même rétabli les valeurs de base du BIOS, mais rien n'y fais !
 
Toujours des BSOD à n'en plus finir sans forcément de rapport les uns avec les autres... Mes drivers sont a jour ainsi que la dernière version du BIOS.
 
J'ai pensé que cela pouvait venir de la barette de RAM restante passée pourtant par un test positif sous MemTestX86...
 
Voici ma config :  
 
CM :ASROCK 970 EXTREME 3
CPU : PHENOM II X 4 965 BE
CG : MSI GeForce GTX 770 Twin Frozr OC GAMING, 2 Go
RAM : G.Skill Kit Extreme3 2 x 4 Go PC12800 ARES CAS9
DD : Western Digital WD Blue 3,5" - SATA III 6 Gb/s - 500 Go (Caviar)  
ALIM : Be Quiet ! Alimentation Pure Power L8-730W CM 80PLUS Bronze
 
Je vous link les rapports de whocrashed et si quelqu'un a des solutions... MERCI D'AVANCE !!! :  
 
DUMP FILES :  
 
System Information (local)
--------------------------------------------------------------------------------
 
computer name: JEREEKO-MC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Extreme3
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4267495424 total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Thu 09/04/2015 10:54:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-43727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
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 Thu 09/04/2015 10:54:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbfilter.sys (usbfilter+0x1ACB)  
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbfilter.sys
product: AMD USB Filter Driver
company: Advanced Micro Devices
description: AMD USB Filter Driver
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.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: usbfilter.sys (AMD USB Filter Driver, Advanced Micro Devices).  
Google query: Advanced Micro Devices DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Thu 09/04/2015 10:48:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
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 Thu 09/04/2015 10:46:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-24835-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xD1 (0x4, 0x2, 0x8, 0x4)
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 Thu 09/04/2015 10:43:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-25131-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
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 Thu 09/04/2015 10:41:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-25038-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xD1 (0xFFFFD8162593E1C7, 0x2, 0x8, 0xFFFFD8162593E1C7)
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 Wed 08/04/2015 15:06:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-27658-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1719A0)  
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Wed 08/04/2015 15:05:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-25038-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)  
Bugcheck code: 0xD1 (0x400, 0x2, 0x8, 0x400)
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 Wed 08/04/2015 15:03:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-24398-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)  
Bugcheck code: 0xD1 (0x624E4D43, 0x2, 0x8, 0x624E4D43)
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 Tue 07/04/2015 08:28:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040715-21278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)  
Bugcheck code: 0xD1 (0xFFFFF87FFD9BD4B4, 0x2, 0x1, 0xFFFFFA80058A21B0)
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.  
 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
20 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:  
 
usbfilter.sys (AMD USB Filter Driver, Advanced Micro Devices)
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
 
 
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 keos !
 
J'ai oublié de préciser que j'ai une carte audio externe Native Instrument Klompete audio 6 également (branchée en usb).
 
J'ai bien vu le résultat mais.... ou trouver ce driver manquant ? j'ai cherché sur le net mais pas de réponses pertinentes pour le moment.
 
 

Bon, je viens de reinstaller le package AMD all in 1 sur le site de la CM AsRock... Nous verrons bien, logiquement il y a un usbfilter.sys tout propre dedans.
 
Je tiens au courant de l'avancée ! (merci a toi Keos )

Ce que tu peux encore faire :
 
Un test du HD avec HD tune, pour voir si il y a pas des secteurs défectueux (je doute que ça puisse générer un BSOD, mais sait-on jamais).  
 
Enlève la carte graphique, et utilise la sortie vidéo de la carte mère, ça utilisera l'IGP du CPU, tu pourras toujours jouer, mais en low.  
 
Assure toi que TOUS tes drivers proviennent des sites des fabriquant, touesdrivers.com est à proscrire.