Topic: WinXP + two of the same cam = BSOD (Page 1 of 1) Pages that link to <a href="https://ozoneasylum.com/backlink?for=30313" title="Pages that link to Topic: WinXP + two of the same cam = BSOD (Page 1 of 1)" rel="nofollow" >Topic: WinXP + two of the same cam = BSOD <span class="small">(Page 1 of 1)</span>\

 
zavaboy
Paranoid (IV) Inmate

From: f(x)
Insane since: Jun 2004

posted posted 06-08-2008 05:46

I have a Logitech QuickCam 3000, I've had it for several years. It's a great cam! Anyway, I have a project that I'd like to do that would require two cams... two of the same (or simlar) cam. So, I got on eBay and got myself another QC 3000 ($20). I already have the drivers installed from my existing cam and everything works great, except when I plug my second cam in. Right when I plug it in, Windows XP notices it and I get the message bubble thing correctly telling me what I plugged in, then a few seconds later I get a rather painful BSOD. Then, I'm sitting here thinking, "This isn't supposed to happen, my computer isn't supposed to BSOD!" (I can't recall the last time I've had a BSOD before this!) I even tried booting with it still plugged in. I get the welcome screen, but not long after I login (but before I get to see my desktop), I get that same BSOD. The only way around it AFAIK is to just not have my second cam plugged in. I also have my sister's QC Orbit plugged in (I tried it for my project, but it doesn't cut it), though I had the hardest time getting it's drivers installed, once I found the CD for it, it has been running along side my QC 3000 with no problems. I tried getting the second QC 3000 working with and without the Orbit plugged in. Thinking it may solve the problem, but my expectations weren't very high, I installed SP3 and the latest updates (I haven't done Windows Update for ages BTW). The updates didn't fix the problem a bit.

So the question is:
Can two of the very same cam be run on Windows XP simultaneously?

If so, how?

reisio
Paranoid (IV) Inmate

From: Florida
Insane since: Mar 2005

posted posted 06-08-2008 10:37

http://gentoo-wiki.com/HOWTO_Install_a_webcam

zavaboy
Paranoid (IV) Inmate

From: f(x)
Insane since: Jun 2004

posted posted 06-10-2008 13:42

In my case, switching to Linux is not an option at this point.

synax
Maniac (V) Inmate

From: Cell 666
Insane since: Mar 2002

posted posted 06-10-2008 21:32

I don't know, I'm with reisio on this one. Unless the primary function of your PC is to play games, ditch Windows for something else. I realize this does not solve your immediate problem, but it was too good of an opportunity to point out how Windows (often) messes up stuff any other OS gets right.

To answer your question, you're experiencing the BSOD because your webcam drivers are conflicting. You can have two webcams installed, provided they don't use the same drivers.

CPrompt
Maniac (V) Inmate

From: there...no..there.....
Insane since: May 2001

posted posted 06-11-2008 02:46

might help : http://support.microsoft.com/kb/326457

could do the F8 thing at startup and go through the processes until it BSOD's again. Might tell you exactly what is causing the issue but finding a fix might be a bit tough.

Later,

C:\

White Hawk
Maniac (V) Inmate

From: zero divided.
Insane since: May 2004

posted posted 06-11-2008 13:37

Yup - same error code refers to a fatal PnP error with several different types of hardware, apparently. Every MS KB article mentioning this error appears to link to a hotfix (here) that requires you to enter an email address in order to download. I'd say it's worth a try...

I found a discussion elsewhere in which it was suggested that one should check that the BIOS setting "PnP aware OS" is set to 'no' (this setting is redundant in all but the older operating systems). This is old advice and may no longer be relevant, especially as the KB articles explain the issue as non-unique identifiers being applied to two (or presumably, more) devices with the same serial number.

It's a bizarre one, I tell you. I know Microsoft get a lot of bashing anyway, but I'm amazed that such a simple and avoidable problem should still be an issue when they claim to have corrected it in SP2. Not an easily forgiven oversight, IMHO.

(Edited by White Hawk on 06-11-2008 13:39)



Post Reply
 
Your User Name:
Your Password:
Login Options:
 
Your Text:
Loading...
Options:


« BackwardsOnwards »

Show Forum Drop Down Menu