[Liqourice]

On one of my computers I've suddenly started having a problem that is somehow related to USB.

I only have one USB device connected to it, a Butler VOIP Dect phone that I use with Skype. Since that's the only one I have I don't know if the problem is related to that unit, cable or it's driver or if it's the USB in general.

Whenever I reboot that computer it BSOD's right about the time when windows should initialize the gfx card and get into the login screen. It seems like it hangs a bit before it does as well. The BSOD doesn't say anything about what driver it is, it only gives a STOP code.

However, if I disconnect the cable to the phone and boots up everything is normal and when I connect it again after windows finished loading it finds the phone and everything works as it should.

This started happening a few weeks ago and I haven't done any changes whatsoever, no installations, no updated drivers, absolutely nothing so I'm stumped as to what can be causing it.

It's not a big issue since I rarely reboot it but it's still a bit annoying to have to disconnect and then connect the cable again each time I do.

[Judas]

check the bios of that system and see if "USB LEGACY SUPPORT" is enabled or disabled, in either case, change it to the opposite of it's current settings and see what happens...

if it doesn't solve anything, change it back.

I have seen some USB ports on some computers, mostly laptops though, that for whatever reason just start screwing up out of the blue during boots or either oventually or right away crash if any USB device is plugged into it.

[Liqourice]

Since this motherboard only have the old USB 1.1 I added a PCI card with USB2.0 when I got the VOIP phone. It didn't work well with just 1.1. But, it's worked fine up until now so who knows.

I'll try that and see what happens.

[Liqourice]

Negative, this didn't fix it. Tried to update the drivers but no change there either.

[Judas]

well it doesn't happen often but occasionally i've seen USB ports just for whatever reason...start screwing up...

for example a little while ago had a machine in using a usb 2.0 wireless adapter for ages... no problems... unplugged it and plugged in a usb flash drive... and since then... the port has been unuseable... while that flash drive continues to work in other machines.... .strange

[Liqourice]

Oh well, as long as it works I just have to remember to pull it out and insert it again if I need to reboot.

[CDsDontBurn]

what is the stop code that it gives you? does the machine restart whenever you get the BSOD? If so, you can disable that so you are able to read what the stop code is and/or if there is also any kind of file associated with the BSOD. To do so do this:

right click "my computer" > properties > "advanced" tab > click the settings button under "startup and recovery" > remove the "automatically restart" check mark under "system failure" > click OK > click OK again.

now, whenever you get a BSOD for anything, you can read what the BSOD is about and you can better determine or troubleshoot the issue.

also, i'd say to update the drivers for the USB card if you didn't update those drivers. you can even try another USB cable if that's possible. or at the very least, a different USB port on that USB card.

[Liqourice]

I already have it set like that, that's how I know I only get a stop code...

And as I said, I only get a stop code that doesn't tell me anything more than "STOP" and a line of hexadecimal numbers. It doesn't refer to any driver or other fault.

I've updated the drivers with no difference, I've tried different ports with no difference. Can't change the cable though, I don't have any other of the same type, I need to buy one first. Can't use the motherboard USB because they're only 1.1 and the software complains that it's not got enough bandwidth.

[OldBuzzard]

You should Google that HEX Stop code. They DO mean something, and you might find the cure to your problem.

This is what you get when you google the infamous 0x00000116 stop code:

- Google Search

There are those of us that have had nightmares about that one

[Tipstaff]

Liqourice, something that just occurred to me. You said you had it hooked up to the USB 1.1 ports at one point. Even though it didn't work very well, did it ever crash when you had it hooked up to those ones, and have you tried having the VoIP phone hooked up to those ports while you booted the machine up in it's current state?

The reason I ask is that I'm wondering if the card itself is faulty. If the machine hangs up during bootup while the VoIP phone is attached to a different USB port, one not related to that add-in card, then the problem could be related to something else within the system, and not the card itself. It could even be the phone itself that is causing the problem. If it doesn't crash/hangup, then you'll know for sure it's the card (or something related to it).

Something else to try would be to completely remove the add-in USB 2.0 card, and reinstall it. The best way to do this would be to go into Device Manager, right-click the add-in card, uninstall it, shut the machine down, remove the card, start the machine up, shut down, reinstall the card, and bootup Windows. At this point I would plug the VoIP phone in, reboot the machine, and see if it hangsup/crashes again. Also, when reinstalling the card, this would be a good opportunity to use a different PCI slot if you have one as using a different PCI slot means the card would be using different resources.

[Liqourice]

I've been thinking in those lines, I just haven't had the time to do it yet. I will whenever I feel I can.