Bug Report OBS crash during Skyrim: SE stream

[Tacktel]

Hi everyone,

I recently started to stream my videogames sessions with OBS Studio which worked really well when I played CS:GO.

I wanted to play to Skyrim: SE but I have some issues with it...
In fact, I can stream about 5 minutes playing this game after what OBS crash.

I opened the log files, the only information about this crash is "capture window no longer exists, terminating capture"...

I just tried to stream The Witcher 3 that worked perfectly to, like CS:GO did...

My computer is powered by a i5 6600k and a GTX970, so I'm not looking for a performance issue.

 

[Tacktel]

Any ideas ? I found that I'm not the only one to have crashes since weeks but none of the responses on the other threads helped me...

 

[RytoEX]

If OBS really crashed ("Woops, OBS has crashed!"), then there should be a crash log at "%AppData%\obs-studio\crashes". If a crash log matching that session exists, please upload that as well. If there are no such crash logs, then what you're describing probably isn't a crash.

 

[Tacktel]

Okay so what I described seems not to be a crash, in fact I don't have the error "Whoops, OBS has crashed!" when it's happening (what it is supposed to do, right ?).
I don't know how to call it, it's a sort of "every features in OBS are freezing at the same time" like my game screen, my webcam, my broadcast...without saying anything other than "capture window no longer exists, terminating capture" in the log file when it happens (window that already exist, my game works perfectly...).

EDIT :
I think my problem is similar to this people issue :
https://obsproject.com/forum/threads/obs-studio-stops-stream.55102/
https://obsproject.com/forum/threads/game-capture-problem-bug.51482/
but the first one didn't get any solution and the second one have apparently dealed with a conflict with an other software...

Well I'm going to do some tests with OBS Classic in a few hours. I'll keep you informed.
If you have any suggestions in relation to my log file you're welcome ;-)

 

[Tacktel]

I did a test in OBS Classic, this time I have an error message before a crash :

Texture->Map failed: some random memory adresses in hexa
Your video card or driver froze and was reset. Please check possible hardware / driver issues. This error can also occur if you have enabled opencl in x264 custom settings.

All my drivers are up to date and other games work perfectly...

 

[RytoEX]

That hexadecimal number is probably not a random memory address, but a DirectX error code. It would be helpful if you pasted the exact error message. You can usually press "Control+C" on any Windows dialog box to copy its text. You could also screenshot it.

Based on that information, and the first thread you linked, I'd normally hazard a guess that you're having the Windows 10 Anniversary Update issue, but your log just says that the game capture window no longer exists, rather than any of the errors that would normally come with the issue. Some more information might help in proving or disproving my theory, especially logs from sessions where you have this issue.

As an aside, you probably shouldn't be using the low-latency presets to stream to Twitch. You probably shouldn't be using NVENC to stream at all, unless your CPU really can't handle Skyrim and x264 at the same time.

 

[Tacktel]

So...my CPU can't handle skyrim but can handle Witcher 3 ? Mmmmh...

I'll post the entire error message if the Anniversary Update issue solution doesn't work, thanks !

 

[RytoEX]

So...my CPU can't handle skyrim but can handle Witcher 3 ? Mmmmh...

That's not at all what I said.

You probably shouldn't be using NVENC to stream at all, unless your CPU really can't handle Skyrim and x264 at the same time.

You should not use NVENC for streaming, unless your CPU can not handle Skyrim and x264 at the same time.
Put yet another way:
If your CPU can handle x264 for streaming while gaming, you should use that.

x264 produces better quality video per bitrate than hardware encoders. At the low bitrates required for Twitch (3500 Kbps max for non-partners), x264 will produce better quality video. So if your CPU can handle live x264 encoding and gaming at the same time, you should be using x264. Generally, the only reason to use a hardware encoder (like NVENC) is if your CPU cannot handle x264 and your other tasks at the same time.

 

[Tacktel]

Thanks for your explanation, I will do more tests with other parameters today ;-)

EDIT:
So, I launched OBS Classic with "Nvidia NVENC" as encode process, got the same issue :
---------------------------
Error
---------------------------
Texture->Map failed: 0x887a0005 0x887a0006
Your video card or driver froze and was reset. Please check for possible hardware / driver issues. This error can also occur if you have enabled opencl in x264 custom settings.
---------------------------
OK
---------------------------

I'll try to fix this with the Anniversary blabla solution ;-)

Meanwhile, if you have other ideas ...

 

[RytoEX]

Texture->Map failed: 0x887a0005 0x887a0006

That is a textbook manifestation of the Windows 10 AU issue. Update to OBS Studio 0.16.3, which includes a built-in workaround with a caveat - when OBS recovers from the error, your stream/recording may pause and then turn green for a few frames. Better than completely freezing, in my opinion, but if you don't like that, you can try the workarounds listed in the linked thread.

 

[Tacktel]

Thanks for your help I'll try that !