Mid-stream crash

BrunoDanUy

BrunoDanUy

New Member
Issue still persists.
I got the "Obs has crashed" pop up again, but stream was working fine, so I was able to continue by ignoring the pop up.
It later crashed definitely when attempting to type in chat.
 
BrunoDanUy

BrunoDanUy

New Member
Is there a way to know which plugin may be causing the issue?
from the list of the log
"
16:28:00.366: Loaded Modules:
16:28:00.366: StreamDeckPlugin.dll
16:28:00.366: win-wasapi.dll
16:28:00.366: win-dshow.dll
16:28:00.366: win-capture.dll
16:28:00.366: vlc-video.dll
16:28:00.366: text-freetype2.dll
16:28:00.366: source-record.dll
16:28:00.366: rtmp-services.dll
16:28:00.366: obs-x264.dll
16:28:00.366: obs-websocket.dll
16:28:00.366: obs-vst.dll
16:28:00.366: obs-transitions.dll
16:28:00.366: obs-text.dll
16:28:00.366: obs-qsv11.dll
16:28:00.366: obs-outputs.dll
16:28:00.366: obs-filters.dll
16:28:00.366: obs-ffmpeg.dll
16:28:00.366: obs-browser.dll
16:28:00.366: image-source.dll
16:28:00.366: frontend-tools.dll
16:28:00.366: enc-amf.dll
16:28:00.366: decklink-output-ui.dll
16:28:00.366: decklink-captions.dll
16:28:00.366: coreaudio-encoder.dll
16:28:00.366: audio-monitor.dll"

I haven't installed most of these. Should I remove all the ones I don't recognize?
 
PaiSand

PaiSand

Active Member
The simple way, like we all say in innumerable answers, is to use the analizer.

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 obsproject.com

You should know which ones you installed. The stream deck plugin is not the issue.
 
BrunoDanUy

BrunoDanUy

New Member
None of the points brought up in the analyzer says that a plugin is causing the crash.

The only point reported by the analyzer that points to an issue is "Max Audio Buffering".
A google search on this term returns:
"Max audio buffering is usually caused by either near-100% CPU usage, or a device with a timecode that doesn't want to sync up with OBS. "
My CPU is not even near reaching 100% usage.

Can I get a direct answer as to what is causing the issue and how to solve it?
 
PaiSand

PaiSand

Active Member
Perfect, your problem is solved.

The analizer analize what is shown by OBS in there, not the third plugins (third party plugins are made by someone else). It just list which plugins you have. Common sense
Now, if you want to solve your issue, remove the plugins and test it. Almost always the fault is on a plugin outdated or not compatible with latest version of OBS.
 
BrunoDanUy

BrunoDanUy

New Member
PaiSand said:
Perfect, your problem is solved.

The analizer analize what is shown by OBS in there, not the third plugins (third party plugins are made by someone else). It just list which plugins you have. Common sense
Now, if you want to solve your issue, remove the plugins and test it. Almost always the fault is on a plugin outdated or not compatible with latest version of OBS.
Click to expand...
So is Audio Monitor the plugin causing the issue?
Been monitoring CPU usage during stream today, and it's definitely not the issue causing the audio buffering.
 
R

rockbottom

Active Member
GPU crashed in the 1st log, unknown in 2nd log. Bad driver? Common between both instances.
16:27:58.541: Driver Version: 31.0.21001.45002
16:01:59.500: Driver Version: 31.0.21001.45002

1st Log
Fault address: 7FFA07073BE4 (c:\program files\obs-studio\bin\64bit\obs.dll)
Thread 142C: obs gpu encode thread (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
0000004C51BFFC90 00007FFA07073BE4 000001B82E58D860 000000008000FE00 000001B800000000 0000000000000001 obs.dll!gpu_encode_thread+0x284

2nd Log
Fault address: 7FF9B031E700 ((null))
Thread 1D6C: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00000073C917F048 00007FF9B031E700 00000188A91743C0 00000188A91743C0 00007FFA0116FB48 000000000000001F <unknown>!0x7ff9b031e700
 
PaiSand

PaiSand

Active Member
The plugin is still intalled:
16:02:01.319: audio-monitor.dllE
Click to expand...

And isn't the only plugin that needs to be removed for actually test if OBS is working correctly.
If you don't put some effort to solve the issue, no one can solve it for you.
 
koala

koala

Active Member
OBS crashed in a procedure called "obs_gpu_encode_thread. From the name, I guess it's a thread that does video encoding for some output. The regular output is not known to cause crashes, so it has to be something else. 3rd party plugins present that deal with video encoding and output: source record. This plugin is known to cause crashes for some setups. So I recommend you remove the source record plugin and try again OBS doesn't crash any more.
 
BrunoDanUy

BrunoDanUy

New Member
koala said:
OBS crashed in a procedure called "obs_gpu_encode_thread. From the name, I guess it's a thread that does video encoding for some output. The regular output is not known to cause crashes, so it has to be something else. 3rd party plugins present that deal with video encoding and output: source record. This plugin is known to cause crashes for some setups. So I recommend you remove the source record plugin and try again OBS doesn't crash any more.
Click to expand...
Amazing, I'll try that. Thanks for your help!

That plugin is really useful for doing recordings while streaming so the alerts don't end up in the final recording, but knowing that it causes issues I can uninstall it and reinstall when I NEED to use it.

I haven't really been recording with it lately, and I've still gotten the crashes, so I imagine there's no way to get around them by changing the plugin config.

Again, thanks for your time!
 
You must log in or register to reply here.
Top