OBS crash after 4hrs of stream

Code: 
Unhandled exception: e
Date/Time: 2026-08-07, 02:50:58
Fault address: 7FFFCD161ADA (c:\windows\system32\kernelbase.dll)
libobs version: 32.0.4 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8875; 64-bit)
CPU: 12th Gen Intel(R) Core(TM) i5-12600K


Thread C0F0: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000009FEDBFF260 00007FFFCD161ADA 00007FFFCD247300 0000000000000000 0000000000000000 0000000000002000 kernelbase.dll!0x7fffcd161ada
0000009FEDBFF360 00007FFF2055B9C7 0000009FEDBFF5E0 0000000000000000 0000028338FA60C0 0000000000000780 obs.dll!video_frame_init+0x467
0000009FEDBFF480 00007FFF20516A35 0000028338FA60C0 0000000000000012 0000000000000780 0000000000000000 obs.dll!obs_source_frame_init+0x55
0000009FEDBFF510 00007FFF2051454A 00000282E3FD5BB0 0000009FEDBFF6B0 00000282E3FD5BE0 00000282E3FD5BE0 obs.dll!obs_source_frame_create+0x5a
0000009FEDBFF540 00007FFF2051EFF6 0000028200000012 0000009FEDBFF6B0 00000282E3FD5BE0 0000000000000100 obs.dll!cache_video+0x226
0000009FEDBFF5B0 00007FFF2051F4EF 00000282E8BDE300 00007FFF8B2CC937 00000000005EEC00 0000000000000000 obs.dll!obs_source_output_video2+0x1bf
0000009FEDBFF6F0 00007FFF8B2C4876 00000282DD47D1B0 0000009FEDBFF800 00000282E8BDE330 D1E5209F00000002 win-dshow.dll!DShowInput::OnVideoData+0x276
0000009FEDBFF730 00007FFF8B2CD7AA 00000282DD47D1B0 00000282E8BDE330 00000282E8BDE330 0000028200000000 win-dshow.dll!DShow::HDevice::SendToCallback+0x8a
0000009FEDBFF7A0 00007FFF8B2CDB03 00000282DDEA40D0 0000000000000000 00000282E422FB38 0000000000000000 win-dshow.dll!DShow::HDevice::Receive+0x2e3
0000009FEDBFF840 00007FFF8B2CBC9E 00000282E8BDE330 0000000000001000 00000282DDEA4250 00000282E8BDE330 win-dshow.dll!DShow::CapturePin::Receive+0x3e
0000009FEDBFF870 00007FFF9E1DAC9F 000002832510C040 00000282E8BDE330 0000000000000000 000002832510C040 ksproxy.ax!0x7fff9e1dac9f
0000009FEDBFF8A0 00007FFF9E1DD5E0 000000283E3B9608 000002832487EA10 000002832510C040 000000283E390AFE ksproxy.ax!0x7fff9e1dd5e0
0000009FEDBFF910 00007FFF9E1D13E2 0000000000000000 0000000000000000 0000000000000080 0000009FEDBFF940 ksproxy.ax!0x7fff9e1d13e2
0000009FEDBFF9E0 00007FFF9E1DDB34 00000282E35D2070 000002832510C2A0 00000282E35D2070 0000000000000002 ksproxy.ax!0x7fff9e1ddb34
0000009FEDBFFA10 00007FFF9E1D2724 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ksproxy.ax!0x7fff9e1d2724
0000009FEDBFFA70 00007FFFCE65E957 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7fffce65e957
0000009FEDBFFAA0 00007FFFCF82AD6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7fffcf82ad6c
...
Parsing the log.
Out of RAM when attempting to get new picture from the Video Capture Device. The strings read from bottom to top - "dshow.dll!DShow::CapturePin::Receive" --> from the device to RAM --> "obs.dll!video_frame_init" - in this step the RAM should be accessed but it failed, the last step with the "kernelbase" is just break on error inside system DLL (thus the program can be terminated by OS individually and PC will work normally). The "Unhandled exception: e" means "ERROR_OUTOFMEMORY" or "Not enough memory resources are available to complete this operation." This is standard Windows error for such events (when RAM is not available for the application).

Prevention.
If the device is too greedy for the RAM consumption and may leak some data - restart OBS time to time - it may help.

There are similar threads:
https://obsproject.com/forum/threads/obs-crashing-for-no-reason.195727/
https://obsproject.com/forum/thread...ding-and-no-mkv-file-in-output-folder.195829/
and many more.
 
My capture card is the Avermedia Live Gamer 4K GC573. I had some browser tabs open which is more than likely the culprit, Firefox has been hogging a lot of memory as of late, I'll cut down on those. Is there anything i could with the capture card to fix?
 
You must log in or register to reply here.
Back
Top