958960 - WebRTC + usbaudio.sys = BlueScreenOfDeath

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Audio/Video, defect)

Description

[jaredfeithen]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140112030204

Steps to reproduce:

I used the windows sysinternals tool "autoruns.exe" to disable usbaudio.sys driver and visited https://apprtc.appspot.com/ ten times--and not once did I encounter a BSOD. Then I used autoruns.exe to enable usbaudio.sys and proceeded to visit https://apprtc.appspot.com/. 3 times out of ten I encountered a BSOD.


Actual results:

Nightly 64bit froze for a second then BSOD


Expected results:

uh no BSOD

Comment 2

[Randell Jesup [:jesup] (needinfo me)]

Does it BSOD with Chrome?

Please indicate what USB devices are attached (including internal USB devices like laptop cameras); you can find this from the Hardware details in System on Windows and detail any devices attached.  Also the version of the USB drivers for the USB ports from Hardware.

Also: what OS and version, what hardware, what drivers are installed for the USB devices and version.  What type of BSOD it indicates (take a photo of the BSOD screen?)

If possible (and it may not work): run a recent Nightly Debug build from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ and set the env variables
NSPR_LOG_MODULES to mediamanager:5,getusermedia:5,webrtc_trace:65535 
NSPR_LOG_FILE to some temp file (to look at after BSOD)
WEBRTC_TRACE_FILE to a different temp file (to look at after BSOD)
and then make it BSOD and upload the log files.

Please update what of this you can as you get the info.  Thanks!

Comment 3

[jaredfeithen]

1 Microsoft Lifecam Studio webcam is attached.
BSOD does not occur under any other browser. 
Windows 7 64 bit. BSOD changes every time.

Comment 4

[jaredfeithen]

Intel 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26 v9.3.0.1011

Comment 5

[jaredfeithen]

Most of the time the BSOD error is 0x0000007e.

Comment 6

[jaredfeithen]

http://anonymousdelivers.us/127136 
here is a kernel dump file ...if that helps

Comment 7

[Paul Silaghi, QA [:pauly]]

(In reply to jaredfeithen from comment #0)
> I used the windows sysinternals tool "autoruns.exe" to disable usbaudio.sys driver
I have a USB camera connected but I can't find usbaudio.sys in autoruns.exe/driver section. Why?

Comment 8

[jaredfeithen]

maybe you need to change the filter options. it is a driver that comes with windows 7. it is published by microsoft so filter options in autruns.

Comment 9

[Paul Silaghi, QA [:pauly]]

(In reply to jaredfeithen from comment #8)
> maybe you need to change the filter options
Found it.
Right click on it/Process Explorer says "usbaudio.sys is not currently running". The USB camera is attached and webRTC running. Thoughts ?

Comment 10

[jaredfeithen]

Dude...process explorer says that about all drivers when you check 'em the way you're checking 'em.

Comment 11

[jaredfeithen]

All i know is i have no problem using webrtc with chrome, but with nightly, i get bsods unless i disable usbaudio.sys.

Comment 12

[Paul Silaghi, QA [:pauly]]

(In reply to jaredfeithen from comment #10)
> Dude...process explorer says that about all drivers when you check 'em the
> way you're checking 'em.
Then it means I just can't reproduce your problem, nightly 29.0a1(2014-01-21), win 7 x64

Comment 13

[Randell Jesup [:jesup] (needinfo me)]

Paul: do you have the same camera/driver?  This sort of problem (BSOD) typically points at a device driver or specific hardware interaction

Jared: Is there a driver for the camera?  That is more likely than the USB driver itself.  If we can't repro it, there's going to be little we can do without some of the logs I mentioned.  Do you have another camera you can try?

Comment 14

[Paul Silaghi, QA [:pauly]]

(In reply to Randell Jesup [:jesup] from comment #13)
> Paul: do you have the same camera/driver? 
Nope, I have a Genius USB camera.

Comment 15

[jaredfeithen]

No, I don't have another camera. And I tried gathering logs the way i was instructed to, but the logs contained nothing but "NUL" characters. As far as drivers go, well, I already narrowed it down to usbaudio.sys--which is a driver that comes included in all microsoft windows 7 operating systems.

Comment 16

[jaredfeithen]

What about the kernel dump file I provided? Have either of you taken a look at it?

Comment 17

[Randell Jesup [:jesup] (needinfo me)]

It's hard to decipher kernel dumps... and they often don't tell you why it happened.  I'm not set up for it.

Have you installed the firmware update for the camera from Microsoft?  http://microsoft.com/hardware/en-us/s/lifecam-studio

There's also a "LifeCam 3.6" download; I'm not sure if that's updated OS drivers or not.

Without logs or the camera I can't do much more.  Logs really should work on Nightly debug builds (you were trying a debug build, right?)

Otherwise we'll have to find someone else with a LifeCam Studio and try it there

Comment 18

[jaredfeithen]

yeah that was like the first thing i tried, but my firmware is up to date and the LifeCam 3.6 download doesn't modify the usbaudio.sys file. and yes, i used a nightly debug build, but the logs produced nothing but NUL (alt+256) characters. so i guess i just wont use webrtc.

Comment 19

[Paul Silaghi, QA [:pauly]]

Do you still reproduce this on the latest nightly ?

Comment 20

[jaredfeithen]

I just updated nightly to the latest version, and yes, on my fifth consecutive visit to https://apprtc.appspot.com/ I received a BSOD error. I did not bother to write down any information; it is chaotic in nature, as the BSOD is different with each occurence. Furtermore, I did not bother collecting a dump, kernel or otherwise, since I have been told you guys can not make use of them. If I can be of further assistance, then let me know.

Comment 21

[Paul Silaghi, QA [:pauly]]

Thank you for your time!