PSA for Windows 10 Anniversary Update users

Status
Not open for further replies.

RytoEX

Forum Moderator
Updating video drivers to latest should resolve this issue. Rest of post preserved for posterity.

TL;DR: Windows 10 Anniversary Update broke stuff.


Best solutions/workarounds: update AMD drivers to the latest version; update OBS Studio to the latest version, or disable your OBS Studio preview. Setup your sources and scenes, disable your preview, then restart OBS and start streaming or recording immediately. Do not edit your sources or add any new sources that have a video preview, or you might trigger this error, and then you'll have to restart OBS. If that doesn't help, then alternatively, you can temporarily run OBS with the OpenGL rendererer in advanced settings, but make sure to change it back to Direct3D 11 as *soon* as we tweet or alert users that Microsoft/Nvidia fixed it; the OpenGL renderer has poor capture performance in comparison to Direct3D 11.

Disclaimer: I'm just a community member trying to collect information, and work out solutions and workarounds. I am not an official OBS Project staff member. I do not speak for the project or the staff. If a moderator or staff member feels this post is out of line, they are welcome to delete it.

Throughout this post, I might use "OBS" instead of "OBS Studio". This is just for brevity, or for making sentences sound less awkward, or because I'm lazy.


Why should I read this?
Are you on Windows 10? Is OBS Studio suddenly crashing or not capturing games? If you answered yes to both of those, then you may be having a rather difficult-to-remedy issue. Read on.


Why write this post?
I'm posting this as a new thread because I've done a lot of copy-and-pasting in a lot of threads over the past few weeks about issues with Windows 10, specifically the Anniversary Update. Using that method, the information I'm trying to share is getting spread inefficiently. It's also becoming more and more difficult to keep the information I've shared to everyone up-to-date and relevant. By making a single post, I can update it with new information as it arises and have a single up-to-date place to which users can be pointed.


Wait, what happened?
Microsoft released the Anniversary Update (AU) for Windows 10. Initially, this broke a bunch of things like webcams. Lots of webcams. Basically, it broke the majority of webcams (no really). For more reading on that, see this thread.

After that, Microsoft released more updates to fix what they broke. Unfortunately, it seems some of those hotfixes broke other things in ways that we don't fully understand.


How do I know if I'm having this problem?
In short, if you are on Windows 10 and OBS is crashing, freezing, or locking up, you may be affected. If you're not on Windows 10, you're not affected by this particular issue.

This issue only affects users who are running Windows 10 AU. If you are on Windows 10, you can check if you're on the Anniversary Update by running "winver" from your Start Menu. See the image below for what the winver utility looks like. If your version is lower than 1607, then you are not on the AU, and you have a different issue. If that says Version 1607, then you're on Windows 10 AU, and you should read on.



However, even being on Windows 10 AU does not mean that you're automatically affected. Many people have no issues on Windows 10, even on the Anniversary Update. To tell for sure, we need to check the OBS Studio logs.

Check your OBS logs at "%AppData%\obs-studio\logs". You get there by pasting that into the Windows Run dialog, which you can access by pressing Windows Key + R. In your logs, do you see a line like the one below?
device_texture_create (D3D11): Failed to create 2D texture (887A0005)
If you see that message, then you are almost certainly affected by this issue. Other possible messages may include:

device_vertexbuffer_create (D3D11): Failed to create buffer (887A0005)
device_swapchain_create (D3D11): Failed to create swap chain (887A0005)
device_resize (D3D11): Failed to resize swap buffers (887A0005)
gs_texture_open_shared (D3D11): Failed to open resource (887A0005)

I'm having problems. How can I fix it?
If you're using an AMD graphics card, this was reportedly fixed in AMD driver version 16.10.2. Update your drivers to the latest version.

If you're using an Nvidia graphics card, unfortunately, there is currently no way for you to completely fix it, but there are some workarounds that you can try. First, consider updating to the latest version of OBS Studio. OBS Studio 0.16.3 introduced a workaround for this problem, but there's a catch. When the error is triggered, instead of freezing completely, the stream/recording may pause briefly and then show some green frames while OBS rebuilds its Direct3D assets. If that's okay with you, go update! If, for some reason, you find that unacceptable...

Currently, some workarounds for getting OBS Studio to work right now on Windows 10 Build 14393 (AU) are as follows:
  1. Disable the OBS Studio preview. (Right click the preview window and uncheck Enable Preview)
  2. Try Display Capture or Window Capture instead of Game Capture.
  3. Use the OpenGL renderer instead of Direct3D 11. (Settings > Advanced > Renderer) (Jim edit: not recommended if capturing games, but it is an option. Set it back to D3D11 when you hear that the issue has been fixed)
  4. If you're using an Nvidia card, rollback your Nvidia drivers to 368.81 or 365.19.
  5. Rollback Windows updates KB3176938, KB3189866, KB3193494, KB3194496, KB3194798, KB3197954, or their successors.
  6. Revert to a Windows 10 build that is before the Anniversary Update. (Uninstall the Anniversary Update for the time being)
  7. Worst case scenario, revert to an older version of Windows (Windows 8.1 or Windows 7). Although it's better to just uninstall the Anniversary Update if you're able for the time being.
Option 1 seems to work reliably under specific conditions. If the error has already occurred behind the scenes, disabling the preview will not work until OBS is restarted. Any capture that shows a video preview (display, window, game, etc.) can also trigger this error. To get the best results, disable your preview, setup your sources and scenes, then restart OBS and start streaming or recording immediately. Do not edit your sources or add any new sources that have a video preview, or you might trigger this error, and then you'll have to restart OBS.
Option 2 might work, but it has also been known to trigger the error in some cases. Keep in mind that using Display Capture comes with a performance penalty compared to Game Capture.
Option 3 seems to work, but it could use more testing and confirmation. Keep in mind that OpenGL does not perform as well as Direct3D on Windows. It will cause a major decrease to capture performance. This is not recommended.
Option 4 is inconsistent. Some people report that it works for them, while others report that it does not help.
Option 5 seems to work for most people, though a few have reported that it did not help.
Option 6 also works without fail, but it is sort of a last resort nuclear option.
Option 7 is very much only if you're desperate.

This is also confirmed to occur in OBS Classic, so using that is not a viable workaround.

One of these might work for you, or none of them may work for you. I've been researching this for weeks and have found the most consistent workarounds to be #1, #5, #6, and #7. However, uninstalling Windows Updates is generally a temporary solution, and it understandably makes people uneasy. Additionally, since I'm unable to reproduce these issues on my computers, it's hard to troubleshoot it and find good workarounds.

If you try any of these on an affected system, please let us know what you did and whether or not it worked for you. Having logs from before and after the applied workarounds would also be helpful.

Please understand that uninstalling specific Windows Updates is a temporary measure, especially on Windows 10. Windows 10 is far more aggressive about its automatic updates than earlier versions of Windows, and Microsoft does not intend for you to be able to turn them off, only delay them.

However, there is a way to forcefully disable receiving Windows Updates on Windows 10. For more info, see this article (with video guide!) by Void4ever.

Please note that uninstalling Windows Updates may also inadvertently break other things, and may expose your system to security vulnerabilities that the updates had patched.

Please note that disabling Windows Updates may expose your system to security vulnerabilities that are patched in updates that you are not receiving.


If you're working on a Windows 10 system and software just suddenly stopped working after a Windows Update, I highly encourage you to report it to Microsoft so that they can investigate what they changed and if their code is at fault. If they changed something significant and expect developers to do things in new ways, then that would also be useful information to have. You can report issues to Microsoft by using the Feedback Hub that is built-in to Windows 10.


What is OBS doing about it? Why can't OBS fix it?
The lead OBS developer (Jim) and some community members are looking into it, and there is a Mantis Issue for this.

Jim has posted his preliminary findings here. OBS Project Staff have reached out to Microsoft, and Microsoft is looking into it.

Jim did say that Windows 10 is causing issues and that so far there hasn't been anything found that points to OBS as being at fault for causing the issue. Nvidia, Sage, Logitech, Dartfish, Firestorm, and many others have pointed to Microsoft breaking things either in the Windows 10 Anniversary Update or its subsequent hotfixes.

Some have suggested that this is caused by how OBS encodes video. As far as I know, it has nothing to do with how OBS encodes. The current consensus is that OBS is not at fault, but that Windows 10 is mismanaging the VRAM, which causes the VRAM to be filled until the DirectX device is "removed" from the system. Certain OBS setups or configurations can exacerbate the issue, but OBS is not currently believed to be causing the issue itself.

2016-10-21: Word from Microsoft is that they've replicated two distinct issues related to the issue detailed here. The latest update is that the D3D developers took a look at it and it got forwarded to the Graphics Kernel team for further investigation.

2016-10-28: News from Microsoft! They have found a bug regarding Nvidia currently, and they're engaging with Nvidia to get it fixed. Details here.

2016-11-04: Jim has built a workaround into OBS Studio 0.16.3.



Some Technical Mumbo-Jumbo
I suspect that the particular update that is causing the most issues to arise is KB3176938 (Build 14393.105). Any Windows 10 Cumulative Update after that one will also have the same patches in it, along with whatever new patches the new updates include. However, since Windows 10 Revision logging was somewhat broken before OBS Studio 0.16.0, and most of the reports I've seen were with OBS Studio 0.15.4, it's hard to tell for sure if a specific update is a factor.

Some people, including Nvidia employees, have pointed to issues with the new Windows Display Driver Model (WDDM) 2.1 that came with the Windows 10 AU. It could be caused by changes in D3D11.4. It could be something changed in DXGI 1.5. It could be something else in the Win10AU changes. It could be changes in any of those things not liking something in the OBS render pipeline. At the moment, we just don't know. It is also possible that the time and effort to research it could also be for nothing, as Microsoft may revert or patch whatever they changed in the first place.



Edits
2016-10-10: Added a workaround. Reordered workarounds. Clarified workaround options. Clarified that the developer is investigating the issue. Changed formatting.

2016-10-12: Clarified the instructions to a couple workarounds. (edited by dodgepong)

2016-10-12: A Jim edit to yell at people to provide log files in the start of the post or he'll hunt them down and point an angry finger at them.

2016-10-13: Add method for disabling Windows Updates on Windows 10, for the brave, daring, or foolish. ;P

2016-10-20: Add a TL;DR to the top mentioning Disable Preview (most reliable and least severe workaround).

2016-10-21: Update from Microsoft.

2016-10-28: Update from Microsoft. Clarification about AMD cards.

2016-11-04: Workaround added in OBS Studio 0.16.3.
 
Last edited:

SoWhoYou

Member
Nice Post! Maybe this will slow down the amount of posts that are made by users having issues that are being caused by the anniversary update.
 
Last edited:
There was also a known issue that I'm also pointing fingers to Microsoft for Windows 10 (since its release date of course) which is causing OBS Classic and OBS Studio in which the GPU is mismanaging the GPU usage and causing lagged frames in the logs while older operating systems never had it. If you want I can link the thread about it comparing the logs on Windows 8.1 and Windows 10 when GPU usage is high. So far it's been confirmed on the majority of the Nvidia video cards and Windows 10 video drivers and I haven't checked to see if the issue can be replicated on AMD video cards.
 

Zyn

New Member
The latest cumulative update for Win10 appears to have fixed the problem, as D3D11 is no longer barfing "Failed to create 2D texture" at me and I successfully streamed for 3+ hours last night without a freeze or any other problem.
 

Z'ignoratio

New Member
Thank you for the information about this issue. I was doing a local capture when this happened to me. The file is not playable and I'm guessing is completely trashed. Tried several MP4 repair tools with no luck. Anybody know of a way to salvage a recording affected by this?
 
Last edited:

Harold

Active Member
There is no way to recover damaged mp4 files in the state of yours.
That is the primary reason we do NOT recommend saving directly to mp4.
 

Z'ignoratio

New Member
There is no way to recover damaged mp4 files in the state of yours.
That is the primary reason we do NOT recommend saving directly to mp4.
Pardon my ignorance, what is the recommendation? I'm specifically using OBS to record gameplay for use in a Youtube video.
 

Harold

Active Member
Normal recommendation is flv or mkv. You need to use mkv if you're using multi-track audio.

If you're not editing before uploading, you can upload either straight to youtube.
 

RytoEX

Forum Moderator
The latest cumulative update for Win10 appears to have fixed the problem, as D3D11 is no longer barfing "Failed to create 2D texture" at me and I successfully streamed for 3+ hours last night without a freeze or any other problem.
If KB3194496 (Windows 10 Build 14393.222) fixes this, I would be ecstatic. I would need to hear of a few more positive reports before making that conclusion. Thanks for reporting to us!
 

RytoEX

Forum Moderator
Is OBS classic getting this same issue?
I haven't heard any reports of it, but I don't really track OBS Classic activity, and I haven't gone looking for them. If you're on a system affected by these issues in OBS Studio, and you're able to test if OBS Classic experiences any similar issues, I'd love to hear the results. However, something to keep in mind is that OBS Classic and OBS Studio, despite having similar names, are pretty much completely different pieces of software, so I wouldn't necessarily expect them to act the same.
 

CrazedLlamaz

New Member
So I am at the end of my sanity right now. I have tried every solution listed above and I still have OBS fail on me. I stream to Beam. When streaming OBS drops the stream, and OBS appears to be frozen, but audio is still picking up.

I am using the most recent version of OBS Studio and I do have the anniversary update.
 

Attachments

Cryonic

Member
Even with the insider build (14936) there are issues and no patches for OBS so far. Thats not the first time when MS changes something in Windows and stuff is not functional for ages. Tested both Classic and Studio.
Studio is freezing, Webcam loading issues, Monitor Capture issue, Preview issues, dropped streams on x264..
Classic freaks out sometimes and does not want to load properly, it crashes with a texture error (GPU driver - meanwhile the game is running fine!) and some other crap.
 

Meswannjr

New Member
If KB3194496 (Windows 10 Build 14393.222) fixes this, I would be ecstatic. I would need to hear of a few more positive reports before making that conclusion. Thanks for reporting to us!
That is the version of Win10 I'm running and all D3D11 is doing is giving me the "Failed to create 2D texture"
 

RytoEX

Forum Moderator
So I am at the end of my sanity right now. I have tried every solution listed above and I still have OBS fail on me. I stream to Beam. When streaming OBS drops the stream, and OBS appears to be frozen, but audio is still picking up.

I am using the most recent version of OBS Studio and I do have the anniversary update.
1:56:37 AM.488: device_texture_create (D3D11): Failed to create 2D texture (887A0005)
You are affected by this issue. Try the workarounds listed in the first post. Let us know what works and what doesn't.


That is the version of Win10 I'm running and all D3D11 is doing is giving me the "Failed to create 2D texture"
Indeed. I've seen several other reports of KB3194496 not changing anything. Seems it doesn't change anything for this issue. =/


Even with the insider build (14936) there are issues and no patches for OBS so far. Thats not the first time when MS changes something in Windows and stuff is not functional for ages. Tested both Classic and Studio.
Studio is freezing, Webcam loading issues, Monitor Capture issue, Preview issues, dropped streams on x264..
Classic freaks out sometimes and does not want to load properly, it crashes with a texture error (GPU driver - meanwhile the game is running fine!) and some other crap.
The bold emphasis is mine. As I stated in the first post, so far neither myself nor the lead developer (nor any of the community moderators/admins) have concluded that this is something that is caused by OBS or can be fixed by OBS. I'm not saying it absolutely definitely cannot be fixed by OBS. I'm just saying that at the present time, no one knows the exact cause. Without knowing the exact cause, there's little hope that we'll stumble upon some sort of code solution.

The only commonality seems to be that all of the reports featuring this error are running the Windows 10 Anniversary Update, so it stands to reason that Microsoft changed something between Windows 10 Build 10586 and Windows 10 Build 14393. Whether that change intentionally altered something with the intent that developers would use some new method or that change unintentionally broke something fundamental to graphics rendering (e.g., VRAM management) is difficult to say at this time.

What is needed right now is to have this issue occur and be easily reproducible on a machine that the developer has access to.
 

Cryonic

Member
Well i hoped that it would be enough to send in logs and information. I know that it is not easy to reproduce, specially on rare systems like mine (my audio interface is really rare and the whole build is kinda unique + i run insider preview with autoupdates active everywhere).
One single machine would not give enough data and it would take weeks if not months to track down and fix the issue or get MS to fix it. As an insider i know the communication speed and how long it will take until we get a regular fix (i dont think that MS will hotfix that, that is not a major issue after all).

I have no idea what MS did there, most likely nothing special. It was not in the insider builds before. I sit for over a year on the insider preview in the fast ring and i skipped only 2 builds. Would have noticed it long before the anniversary update rolled out, if there was something similar. Issues came just right now, where i installed the latest 372.90 GPU driver and the latest 14936 Win10 build.
 

RytoEX

Forum Moderator
Well i hoped that it would be enough to send in logs and information. I know that it is not easy to reproduce, specially on rare systems like mine (my audio interface is really rare and the whole build is kinda unique + i run insider preview with autoupdates active everywhere).
One single machine would not give enough data and it would take weeks if not months to track down and fix the issue or get MS to fix it. As an insider i know the communication speed and how long it will take until we get a regular fix (i dont think that MS will hotfix that, that is not a major issue after all).

I have no idea what MS did there, most likely nothing special. It was not in the insider builds before. I sit for over a year on the insider preview in the fast ring and i skipped only 2 builds. Would have noticed it long before the anniversary update rolled out, if there was something similar. Issues came just right now, where i installed the latest 372.90 GPU driver and the latest 14936 Win10 build.
Microsoft famously broke most webcams on the market when the Anniversary Update was released because their Insider Build reporting didn't pick up the issue.

I've got a spreadsheet full of data on over 50 OBS Studio error logs for this issue. It occurs with all sorts of systems and setups and timings: AMD or Intel CPU; AMD, Nvidia, or Intel GPU; x264, NVENC, or Media Foundation encoders; OBS Studio 0.15.2 to 0.16.2; error appears in 22 seconds or in 54 minutes; running as admin or not. I could still collect more data, but the one consistency so far seems to be Win10AU. =/

Logs and info are still helpful, in case something really specific stands out in even one of them. If we're really lucky, it's something that can be solved with an OBS Studio patch, because that will probably arrive sooner than if we have to wait for a Microsoft patch.
 

Cryonic

Member
Well i get that crap with OBS Classic on Win10 14936 (newer than AU) and 372.90 GPU driver:
Texture Map failed: 0x887a0005 0x887a0006
Video card or driver froze.
It could also occur if you have enabled OpenCL in x264 settings (i did not as far as i know, default x264 settings here, but DOOM might kick in here).
This affects DOOM and OBS Classic.
Since Vulkan is added to other engines right now, we might see more of that in the near future.
With OBS Studio i dont get that texture error, but a truckload of different things that dont even produce errors or have logs so i could link it.

But classic works better with the webcam. I have the usual suspect, the C920, could test an older cheap Creative VF700 720p one - for more information. If the C920 had issues, the forum would be already down, since that webcam is by far the most used for streaming blah.


Edit: never had any issues with the webcam on previous insider builds. Nope. 100% functional in OBS classic, skype and few other instances. Like i said, C920 - that webcam would not slip through if it had huge issues with one of the builds before.
 
Status
Not open for further replies.
Top