USB camera crashes system, but not on concurrent tries...

MichaelD

Lifer
Jan 16, 2001
31,528
3
76
This is weird. I have a Sony USB digicam. I am using the latest drivers for it. This is on my new rig.

Epox 8K5A2+ mobo
XP1600 @ 1750 (PCI bus is at 33MHz)
Latest VIAs (whatever they are...I forget)

Here's what happens. System is up and running. Plug USB cable into camera. Turn camera on. Get error message "USB device failed to initialize" or something like that. BSOD. REBOOT.

BUT, if I leave the camera ON while it reboots, the "removeable device green arrow" is already in the Systray once I get to the desktop. From there, it works fine. I can even shut it off and turn it back on w/o crashing anything. It's just that first time I turn it on. Any ideas?
 

Pink0

Senior member
Oct 10, 2002
449
0
0
this is a software issue not a general hardware issue. Post your thread under tech support.
 

Zebo

Elite Member
Jul 29, 2001
39,398
19
81
Originally posted by: Pink0
this is a software issue not a general hardware issue. Post your thread under tech support.

Then what is it?

I assume you've tried different USB posts and re-scanning device manager.
Try re-insalling usb driver and camera drivers again.
 

MichaelD

Lifer
Jan 16, 2001
31,528
3
76
Carbonyl,

Actually, no; I haven't tried any different ports. :eek:

I don't understand how that would help anyway, though. Don't all the USB ports "empty into" the same "bucket" anyway?

It's worth a shot, though. I'll try that. I don't have a bunch of USB devices. I have my printer, which is always OFF unless I'm using it and my camera. That's it.

I'll try switching ports. Thanks much. Hmmmm...maybe the cable isn't plugged fully in? Man, I didn't check much. :eek:
 

Zebo

Elite Member
Jul 29, 2001
39,398
19
81
I have this probelm with my IBM optical navigator mouse. About 20% of the time it won't be recognizsed on boot. When that happens I move it to another port and tada, auto detect finds it, all good without reboot. Some USB ports are "loose" so I think it fails to make contact. Of it could be the OS does'nt like the driver and fails to load occationally.