locked
Driver IRQL error after Windows 7 SP1 update RRS feed

  • Question

  • I updated my Windows 7 to SP 1 using windows update and since then I'm continuously getting BSODs with error as "DRIVER_IRQL_NOT_LESS_OR_EQUAL". I haven't installed any new hardware or software after/just before OS update. I use a dell XPS 15 laptop with Win 7 home premium, 4GB RAM 500 HDD i5 480M. Please suggest me a solution other than re-installation of OS.
    Friday, June 3, 2011 10:50 AM

Answers

  • The Stop 0xD1 ("DRIVER_IRQL_NOT_LESS_OR_EQUAL") indicate that the system attempted to access pageable memory using a kernel process IRQL that was too high: this error is tipically caused by drivers that have used improper addresses.
    For a complete and useful diagnosis it is necessary to know which are the faulting drivers.

    Look into the Windows logs ("System", above all) and search for any record related to the blue screen scrash that you're experimenting; then post more details (stop code parameters, involved modules file names) here.
    You could also use the program that you can find at the following web address

    http://www.nirsoft.net/utils/blue_screen_view.html

    it will scan your hard disk for memory dump files to allow you to analyze them and understand the causes.

    Let us know something more, if necessary.

    Bye


    Luigi Bruno

    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Friday, June 3, 2011 3:06 PM
  • You may boot in Clean Boot Mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Monday, June 6, 2011 8:53 AM
  • Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244(VS.85).aspx

    This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. We need them to identify the faulty driver.

    You can also contact Microsoft CSS to solve your problem.

    Start by updating all possible drivers and disable security softwares and check again.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Wednesday, June 8, 2011 11:36 AM

All replies

  • The Stop 0xD1 ("DRIVER_IRQL_NOT_LESS_OR_EQUAL") indicate that the system attempted to access pageable memory using a kernel process IRQL that was too high: this error is tipically caused by drivers that have used improper addresses.
    For a complete and useful diagnosis it is necessary to know which are the faulting drivers.

    Look into the Windows logs ("System", above all) and search for any record related to the blue screen scrash that you're experimenting; then post more details (stop code parameters, involved modules file names) here.
    You could also use the program that you can find at the following web address

    http://www.nirsoft.net/utils/blue_screen_view.html

    it will scan your hard disk for memory dump files to allow you to analyze them and understand the causes.

    Let us know something more, if necessary.

    Bye


    Luigi Bruno

    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Friday, June 3, 2011 3:06 PM
  • You may boot in Clean Boot Mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Monday, June 6, 2011 8:53 AM
  • Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244(VS.85).aspx

    This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. We need them to identify the faulty driver.

    You can also contact Microsoft CSS to solve your problem.

    Start by updating all possible drivers and disable security softwares and check again.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:40 AM
    Wednesday, June 8, 2011 11:36 AM