[BSoD] IRQL_NOT_LESS_OR_EQUAL [Windows 10] [Résolu/Fermé]

Bonjour tout le monde !
Ça fait plusieurs jours que j'ai ce problème , des que je lance un gros truc (Photoshop par exemple) ou que je joue à un gros jeux , mon PC crash et affiche "IRQL_NOT_LESS_OR_EQUAL".
J'ai chercher sur plusieurs forums , désespérément en espérant trouver le problème.
Mais la ça commence vraiment à être gênant , sachant que j'ai le bac dans quelques mois , j'aimerais pas que mon PC crash à vie ...
Il faut savoir que mon PC crash depuis que je l'ai envoyé chez l'informaticien (j'avait un soucis de disque dur). Tous mes drivers sont a jours.

Voici ce que m'affiche WhoCrashed :

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 26/02/2017 14:27:00 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 (0xFFFF8101E0B27E28, 0x2, 0x1, 0xFFFFF803289D7864)
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 Sun 26/02/2017 14:22:19 your computer crashed
crash dump file: C:\Windows\Minidump\022617-28390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFD200C7F6DE28, 0x2, 0x1, 0xFFFFF802447C4864)
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.


Si quelqu'un peux me sauver svp