System Information (local)
--------------------------------------------------------------------------------

Computer name: JOSH-PC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., Z170-A
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8525860864 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 5/20/2017 10:45:06 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052017-6515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803A69EDE17, 0xFFFFBF817B9B1E48, 0xFFFFBF817B9B1680)
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 5/20/2017 10:45:06 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!FsbAllocateAtDpcLevel+0x67)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803A69EDE17, 0xFFFFBF817B9B1E48, 0xFFFFBF817B9B1680)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Sat 5/20/2017 3:22:24 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052017-6953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable 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.
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 5/20/2017 12:57:54 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052017-6375-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0x5A564)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFA0D933A8A564, 0xFFFFC881AE26DC90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 Sat 5/20/2017 3:17:56 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052017-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1 (0x72CD21CC, 0x0, 0xFFFF, 0xFFFFBD81B88ABB00)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

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