Unfortunately, I don't have enough information about the problem. I can tell you right now that I don't think it's a bug, and I know you'll probably want to disagree with me here, but bugs typically tend have certain traits. This has more the traits of system issues or something hardware related. The reason why I say this is because bugs are fairly consistent and usually happen to all users when that specific piece of code is encountered.
In this case, this error means that the graphics driver stops working, and can no longer download data from the GPU. This specific type of error is always is returned from a windows function, not an OBS function. This is returned basically from the graphics driver, telling OBS it can no longer download data from the GPU, and that graphics has stopped functioning.
This is very unusual, and most likely not an actual bug for a number of reasons. Firstly, OBS has had extensive testing on many systems, even old old systems with vastly outdated directx 10 hardware, and even that hardware has never really encountered this problem. Secondly, this particular error seems to be completely erratic among users. It's something that has happened in the past, but it's almost entirely random who it happens to. I've never found any sort of link (though I should probably try to document that better). At this point I can't even speculate what's going on when this does happen.
Also, I want you to post a log file so Ican get a good look at your system.
The best thing I could probably suggest is try changing your capturing methods and OBS video settings. If using 60 FPS, try 30. If you're using no downscale, then try some downscale. If using window capture on a game, then try game capture instead, or vise versa. Experiment with these things and see what effects this. If you were to say "It happens when I have an [x] in the scene", then that could give further hints and I could probably start to get some leads as to what's going on.
I know you really don't want to have to deal with this stuff.. and you don't have to. But if you are able to find out this sort of info, it could be helpful in me determining what exacty is going on. Even if it's not something caused by OBS, I could probably find ways around driver issues if I were to know more about what effects it.
