Blue Screen [dxgkrnl.sys] au démarrage

Bonjour, malgré mes recherches, je suis dépourvu de toutes solutions, je m'en remet donc à toi, l'internaute qui saura comprendre ma peine :)
Je vais essayer d'être le plus clair et concis possible, pour faciliter l'échange et la lecture. Merci d'avance de ton aide !

• Je dispose d'un ordinateur qui a 5 ans, fabriqué par un ami qui travail dans l'informatique, je n'avais jusqu'alors eu aucun soucis avec cet ordinateur.
• Le mois dernier, lors des bugs liés au driver Nvidia des cartes GTX, mon ordinateur a été touché. Après que Nvidia est retiré ce pilote, tout allait pour le mieux. Mais voilà, cette semaine le problème est revenu, lorsque je jouais à League Of Legends, un jeu peu gourmand pourtant.
• Il m'est impossible de démarrer mon ordinateur, puisque le blue screen apparait après l'affichage du logo windows. Pourtant, le mode sans échec marche sans problème.
• Ce n'est certainement pas un soucis de virus, j'ai utilisé rogue killer, ccleaner, adwcleaner, aucun soucis détecté, d'autant que je pense prendre soin de mon ordinateur
• J'ai testé la température de mes composants, tout va bien.
• J'ai essayer tout ce que me proposait windows: réparation du démarrage, une restauration systeme, sans succès.
• J'aurais souhaiter désinstaller le possible nouveau driver qui s'est installé, mais je n'ai pas trouvé comment le faire depuis le mode sans échec.
• J'ai cherché tout ce qui aurait pu résoudre mes problèmes, d'après ce que me disait WhoCrashed, sans succès non plus. Je suis donc à un point où je ne trouve plus de solutions.

Voici les résultats des derniers crashes par WhoCrashed. Par ailleurs, je dispose d'une carte graphique Nvidia GeForce GTX 560

Computer name: ADRIEN-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8H61-M PRO
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4275281920 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 02/04/2016 12:43:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040216-24133-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D140)
Bugcheck code: 0x116 (0xFFFFFA8005E6F010, 0xFFFFF88004997E30, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR



On Sat 02/04/2016 12:43:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214)
Bugcheck code: 0x116 (0xFFFFFA8005E6F010, 0xFFFFF88004997E30, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR



On Sat 02/04/2016 12:43:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040216-19624-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sat 02/04/2016 08:38:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040216-23056-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF8000365ECC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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. 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:

dxgkrnl.sys (DirectX Graphics Kernel, Microsoft Corporation)



Merci a toi, mon sauveur.