OBS randomly closing (not crashing)

[Malastrome]

Hello there!

So I've been having problems with OBS ever since January when the Windows 11 24H2 update was forced on me.
There's a lot here, so sorry for the paragraphs.

I've been using Windows 11 since I first built my new computer last year and I've had no issues with OBS. All of the sudden once Windows 11 updates from 23H2 to 24H2, I'm having a lot of problems. OBS starts randomly closing while streaming and it's not generating any crash logs. I come to discover that the mp4s I was loading into my scenes would cause it to close every 2-15 minutes like clockwork. I've used these mp4s for years without issue and they were all fine until the Windows update. I removed those from my OBS scenes entirely, but the issues still persisted. I had reinstalled OBS several times with and without plugins to no avail as well. I even installed older builds and the problem was still happening. Additionally, on scenes that weren't even using the mp4s at the time it would close too.

Eventually I noticed other people complaining online about OBS crashing around when the Windows update came out, so I presumed it was 24H2 and did a clean install back to 23H2.
That seemed like it worked for a time, but the problem came back shortly later and OBS was still randomly closing, albeit much less often. Maybe once every hour or five hours.

As of now, I've done a repair reinstall of Windows and it pushed me forward on to 24H2. The problem with it closing with mp4s loaded into a scene every 2-15 minutes isn't an issue anymore (as far as I can tell), but the random closing is still occurring and I'm at a complete loss as to what the issue could be.

I tried to troubleshoot as much as possible before posting for help, but I would absolutely appreciate help with this. It's been plaguing my streams for months now. I also ran my user logs through the analyzer tool and it didn't come up with anything.
I'll attach a log from when it closed without warning, but I don't have any crash logs I can provide since they just don't generate.


Thank you very much for the help! If you need any other info please let me know!

 

[AaronD]

I got fed up with Windoze $#@! a couple of years ago, switched hard to Linux, and never looked back.

I recommend Ubuntu Studio:

Ubuntu Studio – A free and open operating system for creative people.

ubuntustudio.org

It's designed specifically for creatives, and has a TON of GOOD apps pre-installed and already working for things like drawing, photomanipulation, audio, video, etc. OBS is one of those apps.

 

[Malastrome]

I got fed up with Windoze $#@! a couple of years ago, switched hard to Linux, and never looked back.

I recommend Ubuntu Studio:

Ubuntu Studio – A free and open operating system for creative people.

ubuntustudio.org

It's designed specifically for creatives, and has a TON of GOOD apps pre-installed and already working for things like drawing, photomanipulation, audio, video, etc. OBS is one of those apps.

I'm looking for a solution, though. I'm not wanting to switch operating systems, and I fail to see how recommending switching OS' is considered 'support'.
I'm tempted to completely roll back to Windows 10 to see if that would fix things, but my last consideration before doing that was to ask for help here, because I don't even fully know if Windows is causing the problem.

 

[AaronD]

I'm looking for a solution, though. I'm not wanting to switch operating systems, and I fail to see how recommending switching OS' is considered 'support'.

If it makes it work...

Your original post sounds like Windows is forcing you into something that doesn't work. If that's really true, then ditch Windows. Don't be married to anything.

 

[koala]

If OBS closes unexpectedly, it usually crashed. Does it really not crash but simply close? The log you provided just ends with no conclusion why it ends - as if OBS just continues to run.

 

[rockbottom]

SE & RTMP Multi-out plugins are suspect. SE just sucks but the Multi-out that is installed & active may be stale or bad. The installed version is not listed in the log & the latest version doesn't appear to be fully vetted yet for OBS 31.0.2.

15:48:35.244: obs-multi-rtmp.dll

15:55:25.000: ==== Streaming Start ===============================================
15:55:50.206: [rtmp stream: 'multi-output'] Connecting to RTMP URL rtmp://a.rtmp.youtube.com/live2...
15:55:50.230: [rtmp stream: 'multi-output'] Interface: Realtek Gaming 2.5GbE Family Controller (ethernet, 1000↓/1000↑ mbps)
15:55:50.344: [rtmp stream: 'multi-output'] Connection to rtmp://a.rtmp.youtube.com/live2 (142.251.16.134) successful
15:55:50.344: [rtmp stream: 'multi-output'] Socket send buffer is 65536 bytes

Releases · sorayuki/obs-multi-rtmp

OBS複数サイト同時配信プラグイン. Contribute to sorayuki/obs-multi-rtmp development by creating an account on GitHub.

github.com

 

[prgmitchell]

Hello there!

So I've been having problems with OBS ever since January when the Windows 11 24H2 update was forced on me.
There's a lot here, so sorry for the paragraphs.

I've been using Windows 11 since I first built my new computer last year and I've had no issues with OBS. All of the sudden once Windows 11 updates from 23H2 to 24H2, I'm having a lot of problems. OBS starts randomly closing while streaming and it's not generating any crash logs. I come to discover that the mp4s I was loading into my scenes would cause it to close every 2-15 minutes like clockwork. I've used these mp4s for years without issue and they were all fine until the Windows update. I removed those from my OBS scenes entirely, but the issues still persisted. I had reinstalled OBS several times with and without plugins to no avail as well. I even installed older builds and the problem was still happening. Additionally, on scenes that weren't even using the mp4s at the time it would close too.

Eventually I noticed other people complaining online about OBS crashing around when the Windows update came out, so I presumed it was 24H2 and did a clean install back to 23H2.
That seemed like it worked for a time, but the problem came back shortly later and OBS was still randomly closing, albeit much less often. Maybe once every hour or five hours.

As of now, I've done a repair reinstall of Windows and it pushed me forward on to 24H2. The problem with it closing with mp4s loaded into a scene every 2-15 minutes isn't an issue anymore (as far as I can tell), but the random closing is still occurring and I'm at a complete loss as to what the issue could be.

I tried to troubleshoot as much as possible before posting for help, but I would absolutely appreciate help with this. It's been plaguing my streams for months now. I also ran my user logs through the analyzer tool and it didn't come up with anything.
I'll attach a log from when it closed without warning, but I don't have any crash logs I can provide since they just don't generate.


Thank you very much for the help! If you need any other info please let me know!

You'd want to look in the application logs section of event viewer to see what is going on. If you could screenshot the information there I could probably point you in the right direction. An example of how this might look:

 

[Malastrome]

Thanks for the replies and suggestions! To reply to everyone in order:

Yes! OBS has been closing without warning very randomly, so it doesn't generate a crash log. I have a few more I can post if needed as well, but the prime suspect MAY have been StreamElements popping up that infinite looping error and trying to reset itself.
I've noticed that all of the browser sources I add pop up an error message kind of like SE's did in my log, but everything else only pops up once and it's not looping forever.
Additionally, some of the logs when closing randomly mention memory leaks occurring right at the end, but they don't always happen at the end of every log. It's very weird.

I'll keep that in mind for Multi-out if my problem keeps happening. I had previously used an older version of OBS as well to see if that helped at the time, but it didn't. Again, the issue might just be SE's error message looping.

Thank you for the help! I very much appreciate it!

 

[Malastrome]

You'd want to look in the application logs section of event viewer to see what is going on. If you could screenshot the information there I could probably point you in the right direction. An example of how this might look:

View attachment 112016

Hey thank you very much! I can't really parse the info in the event viewer or logs, so I appreciate the help!
This is one of the errors that occurred from OBS, but the others look about the same. If you need any other info, let me know!

 

[Malastrome]

Oh, one other thing to mention too- I streamed today for about four hours with the SE plugin completely removed and all of the SE browser sources gone, and I didn't come across any problems.
I also left OBS open all night and it didn't close randomly either

 

[prgmitchell]

Oh, one other thing to mention too- I streamed today for about four hours with the SE plugin completely removed and all of the SE browser sources gone, and I didn't come across any problems.
I also left OBS open all night and it didn't close randomly either

Okay then we can assume it is that for now, the se.live plugin wouldn't have been my first guess based on that event viewer screenshot but considering how often it seems to break OBS it wouldn't surprise me either.

 

[Malastrome]

I'll update again once I get a few more streams in if it's all good, or if there are any more problems.
Thanks everyone for the help!

Although just a side question; What's up with the user logs reporting errors on every browser source that's added? Even adding Twitch for alerts does that. They don't loop like SE does thankfully, but I guess is that just normal?

 

[AaronD]

What's up with the user logs reporting errors on every browser source that's added? Even adding Twitch for alerts does that. They don't loop like SE does thankfully, but I guess is that just normal?

Everyone wants to be a web developer, and everyone wants to use web stuff, even for things that it's not appropriate for. (if all you have is a hammer...) So the average internal quality goes down, even for things that it *is* appropriate for, and not everyone cares about internal errors as long as things work at the end. Then those errors fill up your log file.

 

[Malastrome]

Well, back again to report suddenly more problems.
So I switched my alerts over to Twitch Alerts and don't have any sources or plugins using SE anymore. I had a mostly fine nine hour stream aside from one OBS crash (which I know what the problem was with that), but then after I exited the game and switched the scene OBS closed twice in a row.
I was on these same scenes at the start of my stream before I had launched the game, so I'm not sure what the problem could be now.

I attached the logs from when OBS closed. Reminder that crash logs aren't generated when it closes.
Additionally I'm still using the multistream plugin, but if I was able to go nine hours without OBS closing then I don't understand what could have broken near the end of my stream.

Thank you anyone willing to help!

 

[Malastrome]

For the hell of it as well, if anyone wanted to check the crash log from the middle of the stream. I don't think it's related to OBS closing again like previously with SE, but who knows.
For context, I had OBS pop up a message that it had crashed, but I was able to continue streaming for another 2-3 hours before I touched the notification pop up again and OBS finally crashed/closed.

 

[prgmitchell]

For the hell of it as well, if anyone wanted to check the crash log from the middle of the stream. I don't think it's related to OBS closing again like previously with SE, but who knows.
For context, I had OBS pop up a message that it had crashed, but I was able to continue streaming for another 2-3 hours before I touched the notification pop up again and OBS finally crashed/closed.

Yes this matches the event viewer log and is why I mentioned earlier that streamelements wouldn't have been my first suggestion. I would try installing iTunes which will give you a new "CoreAudio" audio encoder option to use in OBS in settings>output. Swap over to that and let me know if you are crashing anymore.

 

[Malastrome]

Yes this matches the event viewer log and is why I mentioned earlier that streamelements wouldn't have been my first suggestion. I would try installing iTunes which will give you a new "CoreAudio" audio encoder option to use in OBS in settings>output. Swap over to that and let me know if you are crashing anymore.

Alrighty I went ahead and got that enabled now. Is it just a different audio encoder and that's it? I wouldn't need to set up anything differently (for now) with my audio right?

 

[prgmitchell]

Alrighty I went ahead and got that enabled now. Is it just a different audio encoder and that's it? I wouldn't need to set up anything differently (for now) with my audio right?

Correct, no other changes to make.

 

[Malastrome]

Thank you very much for the quick help! I won't be streaming again until Wednesday or Friday, so I'll report back after that.

I forgot to mention too, I had streamed without any issues for three 4 hour streams last week, but I didn't have any browser sources active. I'm not sure if adding browser sources again is the problem, but hopefully the codec change helps things.

 

[Malastrome]

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!