Ecran bleu, Crash Dump

Bonjour,
Lorsque je me sers de mon pc, il m'arrive d'avoir des écrans bleu. Ils interviennent souvent quand je joue, mais aussi simplement quand je suis sur internet.

J'ai mis tout les drivers a jours (par le CD fourni avec la carte mere, et par DriverCloud et par les sites constructeurs)

Le pc ne chauffe pas, je surveille la température par plusieurs logiciels et mon processeur ne dépasse pas les 15°

Tout le matériel est compatible et bien installé (pas de RAM mal branchée etc)

J'ai monté le pc moi même,il fonctionne depuis 3 semaines et rencontre ces problèmes depuis le début.

Ma configuration: ASRock Fatal1ty 970 / AMD FX 9590 4.7GHz / Kingston Hyper X 4x4Go / MSI Geforce GTX 770

L’écran bleu :





Le resultat de WhoCrashed :
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 29/12/2015 19:11:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-51558-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1AAD57)
Bugcheck code: 0xA (0x4740, 0x2, 0x1, 0xFFFFF80003084827)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.43
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.43
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.43 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Tue 29/12/2015 19:11:51 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 (0x4740, 0x2, 0x1, 0xFFFFF80003084827)
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 27/12/2015 21:28:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-50216-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x4957)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000C04957, 0xFFFFF88003385858, 0xFFFFF880033850B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 Sun 27/12/2015 20:36:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-63679-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800030DCB8F)
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 Sun 27/12/2015 11:32:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-59982-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xC5 (0x1024, 0x2, 0x1, 0xFFFFF800031C85A5)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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 Sun 27/12/2015 01:18:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-55442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F42180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 27/12/2015 00:14:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-40575-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800030808C5, 0xD, 0xFFFFFA800F8CFB00)
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 Sat 26/12/2015 20:19:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122615-48032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x50 (0xFFFFF88005422268, 0x0, 0xFFFFF800030D1141, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 26/12/2015 17:04:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122615-33181-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800030D45E2)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 26/12/2015 16:28:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122615-49982-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800007F8A0, 0xE5D00001E06D3867, 0xFFFFF6800007FCA0)
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.



Un grand merci a ceux qui prendront le temps de lire et de m'aider a résoudre mon problème...