Problème avec ntkrnlmp.exe

Bonjour
Il y a 1 semaine j'ai fait l'achat d'une nouvelle config:
Carte mère: Asrock 970A-G/3.1
CPU: AMD fx-8350
GPU: Sapphire Radeon R9 390 niro black plate 8 go gddr5
Alimentation: FSP raider 750W
Disque dur: Western Digital purple 1to
Ventirad: Hyper TX3 evo
RAM: kingston hyperX fury 2 * 4go 1866mhz

Alors voila, mon problème est qu'au bout d'un certain temps mon pc freeze et je ne peut plus rien faire (il freeze que quelque fois lorsque je ne fait rien mais tout le temps lorsque je lance un jeux au bout de 5 à 10min) et me met même parfois des bsod. J'ai alors décidé d'utiliser le logiciel WhoCrashed et voici sont rapport:

Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 23/04/2016 15:46:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042316-14781-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xFC (0xFFFFD001C77D6180, 0x8000000000654963, 0xFFFFD000208B2790, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 23/04/2016 15:46:32 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: 0xFC (0xFFFFD001C77D6180, 0x8000000000654963, 0xFFFFD000208B2790, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 23/04/2016 10:14:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042316-13156-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGCONTEXT::SubmitCommand+0x1BA)
Bugcheck code: 0x19 (0x23, 0x4, 0x0, 0xFFFFE0015603D000)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 22/04/2016 06:23:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042216-14046-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0xFFFFE00067EB7F20, 0xFFFFE0006840ABB0, 0x1, 0x2)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 20/04/2016 19:38:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042016-22453-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF801DD09C401)
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 Wed 20/04/2016 19:19:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042016-23125-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800B4D03401)
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.


Il se trouve que presque à chaque fois c'est un erreur venant du module ntkrnlmp.exe Donc si quelqu'un aurait une solution je serais ravis de la savoir.
(je tient a précisé que je suis sur que tout les drivers de carte graphique sont a jour et que ma carte monte jusqu’à 60° en jeux).