Question / Help Glitchy Audio // OBS Crashing

BennnnDaniels

New Member
Hey guys, up until a month or so ago streams were fine, suddenly at random intervals the stream audio will go glitchy, I confirmed it in recordings too, unplugging my audio devices/restarting my pc/OBS fixes it. But I want to trace the issue and get it sorted. I've attached a couple of logs and the latest crash report.

Something to note is when I plug in my camera to the Elgato Camlink and boot up my DSLR it comes up saying a USB has malfunctioned and my mouse stops working for about 30 seconds. Really weird, I reckon it's a driver issue but struggling to locate the source.
 

Attachments

  • Crash 2019-07-15 19-22-38.txt
    150 KB · Views: 44
  • 2019-07-15 19-24-12.txt
    56.2 KB · Views: 14
  • 2019-07-15 19-05-05.txt
    52.4 KB · Views: 8

Sukiyucky

Member
OBS cannot connect to your MOTU audio device. You need to fix that. Try downloading new drivers, especially if you have done a recent Windows update:

Problem #1:
19:05:09.235: [WASAPISource::TryInitialize]:[MOTU Main Out 1-2 (MOTU Audio Wave for 64 bit)] Failed to activate client context: 88890004
19:05:09.235: [WASAPISource::WASAPISource] Device '{0.0.0.00000000}.{02c60e69-cf7e-4f9d-87ee-96052b9a1b39}' not found. Waiting for device


Problem #2:
19:05:10.561: [WASAPISource::WASAPISource] Device '{0.0.0.00000000}.{2383efc2-172d-465d-9858-5a2a2bc2fcfa}' not found. Waiting for device

Then you got problems when switching to your Full Cam Scene. One of your camera sources is messed up. Maybe a Camlink driver problem. Go download new Camlink drivers:

19:05:18.216: Switched to scene 'Full Cam'
19:05:18.218: signal_handler_connect: signal 'item_visible' not found
19:05:18.218: signal_handler_connect: signal 'item_visible' not found


The crash report shows that you opened up a dialog box to change properties. Recall what you were doing and go update the driver to that device:

000000C4551FE300 00007FFE14B5102F 0000000000000000 00000201C8FB24A0 00007FFE14B5C2D0 000000C4551FE618 kswdmcap.ax!0x7ffe14b5102f
000000C4551FE560 00007FFE14B50E68 00000201C8FB24A0 00000201C8FB24A0 000000000000004E 000000C4551FE618 kswdmcap.ax!0x7ffe14b50e68
000000C4551FE5A0 00007FFE14B53DAC 000002019C998A60 000000C4551FE618 000000C4551FECD0 00007FFE63D03CAE kswdmcap.ax!0x7ffe14b53dac
.
.
000000C4551FFC80 00007FFE24E15829 00000201914BA108 00000201914BA108 00000201914BA178 0000020196117D48 win-dshow.dll!DShow::OpenPropertyPages+0xa9

000000C4551FFD10 00007FFE24E156AD 0000000000000001 00000201D09FB8C0 0000000000000005 00000201914BA108 win-dshow.dll!DShow::Device::OpenDialog+0x1dd
000000C4551FFD80 00007FFE24E0837B 0000020186CD60B0 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowInput::DShowLoop+0x2bb
000000C4551FFE00 00007FFE24E085A5 0000000000000000 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowThread+0x25
000000C4551FFE30 00007FFE63817BD4 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffe63817bd
 

BennnnDaniels

New Member
Thank you, I'm updating all my mobo drivers at the moment, I hate intermittent issues like this. Appreciate you taking the time to look through the logs. Will report back.
 

BennnnDaniels

New Member
Updated all my motherboard drivers, including ones for chipset and audio just in case they were conflicting. Haven't had the issue so far but because it's intermittent it's difficult to say. Thanks for you help so far.
 

Sukiyucky

Member
Good to hear.

As a tip, whenever Microsoft does a Windows update, sometimes the first thing to go is the USB. Make it a habit to update all drivers (GPU, Audio, 3rd party h/w) after doing so.
 
Top