Share via

Windows 7 - Blue Screen Driver_IRQL_Not_Less_or_Equal

Anonymous
2010-08-21T20:46:12+00:00

original title: Windows 7 - BSOD - Reason?  Driver_IRQL_Not_Less_or_Equal

My computer prompted me to download an update and restart, I did, and now get a blue screen with the above error message.  I think the problem lies with the ndis.sys. 

I do not have an F8 option for repairing the computer at start up, just F2 and F12. 

Any ideas?

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2010-08-22T01:33:51+00:00

    Hi,

    Try removing and reseating all cards, memory, and cables (both ends when possible) - actually

    remove and replace - do not just snug (this is for a PC not a laptop).

    Setup/Settings (BIOS/CMOS) often F2 as you boot - set CD/DVD drive to 1st in the boot order.

    Use a Windows 7 DVD to boot and see if you can run Startup Repair (see below). Be sure to

    set the boot order back later. On many F12 will allow a one time boot change.

    If you do that and can't boot to a Windows disk then you need help from a real computer shop

    (not leeks and peeks at a Best Buy or other Big Box Stores) or the System maker's Support.

    If possible try with only some of your memory to see if one stick or so is not functioning. Also

    try them in different placement order (see below).


    Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

    The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    Important Information If You Have Received a STOP Code

    If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer,Contact Support.

    If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft articleHow to Fix BlueScreen (STOP) Errors that Cause Windows to Shut Down or Restart Unexpectedly.

    The following actions might prevent an error like this from happening again:

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL Parameters

    The following parameters are displayed on the blue screen.

    Parameter Description
    1 Memory referenced
    2 IRQL at time of reference
    3 0: Read<br><br><br>1: Write<br><br><br>8 : Execute
    4 Address that referenced memory

    Cause

    A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

    This bug check is usually caused by drivers that have used improper addresses.

    If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

    • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
    • The function call was made to a function in another driver, and that driver was unloaded.
    • The function was called by using a function pointer that was an invalid pointer.

    Resolution

    To begin debugging, use a kernel debugger to get a stack trace.

    If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.

    BCCode: D1   0x000000D1  <-- read thishttp://www.faultwire.com/solutions-fatal\_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-\*1210.html?order=votes

    ============================

    These may not help :

    If you do not have a Windows 7 disk you can borrow a friends as they are not copy

    protected. Your System maker will also sell the physical DVD cheap since you already

    own Windows. Also you can make a repair disk on another computer.

    Try Startup Repair - (If at ANY point you gain some but not full access to Windows come

    back and try Startup Repair again.)

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    What are the system recovery options in Windows 7?

    http://windows.microsoft.com/en-us/windows7/What-are-the-system-recovery-options-in-Windows-7

    Try StartUp Repair from Recovery Options or Windows 7 disk.

    How to Run a Startup Repair in Windows 7

    http://www.sevenforums.com/tutorials/681-startup-repair.html

    Also from the COMMAND PROMPT of Recovery Console (if possible) or a Windows 7 disk

    Start - type in Search box -  COMMAND   find at top of list -  RIGHT CLICK  -  RUN AS ADMIN

    sfc /scannow

    How to Repair Windows 7 System Files with System File Checker

    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    Then run checkdisk (chkdsk).

    How to Run Disk Check in Windows 7

    http://www.sevenforums.com/tutorials/433-disk-check.html

    Retry Startup Repair after Chkdsk.

    If needed after those you can try System Restore from Safe Mode or the Recovery or Windows 7

    disk.

    How to Do a System Restore in Windows 7

    http://www.sevenforums.com/tutorials/700-system-restore.html


    If you need to make repair disks - these help repair Windows not re-install.

    How to Create a Windows 7 System Repair Disc

    http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

    ======================================

    If needed :

    What to do if Windows won't start correctly

    http://windows.microsoft.com/en-us/windows-vista/What-to-do-if-Windows-wont-start-correctly

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    What are the system recovery options in Windows 7?

    http://windows.microsoft.com/en-us/windows7/What-are-the-system-recovery-options-in-Windows-7

    =================================

    =================================

    Of course you can't run the memory tests if the computer will not boot though you can try swapping

    some memory in and out to see it that allows a boot.

    Memory tests do not catch all errors such as mismatched memory (possible even for sticks

    that appear to be identical) and when faster memory is placed in system behind slower memory.

    So it is best to also swap sticks in and out to check for those even if all memory tests fail to show

    a problem.

    To test RAM check here - let it run 4+ hours or so.

    www.memtest.org

    For the Windows Memory Diagnostic Tool.

    Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -

    RUN AS ADMIN follow the instructions

    Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic

    Tool

    http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

    How to Run the Memory Diagnostics Tool in Windows 7

    http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

    Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool

    http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

    Hope this helps.


    Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

    4 people found this answer helpful.
    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-03-20T19:17:52+00:00

    I get this error, but not at start-up.  I can start my pc just fine, I get it while gaming, I will just randomly get a crash, often with this error in a blue screen.  I have attached the image of my blue screen error ( http://postimg.org/image/5rt9g9yz7/ ).

    Below are my specs:

    Windows 7 Home Premium Service Pack 1

    Intel Core i7-2600 CPU @ 3.40GHz

    16GB RAM

    64 Bit OS

    Nvidia GeForce GTX 980Ti with latest drive (10.18.13.6451)

    I also had this crash occurring before I updated to the "latest" Nvidia drivers, so I updated.... crash... rolled it back to a prior version... crash... a few other prior versions... crash....  then tried the oldest driver offered on their site (Oct'15).... crashed (although at least this time it ran for 20 mins before crashing).

    My issue is also that I only crash to this error when playing Witcher 3, you suggested in your fix to "If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out."  I'm about to go read through our link on the "D1   0x000000D1", but I'm not sure how to ensure that functions done within the Witcher 3 are not marked as pageable or calling other inline functions that might be paged out.  Hopefully the article will tell that though, but honestly I doubt it...  Just to note this issue could also be related to GOG Galaxy rather than the Witcher 3 specifically, but I'm desperate to find a solution.

    So, wanted to go ahead and post here in case anyone else has thoughts on this...???

    70+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2011-11-20T07:35:59+00:00

    Hi,

    I created a post that might help to troubleshoot this BSOD,

    http://mikemstech.blogspot.com/2011/11/troubleshooting-0xd1.html

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2010-08-22T13:10:37+00:00

    Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2013-12-10T01:36:03+00:00

    Ayuda, hace un tiempo formatie con Windows7 todo bien y como hace una semana mi PC cuesta iniciar por ejemplo, derrepente tenia que iniciar recuperacion, otro tenia que sacar la bateria de las Bios y funcionaba, pero hoy lo prendi y no funciono nada, tampoco me reconoce el teclado ni el mouse, pero si me deja usarlos en las Bios

    0 comments No comments