This is your minidump....
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 0081990a, The address that the exception occurred at
Arg3: eec7aa18, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+81990a
0081990a ?? ???
TRAP_FRAME: eec7aa18 -- (.trap ffffffffeec7aa18)
ErrCode = 00000000
eax=0081990a ebx=e285a5f8 ecx=eec7abf4 edx=00000000 esi=eec7aab0 edi=00000000
eip=0081990a esp=eec7aa8c ebp=eec7acac iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
0081990a ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf819c90 to 0081990a
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
eec7aa88 bf819c90 eec7abf4 eec7b03c eec7ad50 0x81990a
eec7acac bf8176b3 e285a5e8 e205a010 e28bf5a4 win32k!EngTransparentBlt+0x326
eec7acf4 bf817d1a e1bde010 e205a010 e28bf5a4 win32k!SURFREFAPI::SURFREFAPI+0x11f
eec7ad80 bf81797a e285a5f8 e1bde010 e28bf5a4 win32k!SURFREFAPI::SURFREFAPI+0x38d
eec7ade0 bf817ea6 e285a5f8 e1bde010 e28bf5a4 win32k!EngNineGrid+0x6e
eec7ae3c bf818300 e285a5f8 e1bde010 e28bf5a4 win32k!EngDrawStream+0xc5
eec7aea0 bf8186e7 eec7afc4 e28bf5a4 e1bde000 win32k!NtGdiDrawStreamInternal+0x1ff
eec7afc8 bf817f8b 06010a20 00000000 00000000 win32k!GreDrawStream+0x4ff
eec7b110 804de7ec 06010a20 00000060 0113e748 win32k!NtGdiDrawStream+0x9f
eec7b110 7c8feb94 06010a20 00000060 0113e748 nt!KiFastCallEntry+0xf8
0113e6c4 00000000 00000000 00000000 00000000 0x7c8feb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!EngTransparentBlt+326
bf819c90 33ff xor edi,edi
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!EngTransparentBlt+326
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58
FAILURE_BUCKET_ID: 0x8E_win32k!EngTransparentBlt+326
BUCKET_ID: 0x8E_win32k!EngTransparentBlt+326
Followup: MachineOwner
---------
I'm having the same issue. Havent found a solution to fix mine yet.