EL
This was related to your Driver for Intel Graphics Adapter. I would remove the current driver and then install the newest driver available (yours is from 2013) and probably corrupt
Other old drivers needing updating
MBfilt64.sys 7/30/2009 10:40:32 PM
winio64.sys 6/3/2010 11:08:03 PM
SASKUTIL64.SYS 7/12/2011 4:00:01 PM
SASDIFSV64.SYS 7/21/2011 6:03:00 PM
NTIOLib_X64.sys 10/25/2012 5:27:58 AM
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\030715-26421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff803`56810000 PsLoadedModuleList = 0xfffff803`56ae9250
Debug session time: Sat Mar 7 20:03:03.561 2015 (UTC - 5:00)
System Uptime: 4 days 23:50:53.286
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 1, fffff801b5528b5f}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+b4b5f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff801b5528b5f, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80356b73138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
igdkmd64+b4b5f
fffff801`b5528b5f 488901 mov qword ptr [rcx],rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: Vindictus.exe
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME: ffffd0006b6fcf30 -- (.trap 0xffffd0006b6fcf30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe0011ef127d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801b5528b5f rsp=ffffd0006b6fd0c0 rbp=ffffd0006b6fd101
r8=ffffe0011ef2db40 r9=0000000000001000 r10=ffffd0006f001de0
r11=ffffd0006b6fd128 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
igdkmd64+0xb4b5f:
fffff801`b5528b5f 488901 mov qword ptr [rcx],rax ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8035696c4e9 to fffff803569609a0
STACK_TEXT:
ffffd000`6b6fcde8 fffff803`5696c4e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`6b6fcdf0 fffff803`5696ad3a : 00000000`00000001 ffffe001`1ef2db40 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`6b6fcf30 fffff801`b5528b5f : 00000000`00000000 ffffd000`6b6fd101 ffffe001`1fc87000 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`6b6fd0c0 00000000`00000000 : ffffd000`6b6fd101 ffffe001`1fc87000 00000000`00000000 00000000`00000000 : igdkmd64+0xb4b5f
STACK_COMMAND: kb
FOLLOWUP_IP:
igdkmd64+b4b5f
fffff801`b5528b5f 488901 mov qword ptr [rcx],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: igdkmd64+b4b5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52b20a48
FAILURE_BUCKET_ID: AV_igdkmd64+b4b5f
BUCKET_ID: AV_igdkmd64+b4b5f
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_igdkmd64+b4b5f
FAILURE_ID_HASH: {fcd16fe4-87dc-ccae-fe29-f4cb21371e64}
Followup: MachineOwner
---------