Ecran Bleu (BSOD) à répétition, que faire ?

Bonjour à tous. (je sais pas si je suis au bon endroit par contre...)

Voilà depuis quelques temps lorsque je joue à un jeu (FIFA 13 par exemple) et même parfois lorsque je regarde un film en plein écran, l'ordinateur redémarre suite à un écran bleu brusquement.

Lorsque les premiers BSOD sont apparu, j'en ai profité pour réinstaller Win7 + les drivers nécessaire en pensant que ça irait mieux.

Hélàs, j'ai juste installer FIFA13 et dès le deuxième match ça a recommencer.

_IRQL_NOT_LESS_OR_EQUAL
_DRIVER_IRQL_NOT_LESS_OR_EQUAL
_KMODE_EXCEPTION_NOT_HANDLED
_MEMORY_MANAGEMENT
_DRIVER_IRQL_NOT_LESS_OR_EQUAL
_SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
_SYSTEM_SERVICE_EXCEPTION
_SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Voilà chronologiquement les BSOD depuis que j'ai réinstaller Win7. (rapport WC ci dessous.)

Merci d'avance à ceux qui pourront m'aider. :)

------------------------------------------------------------------

Précisément (via logiciel "WhoCrashed):

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 26/03/2013 22:10:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032613-36816-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002D3D94B)
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 Tue 26/03/2013 22:10:12 GMT 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: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002D3D94B)
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 Sat 16/03/2013 23:29:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031713-20950-01.dmp
This was probably caused by the following module: wn111v2w7x.sys (WN111v2w7x+0x39255)
Bugcheck code: 0xD1 (0x30488922, 0x2, 0x1, 0xFFFFF88006C72255)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wn111v2w7x.sys
product: Driver for Atheros OTUS Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device 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: wn111v2w7x.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 06/03/2013 21:45:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-22791-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 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 Wed 06/03/2013 20:53:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-25771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 04/03/2013 22:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030413-20514-01.dmp
This was probably caused by the following module: wn111v2w7x.sys (0xFFFFF8800811809A)
Bugcheck code: 0xD1 (0xFFFFF88009197530, 0x2, 0x0, 0xFFFFF8800811809A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wn111v2w7x.sys
product: Driver for Atheros OTUS Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device 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: wn111v2w7x.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 04/03/2013 22:13:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030413-20826-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003F3ECEE, 0xFFFFF88001F3B6A8, 0xFFFFF88001F3AF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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 04/03/2013 20:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030413-26754-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x82004)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C2004, 0xFFFFF88002E191A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 23/02/2013 11:28:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022313-30950-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880045B7CEE, 0xFFFFF880009CC6A8, 0xFFFFF880009CBF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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.