obs software crashing within 10-15 min of live streaming church service

1. Run OBS as Admin. Right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok.
2. In OBS, go to "Settings -> Advanced" and set "YUV Color Range" to "Partial".
3. Your log contains no streaming session. Results of this log analysis are limited. Please post a link to a streaming log file.
To make a streaming log file, please follow these steps:

1) Restart OBS as Admin.
2) Start your stream for at least 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Once OBS crashes, re-open OBS as Admin.
4) Select Help > Log Files > Upload Last Log File and Crash Reports > Upload Last Crash Report. Send those links here.
 
Also, curious why the camera input settings include YUY2 format (sorry not my area of expertise)
18:30:05.874: [DShow Device: 'Video Capture Device'] settings updated:
18:30:05.874: video device: ezcap U3 capture
18:30:05.874: format: YUY2

Blackie - hopefully you realize that is a 6 generation old ultra-low power laptop CPU, optimized for battery life, not the computationally demanding task of real-time video encoding. I recommend monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization [for ex. using Task manager’s Performance tab and/or Resource Monitor] to see if your system is being maxed out with your settings https://obsproject.com/wiki/General-Performance-and-Encoding-Issues and https://obsproject.com/wiki/GPU-overload-issues

As such, though your laptop may have worked up till now, you may want to optimize Operating System by turning off unnecessary background processes, OS-level visual eye candy, etc. if you haven't already [probably won't make a big difference, but every little bit may help on an under-powered system like you have]
And turn off Game DVR presuming no reason to have it one

And possibly test with MacAfee disabled/uninstalled? Personally, I don't trust M$ [distrust earned over decades]. But, if you use safe compute practices (don't log in with admin rights, careful what is installed/run, etc), then just using MS Defender in this use case is probably fine. AV updates from 3rd party has caused problems before (not that this is the case for you, but not something to ignore the possibility of)

Personally, I avoid running anything but Updates as Admin. But on a system like yours you may end up not having a choice. I'd start with fixing the color range items mentioned, then doing OS optimizations (like turning off Zoom, etc if not in use during livestream), and testing streaming from there. Only if after everything else fails, would I go to running OBS as Admin. Also, recognize that many OBS settings are stored in your user profile. *If* you log on with non Admin account, then use RunAs for OBS, you will need to reset most (all?) OBS settings
 
Back
Top