Wasapi Device Failed to start?

[Impla]

I have cracked the obs and I get this data in the log file.

 

[cyclemat]

did you use 2 webcams or a video capture device on your PC ?

check that your USB port is not overloaded.

start this programm and make a screenshot it shows all USB devices

USB Device Tree Viewer

 

[faeddin]

i'm running into the same issue, though it only shows one device failing to start every three seconds

WASAPI: Device '{0.0.0.00000000}.{89c847ed-b254-4ff3-a619-2814f168841c}' failed to start

this is the screenshot from my usb tree viewer. these 4 ports (13 through 16) are shown as Connection Status 3 = Device General Failure, although I can't even identify what ports are those, since all my connected devices are already listed here.

I used a USB hub weeks ago with some other stuff plugged into it, could this have something to do with this? and if it did, how do I fix this?

 

[cyclemat]

try to brin the C600 to the 3.0 root hub

 

[cyclemat]

SORRY c920

 

[faeddin]

I did, and it wasn't the issue. turns out my computer was freezing due to OBS v27.2 not working well with some nvidia cards

i rolled back to 27.1.3 and everything is working again just fine

thanks anyway for the help!

 

[Impla]

 

[Matthew M. Dean]

Something within Windows has changed. Came across this error and I was fine last month. Reverting to 27.3.1 did not resolve the issue. I have the C615 on W11.

Just like your log shows I get:
21:39:46.727: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{21e8efdf-3199-4bd7-9898-edbc04a9a11a}] Failed to enumerate device: 80070490
21:39:46.727: WASAPI: Device '{0.0.0.00000000}.{21e8efdf-3199-4bd7-9898-edbc04a9a11a}' failed to start

It worked everywhere else, Radeon Live, Camera App, Firefox, etc. It refused to work in OBS. I found a solution.
Device Manager -> Uninstall >check "Attempt to remove the driver for this device" > Replug the Webcam
Notice the camera no longer has "Logitech" in the name.

When I click Configure Video, it no longer shows

Instead its now, atleast for me

 

[Matthew M. Dean]

After further experimentation it turns out the old/new driver with the white webcam properties is https://www.logitech.com/pub/video/lws/lws280.exe and what Windows used to download. It shows "Logitech HD Webcam C615" as an Imaging Device instead of Camera and no longer works with OBS.

"Imaging Device" driver that stopped working with only OBS

"Camera" driver that works with OBS

 

[cyclemat]

try the ghub !

 

[Michael Berry]

I don't know if this will help anyone else but I was getting this same or similar error about a device failing to start. I'm on version 27.2.3. I came upon this thread and it wasn't super helpful but I found that mine was caused by an audio source that I was no longer using. This was my log:

13:46:36.481: [win-wasapi: 'Me Only Keys'] update settings:
13:46:36.481: device id: {0.0.1.00000000}.{b4a1f620-6304-4f77-a5df-92d546bfa9b6}
13:46:36.481: use device timing: 0
13:46:36.481: [WASAPISource::TryInitialize]:[{0.0.1.00000000}.{b4a1f620-6304-4f77-a5df-92d546bfa9b6}] Failed to enumerate device: 80070490
13:46:36.481: WASAPI: Device '{0.0.1.00000000}.{b4a1f620-6304-4f77-a5df-92d546bfa9b6}' failed to start

I kept getting a repeating failed to load message. After deleting this source from all my scenes it has gone away.

 

[petejohnson]

I don't know if this will help anyone else but I was getting this same or similar error about a device failing to start. I'm on version 27.2.3. I came upon this thread and it wasn't super helpful but I found that mine was caused by an audio source that I was no longer using. This was my log:


I kept getting a repeating failed to load message. After deleting this source from all my scenes it has gone away.

I've been dealing with this for months. This was very helpful. I just got rid of a ton of audio sources and all the "failed to start" messages have disappeared.

 

[dennisdominic]

It was related to my unused Audio only input source.
I deleted it and the error messages is gone.

 

[ampedPF]

I tried using USB Tree Viewer but couldn't find the device at fault.

I don't know if this will help anyone else but I was getting this same or similar error about a device failing to start. I'm on version 27.2.3. I came upon this thread and it wasn't super helpful but I found that mine was caused by an audio source that I was no longer using. This was my log:


I kept getting a repeating failed to load message. After deleting this source from all my scenes it has gone away.

Thanks to this comment I investigated my audio sources and found out that it was also related to one of my audio input source that was muted 99.99% of the time: a VB-Audio cable from the Voicemeeter devs that I've been tinkering with with a soundboard.
I cross-checked using Voicemeeter Driver Installation Checker and the ID did match!

 

[skts]

did you use 2 webcams or a video capture device on your PC ?

check that your USB port is not overloaded.

start this programm and make a screenshot it shows all USB devices

USB Device Tree Viewer

Why did you asked about "2 webcams or a video capture device"? -> This is right my case.

I have a dual-pc setup, 1x Cam Link for video cam and 1x AVermedia GC573 for Game PC desktop. I open OBS (without recording or streaming) and just wait. In cca 5 minutes both freeze – Cam Link and AVermedia, nothing else. I can switch scenes, I can close-open OBS, nothing changes. I must restart Stream PC and everything works fine .... 5 minutes with OBS opened.

It can be USB overloaded? Thanks for help, guys.

In attachment is my log file (this is one of my bigger scene colletion, but it has the same behaviour in scene collection with CamLink and AVerMedia in one scene.

 

[Mark Weiss]

Since spring, OBS could not hear audio from my MOTU 896 anymore. I also noticed a drastic increase in load time to start OBS after that. I worked around the problem by installing ASIO plugin. But the log has thousands of these entries:


18:43:04.327: WASAPI: Device '{0.0.1.00000000}.{354690b3-7e18-4ada-95a0-4999a429db7e}' failed to start
18:43:07.346: WASAPI: Device '{0.0.1.00000000}.{354690b3-7e18-4ada-95a0-4999a429db7e}' failed to start
18:43:10.365: WASAPI: Device '{0.0.1.00000000}.{354690b3-7e18-4ada-95a0-4999a429db7e}' failed to start
18:43:13.384: WASAPI: Device '{0.0.1.00000000}.{354690b3-7e18-4ada-95a0-4999a429db7e}' failed to start


and I searched the Windows registry and found the device is MOTU 896. I don't know why suddenly this is happening, except maybe Windows updated system in late May. It's been an infuriating problem because my streams had no audio for months until I found ASIO plugin. But the log files are filling up with this error and trying to start device every 3 seconds cannot be good for efficiency. Would like to solve this once and for all.

 

[qu1_qu3]

Hey guys i solved mine by killing the mic/aux audio device from a scene that i havent been using so sup was an unused audio source