Bonjour,
Je vais directement expliquer mon problème et je m'excuse par avance pour les fautes d'orthographe.
Depuis quelque jour, après avoir démarré un jeu mon ordinateur commence a freez et à planter pour aucune raison, voir même blue screen(uniquement en jouant). comme dans le titre je vous envoie la raison de mon crash.
 
On Wed 02/10/2019 18:08:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100219-4062-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF80899432E48)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80899432E48, 0xFFFFCB0BFC8CF7F8, 0xFFFFCB0BFC8CF040)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms2.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 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.  
 
Si quelqu'un connais la raison et peux me sauver ça serais génial...

Bon je viens de finir une recherche avec une invite de commande et j'ai des fichier corrompus mais je sais pas comment m'en sortir...

Cela viens de windows defender d'après l'analyse mais il me faudrait de l'aide  
je vous poste une de mes 10 erreurs ...
2019-10-02 18:21:00, Info                  CSI    00004e8f [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-10-02 18:21:00, Info                  CSI    00004e90 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.

Toujours de nouvelle erreur plus incompréhensible ... si quelqu'un s'y connait, merci d'avance.
 
On Thu 03/10/2019 19:39:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100319-4515-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80344686E46)  
Bugcheck code: 0xD1 (0xFFFFB687929121E0, 0x2, 0x0, 0xFFFFF80344686E46)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.  
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.  
The crash took place in a 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 03/10/2019 19:39:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: netio.sys (0xFFFFF80344686E46)  
Bugcheck code: 0xD1 (0xFFFFB687929121E0, 0x2, 0x0, 0xFFFFF80344686E46)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.  
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.  
The crash took place in a 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.  

Toutes ces erreurs sont très disparates et ne pointent aucun problème en particulier.
Du coup ça pourrait venir d'un problème au niveau OS (que la commande SFC n'arrive pas à corriger visiblement) ou matériel (typiquement un composant "central" comme la carte mère).
 
Tu peux aussi tester tes disques avec CrystalDiskInfo et HDTune ainsi que ta mémoire avec memtest.
Même si j'y crois moyen...
 
Sinon vu que l'OS ne s'en sort pas, je te dirai bien de tenter une réinitialisation de Windows en conservant tes données (en ayant fait un backup au préalable).