PSA for Windows 10 Anniversary Update users
- Thread starter RytoEX
- Start date
- Status
I'm not surprised that the 887A0005 error would occur in OBS Classic, but since the issue does not occur on my computer, I cannot personally test it. I'm relying on reports and information from others, and since I primarily read the OBS Studio Windows Support forum (where I can most effectively troubleshoot other problems), I don't usually see reports from OBS Classic users. I've asked a few community members to test this and can now confirm it does also occur on OBS Classic.
As far as I know, adding OpenCL to your custom x264 settings has no actual tangible benefit and will only cause issues.
All I know about Vulkan is that Game Capture for Vulkan (and DX12) is not yet supported. The issue occurs on many games from recent games (ARK, Battlefield 1, Dark Souls 3, Dead By Daylight, Overwatch, etc.) to older games (BioShock, World of Warcraft, Minecraft, etc.). It can even occur while not running/capturing a game at all. Given this information, I'm not sure how more widespread adoption of Vulkan will increase the number of occurrences of this issue.
The issue I've addressed in this thread (not the webcam issue) seems to occur most commonly when the graphics card is under heavy load. If Vulkan creates more load on a graphics card than DX11, then perhaps that could cause it to occur more often, but that's unknown at this time.
Regarding the webcam issue, at the risk of going outside the intended scope of this thead...
That's the thing though. The C920 was most definitely broken by Win10AU (see this thread and this MSDN thread), even in previous Insider Builds (see this post in the MSDN thread, which shows the issue was reported here). It has supposedly been partially fixed in a recent Windows Update (KB3176938, noted here by Logitech). And again, it was all UVC devices, not just the C920.
As a result of the extreme webcam issues with AU, Microsoft may have slowed down the rollout to give them more time to check their telemetry data during their phased rollout (this has been posted by several online tech news outlets). By the time the rollout expanded, KB3176938 may have arrived, which jives with the fact that most reports I saw arrived in September (after the August 31, 2016 delivery date for KB3176938). I've done a lot of reading and research on the subject.
You tried every single workaround (except trying an earlier version of Windows) and none of them worked? Your previous log shows that you are still on the latest Windows 10 patch, which means you didn't rollback any Windows Updates, or they immediately reinstalled themselves. What Nvidia drivers were you using when you first saw this problem, and what drivers did you rollback to?
Last edited:
Yeah i had issues with the webcam in the past, but i was using Classic for the most part of the Win10 usage period and it never crapped out like now.
So far i can tell: i can stream simple games like LoL without issues, since that loads the GPU up to 50% while streaming and still run at like 150+ FPS average. Vulkan gives me instant 99% GPU usage which is cool for gaming, bad for streaming. This game gave me the error, which made OBS classic crash.
Studio is just freezing, stopping streaming while showing me normal preview, the preview on monitor capture works with 1-2 FPS, webcam does not work sometimes and many other issues.
I can definetly confirm that Win10 is doing something strange here.
What i did to my system so far: reinstalled OBS (both), clean scenes, fresh start - nothing changed.
Wiped off the GPU driver and Expirience with DDU, installed fresh drivers - nothing changed.
Cleaned the system from junk and made sure nothing that has access to the GPU will somehow kick in - same issue.
Tested multiple heavy games (BF4 64ppl maps, Crysis3, older titles with DSR blah) - all of them show the same behavior with Studio, some crashed Classic once i managed to load the GPU completly by throwing high AA or 4k DSR at it.
Not a single trick worked. I removed my old win installation before, so no rollback on the preview and no intention on doing that - it mostly does more harm than good anyway.
I will definetly stay on Win10, since that is a really good OS in general, just some minor issues have to be fixed. I hope MS learns how to work with hardware and software developers, driver teams and other essential stuff so they dont release broken stuff or at least get enough infos out so it can be fixed during previews.
I mean i have nothing against playing betatester with insider builds, but definetly not a stable Win10 release. This is the worst for someone who has to go live and keep the schedule up and running. Specially when new games are on the list and new drivers are not optional, they are must have.
So far i can tell: i can stream simple games like LoL without issues, since that loads the GPU up to 50% while streaming and still run at like 150+ FPS average. Vulkan gives me instant 99% GPU usage which is cool for gaming, bad for streaming. This game gave me the error, which made OBS classic crash.
Studio is just freezing, stopping streaming while showing me normal preview, the preview on monitor capture works with 1-2 FPS, webcam does not work sometimes and many other issues.
I can definetly confirm that Win10 is doing something strange here.
What i did to my system so far: reinstalled OBS (both), clean scenes, fresh start - nothing changed.
Wiped off the GPU driver and Expirience with DDU, installed fresh drivers - nothing changed.
Cleaned the system from junk and made sure nothing that has access to the GPU will somehow kick in - same issue.
Tested multiple heavy games (BF4 64ppl maps, Crysis3, older titles with DSR blah) - all of them show the same behavior with Studio, some crashed Classic once i managed to load the GPU completly by throwing high AA or 4k DSR at it.
Not a single trick worked. I removed my old win installation before, so no rollback on the preview and no intention on doing that - it mostly does more harm than good anyway.
I will definetly stay on Win10, since that is a really good OS in general, just some minor issues have to be fixed. I hope MS learns how to work with hardware and software developers, driver teams and other essential stuff so they dont release broken stuff or at least get enough infos out so it can be fixed during previews.
I mean i have nothing against playing betatester with insider builds, but definetly not a stable Win10 release. This is the worst for someone who has to go live and keep the schedule up and running. Specially when new games are on the list and new drivers are not optional, they are must have.
Steelbeard
Member
I can get OBS to work, but the Sync Offset for Audio is just messed up and never actually delays. I don't really know what would be causing it, but after numerous tests, the culprit seems to be the Anniversary Update.
Nevermind, found this thread that indicated that I was incorrect, and even though it wasn't syncing in the preview, it was fully sync'd in the recording and stream. https://obsproject.com/forum/threads/mic-sync-offset-appears-not-to-be-working.20064/
Nevermind, found this thread that indicated that I was incorrect, and even though it wasn't syncing in the preview, it was fully sync'd in the recording and stream. https://obsproject.com/forum/threads/mic-sync-offset-appears-not-to-be-working.20064/
Last edited:
Jayson's Rage
New Member
This really sucks to be honest. My cam/game will freeze no matter what type of scene I'm using (game/window/monitor capture), but somehow the audio still transmits. And I can't stop the stream or recording without exiting OBS itself.
Jayson's Rage
New Member
I just tested recording for 2 hours straight (way more than the 5-10 it'd take for my stream to freeze) and no issues. It must have something to do with the x264 encoder as there is no problem with the NVENC H.264 Encoder.
I've reviewed over 50 reports of this issue. The encoder used varied. Some used NVENC, some used x264, some used Media Foundation encoders, and some logs didn't even get to an encoder before the issues occurred. If you were actually getting an 887A0005 error, and you're not experiencing issues with NVENC, count yourself lucky.
Jayson's Rage
New Member
The weird thing is I never got any errors. The visual portion of my stream would just freeze and I'd have to close the program. It wouldn't let me stop streaming or recording without exiting the program, but I didn't have to force close it.
Do you mean that your log files never showed any errors, or do you mean that you never had any visual GUI alerts mentioning an error?
Jayson's Rage
New Member
Never had visual GUI alerts that prompted an error. Looking at the log file, it says something about a memory leak, but it didn't affect my gameplay at all. Just the stream/OBS.
The two log files:
http://pastebin.com/WefjhtsF
http://pastebin.com/wRExf8XU
::EDIT::
I also just finished streaming CS:GO for an hour, and no issues. Is it just the more graphically intense games?
The two log files:
http://pastebin.com/WefjhtsF
http://pastebin.com/wRExf8XU
::EDIT::
I also just finished streaming CS:GO for an hour, and no issues. Is it just the more graphically intense games?
Last edited:
OG See OH Zee
Member
CSGO doesn't use much memory in the first place.
Also on an extra note that it seems so far no problems after a new update for Windows 10 came out. Done a Black Ops 3 session with textures set to Extra (since this uses a ridiculous amount of VRAM) and so far no freezing on OBS Studio.
Jayson's Rage
New Member
^ That's what I'm saying. My issues before were when I was streaming Forza Horizon 3
Last edited:
Just as a heads up, there are no visual GUI alerts for the error I've described in this thread. Your logs do not show the error that this thread is about. I would just count yourself lucky.
Forza Horizon 3 has been known to trigger this bug. But again, older games like BioShock, WoW, and Minecraft can also trigger this bug.
Unfortunately, I've seen other people with the latest Windows 10 update (KB3194496, Build 14393.222) still reporting issues.
Well, i reinstalled my Win10, got some crappy errors (could not install the latest update, the mentioned build .222) and freezes. By forcing the update via USB stick and what we used to call "repair install" before, i managed to update the regular Win10 to the latest build.
I didnt test it a lot, but at least the webcam was instantly loaded without any dancing and calling to the hardware gods.
But still, so many issues. When i drop my BIOS to default settings, Win10 refuses to load and hangs in auto repair. Like WTF.
But once we get a stable copy of Win10 installed, we want everything to run buttersmooth, so i hope software developers jump on the bug train and help with fixing it.
P.S. i never had so many issues with Win10, even the fast ring preview builds were more stable, with only minor bugs - nothing that severe that requires heavy registry hacks or forcing updates via install media...
I didnt test it a lot, but at least the webcam was instantly loaded without any dancing and calling to the hardware gods.
But still, so many issues. When i drop my BIOS to default settings, Win10 refuses to load and hangs in auto repair. Like WTF.
But once we get a stable copy of Win10 installed, we want everything to run buttersmooth, so i hope software developers jump on the bug train and help with fixing it.
P.S. i never had so many issues with Win10, even the fast ring preview builds were more stable, with only minor bugs - nothing that severe that requires heavy registry hacks or forcing updates via install media...
Ryan1derlin
New Member
https://gist.github.com/68f93047aff0d2cbd28de9e1689cf58a is there nothing that I can do... I literally havent been able to stream for weeks
As I previously replied in the thread you posted, there are several possible workarounds listed in the first post of this thread, so there are things you can try. I can't guarantee that any of them will work though, as I've heard varying results from different people. If you do try them, please let us know what worked and what didn't.
Ryan1derlin
New Member
none of them worked
The log you posted indicates that you still had recent Windows Updates and the Anniversary Update installed.
- Status