Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Laptop crashes when playing games.

  • Please log in to reply
1 reply to this topic

#1 Gosberg


  • Members
  • 1 posts
  • Local time:04:26 AM

Posted 26 July 2015 - 02:49 AM



So everytime I play certain games, such as fallout: new vegas, poker night at the inventory 2 or walking dead 2,

I always have PC crashes related to my driver IRQL being less or not equal (igdkmd64.sys)


My laptop model is: Acer E1-472G

Intel core 15-4200U

4GB Ram

Nvidea Gefore 820M

OS: Windows 8.1 Single Language 64 bit


However, I do notice that the system has been warning me of low memories. 


Memory dump:

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff800`b448d000 PsLoadedModuleList = 0xfffff800`b47549b0
Debug session time: Sun Jul 26 09:57:11.995 2015 (UTC + 8:00)
System Uptime: 0 days 18:47:35.728
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`32fde018).  Type ".hh dbgerr001" for details
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff80001cd9a17}
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+62a17 )
Followup: MachineOwner
3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80001cd9a17, address which referenced memory
Debugging Details:
READ_ADDRESS:  0000000000000028 
fffff800`01cd9a17 83782802        cmp     dword ptr [rax+28h],2
PROCESS_NAME:  dwm.exe
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
TRAP_FRAME:  ffffd00035c76f20 -- (.trap 0xffffd00035c76f20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00003d0ce68
rdx=ffffe00006b0d480 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001cd9a17 rsp=ffffd00035c770b0 rbp=ffffe00006b06920
 r8=ffffe00001d1abf0  r9=00000000ffffffff r10=0000000000000002
r11=ffffd00035c770a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`01cd9a17 83782802        cmp     dword ptr [rax+28h],2 ds:00000000`00000028=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800b45e8be9 to fffff800b45dd0a0
ffffd000`35c76dd8 fffff800`b45e8be9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`35c76de0 fffff800`b45e743a : 00000000`00000000 00000000`93380000 00000000`00000000 ffffd000`35c76f20 : nt!KiBugCheckDispatch+0x69
ffffd000`35c76f20 fffff800`01cd9a17 : ffffe000`004b8000 00000000`00000002 ffffe000`03d0c000 00000000`ffffffff : nt!KiPageFault+0x23a
ffffd000`35c770b0 fffff800`01c9366a : ffffd000`35c77201 00000000`93380000 ffffe000`ffffffff ffffe000`ffffffff : igdkmd64+0x62a17
ffffd000`35c77150 fffff800`018c00b6 : ffffe000`01b67bc0 ffffc000`02b5f000 00000000`00000001 fffff800`018c02cb : igdkmd64+0x1c66a
ffffd000`35c771a0 fffff800`018bfc88 : ffffd000`35c774a0 ffffd000`35c77230 00000000`00000001 ffffc000`02b5f000 : dxgkrnl!ADAPTER_RENDER::DdiCreateAllocation+0xba
ffffd000`35c771e0 fffff800`018c0f83 : ffffd000`35c774a0 ffffd000`35c774a0 ffffd000`35c77750 00000000`00000001 : dxgkrnl!DXGDEVICE::CreateDriverAllocations+0x10c
ffffd000`35c77270 fffff800`018bf864 : ffffc000`12bbab60 ffffc000`12bbab60 ffffd000`35c77b80 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0x463
ffffd000`35c77980 fffff800`b45e88b3 : 0000002f`0df9bfb0 ffffd000`35c77b00 ffffc000`0c53cc00 ffffc000`02b5f000 : dxgkrnl!DxgkCreateAllocation+0x404
ffffd000`35c77b00 00007ffb`6297138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000002f`0df9bed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`6297138a
fffff800`01cd9a17 83782802        cmp     dword ptr [rax+28h],2
SYMBOL_NAME:  igdkmd64+62a17
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME:  igdkmd64.sys
FAILURE_BUCKET_ID:  AV_igdkmd64+62a17
BUCKET_ID:  AV_igdkmd64+62a17
FAILURE_ID_HASH_STRING:  km:av_igdkmd64+62a17
FAILURE_ID_HASH:  {edfec275-410d-80f8-25b6-a2973bdc5dec}
Followup: MachineOwner

Edited by Gosberg, 26 July 2015 - 05:43 AM.

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:26 PM

Posted 28 July 2015 - 05:24 AM

Update your Intel graphics driver.


Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/


Edited by usasma, 28 July 2015 - 05:24 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users