Livestream insta-crashed (twice)— "graphics thread (Crashed)"

[Jate]

Any help with this?
I don't have much knowledge reading the crash reports, but here seems to be the main parts:


Unhandled exception: c0000005
Date/Time: 2021-12-08, 20:22:08
Fault address: 7FFC1C248BF9 (c:\windows\system32\d3d11.dll)
libobs version: 27.1.3 (64-bit)
Windows version: 10.0 build 19043 (release: 2009; revision: 1348; 64-bit)
CPU: Intel(R) Core(TM) i5-10600KF CPU @ 4.10GHz


Thread 4FE4: libobs: graphics thread (Crashed)
---

Thoughts?
Thank you!

 

[WizardCM]

This crash seems to be caused by the move transition plugin. Make sure you're running the latest version, and if you are I'd recommend reporting the issue to Exeldro.

 

[Jate]

Thank you so much for replying!
I'm slowly slipping into a mild depression over this— I currently stream full time hours, and this is still crashing multiple times a day now.

I do use the move plugin, so went in and removed it tonight just to test (and messaged Exeldro, though feel bad since he's a saint and probably busy on the next plugin I'm going to use every day).

However... I still crashed again just now.
I uploaded the crash log, but it looks fairly similar to my eyes. How did you know to suspect the move plugin? Seen others with the same error maybe? Anything look different here?

Thank you again.

 

[FerretBomb]

Just as a heads-up, d3d11.dll crashes are most often caused by two things; Ryzen-based systems with unpatched microcode bugs (which a motherboard BIOS flash can fix), and unstable overclocks. If your system IS overclocked, you might consider trying to dial it back to stock.
That said, I've seen a handful of these reports lately and most of them DID use the move plugin. But all of them were Ryzen systems, and the BIOS flash fixed it in their case. Not so much in yours, unless you've got an overclock going on that may not be as stable as you might think.

 

[WizardCM]

And to answer your question about why I think it's related to the transition plugin, the first chunk of the stack trace includes

move-transition.dll!move_video_render+0x10b4

 

[Jate]

Just as a heads-up, d3d11.dll crashes are most often caused by two things; Ryzen-based systems with unpatched microcode bugs (which a motherboard BIOS flash can fix), and unstable overclocks. If your system IS overclocked, you might consider trying to dial it back to stock.
That said, I've seen a handful of these reports lately and most of them DID use the move plugin. But all of them were Ryzen systems, and the BIOS flash fixed it in their case. Not so much in yours, unless you've got an overclock going on that may not be as stable as you might think.

Good to know! I don't have any OC on my graphics card, but it's possible there's some on my CPU (though not beyond the default "boost"). Looking at my errors, I think most of my problems seem to be graphics related. Could this indicate hardware failure? I'm surprised it's only OBS that crashes if so.

Thank you again!

 

[FerretBomb]

Good to know! I don't have any OC on my graphics card, but it's possible there's some on my CPU (though not beyond the default "boost"). Looking at my errors, I think most of my problems seem to be graphics related. Could this indicate hardware failure? I'm surprised it's only OBS that crashes if so.

Thank you again!

The d3d11.dll crashes I was referring to were CPU overclocks.
Yes, d3d11.dll is a graphic component, but that does NOT mean that the graphic subsystem is necessarily responsible for originating the crash.
It COULD still be the Move transition causing the issue (or triggering the underlying issue, again, have seen a number of crashes where the stack trace showed the move transition plugin as the crash point). But most of the prior cases I've helped out with, the fix was a BIOS update for Ryzen systems, and bringing an overclock back to stock speeds for Intel.

The other option is to remove the Move transition from your OBS install. Even if it's just triggering an underlying issue, removing the trigger would at least get you going again.
But if I were in your shoes, I'd definitely check if the system is overclocked (even if it is OC'd within the advertised 'boost' range, that does not guarantee stability!), and return the system to stock speeds as a first-step.

 

[Jate]

I'll definitely look into that. Yesterday, I finally made a backup of my OBS folder and installed, then only installed the plugins I really needed. From that, my stream has been mostly stable so far (I got the same error and crash as soon as I loaded it, but not after starting stream), so I'm at least moving in the right direction. I'd love to upgrade the 980Ti, but... you know how the GPU market is right now.

I'll check the CPU OC and if there's any bios updates. Thanks for the tips!