Bugcode_USB_Driver

  • Thread starter Thread starter Brcobrem
  • Start date Start date
B

Brcobrem

Hi,

I configured an accociate's Dell Inspiron 1501 laptop with the intent
on
connecting a Cingular SmartPhone 2125 (Windows Mobile 5) via the
phone's
native "Modem Link" software (aka "tethering via USB cable").
Basically, you
create a "Dial-Up" connectoid in XP with a special phone number, start
the
Modem Link software on the phone, and then make the "Dial-Up"
connectoid
"dial" the phone. You then have access from the laptop to the internet
via
the phone's EDGE service.

Before the Dell, they successfully used Modem Link on an old AMD K6
300 NEC
laptop. The new Dell is running XP Pro SP2 (ie. a bare XP SP2
installation
with only critical updates installed: no antivirus, antispam, no 3rd
party
software whatsoever). The Modem Link software works for about 3
minutes (they
have internet connectivity) and then the Dell laptop bluescreens with:

Bugcode_USB_Driver
Stop: 0x000000FE (0x00000005, 0x89BCB080, 0x10024387, 0x89C61F90)

In the context of "Stop: 0x000000FE" , my research shows that
0x00000005
means:

"A hardware failure has occurred due to a bad physical address found
in a
hardware data structure. This is not due to a driver bug."

Could someone explain to me in a little simpler way (if at all
possible)
just what the above paragraph means?

I'm trying to determine if the problem is in the USB chip set in the
laptop,
or a problem with the USB tethered SmartPhone.

Thanks,
Brcobrem
 
Hi ,

Thank you very much for the reply. Apparently you found the same msdn
article that I did. Did you notice that it says ". . . This is not due
to a driver bug." ?

But you think it actually is a driver bug?

Thanks again,
Brcobrem
 
Brcobrem said:
Hi ,

Thank you very much for the reply. Apparently you found the same msdn
article that I did. Did you notice that it says ". . . This is not due
to a driver bug." ?

But you think it actually is a driver bug?
Click to expand...
If it`s a software bug, it should show up as such, in the
Event Viewer, under either Applications or System.
That`s why I mentioned the EV.

bw..
 
Hi All,

I'll spare you the tedium that it took to uncover the solution, but it
turns out it was some kind of issue with the factory supplied RAM (ie.
two 1GB sticks). Swapped in two pieces of a different manufacurer's
RAM and the "Bugcode_USB_Driver
Stop: 0x000000FE (0x00000005" bluescreen problem simply went
completely away.

Regards,
Brcobrem
 
Back
Top