Ecrans bleus intempestifs

Rebonjour, merci pour la réponse ! J'ai fait un analyze sur Whocrashed et j'ai ça :

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 27/11/2016 12:37:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112716-4859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x139 (0x3, 0xFFFFC4809A55B330, 0xFFFFC4809A55B288, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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/11/2016 12:37:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112716-13703-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 Sun 27/11/2016 12:37:58 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!WfpAssociateContextToFlow+0x1109)
Bugcheck code: 0x139 (0x3, 0xFFFFC4809A55B330, 0xFFFFC4809A55B288, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: The kernel has detected the corruption of a critical data structure.
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/11/2016 12:37:12 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112716-4875-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 Sun 27/11/2016 12:34:28 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112716-13593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x139 (0x3, 0xFFFFB900924BCD30, 0xFFFFB900924BCC88, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 5 are included in this report. 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 375.95 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Désolée je savais pas ce qu'il fallait que je poste exactement.
Merci de l'aide :)