Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows Xp Will Only Load In Safe Mode

  • Please log in to reply
1 reply to this topic

#1 Melody


  • Members
  • 1 posts
  • Local time:03:51 AM

Posted 08 August 2006 - 10:40 PM

My computer will not start windows xp. Instead it continually reboots with a error message: Driver IRQL Not Less or Equal. Tech info: stop 0x000000D1 (0x75FFFFE3, 0x00000002, 0x00000000, 0xFA1B52B8). Also, my mouse no longer is recognized by my computer but the keyboard is working fine. They are both PS2 and connect into the same box.

BC AdBot (Login to Remove)


#2 raresolid


  • Members
  • 6 posts
  • Local time:01:51 AM

Posted 08 August 2006 - 11:46 PM

Hi there,

Usually this error message means a problem with a device driver, or more commonly the computer has more then one device sharing the same IRQ.

You can first check to see if any of the hardware in your system is using the same IRQ by going to Start>Run, the typing in winmsd then clicking OK.

Click the Plus sign by Hardware Resources, and then selecting IRQ's. In the IRQ section you will see three headings that say Resource, Device and Status.

The goal is to have each device on it's own IRQ, but in some cases multiple devices will use the same IRQ. It is possible that there are just to many devices using the same IRQ and this is causing your error message. If you like, maybe you can paste what you see, so that we can better understand the configuration of your system. In addition, if changes have been made to your BIOS, or you are running a virus scanner, you may want to check the BIOS and set your IRQ settings to AUTO, and disable your virus scanner to see if that works. Bad drivers, or improperly removing/upgrading device drivers OR recently installing new hardware or drivers may cause this.

Below is some technical information about the problem. Source is from Microsoft.


Error Message:

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

User Action:
This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner’s manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

Edited by raresolid, 08 August 2006 - 11:50 PM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users