System Information (local)
--------------------------------------------------------------------------------
Computer name: SKYGIN_TOMV4-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7821, MSI, Z87-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17121091584 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 31/05/2016 16:27:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053116-14024-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x4A (0x76F9BBAA, 0x2, 0x0, 0xFFFFF88008BA2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 31/05/2016 16:27:10 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: 0x4A (0x76F9BBAA, 0x2, 0x0, 0xFFFFF88008BA2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 22/05/2016 20:20:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052216-14414-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800F20D6D0, 0xFFFFF80000B9A3D8, 0xFFFFFA801206B280)
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 Sat 21/05/2016 20:55:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052116-13431-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800F20E360, 0xFFFFF80000B9A3D8, 0xFFFFFA80124AC610)
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 Tue 17/05/2016 20:44:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051716-13696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800F10F6C0, 0xFFFFF80000B9A3D8, 0xFFFFFA80136123A0)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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.