Bug Report Window Capture Crashing Display Driver - Help?

[Oymoron5]

Hi there guys,

I have only just started streaming recently and have been really happy with the OBS program. However, I have come across a problem, in that whenever I try to window capture (in order to overlay Twitch chat in my stream) within 5 minutes or so my display driver will crash and recover. I have tried troubleshooting this problem by myself to no avail, so I was hoping someone here might be able to help?

When the driver crashes and recovers the following message is displayed:
"Display driver ha stopped responding and has successfully recovered"

and in Windows Event viewer the following event is seen:
"Display driver amdkmdap stopped responding and has successfully recovered."

In OBS I am capturing my PS3 through an Elgato Game Capture HD, I am also capturing my webcam, and I want to overlay the Twitch chat as well. If I don't have the chat window capture then the stream works fine, however as soon as I add in that window capture my display driver crashes within a few minutes, as I have mentioned. Prior to crashing everything works fine though and I have not experienced this problem with anything else.

Troubleshooting I have performed so far:
-Updating graphics drivers
-Updating system BIOS
-Updating chipset drivers
-Uninstalling and reinstalling OBS
-Window capturing with and without colour key enabled
-Window capturing different windows (e.g. Twitch chat in chrome and Twitch chat in Hexchat)


This is my most recent log file:

09:01:32: Open Broadcaster Software v0.622b - 32bit (´・ω・｀)
09:01:32: -------------------------------
09:01:32: CPU Name: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
09:01:32: CPU Speed: 2295MHz
09:01:32: Physical Memory:  4095MB Total, 4095MB Free
09:01:32: stepping id: 9, model 58, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 8, total cores 4
09:01:32: monitor 1: pos={0, 0}, size={1366, 768}
09:01:32: Windows Version: 6.2 Build 9200
09:01:32: Aero is Enabled
09:01:32: -------------------------------
09:01:32: OBS Modules:
09:01:32: Base Address     Module
09:01:32: 00F20000         OBS.exe
09:01:32: 70680000         OBSApi.dll
09:01:32: 72480000         DShowPlugin.dll
09:01:32: 72CC0000         GraphicsCapture.dll
09:01:32: 71800000         NoiseGate.dll
09:01:32: 72C70000         PSVPlugin.dll
09:01:32: ------------------------------------------
09:01:32: Adapter 1
09:01:32:   Video Adapter: AMD Radeon HD 7600M Series
09:01:32:   Video Adapter Dedicated Video Memory: 2125463552
09:01:32:   Video Adapter Shared System Memory: 2169438208
09:01:32:   Video Adapter Output 1: pos={0, 0}, size={1366, 768}, attached=true
09:01:32: =====Stream Start: 2014-05-11, 09:01:32===============================================
09:01:32:   Multithreaded optimizations: On
09:01:32:   Base resolution: 1280x720
09:01:32:   Output resolution: 640x360
09:01:32: ------------------------------------------
09:01:32: Loading up D3D10 on AMD Radeon HD 7600M Series (Adapter 1)...
09:01:32: ------------------------------------------
09:01:32: Audio Format: 44100 Hz
09:01:32: ------------------------------------------
09:01:32: Audio Channels: 2 Ch
09:01:32: Playback device Default
09:01:32: ------------------------------------------
09:01:32: Using desktop audio input: Speakers (Realtek High Definition Audio)
09:01:32: Global Audio time adjust: 0
09:01:32: ------------------------------------------
09:01:32: Using auxilary audio input: Microphone (Realtek High Definition Audio)
09:01:32: Mic time offset: 1400
09:01:32: ------------------------------------------
09:01:32: Audio Encoding: AAC
09:01:32:     bitrate: 80
09:01:32: Using Window Capture
09:01:32: ------------------------------------------
09:01:32:     device: TOSHIBA Web Camera,
09:01:32:     device id \\?\usb#vid_04f2&pid_b303&mi_00#7&2d78d847&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global,
09:01:32:     chosen type: YUY2, usingFourCC: false, res: 320x240 - 320x240, frameIntervals: 333332-666666
09:01:32:     use buffering: true - 14000000, fourCC: 'YUY2'
09:01:32:     audio device: Disable,
09:01:32:     audio device id Disabled,
09:01:32:     audio time offset 0,
09:01:32:
09:01:32: Using directshow input
09:01:32: ------------------------------------------
09:01:32:     device: Elgato Game Capture HD,
09:01:32:     device id {39F50F4C-99E1-464a-B6F9-D605B4FB5918},
09:01:32:     chosen type: UYVY, usingFourCC: false, res: 1280x720 - 1280x720, frameIntervals: 333333-333333
09:01:32:     use buffering: true - 0, fourCC: 'UYVY'
09:01:32:
09:01:32: Using directshow input
09:01:32: Scene buffering time set to 400
09:01:32: ------------------------------------------
09:01:32: Video Encoding: x264
09:01:32:     fps: 30
09:01:32:     width: 640, height: 360
09:01:32:     preset: veryfast
09:01:32:     profile: main
09:01:32:     keyint: 60
09:01:32:     CBR: yes
09:01:32:     CFR: yes
09:01:32:     max bitrate: 560
09:01:32:     buffer size: 360
09:01:32: ------------------------------------------
09:03:24: ------------------------------------------
09:03:24:     device: Elgato Game Capture HD,
09:03:24:     device id {39F50F4C-99E1-464a-B6F9-D605B4FB5918},
09:03:24:     chosen type: UYVY, usingFourCC: false, res: 1280x720 - 1280x720, frameIntervals: 333333-333333
09:03:24:     use buffering: true - 0, fourCC: 'UYVY'
09:03:24:
09:03:24:     device audio info - bits per sample: 16, channels: 2, samples per sec: 48000, block size: 4
09:05:29: Total frames encoded: 7096, total frames duplicated: 195 (2.75%)
09:05:29: Total frames rendered: 6910, number of late frames: 4 (0.06%) (it's okay for some frames to be late)
09:05:33:
09:05:33: Profiler time results:
09:05:33:
09:05:33: ==============================================================
09:05:33: video thread frame - [100%] [avg time: 4.279 ms] [children: 65.6%] [unaccounted: 34.4%]
09:05:33: | scene->Preprocess - [63%] [avg time: 2.694 ms]
09:05:33: | GPU download and conversion - [2.59%] [avg time: 0.111 ms] [children: 2.27%] [unaccounted: 0.327%]
09:05:33: | | flush - [1.94%] [avg time: 0.083 ms]
09:05:33: | | CopyResource - [0.234%] [avg time: 0.01 ms]
09:05:33: | | conversion to 4:2:0 - [0.0935%] [avg time: 0.004 ms]
09:05:33: Convert444Threads - [100%] [avg time: 0.128 ms] [children: 96.1%] [unaccounted: 3.91%]
09:05:33: | Convert444toNV12 - [96.1%] [avg time: 0.123 ms]
09:05:33: encoder thread frame - [100%] [avg time: 0.33 ms] [children: 0.909%] [unaccounted: 99.1%]
09:05:33: | sending stuff out - [0.909%] [avg time: 0.003 ms]
09:05:33: ==============================================================
09:05:33:
09:05:33:
09:05:33: Profiler CPU results:
09:05:33:
09:05:33: ==============================================================
09:05:33: video thread frame - [cpu time: avg 2.616 ms, total 18078.1 ms] [avg calls per frame: 1]
09:05:33: | scene->Preprocess - [cpu time: avg 2.209 ms, total 15265.6 ms] [avg calls per frame: 1]
09:05:33: | GPU download and conversion - [cpu time: avg 0.038 ms, total 265.625 ms] [avg calls per frame: 1]
09:05:33: | | flush - [cpu time: avg 0.022 ms, total 156.25 ms] [avg calls per frame: 1]
09:05:33: | | CopyResource - [cpu time: avg 0.004 ms, total 31.25 ms] [avg calls per frame: 1]
09:05:33: | | conversion to 4:2:0 - [cpu time: avg 0.004 ms, total 31.25 ms] [avg calls per frame: 1]
09:05:33: Convert444Threads - [cpu time: avg 0.08 ms, total 1109.38 ms] [avg calls per frame: 2]
09:05:33: | Convert444toNV12 - [cpu time: avg 0.08 ms, total 1109.38 ms] [avg calls per frame: 2]
09:05:33: encoder thread frame - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
09:05:33: | sending stuff out - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
09:05:33: ==============================================================
09:05:33:
09:05:33: =====Stream End: 2014-05-11, 09:05:33=================================================
09:14:15: Memory Leaks Were Detected.
09:14:15:

Hoping there is someone out there who might be able to provide some advice as to how to fix my problem.

Edit: This is all running on my Toshiba Satellite L850 laptop

 

[Lain]

Hm, interesting. An AMD laptop that actually has the AMD as its primary device. Rarely see that these days. Laptops are kind of difficult to deal with, but it's usually only with switchable laptops. Outside of drivers I'm not entirely sure what to suggest -- I'm kind of wanting to test some newer versions that are upcoming but won't be able to do it with capture device support for a while.

 

[Oymoron5]

Thanks for replying Jim.
Just to clarify, OBS does not crash when my display driver crashes.
I don't really know what else to say haha. But if there is anything else you need me to provide that could help then I am happy to.

I have sort of given up on trying to fix it myself, so I found Sickbattery's IRC chat plugin for OBS yesterday and will just use that to overlay chat for now. However, although this fixes my problem for overlaying chat, I will still be unable to add in things like a speed run timer and such if I wish to in the future.

 

[Lain]

Yea, I do wish I could help, but when the drivers do something like that it usually means that we don't really have much control over it -- it just means the drivers don't like some particular aspect of what's going on with the computer (even drivers have bugs or certain parts that are prone to bugs due to the difficulty to test, laptops are particularly susceptible to this behavior).

There's not too much that can be done outside of experimentation and trying to work around it trial and error on either your end or OBS' end.

If you do figure out what works and what doesn't, make sure to state exactly what you do though. Also, thank you for noting the specific laptop, that does help, at least for potentially getting such hardware in the future and making note of what has been known to happen with what.

 

[Oymoron5]

Yeah okay, well thank you for your expertise and insight anyway Jim. I love the program and will just find way's around the problem until I get a desktop in the next couple of years. I will kept testing it when I can think of things and when there are updates, but at least now I have been able to add chat through another means :)

I could always talk to AMD about the problem, but I doubt they would do anything.

 

[Lain]

Well when we release our new version I'd love to test that both with DirectX and OpenGL, but we won't be able to replicate the same conditions for quite some time, so there's probably not much either of us can do except wait. I'm really sorry about the trouble, I know it's a pain to deal with.

 

[Oymoron5]

Yeah okay, that would be great. And it's fine, you have been more than helpful, and at least I have an alternative to the window capture for what I need at the moment :)

 

[yanis31]

i have the same issue with my PC - AMD FX8370E, 8gb ram and a GTX780 poseidon,
nvidia driver crashes and recovers atleast during "preview" - runs fine in game/ havent noticed the message popup or game problems etc.
(driver version 344.75 WHQL Windows 8.1 Pro - 64bit OBS / current newest driver from nvidia is problematic so i'm skipping it for now)
if i untick the window capture in the preview the problem goes away - im also using transparency on the window,
chat plugin doesnt seem to work with the newest OBS release so only reason im using this (it does look kinda better to be honest too)