OBS randomly closing (not crashing)

[prgmitchell]

I let OBS sit idle (not streaming) overnight and I think around six or so hours later it closed again. My bed is near my PC so I noticed that my webcam had shut off. Reopening OBS I got the message that it closed unexpectedly as per usual and yet again there was no crash report. I think worse yet is that the log didn't even show anything after I switched scenes around hours prior.

Just in the event it's something with the multistream plugin from Sorayuki, I uninstalled that and switched to Aitum Multistream.

The crash log feels like to me it was independent of whatever is going on with my setup. I'll keep the CoreAudio Encoder enabled and see if that crash crops up again, but the problem could be something else entirely.

In case it's helpful at all, I have these mp4s I play as literal backgrounds to specific scenes I'm on. So like I'll record a nice scenic spot in a game, edit it a bit in Premiere Pro so it's looped nicely, and then have those play on my starting up scene when I first start streaming, BRB scene, and when I have chat up on-screen before I start playing anything as a sort of Just Chatting section.

I don't know if there could be a problem with those maybe? When I went to end my stream last night I popped back over to the Just Chatting scene that plays one of those mp4s, that's when OBS closed twice in a row. So it's especially weird it was in such quick succession. Also weird that I was on that same scene at the start of my stream for twenty minutes with no problem.

Or aside from all that, could it be browser sources being messed up again somehow?

I'm trying to provide as much as I can here for troubleshooting avenues, so hopefully any of these lines of thought spark something!

Sorry, I didn't realize when I made my suggestion that you are also having issues when you are not streaming/recording.....the audio encoder would make no difference here. I suggested it because the crash is with ffmpeg which would've meant it was either the audio encoder that was being used or possibly just a media source you have added in your scene collection since those use ffmpeg as well.

 

[Malastrome]

Sorry, I didn't realize when I made my suggestion that you are also having issues when you are not streaming/recording.....the audio encoder would make no difference here. I suggested it because the crash is with ffmpeg which would've meant it was either the audio encoder that was being used or possibly just a media source you have added in your scene collection since those use ffmpeg as well.

All good no worries. It did crash the one time, so there's a potential fix for that at least.

 

[Malastrome]

Updating again with an interesting development, and potentially a question for anyone that could have an idea.
So removing the media source backgrounds from all of my scenes I mentioned in one of my prior posts didn't cause OBS to close at all while idling for 12+ hours. Then today I added the backgrounds back in as VLC sources and I still haven't had any problems all day idling.

So as of now it seems like things are on the up and up, but I'll have to see how my next few streams go next week to really confirm if everything is fine now.
So my current question is, why after years of using media sources with these specific videos, that some are a gig or two in size, would they suddenly break now, or what setting could be the culprit for why they don't work now?

Additionally looking back to September, I remembered that I got a replacement/upgraded CPU from Intel when I sent my faulty one in to confirm it was bad (It was an I9 13900K, they sent me an I9 14900K). I flashed my BIOS with an update to prevent the problem that their CPUs were having when they were recalling them. Could the BIOS flash have caused my problems with OBS by changing a setting or something? I wasn't having problems until January granted, but just another thought I had.

Thank you again for the help! I'm hoping this just about solves the problems I've been having.

 

[Suslik V]

Unhandled exception: c0000005
...
Thread 6E60: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000021E98FF9D0 00007FF83AB8656F 0000000000000000 000001542CD5D470 00000154DB1B57D4 00007FF800000018 avcodec-61.dll!0x7ff83ab8656f
00000021E98FFB00 00007FF83AB86FB7 0000000000000008 0000000000000008 00000154D7BC7BE0 000001542CD5D470 avcodec-61.dll!0x7ff83ab86fb7
00000021E98FFB70 00007FF83AB870C6 0000000000000018 00000154D7BC7BE0 000001542CD5A060 00000000000000C8 avcodec-61.dll!0x7ff83ab870c6
00000021E98FFBC0 00007FF83AAF8288 000001542CD5A060 00000154DB1B57D4 0000000000000018 00000000000000C8 avcodec-61.dll!0x7ff83aaf8288
00000021E98FFCC0 00007FF83AAF93E0 0000015400000140 00000154000000B4 000000000000001C 00007FF900000004 avcodec-61.dll!0x7ff83aaf93e0
00000021E98FFD60 00007FF83AAFD2F2 00000154C246B320 0000000000000000 0000000000000000 0000000000000000 avcodec-61.dll!0x7ff83aafd2f2
00000021E98FFE20 00007FF83AB7FD84 00000154D73AF660 0000000000000000 0000000000000000 0000000000000000 avcodec-61.dll!0x7ff83ab7fd84
00000021E98FFE50 00007FF9082E4EA0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ff9082e4ea0
00000021E98FFE80 00007FF909CFDBE7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff909cfdbe7
00000021E98FFEB0 00007FF90A905A6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff90a905a6c

This crash likely (my own assumption) during playback of the .webm file in Media Source of OBS (you had the one named "Retro Side Gears.webm"). Sometimes users has Stinger transition and using .webm file.

If the mentioned media file is really the cause of the problem, you may try to find developer, for example in Discord (links in top right corner of the screen), and share your findings. Also, developers may ask for memory dumps (can be created in background on application "close", you'll be instructed how to do it if needed).

At least, on this forum there were similar threads (all has truncated crash logs, so it is hard to analyze), different CPUs. Thus I assume that your hardware is OK. Examples:

OBS Crashing due to avcodec-61 and nvencodeapi64.dll

The first type of crash: nvencodeapi64.dll Could you advice what to do? My OBS crashing due to nvencodeapi64.dll Crash #3: Fault address: 7FFF753F5D10 (c:\windows\system32\nvencodeapi64.dll) Crash report: https://obsproject.com/logs/aPnO72mwWySM2On3 Current log...

obsproject.com

OBS Crashing recently pointing towards avcodec-61.dll

Recently my OBS has been crashing multiples times per stream and I am not sure why or what update did it? Could have been the windows 24H2 one or the 31.0.1 OBS update I have no clue but it has never been this bad before and has worked generally fine...

obsproject.com

 

[prgmitchell]

Updating again with an interesting development, and potentially a question for anyone that could have an idea.
So removing the media source backgrounds from all of my scenes I mentioned in one of my prior posts didn't cause OBS to close at all while idling for 12+ hours. Then today I added the backgrounds back in as VLC sources and I still haven't had any problems all day idling.

So as of now it seems like things are on the up and up, but I'll have to see how my next few streams go next week to really confirm if everything is fine now.
So my current question is, why after years of using media sources with these specific videos, that some are a gig or two in size, would they suddenly break now, or what setting could be the culprit for why they don't work now?

Additionally looking back to September, I remembered that I got a replacement/upgraded CPU from Intel when I sent my faulty one in to confirm it was bad (It was an I9 13900K, they sent me an I9 14900K). I flashed my BIOS with an update to prevent the problem that their CPUs were having when they were recalling them. Could the BIOS flash have caused my problems with OBS by changing a setting or something? I wasn't having problems until January granted, but just another thought I had.

Thank you again for the help! I'm hoping this just about solves the problems I've been having.

Media sources use ffmpeg so the root cause would probably be a change on their end, the dependencies that OBS uses are frequently updated.

 

[Malastrome]

Unhandled exception: c0000005
...
Thread 6E60: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000021E98FF9D0 00007FF83AB8656F 0000000000000000 000001542CD5D470 00000154DB1B57D4 00007FF800000018 avcodec-61.dll!0x7ff83ab8656f
00000021E98FFB00 00007FF83AB86FB7 0000000000000008 0000000000000008 00000154D7BC7BE0 000001542CD5D470 avcodec-61.dll!0x7ff83ab86fb7
00000021E98FFB70 00007FF83AB870C6 0000000000000018 00000154D7BC7BE0 000001542CD5A060 00000000000000C8 avcodec-61.dll!0x7ff83ab870c6
00000021E98FFBC0 00007FF83AAF8288 000001542CD5A060 00000154DB1B57D4 0000000000000018 00000000000000C8 avcodec-61.dll!0x7ff83aaf8288
00000021E98FFCC0 00007FF83AAF93E0 0000015400000140 00000154000000B4 000000000000001C 00007FF900000004 avcodec-61.dll!0x7ff83aaf93e0
00000021E98FFD60 00007FF83AAFD2F2 00000154C246B320 0000000000000000 0000000000000000 0000000000000000 avcodec-61.dll!0x7ff83aafd2f2
00000021E98FFE20 00007FF83AB7FD84 00000154D73AF660 0000000000000000 0000000000000000 0000000000000000 avcodec-61.dll!0x7ff83ab7fd84
00000021E98FFE50 00007FF9082E4EA0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ff9082e4ea0
00000021E98FFE80 00007FF909CFDBE7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff909cfdbe7
00000021E98FFEB0 00007FF90A905A6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff90a905a6c

This crash likely (my own assumption) during playback of the .webm file in Media Source of OBS (you had the one named "Retro Side Gears.webm"). Sometimes users has Stinger transition and using .webm file.

If the mentioned media file is really the cause of the problem, you may try to find developer, for example in Discord (links in top right corner of the screen), and share your findings. Also, developers may ask for memory dumps (can be created in background on application "close", you'll be instructed how to do it if needed).

At least, on this forum there were similar threads (all has truncated crash logs, so it is hard to analyze), different CPUs. Thus I assume that your hardware is OK. Examples:

OBS Crashing due to avcodec-61 and nvencodeapi64.dll

The first type of crash: nvencodeapi64.dll Could you advice what to do? My OBS crashing due to nvencodeapi64.dll Crash #3: Fault address: 7FFF753F5D10 (c:\windows\system32\nvencodeapi64.dll) Crash report: https://obsproject.com/logs/aPnO72mwWySM2On3 Current log...

obsproject.com

OBS Crashing recently pointing towards avcodec-61.dll

Recently my OBS has been crashing multiples times per stream and I am not sure why or what update did it? Could have been the windows 24H2 one or the 31.0.1 OBS update I have no clue but it has never been this bad before and has worked generally fine...

obsproject.com

So the webm Retro Side Gears is something on another scene that wasn't on the scene I was using when OBS crashed. If that crash crops up again then I'll remove that, thanks for the heads up. But the overall problem here for the original post wasn't the crash, it was with OBS closing randomly without acknowledging that it had crashed via a crash log.
The other media I had in other scenes were pretty much like wallpaper engine wallpapers that I made myself. They're in the background of some of my scenes, but not the one that generated the crash. They were on the scenes that would cause OBS to close randomly.
It's a weird circumstance if you don't know the layout lol So sorry for any confusion! The crash log was just in a manner of, "Oh while I'm here this happened too that I'm pretty sure is unrelated to the current problem- Which it seems like it was with OBS closing.

But it's good to know regardless that it most likely wasn't some hardware problem. Thank you for checking!

 

[Malastrome]

Media sources use ffmpeg so the root cause would probably be a change on their end, the dependencies that OBS uses are frequently updated.

That's very good to know then. I can't remember, but I wouldn't be surprised if I had updated OBS at that time or shortly after when Windows had updated to 24H2.
I'll update again on results sometime next week, or if I have any more problems. Thank you!

 

[Suslik V]

...the webm Retro Side Gears is something on another scene that wasn't on the scene I was using when OBS crashed.

It doesn't matter. What I see from the logs - it is looping and running from OBS launch.
In your logs this media source has attribute: restart_on_activate: no

If you made unchecked Restart playback when source becomes active option then Media Source will always start during OBS launch (even when this Media Source disabled/invisible/not_in_the_current_scene). This is by design.

But the overall problem here for the original post wasn't the crash, it was with OBS closing randomly without acknowledging that it had crashed via a crash log.

@koala said in the start of this thread that this is application crash (unusual termination of the program run). But some crashes so complicated that requires help from the developer to be resolved. Please, consider to ask for more help (if issue will be resolved it may improve OBS too).