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.

Photo

BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL error


  • Please log in to reply
5 replies to this topic

#1 papermate09

papermate09

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:34 PM

Posted 19 January 2015 - 07:22 PM

Hello everyone,

 

I just purchased a new computer, its a Lenovo Z750: intel i7 processor, Nvidia graphics geforce 850M, running windows 8.1 with 8gb of RAM and 1 TB of hard disk.

 

I got this computer less than a week ago. I was playing Civilization 4 and using the Nvidia graphics card (computer has two: nvidia and intel HD 4600, the latter comes with the processor) when my computer crashed and it prompted me the Blue Screen, the error it gave me is the same one as the title. I tried finding out what the cause of the problem may have been and all I read was that it most likely has to do with a driver issue.

 

I ended up finding a "partial" step by step solution through this forum. I gave it a shot and I am where I am now. This is the thread that provided the solution: 

 

                         http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

 

The author says to use a debugging tool to read the .dmp file, which is what i did (I used WinDbg x64) and I extracted the .dmp file. So, basically I'm just following the authors instructions about posting my .dmp file . It would be great to get some help! If you have any further questions, please let me know! Below is the text to the dmp file.

 

Thanks again,

Pablo

 

 

 
Microsoft ® Windows Debugger Version 6.3.9600.17298 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
 
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: SRV*c:\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.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff803`7fa15000 PsLoadedModuleList = 0xfffff803`7fcdf2d0
Debug session time: Mon Jan 19 13:56:25.334 2015 (UTC - 8:00)
System Uptime: 2 days 13:08:19.133
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`5569f018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.......................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {28, 2, 0, fffff80113487287}
 
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+63287 )
 
Followup: MachineOwner
---------
 
4: 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: fffff80113487287, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000028 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
igdkmd64+63287
fffff801`13487287 83782802        cmp     dword ptr [rax+28h],2
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  AV
 
PROCESS_NAME:  dwm.exe
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
TRAP_FRAME:  ffffd00023a32f30 -- (.trap 0xffffd00023a32f30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00091de8e68
rdx=ffffe0009a21bdc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80113487287 rsp=ffffd00023a330c0 rbp=ffffe0009a21e480
 r8=ffffe000968dc490  r9=00000000ffffffff r10=0000000000000002
r11=ffffd00023a330b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
igdkmd64+0x63287:
fffff801`13487287 83782802        cmp     dword ptr [rax+28h],2 ds:00000000`00000028=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff8037fb74ae9 to fffff8037fb68fa0
 
STACK_TEXT:  
ffffd000`23a32de8 fffff803`7fb74ae9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23a32df0 fffff803`7fb7333a : 00000000`00000000 00000000`94500000 00000000`00000000 ffffd000`23a32f30 : nt!KiBugCheckDispatch+0x69
ffffd000`23a32f30 fffff801`13487287 : ffffe000`9148f000 00000000`00000002 ffffe000`91de8000 00000000`ffffffff : nt!KiPageFault+0x23a
ffffd000`23a330c0 fffff801`1344097a : ffffd000`23a33201 00000000`94500000 ffffe000`ffffffff ffffe000`ffffffff : igdkmd64+0x63287
ffffd000`23a33160 fffff801`1250bcb6 : ffffe000`917391c0 ffffc000`51d26000 00000000`00000001 fffff801`1250b30f : igdkmd64+0x1c97a
ffffd000`23a331b0 fffff801`1250b8f0 : ffffd000`23a334b0 ffffd000`23a33240 00000000`00000001 ffffc000`51d26000 : dxgkrnl!ADAPTER_RENDER::DdiCreateAllocation+0xba
ffffd000`23a331f0 fffff801`12509a86 : ffffd000`23a334b0 ffffd000`23a334b0 ffffd000`23a33760 00000000`00000001 : dxgkrnl!DXGDEVICE::CreateDriverAllocations+0x104
ffffd000`23a33280 fffff801`12509431 : ffffc000`51d26000 ffffd000`23a33b01 ffffd000`23a33a70 00000000`00000700 : dxgkrnl!DXGDEVICE::CreateAllocation+0x456
ffffd000`23a33990 fffff803`7fb747b3 : ffffe000`8dfab080 ffffd000`23a33b00 00000000`000000bc ffffc000`51d26000 : dxgkrnl!DxgkCreateAllocation+0x391
ffffd000`23a33b00 00007ffc`c69c138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000000e`1c21bc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`c69c138a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
igdkmd64+63287
fffff801`13487287 83782802        cmp     dword ptr [rax+28h],2
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  igdkmd64+63287
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: igdkmd64
 
IMAGE_NAME:  igdkmd64.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  524b0131
 
FAILURE_BUCKET_ID:  AV_igdkmd64+63287
 
BUCKET_ID:  AV_igdkmd64+63287
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:av_igdkmd64+63287
 
FAILURE_ID_HASH:  {c23f1390-e66c-5d68-5d75-e53c9bbaab1f}
 
Followup: MachineOwner
---------
 

 



BC AdBot (Login to Remove)

 


#2 ramsforever

ramsforever

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:34 PM

Posted 19 January 2015 - 09:01 PM

Try re seating the RAM.

 

Try pulling one out at a time (not sure how many you have) , and running the software.

 

Good luck!
 



#3 papermate09

papermate09
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:34 PM

Posted 19 January 2015 - 09:27 PM

ramsforever, Thanks for the suggestion but I think I want to try something software related before touching any of the components. Is there any reason as to why you're suggesting that? What would that do?



#4 ramsforever

ramsforever

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:34 PM

Posted 19 January 2015 - 09:29 PM

In my expierence, that BSOD is RAM related.



#5 Victoria-Joe

Victoria-Joe

  • Members
  • 46 posts
  • OFFLINE
  •  
  • Local time:10:04 AM

Posted 20 January 2015 - 06:15 AM

BSOD problem is caused by old or corrupted drivers. So, first check your Nvidia graphic card by trying another one. If your graphic card is ok, then another method i.e. to boot into safe boot and run system restore.



#6 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,596 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:34 AM

Posted 20 January 2015 - 08:04 AM

I don't know why people are recommending to upgrade the NVIDIA drivers or checking the RAM, since the driver that crashed belongs to an Intel Graphic Card (igdkmd64.sys). Maybe it's possible that the OEM NVIDIA drivers that allows the use of two graphic card weren't installed properly, causing the crash, but for now it's too soon to say. papermate, are you sure that your laptop is a Lenovo IdeaPad Z750? Can you give me the model number written on it, or under the laptop on a sticker?


Edited by Aura., 20 January 2015 - 08:05 AM.

unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users