Comme ça ?
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-K
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8530100224 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 07/10/2016 14:07:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100716-4125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x9F (0x3, 0xFFFFC282102093B0, 0xFFFFF800A4B84960, 0xFFFFC282152AE2A0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 Fri 07/10/2016 14:07:43 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: 0x9F (0x3, 0xFFFFC282102093B0, 0xFFFFF800A4B84960, 0xFFFFC282152AE2A0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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
--------------------------------------------------------------------------------
2 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'ai regardé dans le journal j'ai pas vu d'erreurs qui serait responsable, il y en a pas eu juste avant le crash en tout cas
Message édité par chems21 le 13-10-2016 à 14:47:23
