OBS just closing wo/errors

[Suslik V]

Is there new crash report? Nobody of developers will look at the crash reports from old version of OBS. Use most recent OBS. Most recent version of OBS can be found here (under the "Assets" spoiler):

Releases · obsproject/obs-studio

OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio

github.com

Nobody will look at errors that can be analyzed by machine:

Analyzer | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.

obsproject.com

Solve these first.

If you finally made it here.
If program crashes without making crash report then you need to find developer (some can be found in Discord - there is links in the top right corner of the forum), you'll be instructed how to make memory dump on application exit. The conversation with developer may look similar to this: https://obsproject.com/forum/threads/obs-crashing-all-the-time-from-rtsp-sources.165637/post-608704 - you making the memory dump and shares it privately with the developer. Then you waiting for results.

If you tired and know that some previous version of OBS worked OK for you - use it instead.

 

[Fan4eG]

Is there new crash report?

emm.. the last one of mine.

Use most recent OBS

funny. i aint switching to the new version till im sure all the plugins support it. would be dumb to do it otherwise.

Nobody will look at errors that can be analyzed by machine

da hell is that means?

Solve these first

what do u mean? HAGS? i disable it and nthg change.

then you need to find developer

for real. cant believe i didnt think of just hitting up the dev right away, thanks for the help.

 

[Fan4eG]

@R1CH can i beg you for help please?

 

[Suslik V]

I forgot to add.

The "Crash Reports" are special log-files of OBS. By default, crash reports are located in the folder:
%APPDATA%\obs-studio\crashes

They are different from the OBS session logs that are named "Log Files" in Help menu of OBS and located in the folder:
%APPDATA%\obs-studio\logs

-------------------------

i aint switching to the new version till im sure all the plugins support it. would be dumb to do it otherwise

...deleting all the plugins (by removing their .dll files from the plugins folder in Program Files\obs-studio\obs-plugins)...

So, it was quite possible to run newer OBS without the plugins, wasn't it? So, why you have tested the old, not fixed, version of OBS when newer release was available? If you need help from the developer - you need latest build of OBS.

In the log I see:

02:36:33.451: Current Date/Time: 2025-04-11, 02:36:33
...
02:36:33.557: OBS 31.0.1 (64-bit, windows)
...
02:36:33.562:       HAGS Status:    Enabled (Default: No, Driver status: Supported)

and so on. But you said that:

HAGS gave pretty much the same results

This was in the one post. You need some logic in you actions. You writing one info and posting logs from other attempts. How you will speak to developer? "I did something and it doesn't work" - this way? You need some algorithm. Step by step to solve the issues.

-------------------------

Here, on the forum, users can gather statistic and rise alarm for old and rare issues present in OBS. But that's all. If you have found solution to some problem - you can share it. I don't think that it is place to beg for something or similar. If you have some suggestions that can improve OBS, here is: https://ideas.obsproject.com/

 

[Fan4eG]

So, it was quite possible to run newer OBS without the plugins, wasn't it?

i dont get the point of this, when the same problems were happening on the older version too (then it was the latest one). i dont get it, is it really that hard to understand? if you go back to the first pages of this thread, i wrote that i switched to the new THEN version of obs, like 31.0.2, and the issues were the same. theres just no point in updating to a new version.

You need some logic in you actions

i legit thought it was just common sense — i turned off HAGS, launched obs, started a test stream, it ran for like a minute then crashed again with that same avcodec error. then i turned HAGS back on (since i need it for frameGen in games). figured that was so basic i didnt even bother mentioning it. fine. from now on ill report every little sneeze in here, my bad.


and again, lol, this is just funny at this point. how come obs used to work perfectly fine with HAGS all the time before, then outta nowhere it just starts closing with that avcodec-61.dll error. and something tells me this aint about plugins or HAGS at all.

 

[PaiSand]

In your latest log file you can't see anything related to a crash, just HAGS and other issues related to incorrect use of sources that are known to cause problems.
Only deleting the plugin's DLLs may not be enough for some plugins that store files within %appdata%\obs-studio\ or other folders within the OBS installation. This files need to be removed too.
So, you didn't presented any new crash report, along with its corresponding log file, showing the issue on the avcodec-61.dll, needed to advance on an analysis of the issue. No new crash report on the issue, the issue isn't present anymore.

If you want the issue resolved you should do what is asked to do to narrow the problem. If the problem isn't present anymore after doing what is asked to do, the issue was solved.

If the issue is caused by a third party app, plugin, script or anything not related to OBS, then you need to get in contact with their support.

 

[Suslik V]

Look, you can test the issue against different versions of the program and different OSes. But when you asking developer for help you should provide latest results for the latest version of the program. There are many developers for the project. Nobody keeps in mind all the changes. You can mention that issue is the same as it was in some particular version of the program. But the project is moving forward. It is hard to analyze data from the past when everything was changed.

...my OBS started to close during streaming, without any error.

...it just starts closing with that avcodec-61.dll error

Two different issues?

 

[Fan4eG]

cause problems

how come obs didnt closing before even tho it had the same exact issues in the log file back then too?

Only deleting the plugin's DLLs may not be enough

so how am i even supposed to properly remove them if i didnt use an installer, just grabbed the zip from github?

So, you didn't presented any new crash report, along with its corresponding log file, showing the issue on the avcodec-61.dll

i have no clue where that error shows up in the log file, im talkin about the "event viewer" in windows.

you should do what is asked to do to narrow the problem

and like, for the hundredth time, what exactly are yall asking me to do? disable HAGS and remove screene capture and game capture from the same source? that makes no sense, cause before this issue came up — with those same HAGS and capture setups — obs was running just fine for years. now suddenly its broken.


i was just thinking itd be way easier to just reinstall obs or even windows, instead of spending 3 weeks trying to fix a problem "no one even knows how to deal with" xd

 

[Fan4eG]

Two different issues

друже, if you actually paid attention to what i said, then no — its just one error. again, OBS shuts down clean, like alt+f4 розумієш?
the avcodec-61.dll error only shows up in Windows "Event Viewer" — thats the only place i even figured out why its crashing.

 

[Suslik V]

...trying to fix a problem "no one even knows how to deal with"

Not quite true. There were good suggestions, one of them:

My recommended solution at the moment while we still research these would be to install VLC and swap your media sources over to VLC sources instead.

But you decided to infinitely repair the bike instead of riding it:

I just don't want to deal with all this VLC stuff...

Spoiler: in depth

...I still don't have VLC source item in OBS

You shouldn't change the path that it is installed to at all.

...path where OBS looking for VLC files are hardcoded in Windows version and read from the registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\VideoLAN\VLC]
"InstallDir"

OBS expects "libvlc", "libvlccore" libraries and "plugins" folder of VLC Player in this directory (parameter "InstallDir") – tested for VLC v3.0.6, 64-bit.

Anyway, let's us hope that the issue will be resolved at some point. If you need tools to analyze what encoder was used in the media file, then you may try MediaInfo util, it has nice feature to export in the "text" format.

For info. In this post I wrote what FFmpeg libs are used in official OBS builds for Windows: https://obsproject.com/forum/threads/obs-crashes-while-recording-video.185200/post-678058

 

[Fan4eG]

one of them

yeah, i thought the same at first, but that means id have to rework a TON of sources in OBS, resize em, crop em, all that stuff, u got it. so im thinkin ill update to the latest version first (even if the plugins aint ready yet) and see what i can do. if that dont work, ill just reinstall OBS. but honestly, it already feels like a system issue, so ill probably end up reinstalling the whole thing.

instead of riding it

i tried installin it, you read the thread yourself. it just never showed up in OBS. someone even pointed that out, called it weird. anyway, i decided to drop it.


i can still send the crash report if that helps anyone.

 

[prgmitchell]

After you said it wasn't working I linked the correct installer and was willing to troubleshoot that but you stated it would take "too much time" to swap over your sources.....which is a bit ironic when you consider how long this thread has gone on afterwards. Looking at the same crash logs over and over isn't going to yield new info or solutions. The entire point of my suggestion was to confirm that it is your media sources that are the direct cause of your crashes and until you do that you are kind of frozen in time with this issue.

 

[Fan4eG]

After you said it wasn't working I linked the correct installer and was willing to troubleshoot that but you stated it would take "too much time" to swap over your sources.....which is a bit ironic when you consider how long this thread has gone on afterwards. Looking at the same crash logs over and over isn't going to yield new info or solutions. The entire point of my suggestion was to confirm that it is your media sources that are the direct cause of your crashes and until you do that you are kind of frozen in time with this issue.

so lemme get this straight — is it actually the “proper” way to use media sources in OBS only through VLC? like not just for me, but in general? cuz I seriously don’t get why this issue happens specifically on my setup. someone said .webm might be the cause, but I already fixed that — so it ain't that. then why is it always me and always ffmpeg sources actin up?

and even if I switch every single thing to VLC, how the hell do I know it won’t break again later? maybe after an update, and then the VLC sources become the new problem? ok, ill do it next time and write about it here.

 

[prgmitchell]

so lemme get this straight — is it actually the “proper” way to use media sources in OBS only through VLC? like not just for me, but in general? cuz I seriously don’t get why this issue happens specifically on my setup. someone said .webm might be the cause, but I already fixed that — so it ain't that. then why is it always me and always ffmpeg sources actin up?

and even if I switch every single thing to VLC, how the hell do I know it won’t break again later? maybe after an update, and then the VLC sources become the new problem? ok, ill do it next time and write about it here.

You are describing troubleshooting.... "what if" doesn't really matter until you test it, that is the point of this. You are trying to play whack-a-mole with guesses instead of just eliminating what seems to be the source of the issue (your ffmpeg based media sources) and seeing if you continue to crash.

 

[Fan4eG]

You are describing troubleshooting.... "what if" doesn't really matter until you test it, that is the point of this. You are trying to play whack-a-mole with guesses instead of just eliminating what seems to be the source of the issue (your ffmpeg based media sources) and seeing if you continue to crash.

Do you have any idea why this started happening spontaneously and for no reason? considering it just happened all at once and that I didn't update the wind or OBS or plugins.

 

[prgmitchell]

Do you have any idea why this started happening spontaneously and for no reason? considering it just happened all at once and that I didn't update the wind or OBS or plugins.

Nope, but also not really super relevant to figure out until the issue is actually confirmed.

 

[Fan4eG]

Nope, but also not really super relevant to figure out until the issue is actually confirmed.

Okay, I'll try replacing the sources with VLС
Can you please explain the plan of action in more detail? I already have VLС installed, but the sources did not appear. I also did something in the registry, but they did not appear either.

 

[prgmitchell]

Run the installer here: https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe
It should default to the path above when installing but if it isn't for some reason change it to that.

OBS will recognize it once this is done and enable the source...if it isn't working currently that would imply that it wasn't installed to the correct location for some reason.


EDIT: you really shouldn't have to do anything with the registry but you can confirm that it looks correct, OBS is looking here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VideoLAN\VLC

 

[Fan4eG]

View attachment 112838


Run the installer here: https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe
It should default to the path above when installing but if it isn't for some reason change it to that.

OBS will recognize it once this is done and enable the source...if it isn't working currently that would imply that it wasn't installed to the correct location for some reason.


EDIT: you really shouldn't have to do anything with the registry but you can confirm that it looks correct, OBS is looking here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VideoLAN\VLC
View attachment 112839

ty. I'll try again later today and report back after the tests.

 

[Fan4eG]

View attachment 112838


Run the installer here: https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe
It should default to the path above when installing but if it isn't for some reason change it to that.

OBS will recognize it once this is done and enable the source...if it isn't working currently that would imply that it wasn't installed to the correct location for some reason.


EDIT: you really shouldn't have to do anything with the registry but you can confirm that it looks correct, OBS is looking here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VideoLAN\VLC
View attachment 112839

yeah and one more.
Can I skip adding new VLC sources to my current OBS profile and just make a brand new one with VLC to test it there? Or do I gotta fully replace the old sources by deleting em and adding VLC instead?
So, do I gotta stick with VLC sources long-term? Or can I switch back to default ones later on? Cuz I'm planning to reinstall Windows soon anyway.

​