Windows 7 - Blue Screen 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.

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.

The following parameters are displayed on the blue screen.

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.

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 this
http://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.