DLink DSL Modem and IRQL NOT LESS THAN OR EQUAL

  • Thread starter Thread starter Murray Neal
  • Start date Start date
M

Murray Neal

I have a DLink DSL200 ASDL modem that works fine on my old
Win98 machine. I have a new HP laptop (ZE4315) running XP
SP1 with ALi Chipset that every time I plug the modem in
to the USB port I get a blue screen error IRQL NOT LESS
THAN OR EQUAL.

I have the latest driver from DLink and HP tell me the
motherboard drivers are up to date (Don't necessaryily
believ them) I am rapidly comeing to the conclusion that
this may be driver incompatibity that I am not going to be
able to fix. Any help would be appreciated.

Cheers
Murray
 
Murray Neal said:
I have a DLink DSL200 ASDL modem that works fine on my old
Win98 machine. I have a new HP laptop (ZE4315) running XP
SP1 with ALi Chipset that every time I plug the modem in
to the USB port I get a blue screen error IRQL NOT LESS
THAN OR EQUAL.

I have the latest driver from DLink and HP tell me the
motherboard drivers are up to date (Don't necessaryily
believ them) I am rapidly comeing to the conclusion that
this may be driver incompatibity that I am not going to be
able to fix. Any help would be appreciated.
Click to expand...

Does the BSOD tell you which driver the system thinks is at fault? Does the
BSOD appear immediately after you insert the plug, or after some PnP
chugging? Have you been to the HP support site to get all the latest
drivers for your system? Do you have the latest *XP* drvier from DLink? Is
there also a Windows 2000 driver that you can try? Have you been to Windows
Update and downloaded any driver updates? Are there other USB ports that
you can try? Have you tried it through a hub?

Sorry that there are only questions, but you didn't give enough information
to give a definitive answer, so these may help you get going in the right
direction.

Phil
--
Philip D. Barila Windows DDK MVP
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
E-mail address is pointed at a domain squatter. Use reply-to instead.
 
Back
Top