none
IRQL_NOT_LESS_OR_EQUAL [BSOD Windows 8.1] RRS feed

  • Question

  • Hello, please help me. I'm having a problem with IRQL_NOT_LESS_OR_EQUAL [BSOD Windows 8.1]  

    here is my dump file : https://skydrive.live.com/redir?resid=B98BB87394A64481%21474

    this is my PC information : https://skydrive.live.com/redir?resid=B98BB87394A64481!475&authkey=!AC_YzPtzQSbDOUw&ithint=file%2c.speccy

    Thursday, December 12, 2013 12:30 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffff80002f5cc47, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: fffff8005f933340: Unable to get special pool info
    fffff8005f933340: Unable to get special pool info
    GetUlongFromAddress: unable to read from fffff8005f9ce208
    0000000000000028 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    igdkmd64+62c47
    fffff800`02f5cc47 83782802        cmp     dword ptr [rax+28h],2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  dwm.exe
    
    TRAP_FRAME:  ffffd000226bdbb0 -- (.trap 0xffffd000226bdbb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00000237e68
    rdx=ffffe0000808bdc0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f5cc47 rsp=ffffd000226bdd40 rbp=ffffe00008094b70
    r8=ffffe00001365a60  r9=00000000ffffffff r10=0000000000000002
    r11=ffffd000226bdd38 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    igdkmd64+0x62c47:
    fffff800`02f5cc47 83782802        cmp     dword ptr [rax+28h],2 ds:00000000`00000028=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8005f7da7e9 to fffff8005f7ceca0
    
    STACK_TEXT:  
    ffffd000`226bda68 fffff800`5f7da7e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`226bda70 fffff800`5f7d903a : 00000000`00000000 00000000`925c0000 00000000`00000000 ffffd000`226bdbb0 : nt!KiBugCheckDispatch+0x69
    ffffd000`226bdbb0 fffff800`02f5cc47 : ffffe000`003c5000 00000000`00000002 ffffe000`00237000 00000000`ffffffff : nt!KiPageFault+0x23a
    ffffd000`226bdd40 ffffe000`003c5000 : 00000000`00000002 ffffe000`00237000 00000000`ffffffff ffffe000`01365a60 : igdkmd64+0x62c47
    ffffd000`226bdd48 00000000`00000002 : ffffe000`00237000 00000000`ffffffff ffffe000`01365a60 00000000`00000000 : 0xffffe000`003c5000
    ffffd000`226bdd50 ffffe000`00237000 : 00000000`ffffffff ffffe000`01365a60 00000000`00000000 ffffe000`00237000 : 0x2
    ffffd000`226bdd58 00000000`ffffffff : ffffe000`01365a60 00000000`00000000 ffffe000`00237000 00000000`00000000 : 0xffffe000`00237000
    ffffd000`226bdd60 ffffe000`01365a60 : 00000000`00000000 ffffe000`00237000 00000000`00000000 ffffe000`01365a78 : 0xffffffff
    ffffd000`226bdd68 00000000`00000000 : ffffe000`00237000 00000000`00000000 ffffe000`01365a78 ffffc000`10b7e502 : 0xffffe000`01365a60
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    igdkmd64+62c47
    fffff800`02f5cc47 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

    Hi,

    According to the dump file, the BSOD was caused by igdkmd64.sys driver.

    I suggest you update Intel Graphics driver to test it.

    https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3712&DwnldID=23405&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&lang=eng

    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    Regards,


    Kelvin hsu
    TechNet Community Support


    Friday, December 13, 2013 8:34 AM
    Moderator
  • Hey thanks, i think its work. But the Intel Graphics i have to download from manufacturer website. Not from Intel website. 
    Friday, December 13, 2013 11:34 AM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        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: fffff80002f5cc47, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: fffff8005f933340: Unable to get special pool info
    fffff8005f933340: Unable to get special pool info
    GetUlongFromAddress: unable to read from fffff8005f9ce208
    0000000000000028 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    igdkmd64+62c47
    fffff800`02f5cc47 83782802        cmp     dword ptr [rax+28h],2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  dwm.exe
    
    TRAP_FRAME:  ffffd000226bdbb0 -- (.trap 0xffffd000226bdbb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00000237e68
    rdx=ffffe0000808bdc0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f5cc47 rsp=ffffd000226bdd40 rbp=ffffe00008094b70
    r8=ffffe00001365a60  r9=00000000ffffffff r10=0000000000000002
    r11=ffffd000226bdd38 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    igdkmd64+0x62c47:
    fffff800`02f5cc47 83782802        cmp     dword ptr [rax+28h],2 ds:00000000`00000028=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8005f7da7e9 to fffff8005f7ceca0
    
    STACK_TEXT:  
    ffffd000`226bda68 fffff800`5f7da7e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`226bda70 fffff800`5f7d903a : 00000000`00000000 00000000`925c0000 00000000`00000000 ffffd000`226bdbb0 : nt!KiBugCheckDispatch+0x69
    ffffd000`226bdbb0 fffff800`02f5cc47 : ffffe000`003c5000 00000000`00000002 ffffe000`00237000 00000000`ffffffff : nt!KiPageFault+0x23a
    ffffd000`226bdd40 ffffe000`003c5000 : 00000000`00000002 ffffe000`00237000 00000000`ffffffff ffffe000`01365a60 : igdkmd64+0x62c47
    ffffd000`226bdd48 00000000`00000002 : ffffe000`00237000 00000000`ffffffff ffffe000`01365a60 00000000`00000000 : 0xffffe000`003c5000
    ffffd000`226bdd50 ffffe000`00237000 : 00000000`ffffffff ffffe000`01365a60 00000000`00000000 ffffe000`00237000 : 0x2
    ffffd000`226bdd58 00000000`ffffffff : ffffe000`01365a60 00000000`00000000 ffffe000`00237000 00000000`00000000 : 0xffffe000`00237000
    ffffd000`226bdd60 ffffe000`01365a60 : 00000000`00000000 ffffe000`00237000 00000000`00000000 ffffe000`01365a78 : 0xffffffff
    ffffd000`226bdd68 00000000`00000000 : ffffe000`00237000 00000000`00000000 ffffe000`01365a78 ffffc000`10b7e502 : 0xffffe000`01365a60
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    igdkmd64+62c47
    fffff800`02f5cc47 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

    Hi,

    According to the dump file, the BSOD was caused by igdkmd64.sys driver.

    I suggest you update Intel Graphics driver to test it.

    https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3712&DwnldID=23405&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&lang=eng

    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    Regards,


    Kelvin hsu
    TechNet Community Support


    Friday, December 13, 2013 8:34 AM
    Moderator
  • Hey thanks, i think its work. But the Intel Graphics i have to download from manufacturer website. Not from Intel website. 
    Friday, December 13, 2013 11:34 AM