Bug Report OBS crashing with Game Capture, seems to be caused by last Win10 Update

[jscoys]

Hi,

It seems, when I go on the forum, that I'm not the only one suffering from multiple crashs. It is now really annoying and the software become more and more useless caused to that.

I start a broadcast to Twitch and then, after x minutes or x hours, it just freeze. The picture is frozen in OBS, and if I click on "Stop broadcast" it write "stopping..." and it just never change. It happens only with Game Capture. If I broadcast my screen on twitch when I do some programming stuffs, it works several hours without any issues. I will put the log here to show you what happens.

It seems to arrive since the last anniversary of Windows 10 patch from Microsoft...

It is really annoying and I'm thinking more and more to go on XSplit. I really like OBS for all its customization possibilities, and I really don't want to switch...

When I go into the logs, it seems that what repeat often is this :
20:56:59.501: device_texture_create (D3D11): Failed to create 2D texture (887A0005)

I don't know if it related or not. Really hope you'll do something, it's really urgent!!!

 

[gnazghoul]

This is the exact issue I am having.

 

[OG See OH Zee]

Uninstall KB3189866 as a temporarily solution or lower the texture quality in the game to reduce VRAM. Seems the Windows 10 patch over a week ago is breaking OBS when on VRAM-intensive games.

Also while I'm at it...

21:00:47.025: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 7690 (4.3%)

That line shows you're overloading your GPU. Given Dead by Daylight runs poorly on the GTX 750 Ti yet being GPU-intensive I highly recommend you switch from 60fps to 30fps on OBS.

 

[jscoys]

Thx for advice, I will switch to 30 fps.

However, is there someone from devs who is aware of this problem and working on fixing it? We can't just uninstall all new Microsoft patches. It will be necessary to go ahead and to adapt OBS to the constant evolution of Windows 10, not the opposite!

 

[RytoEX]

Thx for advice, I will switch to 30 fps.

However, is there someone from devs who is aware of this problem and working on fixing it? We can't just uninstall all new Microsoft patches. It will be necessary to go ahead and to adapt OBS to the constant evolution of Windows 10, not the opposite!

The OBS Studio developer is aware, as far as I know. However, you may want to know that there have been posts by Nvidia that Microsoft broke something in Windows 10 with their drivers, so this may not be up to OBS Studio to fix. This error is fairly recent, and it seems to rely on a particular combination of hardware (Nvidia GPU) and software (Windows 10 AU, sometimes plus hotfixes, sometimes not, possibly a specific Nvidia driver or later) in order to reproduce it.

 

[jscoys]

Ok man thx for information. BUT... I just twitched for 2 hours now with Xplit Broadcaster and..... it worked well! No crash or freeze! So you can say everything you want : what in the Xsplit makes it work fine and which is not in ObS? Its the same OS with anniversary and latest patch from Microsoft... no you won't convince me that OBS devs don't have something to change or adapt!

 

[WIll Treaty]

Getting the exact same problem.

 

[c3r1c3]

Just to note: Xsplit and OBS do not employ the same rendering techniques, so to compare them is fallacy. Just because something works in XSplit doesn't mean it'll work in OBS or vice versa.

Microsoft decided to release an update (Anniversary Update, or "AU") that breaks many things. It's gotten so bad that MS has GREATLY reduced the roll-out of the patch (and even has issued post-AU patches) to try and fix some of their problems.

The issue appears to be that Windows mismanages the VRAM in the system and overcommits it, which causes various failures, including the one mentioned above. Saying that OBS can fix it is like running a system with 1 Gig of ram, and blaming OBS that Windows takes forever to boot up and has issues running anything (including OBS).

It's a (much) lower level issue then OBS.

 

[jscoys]

Ok so we need to wait for Microsoft to resolve the problem. Alas I have to use Xsplit in the meanwhile...