Bug Report OBS freezing after a few minutes

R

R69

New Member
Hello OBS folks, I am having a problem, which I hope, you can help me out with.

My goal is to record some longer in-game footage, using my i5 3570K's Quick Sync function. Recording itself works just fine and OBS puts out a working .mp4 file, but only if I keep the length of the clips short. Unfortunately OBS doesn't seem to be able to record several minutes in one go for me (the longest it lasted was 13 minutes so far). The recording randomly seems to stop and I get that "Woops! OBS has crashed. Would you like to view a crash report?" message alongside the following crash report:

Code: 
OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

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

**** UNHANDLED EXCEPTION: 80000003
Fault address: 000007FEFCED3CA2 (c:\windows\system32\kernelbase.dll)
OBS version: Open Broadcaster Software v0.62b test build 1
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz

Crashing thread stack trace:
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000000002FEE28 000007FEFCED3CA2 000007FED62606D0 0000000000007530 00000000002FED88 0000000000000000 kernelbase.dll!0x7fefced3ca2
00000000002FEE30 000007FED6231243 00000000003A0800 000000013F9EB4F8 00000000003A0800 000007FF00000002 obsapi.dll!OSTerminateThread+0x33
00000000002FEE60 000000013F945623 0000000000000001 0000000000000000 0000000000000001 000000000042B330 obs.exe!OBS::Stop+0x163
00000000002FEF00 000000013F943722 0000000000000000 00000000003380C0 0000000000000000 000007FEF4939518 obs.exe!OBS::StopRecording+0x22
00000000002FEF30 000000013F91341E 0000000000000001 00000000002FF080 0000000000000402 0000000000000000 obs.exe!OBS::CallHotkey+0x8e
00000000002FEF80 000000013F96BEEB 0000000000000000 0000000000000001 000007FFFFFA0000 0000000000000000 obs.exe!OBS::OBSProc+0x1bfb
00000000002FF170 0000000076CE9BD1 00000000002FF468 000000013F96A2F0 00000000008A0250 00000000008A0250 user32.dll!0x76ce9bd1
00000000002FF230 0000000076CE98DA 0000000000000000 0000000000000000 000000013F96A2F0 0000000000000001 user32.dll!0x76ce98da
00000000002FF2B0 0000000076CE67C2 0000000000160635 0000000000160635 000000013F96F750 0000000000660000 user32.dll!0x76ce67c2
00000000002FF340 000000013F937729 0000000000000000 0000000000000005 000000013F910000 0000000000000000 obs.exe!WinMain+0xa39
00000000002FF8E0 000000013F9AC7F0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!__tmainCRTStartup+0x148
00000000002FF920 0000000076DE59ED 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x76de59ed
00000000002FF950 0000000076F1C541 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x76f1c541

Video thread stack trace:
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000000A54F6B8 0000000076F412FA 0000000000000002 0000000000000000 0000000000655EF0 000007FED621F4BD ntdll.dll!0x76f412fa
000000000A54F6C0 000007FEFCEA10DC 0000000000000001 000007FED6424D00 0000000000000000 0000000000000178 kernelbase.dll!0x7fefcea10dc
000000000A54F760 000000013F94B110 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!OBS::MainCaptureLoop+0x1a70
000000000A54FC00 000000013F9480A9 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!OBS::MainCaptureThread+0x9
000000000A54FC30 0000000076DE59ED 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x76de59ed
000000000A54FC60 0000000076F1C541 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x76f1c541

Encode thread stack trace:
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000000A2DF598 0000000076F4186A 0000000000000000 0000000000000000 0000000000000000 0000000000000398 ntdll.dll!0x76f4186a
000000000A2DF5A0 000007FEFCEA1430 000000000A2DF6E8 000000000A2DF6D0 0000000000000000 0000000076F3E40B kernelbase.dll!0x7fefcea1430
000000000A2DF6A0 0000000076DE06E0 0000000000000000 000000000A2DF8F0 0000000000393C00 000000000A2DF7D1 kernel32.dll!0x76de06e0
000000000A2DF730 000000013F92C6D3 0000000000393C00 000000000A2DF900 000000000A2DF8F0 0000000000000000 obs.exe!QSVEncoder::ProcessEncodedFrame+0x53
000000000A2DF830 000000013F92D55A 00000000003A0B08 000000000A2DFA10 00000000003A0B08 000000000A2DF939 obs.exe!QSVEncoder::Encode+0xba
000000000A2DF8C0 000000013F948AEF 00000000000B69F1 0000000000000003 0000000000000031 0000000000000000 obs.exe!OBS::ProcessFrame+0xcf
000000000A2DF9A0 000000013F949150 0000000000000001 0000000000000001 000000000000AF51 0000000000006592 obs.exe!OBS::EncodeLoop+0x540
000000000A2DFAE0 000000013F948099 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!OBS::EncodeThread+0x9
000000000A2DFB10 0000000076DE59ED 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x76de59ed
000000000A2DFB40 0000000076F1C541 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x76f1c541

A minidump was saved to C:\Users\XXX\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-04-15_5.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address                      Module

I already went back to my CPU's default clocking speed (I've had it overclocked to 4,2 Ghz previously) and tried recording with worse quality, but it still keeps freezing. If further hardware specifications are relevant, let me know.

Thanks for all suggestions in advance!
Greetings R69
 

Attachments

  • R69 minidump.zip
    70 KB · Views: 15
R

R69

New Member
That does seem to work just fine without crashing, but x264 isn't really an option to me, since I want the performance hit to be minimal. I've been using other capturing tools such as Fraps & Shadowplay previously and to me their downside always was increased load on either the CPU or the dedicated GPU. It seems like a good idea to let the iGPU take care of the capturing, while the CPU's and dedicated GPU's power remains for the actual game rendering. I maybe should have mentioned this beforehand, but thanks for your suggestion.

I've noticed the "QSVHelper.exe *32" process remains active in the task manager after OBS freezes/crashes. It has a CPU load of 25% and must be manually terminated.
 
You must log in or register to reply here.
Top