locked
BSOD ( IRQL Not Less Or Equal ) Windows 8.1 , Asus N550LF RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    ==================================================
    Dump File         : 122213-23953-01.dmp
    Crash Time        : 12/22/2013 9:33:28 AM
    Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code    : 0x000000d1
    Parameter 1       : 00000000`00000028
    Parameter 2       : 00000000`00000002
    Parameter 3       : 00000000`00000000
    Parameter 4       : fffff800`01f0ac47
    Caused By Driver  : igdkmd64.sys
    Caused By Address : igdkmd64.sys+62c47
    File Description  : Intel Graphics Kernel Mode Driver
    Product Name      : Intel HD Graphics Drivers for Windows 8(R)
    Company           : Intel Corporation
    File Version      : 10.18.10.3308
    Processor         : x64
    Crash Address     : ntoskrnl.exe+14dca0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\WINDOWS\Minidump\122213-23953-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 9600
    Dump File Size    : 302,992
    Dump File Time    : 12/22/2013 9:34:48 AM
    ==================================================

    Thank you in advance :)

    Sunday, December 22, 2013 8:49 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    VK

    This one crash was related to your Driver for Intel Graphics Adapter and there are many, many users experiencing this problem with this driver.  I would revert back one full generation to an older driver until Intel releases the fix.

    *** 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 )

    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

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Monday, December 23, 2013 8:37 AM
    Monday, December 23, 2013 7:37 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Right now I'm updating the Intel drivers
    Sunday, December 22, 2013 9:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I cant update my Intel drivers because the newest version of the intel drivers are not checked by the company....

    What should I do ? :/

    Sunday, December 22, 2013 9:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ok I "updated" my intel drivers , there was a drivers page on the asus website for windows 8.1 , But it downloaded the same driver version what I had, but I updated it. Someone :D pls help.
    Sunday, December 22, 2013 9:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please follow our instructions for finding and uploading the files we need to help you fix your computer.  They can be found here
    If you have any questions about the procedure please ask

    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by kelvin_hsu Monday, December 23, 2013 3:16 AM
    Sunday, December 22, 2013 2:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    http://rapidshare.com/share/EA3357D1B306491B8275B9DD2A9DBB8D
    Monday, December 23, 2013 7:20 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    VK

    This one crash was related to your Driver for Intel Graphics Adapter and there are many, many users experiencing this problem with this driver.  I would revert back one full generation to an older driver until Intel releases the fix.

    *** 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 )

    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

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Monday, December 23, 2013 8:37 AM
    Monday, December 23, 2013 7:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you so much :) , I will do that if it happens again , (It didn't happened after I updated it from Asus.com) But now if it happens I know what to do :) thank you !

    Monday, December 23, 2013 8:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It just happened again , I had to restore my laptop , now Im using Windows 8 with the 9.xxxx Intel Drivers.

    I hope the problem wont show up again.

    Monday, December 23, 2013 5:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    OK Everything is working fine with 8.0  thank you guys :)
    Friday, February 7, 2014 12:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey, I am having the same problem. Are you still experiencing problems after reverting back to 8.0 from 8.1?
    I was wondering if I could get a quick tutorial of how to revert back to 8.0 from 8.1 and all the little details I must do so that I don't mess anything up.
    Thursday, February 27, 2014 6:57 AM