"irql_not_less_or_equal"

[The Fifth Horseman]

Whenever I connect my USB mouse to an USB port, Windows displays a BSOD with that message. If plugged before Windows boots, then the PC just restarts and keeps repeating that.

What might be the cause? How to solve it?

[efthimios]

What brand is the mouse, and did it come with any software/drivers? If yes, then install them first before you plug in the mouse?

[The Fifth Horseman]

A4tech. Yes and Yes. The BSOD appears mere second after windows displays "finished installing new hardware" after I plug the mouse in.

[efthimios]

In that case, have you tried uninstalling the mouse drivers, then just plug in the mouse without installing the official drivers first?
Also, if you have any other usb devices, try to remove them first, to see if there is some kind of a conflict there.

[Koen]

That's funny! I just had that error message too, saying my bios was too old. Also a blue screen with IRQL_NOT_LESS_OR_EQUAL... :ot:

[The Fifth Horseman]

In that case, have you tried uninstalling the mouse drivers, then just plug in the mouse without installing the official drivers first?
Been there, ends exactly the same way.
Also, if you have any other usb devices, try to remove them first, to see if there is some kind of a conflict there.
Don't have any.

[efthimios]

Well, I have a few more suggestions.
Try a different USB port. If you are using a USB hub, don't.
My guess is that you had another mouse before this one, right? And USB too, right? If yes, did you uninstall all software related to that one?
Tried to download any new driver from the manufacturer?
Try loading windows in safe mode then plug in the mouse?
I guess there is a chance that the mouse itself is broken. Or that Windows just plain do not like it. If nothing works, try to use the mouse on another pc just to be sure that it is not broken.

[Data]

well that error means that windows and your hardware aren;t friends

replace either. (you probably have to reinstall windows or so)

[The Fifth Horseman]

Try a different USB port.
Been there, done that. No difference.
If you are using a USB hub, don't. No hub in use.
My guess is that you had another mouse before this one, right? And USB too, right?
You could say so. Same mouse but plugged into PS/2 socket via USB-PS2 adapter. However there I have to boot up Windoze with a different mouse, and switch it later b/c the USB one does not power up correctly.
If yes, did you uninstall all software related to that one?Yes, tried that and no effect.
Tried to download any new driver from the manufacturer? Yup.

Try loading windows in safe mode then plug in the mouse? Didn't do that yet.

I guess there is a chance that the mouse itself is broken. Or that Windows just plain do not like it. If nothing works, try to use the mouse on another pc just to be sure that it is not broken.
Mouse is second one after the store replaced the first. Same effect. Worked on other hardware without problems.

replace either. (you probably have to reinstall windows or so)
:wall: :wall: :wall: Dammit. Cannot right now.

[efthimios]

So the mouse works when used with PS/2? If yes, then (having first removed any traces of any drivers etc) having the mouse plugged in the ps/2 co to device manager and remove the mouse from the system that way. When you do unplug, check and remove any reference to it from the registry (manually) and reboot. A When xp finishes loading, plug in the mouse to the usb.


If that doesn't work, try what I said about safe mode.

It sounds like a driver conflict, and that PS/2 might just might be the problem. :blink:

[Apocalypse Dude]

This message is sometimes also given when a USB 2.0 device is plugged into a USB 1.1 port. But with a mouse this sounds unlikely to me. But you could check it anyway...

[Playbahnosh]

I had exactly the same problems here. I have some advices regarding this:

- Do you have Daemon Tools or any virtual disk drives? Try uninstalling them. They do cause hardware IRQ failures.

- Try swiching off the "Video RAM cachable" option in the BIOS. That solved the thing for me.

- Try swiching off the L2 internal cache in BIOS. That causes similar things, mostly in AMD systems.

- There is a driver that Daemon and some other VCD apps install (sorry dont remember the file name). Write down the driver that causes the problem, its on the BSOD, xxxxx.sys or something. Restart in safe mode (ya know F5) and find that file with the window$ search engine, and delete it. This should solve your prob.

Tell if I was any help :ok: