[shassouneh]

Hi All,
I sometimes get this BSOD (Blue Screen of Death) and I think It might have to do with my Logitech wireless USB mouse.. The message in its entirety reads as follows. I have bolded the important parts

Quote

I have also included a link to my system information below...

TXT an...ARGET AS

I'm running Windows XP Professional with Service Pack 1

If you can help, please do not hesitate to offer some feedback. Thank you.

[el_vago32]

Check THIS

[shassouneh]

Thanx for the reply, BUT I forgot to mention or stress two main points

1.) I tried updating to the latest software from Logitech, including the newest driver and mouseware software, and I still have the same problem
2.) The stop screen does NOT (repeat: NOT) appear at shutdown or reboot. It happens almost randomly when I am running windows!!! It can take anywhere form an hour to a day to happen!
3.) Kbdclass.sys is NOT what i get. I get LHidUSB.sys

Can anyone please provide further help?

[shassouneh]

Thanx for the greeting AlecStaar. good to see you too.
Do you mean the standrad driver that Windows XP uses when it auto detects the mouse, or to force a PS/2 driver?
Note that this mouse is a Wireless USB mouse, with a scroll button.
Would a PS/2 driver work for this, with scrolling functinality?
Please clarify. your feedback is much appreciated

[shassouneh]

LOL, good point. They are probably both pushed too hard AND rookies at the same time.

As for the XP drivers, theyare just as problematic as the logitech ones. The only reason i even tried the logitech ones is because the XP ones seemed to give blue screens.

Now BOTH the XP/Logitech drivers give blue screens (the same blue screen descriebd above).

Any ideas?

Thanx for all the help everyone

[ThC 129]

well if the driver is logitech related then try physically removing all logitech software from you computer. I would also try and track down what else is using the same IRQ that the mouse is using.

If all else fails contact logitech and tell em the problem, i have never heard of a problem like this but out there in computer user land im sure someone else is having something like this happen.

It seems to be an IRQ routing problem of some sort or another. Im really at a loss to try and tell you what to do.