BSOD à répétition et à court d'idées

Bonjour, à tous ^^

Comme indiqué dans le titre, je suis l'une des nombreuses victimes de BSOD à répétition ... et j'avoue avoir essayé tout ce qui me passait par la tête pour tenter de le régler.

Globalement, j'ai récemment installé du nouveau matériel (Carte mère et Processeur de type AMD) et depuis, il enchaîne les Ecrans bleus de manière complètement aléatoire (Je peux faire deux fois la même action, le BSOD ne se déclenche pas forcément sur le coup, mais plus tard sans réelle logique)

J'ai essayé plusieurs logiciels pour tout mettre à jour (DriverCloud, FileHippo.AppManager, Catalyst auto, etc). J'ai même changé mon alimentation, pensant reconnaître les signes d'une alim défaillante, mais ça n'a rien changé non plus. (Malgré le fait qu'à présent, les deux seuls choses qui soient d'origine dans cet ordinateur soit la barète RAM (Vérifiée aussi) et ma carte graphique.

J'ai été voir un peu partout pour trouver une solution à ce problème qui dure depuis plus d'un mois, mais ... rien n'y fait et je commence à désespérer.

Voilà ma config actuelle :

Systeme d'Exploitation : Windows 7 Ultimate, 6.1.7601 Service Pack 1 7601

Carte mère : Gigabyte F2A88XM-HD3
Chipset : Family 15h (Models 30h-3fh) Processor Root Complex
Processeur : AMD A8-7670K Radeon R7 10 Compute Core 4C+6G, 3600 Mhz, 2 Core
Carte Graphique : NVIDIA GeForce GT630

Voici les derniers rapports de "Whocrashed"

On Sat 17/10/2015 10:51:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-20857-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF880055B0483)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF880055B0483)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.
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 17/10/2015 10:51:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15483)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF880055B0483)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.
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 Fri 16/10/2015 23:22:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-20826-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72680)
Bugcheck code: 0xA (0xFFFFF88032765E80, 0x2, 0x0, 0xFFFFF80003302C0C)
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 Fri 16/10/2015 19:41:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101615-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7C296)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800032D2296, 0xFFFFF880033CB938, 0xFFFFF880033CB190)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Thu 15/10/2015 23:12:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101615-21512-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF88004745483)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF88004745483)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.
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 Thu 15/10/2015 22:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101615-21824-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72680)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xC050004, 0xFFFFFA80075C5DD0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 15/10/2015 21:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101515-21262-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7027)
Bugcheck code: 0x10D (0x6, 0x3, 0x57FFA739188, 0xFFFFFA8005283770)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Tue 13/10/2015 19:11:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-19999-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8801253E4D2)
Bugcheck code: 0xD1 (0x58, 0x9, 0x0, 0xFFFFF8801253E4D2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Mon 12/10/2015 19:19:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101215-22386-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF88004415483)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF88004415483)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.
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 Mon 12/10/2015 17:40:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101215-21574-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72680)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003592128, 0xFFFFF88007B24EE0, 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.

D'avance, je vous remercie de vos réponses :)