Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\UserName\Desktop\MINIDUMPS\052517-4875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`42804000 PsLoadedModuleList = 0xfffff800`42b505a0
Debug session time: Thu May 25 16:50:32.277 2017 (UTC - 4:00)
System Uptime: 0 days 0:00:19.942
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
BugCheck C9, {220, fffff80b11351f30, ffffef815380eca0, ffff8883a327f040}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
	This IRP should either have been completed earlier or should have been passed
	down.
Arg2: fffff80b11351f30, The address in the driver's code where the error was detected.
Arg3: ffffef815380eca0, IRP address.
Arg4: ffff8883a327f040, ProviderId.

Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING:  10.0.15063.296 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER:  System manufacturer
SYSTEM_PRODUCT_NAME:  System Product Name
SYSTEM_SKU:  SKU
SYSTEM_VERSION:  System Version
BIOS_VENDOR:  American Megatrends Inc.
BIOS_VERSION:  3401
BIOS_DATE:  03/15/2017
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT:  Z170 PRO GAMING
BASEBOARD_VERSION:  Rev X.0x
DUMP_TYPE:  2
BUGCHECK_P1: 220
BUGCHECK_P2: fffff80b11351f30
BUGCHECK_P3: ffffef815380eca0
BUGCHECK_P4: ffff8883a327f040
BUGCHECK_STR:  0xc9_220
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP:
HIDCLASS!HidpMajorHandler+0
fffff80b`11351f30 488bc4          mov     rax,rsp

FOLLOWUP_IP:
HIDCLASS!HidpMajorHandler+0
fffff80b`11351f30 488bc4          mov     rax,rsp

IRP_ADDRESS: ffffef815380eca0
DEVICE_OBJECT: ffff8883a0586060
DRIVER_OBJECT: ffff8883a3fd8930
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAULTING_MODULE: fffff80044f70000 SaiMini
CPU_COUNT: 4
CPU_MHZ: db0
CPU_VENDOR:  GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: A0'00000000 (cache) A0'00000000 (init)
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
CURRENT_IRQL:  2
ANALYSIS_SESSION_HOST:  UserName-PC
ANALYSIS_SESSION_TIME:  05-26-2017 13:26:13.0735
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800428729dd - nt!MmAccessFault+d5d
	[ f6:87 ]
    fffff80042886ea3 - nt!MiIssueHardFault+233 (+0x144c6)
	[ f6:87 ]
    fffff8004289677b-fffff8004289677c  2 bytes - nt!MiInitializeTransitionPfn+27 (+0xf8d8)
	[ 80 fa:00 f2 ]
    fffff800428a8077 - nt!KiExpandKernelStackAndCalloutOnStackSegment+167 (+0x118fc)
	[ f6:87 ]
    fffff800428a80a6-fffff800428a80a7  2 bytes - nt!KiExpandKernelStackAndCalloutOnStackSegment+196 (+0x2f)
	[ 80 fa:00 f2 ]
    fffff800428a80fa-fffff800428a80fb  2 bytes - nt!KiExpandKernelStackAndCalloutOnStackSegment+1ea (+0x54)
	[ 80 fa:00 f2 ]
    fffff8004290c336-fffff8004290c337  2 bytes - nt!MiReadyFlushMdlToWrite+2e (+0x6423c)
	[ 80 fa:00 f2 ]
    fffff80042a18abc - nt!MiLogNonPagedPoolReleaseEvent+28 (+0x10c786)
	[ f6:87 ]
12 errors : !nt (fffff800428729dd-fffff80042a18abc)

MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
MEMORY_CORRUPTOR:  LARGE
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
BUCKET_ID:  MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE
TARGET_TIME:  2017-05-25T20:50:32.000Z
OSBUILD:  15063
OSSERVICEPACK:  296
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK:  272
PRODUCT_TYPE:  1
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID:  0
OSBUILD_TIMESTAMP:  2017-04-27 19:52:30
BUILDDATESTAMP_STR:  160101.0800
BUILDLAB_STR:  WinBuild
BUILDOSVER_STR:  10.0.15063.296
ANALYSIS_SESSION_ELAPSED_TIME: 16c5
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:memory_corruption_large
FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------