OBS keeps crashing at channel redemptions

M

MindreaderDave

New Member
Ok. So I have a bunch of channel redemptions and scenes to host them. It's only been a problem recently and I'm unsure why.

Sometimes it works without a hitch. Other times some rewards crash more than others, and other times any reward can crash the stream. I'm not entirely sure what's making the difference or what to troubleshoot.

I recently got the plugin manager "Discovery" and updated my plugins that it showed needed updating. That seemed to help make things run smoother, but I'm still having this issue. I use Streamer.bot to manage the redemptions. And I use StreamUp for some of these redemptions as well.

I'm not sure if there's something I need to optimize or if maybe a particular plugin is causing the issue. I was using the Dynamic Delay plugin for something and recently started using it for something else (less intensive) instead and had no issues prior to that. I don't know if that's just a random correlation or not. I'm not very tech savvy so I really do need the help.

Any ideas of what the problem is and how to fix it?

Here's the log file from the last crash (I wasn't streaming on this one, just testing things and it predictably crashed).

 
23:14:52.951: ==== Shutting down ==================================================
Click to expand...
This doesn't appear to be a 'crash', something is exiting OBS. It appears that a websocket connection was established just beforehand, most likely from Streamer.bot; unfortunately, we can't really offer support for third-party software, even if it interfaces/is used with OBS. I'd suggest reaching out to the Streamer.bot developers for assistance.

If you did receive the 'Whoops!' dialog, please post your most recent crashlog (from the Help menu in OBS) and we can take a look.
 
FerretBomb said:
If you did receive the 'Whoops!' dialog, please post your most recent crashlog (from the Help menu in OBS) and we can take a look.
Click to expand...

Ok, I went to the Streamer.bot discord to see what they can do there.

I did also get a "Whoops!" dialog on my most recent one. This one didn't involve any software outside of OBS, it was simply switching to a scene that seems to cause a lot of crashes without activating any channel redemptions. Here is the log from that one. This sounds like I might have two separate problems going on so this is useful. Thank you for helping me figure that out. Hopefully you have an idea for this one too?

 
Hmmmm. According to that, the crash is in libobs, potentially caused by the d3d11 library, or the Move Transition plugin.
Was Streamer.bot/StreamUp still running at the time? I'm wondering if they're pushing bad parameters through the websockets interface. Usually the Move transition isn't problematic, but if it's being fed weird parameters I could understand it causing a crash.

Normally d3d11 crashes come from an unstable overclock, or on early Ryzen-based systems an unaddressed CPU bug that can be fixed with a motherboard firmware update. If you haven't flashed your mobo firmware in a while, it may be worth checking if there's a newer version available.
 
I didn't have Streamer.bot running at the time. And this particular scene wasn't a StreamUp scene. I had made this one from scratch. Is there a way to fix the parameters being pushed through the websockets interface? I'm not very tech savvy so I don't even know how to check for that.

With regards to flashing my mobo firmware (which I doubt I've ever done because I don't know what that is), would you have a link or could you detail the steps I would need to do? I'm sorry, I'm learning all of this as I go and don't have much background knowledge. I really do appreciate the help as I have no idea how I would figure this out on my own.
 
FerretBomb said:
Hmmmm. According to that, the crash is in libobs, potentially caused by the d3d11 library, or the Move Transition plugin.
Was Streamer.bot/StreamUp still running at the time? I'm wondering if they're pushing bad parameters through the websockets interface. Usually the Move transition isn't problematic, but if it's being fed weird parameters I could understand it causing a crash.

Normally d3d11 crashes come from an unstable overclock, or on early Ryzen-based systems an unaddressed CPU bug that can be fixed with a motherboard firmware update. If you haven't flashed your mobo firmware in a while, it may be worth checking if there's a newer version available.
Click to expand...

Hey! I just wanted to say thank you. I ended up getting motherboard bios updated and it seems to have solved the issue! So thank you so much for helping with this and your explanations. I would've never discovered that without your help.
 
You must log in or register to reply here.
Back
Top