Question / Help OBS Crashes Upon Opening "Woops, OBS Has Crashed!"

AsherShow · Dec 29, 2018

Below is My Crash Report. Updated my Nvidia Graphics now im getting an error.

Also if you could you let me know how to read crash reports (so i dont have to keep coming to the form) that would be great thanks

Suslik V · Dec 29, 2018

Look at this thread: https://obsproject.com/forum/threads/obs-crash-when-changing-to-a-certain-scene-collection.91800/
follow the steps and your capture device may become alive.

koala · Dec 29, 2018

AsherShow said:
Also if you could you let me know how to read crash reports (so i dont have to keep coming to the form) that would be great

That's not an easy thing to tell. If someone writes a comprehensive how-to-read-an-obs-crashlog guide, nobody will read it, because it is too long.
The thing that most often happens is that some thread crashes due to a 3rd party dll or driver. Let's look into your log. Start notepad and load the crash log. Look at the top of the file:

Code:

Unhandled exception: c0000005
Date/Time: 2018-12-29, 1:15:24 AM
Fault address: 7FFDEE784989 (c:\windows\system32\ntdll.dll)
libobs version: 22.0.2 (64-bit)
Windows version: 10.0 build 17134 (revision: 472; 64-bit)
CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz


Thread 1F50 (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000008F529F8690 00007FFDEE784989 0000000000000000 000002822EC24660 00000000FFFFFFFE 0000000000000000 ntdll.dll!0x7ffdee784989
0000008F529F8740 00007FFDEE77EFB7 000002822EC24640 0000008F529F8AA0 0000000000000000 0000000000000000 ntdll.dll!0x7ffdee77efb7
0000008F529F8770 00007FFDEE77EED0 00007FFDCF63FDE8 0000000000000000 00007FFD00000000 000002827DC80000 ntdll.dll!0x7ffdee77eed0
0000008F529F87A0 00007FFD87F2B27B 0000000000000000 00007FFD884DFEF8 0000000000000000 FFFFFFFFFFFFFFFC videocaptureapi.dll!0x7ffd87f2b27b
0000008F529F8A10 00007FFD87F2B62B 00007FFD884DFEF8 00007FFD884DF010 00007FFD87E93F50 00007FFD884E0DC0 videocaptureapi.dll!0x7ffd87f2b62b
0000008F529F8A40 00007FFD87F2B3DC 0000028200000005 00000282109D1D90 0000000000000001 FFFFFFFFFFFFFFFF videocaptureapi.dll!0x7ffd87f2b3dc
0000008F529F8AB0 00007FFD87E7E2C7 00000282109D1D90 0000000000000001 0000000000000000 0000000000000000 videocaptureapi.dll!0x7ffd87e7e2c7
0000008F529F9690 00007FFD88C5809C 00000282109D1DA8 00000282109D1DA8 0000000000000001 0000000000000001 videocapturefilter.ax!0x7ffd88c5809c
0000008F529F9B00 00007FFD88C5A524 0000028212178010 0000000000000000 00000000FFFFFFFF 00007FFDB29DA365 videocapturefilter.ax!0x7ffd88c5a524
0000008F529FF680 00007FFDB29DE7B5 00000282109D1DA8 0000008F000009CF 0000008F529FF778 00000282109D1DA8 quartz.dll!0x7ffdb29de7b5
0000008F529FF7B0 00007FFDB29DE513 00000282105A5AC8 000002827FDED690 00000282105A5B98 00000282105A5B98 quartz.dll!0x7ffdb29de513
0000008F529FF7E0 00007FFDCF629669 00000282105A5AE8 00007FFDCF61DB40 00000282105A5B98 00000282105A5B98 win-dshow.dll!DShow::HDevice::SetupVideoCapture+0x5e9
0000008F529FF920 00007FFDCF6287DF 0000028202EF26D8 0000008F529FFA60 00000282109D1DA8 0000028202EF2650 win-dshow.dll!DShow::HDevice::SetVideoConfig+0x19f
0000008F529FF960 00007FFDCF61C975 0000000000000001 0000028202EF2650 0000028202EF2650 0000000000000000 win-dshow.dll!DShowInput::UpdateVideoConfig+0x5a5
0000008F529FFBF0 00007FFDCF61810D 0000028202EF2650 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowInput::DShowLoop+0x13d
0000008F529FFC80 00007FFDCF6184B5 0000000000000000 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowThread+0x25
0000008F529FFCB0 00007FFDEBDF3034 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffdebdf3034
0000008F529FFCE0 00007FFDEE7D3691 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffdee7d3691

Thread E30
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000008F514FE788 00007FFDEE7FAA24 0000028210685C80 0000028202FBC3B0 0000000000000001 00007FFDDC7C405F ntdll.dll!0x7ffdee7faa24
0000008F514FE790 00007FFDEAB69252 0000028202EF1FD0 00007FFDDB98A365 0000028200000000 0000000000000CD8 kernelbase.dll!0x7ffdeab69252

In the first lines you see the crash date and OBS and Windows version. That's the only important info for the first glance. Make sure the log is current and that OBS is current.

Then follows a list of the call stack of every thread. We only look at the top thread, this is the thread that actually crashed. At the right of that text block you find a list of DLLs. The topmost DLL is the where the crash actually happened, but beware: the faulty dll is often below it. Often, a dll calls another dll in a way that makes that dll crash.
So I go from top to bottom and check each dll: is it a Windows DLL, or is it a OBS DLL, or is ist some other DLL (brought with some 3rd party app/driver)? I act on the assumption that only a 3rd party DLL is the cause for the crash. And not a Windows or OBS dll. This is a simplification, of course.

The top is ntdll.dll. I search for it on my system and I see: this is from Microsoft in the Windows directory. A Windows DLL.
The next is videocaptureapi.dll. I search for it on my system, and I am unable to find it. Ah! this is a 3rd party DLL from an app I don't own. I go to Google and enter "videocaptureapi.dll". The results suggest this a part of the Elgato software, for a capture card or webcam.

That's all for your log. We found the culprit: The Elgato software. Do the usual troubleshooting if a device is malfunctioning: Uninstall the driver, reboot, get the newest driver from the vendor's website and install it. Check connections. Remove and reinstall the device. If it is USB: try a different port, a port without hub, a different cable.

AsherShow · Jan 10, 2019

koala said:
That's not an easy thing to tell. If someone writes a comprehensive how-to-read-an-obs-crashlog guide, nobody will read it, because it is too long.
The thing that most often happens is that some thread crashes due to a 3rd party dll or driver. Let's look into your log. Start notepad and load the crash log. Look at the top of the file:

Code:

Unhandled exception: c0000005 Date/Time: 2018-12-29, 1:15:24 AM Fault address: 7FFDEE784989 (c:\windows\system32\ntdll.dll) libobs version: 22.0.2 (64-bit) Windows version: 10.0 build 17134 (revision: 472; 64-bit) CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz Thread 1F50 (Crashed) Stack EIP Arg0 Arg1 Arg2 Arg3 Address 0000008F529F8690 00007FFDEE784989 0000000000000000 000002822EC24660 00000000FFFFFFFE 0000000000000000 ntdll.dll!0x7ffdee784989 0000008F529F8740 00007FFDEE77EFB7 000002822EC24640 0000008F529F8AA0 0000000000000000 0000000000000000 ntdll.dll!0x7ffdee77efb7 0000008F529F8770 00007FFDEE77EED0 00007FFDCF63FDE8 0000000000000000 00007FFD00000000 000002827DC80000 ntdll.dll!0x7ffdee77eed0 0000008F529F87A0 00007FFD87F2B27B 0000000000000000 00007FFD884DFEF8 0000000000000000 FFFFFFFFFFFFFFFC videocaptureapi.dll!0x7ffd87f2b27b 0000008F529F8A10 00007FFD87F2B62B 00007FFD884DFEF8 00007FFD884DF010 00007FFD87E93F50 00007FFD884E0DC0 videocaptureapi.dll!0x7ffd87f2b62b 0000008F529F8A40 00007FFD87F2B3DC 0000028200000005 00000282109D1D90 0000000000000001 FFFFFFFFFFFFFFFF videocaptureapi.dll!0x7ffd87f2b3dc 0000008F529F8AB0 00007FFD87E7E2C7 00000282109D1D90 0000000000000001 0000000000000000 0000000000000000 videocaptureapi.dll!0x7ffd87e7e2c7 0000008F529F9690 00007FFD88C5809C 00000282109D1DA8 00000282109D1DA8 0000000000000001 0000000000000001 videocapturefilter.ax!0x7ffd88c5809c 0000008F529F9B00 00007FFD88C5A524 0000028212178010 0000000000000000 00000000FFFFFFFF 00007FFDB29DA365 videocapturefilter.ax!0x7ffd88c5a524 0000008F529FF680 00007FFDB29DE7B5 00000282109D1DA8 0000008F000009CF 0000008F529FF778 00000282109D1DA8 quartz.dll!0x7ffdb29de7b5 0000008F529FF7B0 00007FFDB29DE513 00000282105A5AC8 000002827FDED690 00000282105A5B98 00000282105A5B98 quartz.dll!0x7ffdb29de513 0000008F529FF7E0 00007FFDCF629669 00000282105A5AE8 00007FFDCF61DB40 00000282105A5B98 00000282105A5B98 win-dshow.dll!DShow::HDevice::SetupVideoCapture+0x5e9 0000008F529FF920 00007FFDCF6287DF 0000028202EF26D8 0000008F529FFA60 00000282109D1DA8 0000028202EF2650 win-dshow.dll!DShow::HDevice::SetVideoConfig+0x19f 0000008F529FF960 00007FFDCF61C975 0000000000000001 0000028202EF2650 0000028202EF2650 0000000000000000 win-dshow.dll!DShowInput::UpdateVideoConfig+0x5a5 0000008F529FFBF0 00007FFDCF61810D 0000028202EF2650 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowInput::DShowLoop+0x13d 0000008F529FFC80 00007FFDCF6184B5 0000000000000000 0000000000000000 0000000000000000 0000000000000000 win-dshow.dll!DShowThread+0x25 0000008F529FFCB0 00007FFDEBDF3034 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffdebdf3034 0000008F529FFCE0 00007FFDEE7D3691 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffdee7d3691 Thread E30 Stack EIP Arg0 Arg1 Arg2 Arg3 Address 0000008F514FE788 00007FFDEE7FAA24 0000028210685C80 0000028202FBC3B0 0000000000000001 00007FFDDC7C405F ntdll.dll!0x7ffdee7faa24 0000008F514FE790 00007FFDEAB69252 0000028202EF1FD0 00007FFDDB98A365 0000028200000000 0000000000000CD8 kernelbase.dll!0x7ffdeab69252

In the first lines you see the crash date and OBS and Windows version. That's the only important info for the first glance. Make sure the log is current and that OBS is current.

Then follows a list of the call stack of every thread. We only look at the top thread, this is the thread that actually crashed. At the right of that text block you find a list of DLLs. The topmost DLL is the where the crash actually happened, but beware: the faulty dll is often below it. Often, a dll calls another dll in a way that makes that dll crash.
So I go from top to bottom and check each dll: is it a Windows DLL, or is it a OBS DLL, or is ist some other DLL (brought with some 3rd party app/driver)? I act on the assumption that only a 3rd party DLL is the cause for the crash. And not a Windows or OBS dll. This is a simplification, of course.

The top is ntdll.dll. I search for it on my system and I see: this is from Microsoft in the Windows directory. A Windows DLL.
The next is videocaptureapi.dll. I search for it on my system, and I am unable to find it. Ah! this is a 3rd party DLL from an app I don't own. I go to Google and enter "videocaptureapi.dll". The results suggest this a part of the Elgato software, for a capture card or webcam.

That's all for your log. We found the culprit: The Elgato software. Do the usual troubleshooting if a device is malfunctioning: Uninstall the driver, reboot, get the newest driver from the vendor's website and install it. Check connections. Remove and reinstall the device. If it is USB: try a different port, a port without hub, a different cable.

Tremendously helpful. Thank you

Question / Help OBS Crashes Upon Opening "Woops, OBS Has Crashed!"

AsherShow

New Member

Attachments

Suslik V

Active Member

koala

Active Member

AsherShow

New Member