Question / Help My OBS crashes shortly after stream starts

[Povlava]

Hello I start up my OBS and then begin to to stream hearthstone in windowed mode. I noticed if I alt tab between certain programs OBS crashes. Knowing that information I proceeded to start up OBS and go immediately to hearthstone thinking that it wouldn't crash and yet it did. Is it a memory issue or a software issue? Here is the crash log.


This crash appears to have occured in the 'c:\windows\system32\igd10umd32.dll' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 62EE3F09 (c:\windows\system32\igd10umd32.dll)
OBS version: Open Broadcaster Software v0.625b
Windows version: 6.2 (Build 9200)
CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
11B7EE10 62EE3F09 05F54680 00000003 11B7EEFC 038F3FA0 igd10umd32.dll!0x62ee3f09
11B7EE2C 6313341B 05355E90 00000000 0534F8A0 00000028 igd10umd32.dll!0x6313341b
11B7EE50 630D002B 0533954C 0534F8A0 00000001 0533954C igd10umd32.dll!0x630d002b
11B7EE94 630EAC5B 0533954C 11B7EF64 00000000 05338400 igd10umd32.dll!0x630eac5b
11B7EED8 630EF51F 0533954C 0534D0C4 00000000 00000000 igd10umd32.dll!0x630ef51f
11B7EFF4 630EE924 0533954C 0534D0C4 00000000 00000000 igd10umd32.dll!0x630ee924
11B7F040 630D5DB7 0534D0C4 00000000 00000000 00000000 igd10umd32.dll!0x630d5db7
11B7F088 630CC1F5 0562EE10 05678B90 00000000 00000000 igd10umd32.dll!0x630cc1f5
11B7F0CC 628BCA0E 05678B90 00000000 00000000 00000000 nvumdshim.dll!0x628bca0e
11B7F0FC 628BAEC5 055542A8 00000000 05622A20 00000000 nvumdshim.dll!0x628baec5
11B7F160 628B80E6 055542A8 00000000 00000000 00000000 nvumdshim.dll!0x628b80e6
11B7F1D0 628BA5DF 00B7F23C D43E1361 052C7EB8 05675788 nvumdshim.dll!0x628ba5df
11B7F218 637D0D45 0567586C 00000000 0567B128 00000000 d3d11.dll!0x637d0d45
11B7F264 637DE0E2 05675788 00000000 00000000 D4722B81 d3d11.dll!0x637de0e2
11B7F284 63C60141 052C7EB8 013F2C00 013F2C00 05675778 dxgi.dll!0x63c60141
11B7F2DC 003FD0AB 00000000 013F2C00 00000001 0550D628 obs.exe!D3D10OutputDuplicator::AcquireNextFrame+0x18b
11B7F358 004052EB 0347F5E0 00000001 00000040 0000918E obs.exe!DesktopImageSource::PreprocessWindows8MonitorCapture+0x1b
11B7F3A0 004054DC 03320000 00000000 00426B46 00000000 obs.exe!DesktopImageSource::Preprocess+0x2c
11B7F634 5D3B5438 00000000 00000000 00000000 01000100 obsapi.dll!Scene::Preprocess+0x28
11B7F640 00426B46 75A286E3 00000000 11B7F964 76F0BE99 obs.exe!OBS::MainCaptureLoop+0x9c6
11B7F918 00424E55 00000000 11B7F964 76F0BE99 00000000 obs.exe!OBS::MainCaptureThread+0x5
11B7F91C 75A286E3 00000000 C1411226 00000000 00000000 kernel32.dll!0x75a286e3
11B7F928 76F0BE99 00424E50 00000000 FFFFFFFF 76F81E8B ntdll.dll!0x76f0be99
11B7F96C 76F0BE6C 00424E50 00000000 00000000 00000000 ntdll.dll!0x76f0be6c

A minidump was saved to C:\Users\Mike Bets\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-08-26_5.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module

 

[Lain]

On switchable-graphics laptops with windows 8+, monitor capture is subject to instability due to the fact that the intel/nvidia drivers have to communicate with one another. It's a driver issue, to sum it up, and they still have yet to fix it, it seems. I would recommend using a different method of capture.