Ecran bleu

Salut Pierre,

Voici un rapport effectué par le logiciel WhoCrashed. Je ne sais pas si se sera suffisant mais je le joins quand même: file:///D:/T%C3%A9l%C3%A9chargements/WhoCrashedOutput.htm

J'ai page introuvable

Aie bon je te donne un copié-collé:

Computer name: FABRICE-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170-K
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17107628032 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 7/01/2016 15:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-6208-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC61BF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001261BF, 0xFFFFF8800D560F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 7/01/2016 15:09:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xD3CB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001261BF, 0xFFFFF8800D560F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 6/01/2016 13:27:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010616-6630-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C7F8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034387F8, 0xFFFFF880039637A8, 0xFFFFF88003963000)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.

J'ajoute que j'ai fais un test de mémoire RAM et que tout est ok de ce coté.

https://support.microsoft.com/en-us/windows/resolving-stop-blue-screen-errors-in-windows-7-4460e54f-ca4c-df7e-1c75-e4fa492ff7d2

Fait tout ça.
Et recherche en parrallèle:
0x1000007E
0xC0000005, 0xFFFFF960001261BF, 0xFFFFF8800D560F80
0xC0000005, 0xFFFFF960001261BF, 0xFFFFF8800D560F80

Ce sont tes codes d'erreur.