So my comp keeps crashing everytime i try to play a game. Blue screen with DRIVER_IRQL_NOT_LESS_OR_EQUAL

Question

So i read that i can post a link to show my minidump files for people to see whats wrong. The link is here
https://onedrive.live.com/redir?resid=88FC768A03F5745A%21295
If someone could get back to me asap and let me know what i need to do to fix this that would be great thanks.

Answer 1

9csc1
These were virtually all related to your Driver for Intel Graphics Adapter.  I would install the newest driver available as a first step
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\061014-17750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Users\Ken\Desktop
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Users\Ken\Desktop
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff800`3027b000 PsLoadedModuleList = 0xfffff800`305452d0
Debug session time: Tue Jun 10 16:47:33.874 2014 (UTC - 4:00)
System Uptime: 0 days 2:29:19.667
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff80038e84c47}
*** 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+62c47 )
Followup: MachineOwner
0: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80038e84c47, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800305cf138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000028
CURRENT_IRQL: 2
FAULTING_IP:
igdkmd64+62c47
fffff800`38e84c47 83782802 cmp dword ptr [rax+28h],2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: dwm.exe
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: ffffd0002250dbc0 -- (.trap 0xffffd0002250dbc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00144f37e68
rdx=ffffe00147044b70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80038e84c47 rsp=ffffd0002250dd50 rbp=ffffe00147047010
r8=ffffe00140053270 r9=00000000ffffffff r10=0000000000000002
r11=ffffd0002250dd48 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
igdkmd64+0x62c47:
fffff800`38e84c47 83782802 cmp dword ptr [rax+28h],2 ds:00000000`00000028=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800303daae9 to fffff800303cefa0
STACK_TEXT:
ffffd000`2250da78 fffff800`303daae9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2250da80 fffff800`303d933a : 00000000`00000000 00000000`93bc0000 00000000`00000000 ffffd000`2250dbc0 : nt!KiBugCheckDispatch+0x69
ffffd000`2250dbc0 fffff800`38e84c47 : ffffe001`44528000 00000000`00000002 ffffe001`44f37000 00000000`ffffffff : nt!KiPageFault+0x23a
ffffd000`2250dd50 ffffe001`44528000 : 00000000`00000002 ffffe001`44f37000 00000000`ffffffff ffffe001`40053270 : igdkmd64+0x62c47
ffffd000`2250dd58 00000000`00000002 : ffffe001`44f37000 00000000`ffffffff ffffe001`40053270 00000000`00000000 : 0xffffe001`44528000
ffffd000`2250dd60 ffffe001`44f37000 : 00000000`ffffffff ffffe001`40053270 00000000`00000000 ffffe001`44f37000 : 0x2
ffffd000`2250dd68 00000000`ffffffff : ffffe001`40053270 00000000`00000000 ffffe001`44f37000 00000000`00000000 : 0xffffe001`44f37000
ffffd000`2250dd70 ffffe001`40053270 : 00000000`00000000 ffffe001`44f37000 00000000`00000000 ffffe001`40053288 : 0xffffffff
ffffd000`2250dd78 00000000`00000000 : ffffe001`44f37000 00000000`00000000 ffffe001`40053288 ffffc000`fed6f302 : 0xffffe001`40053270
STACK_COMMAND: kb
FOLLOWUP_IP:
igdkmd64+62c47
fffff800`38e84c47 83782802 cmp dword ptr [rax+28h],2
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: igdkmd64+62c47
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52379d96
FAILURE_BUCKET_ID: AV_igdkmd64+62c47
BUCKET_ID: AV_igdkmd64+62c47
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_igdkmd64+62c47
FAILURE_ID_HASH: {e3d07e26-2f02-07d7-4e5b-3db83ddd8cd4}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag