Darth Cyrax

Maybe I'll try reinstalling the components to my internet service, as that is probably where the drivers originally came from.

Darth Cyrax

Well, that didn't work. I at least found the Windows XP disk techpro5238 mentioned earlier, but it turns out it's the sevice pack 1 cd, and a couple files required the sevice pack 2 disk to be repaired, but this disk is the only one I can find. BTW, Thanks for your help and support.

Darth Cyrax

You guys have given me some great advice, but I don't know where to go from here. As I said earlier, I disabled every USB device except the three that disable my internet connection when disabled. Does that mean the problem is coming from one of those drivers? If so, what should I do? I found the drivers peterdiva mentioned; I also found the website of their maker, but the website is in an oriental language(Korean, Japanese?). If I can't update them, should I delete or move them if they are causing a problem? Any sort of guidance would be extremely appreciated at this point. Thanks in advance.

peterdiva

What are you using to connect to the Internet? Post the make and model number of it.

Darth Cyrax

Thanks for your response, peterdiva. I use PCMCIA card (I have a desktop, so I use a PCMCIA adapter). It is labeled as "BroadbandAccess/NationalAccess PC Card", by Verizon Wireless, the full product number is: PC5740VW. The is something else on it that might be useful, it is "FCC ID:PP4PX-100", this is right above the product #. If you need any more info, feel free to ask.

jcgriff2

Hi Everyone. . .

Darth Cyrax...


Several of the memory dumps indicated the PC5470 card to be a contributing factor in the BSODs by naming the Cruitel driver pwi_mdm.sys. I believe it to be the reason that the Microsoft USB Miniport Driver usbohci.sys faulted. Verizon is not alone here. This card is manufactured by Curitel Communications, Inc., South Korea, and has its origins in Windows 98.

Unfortunately, you and others are being sold this card that contains an old and poorly written driver v4.32.0.2711, dated May 4, 2005 (the most recent). If this isn't bad enough, it is now being sold to consumers with Vista - and that is doomed to fail.

Regards. . .

jcgriff2

Darth Cyrax

Thank you for this.... revealing information, jcgriff2. If that truly is the problem, then the only solution seems to be to get a new card or a different type of internet connection. Odd that a card with this nasty problem would still be on the market. The only guess I can make is they don't expect people to play online games w/this card, because it crashes very often then. Otherwise, it really isn't that problematic, you have to use internet explorer for a couple hours before it crashes.

jcgriff2

Hi Darth Cyrax...

Unfortunately, it is becoming more the norm. I saw this thread and followed it remembering where I have been in the past and where peterdiva and techpro5238 were going with you here. I was plagued by BSOD last winter caused by a Realtek RTL8185 wireless adapter. Ironically it was purchased to replace a wired connection linked to earlier BSODs.

It is nearly impossible to know the name and version of a driver prior to purchasing a piece of hardware like this - let alone one even thinking to ask such a question. These days, I tell family and friends to always tell Verizon, Comcast, AT&T, etc... that they are going to upgrade to Vista and therefore need Vista compatible hardware - as it will usually run under XP without problems and there is no doubt that when they upgrade to Vista that drivers are available.

Good Luck to you. . .

jcgriff2

Darth Cyrax

Unfortunate, indeed. It is a shame that this problem is not being addressed by those responsible for it , but thanks for everyone's help anyway. Jcgriff2, I'll remember to tell them I upgraded to Vista if that's what it takes for to get decent hardware . Once again, thanks for your help, jcgriff2, techpro5238, and peterdiva.

The Fark Knight

I've been having this problem for almost a week now and it's pretty much buggin me. Googled and bing'd but to no avail. Addl. research with my mates pointed me to the following solution:

- the bugcode_usb_driver is caused by power management problems with a certain or any usb/usb bus device.
- in my case I had cascaded 3 5-port usb hubs from a single usb port on my mobo which was the source of the problem.
- each hub wanted 370 mAh of power. This was find for empty hubs, but as I added devices, the critical point got nearer and nearer.
- Once I crossed the threshold with my devices, the devices would simply stop working.
- This would invariably be followed by the bsod.

= Soln: Right-clik My computer, Properties-> Hardware -> Device manager
= in the USB root tree, find the usb devices that are being used.
= right click on the most essential devices (all the hubs in my case), goto power management tab
= uncheck "Allow to turn this device off to save power"
= Apply and re-do for next device. (Im on a desktop, dunno about laptops)

Reason: Winders wants to turn the device off and the device (my mouse, forex) does not want to turn off, they fight, and bsod appears.

Hope this works.


-The Fark Knight

Darth Cyrax

Hello again. Sorry for not updating this, but I actually solved the problem by changing motherboards. I now am running an ASUS P5Q motherboard and haven't had one of those BSODs since.
So yes, indeed.