OBS Suddenly crashing during streams

W

wltedflwr

New Member
Hi,
I am fairly new to this and I have learned almost all of what i've built in OBS on my own. The last 2 times I streamed my OBS crashed in the middle of it. One day it crashed like 3 likes maybe an hour or so apart and the today in only crashed once but still never used to do this. Each time I was able to bring it back up immediately without safemode and had no issues until it crashed again. I also was not seeing a drop in bit rate and I never have dropped frames. I've made no configuration changes prior to it happening and had an uneventful stream on April 25, 26, and 30.

Here is the crash report log from today's crash: https://obsproject.com/logs/crashes/3AHBAXwGFRIgglpg

Please let me know if you need anything else because again, very new to all this.
 
Code: 
Unhandled exception: e
Date/Time: 2026-05-09, 12:34:20
Fault address: 7FF90D5679DA (c:\windows\system32\kernelbase.dll)
libobs version: 32.0.4 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8246; 64-bit)
CPU: AMD Ryzen 3 7320U with Radeon Graphics

Thread 237C: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000007ECABFF550 00007FF90D5679DA 0000000000000004 00007FF90FF5CD14 0000000000000002 0000000000000000 kernelbase.dll!0x7ff90d5679da
0000007ECABFF650 00007FF8CCA4B9C7 0000000000000000 0000000000000000 000001E4CE331400 0000000000000000 obs.dll!video_frame_init+0x467
0000007ECABFF770 00007FF8CCA06A35 000001E4CE331400 0000000000000004 0000000000000F00 0000000000000000 obs.dll!obs_source_frame_init+0x55
0000007ECABFF800 00007FF8CCA0454A 000001E4DC1D8AF0 0000007ECABFF9A0 000001E4DC1D8B20 000001E4DC1D8B20 obs.dll!obs_source_frame_create+0x5a
0000007ECABFF830 00007FF8CCA0EFF6 000001E400000004 0000007ECABFF9A0 000001E4DC1D8B20 000001E4DC1D8320 obs.dll!cache_video+0x226
0000007ECABFF8A0 00007FF8CCA0F4EF 000001E4DB780C00 00007FF8CB4FC937 0000000000FD2000 0000007ECABFFA3C obs.dll!obs_source_output_video2+0x1bf
0000007ECABFF9E0 00007FF8CB4F4876 000001E4E7520AD0 0000007ECABFFAF0 000001E4DB780C70 D1E5209F00000002 win-dshow.dll!DShowInput::OnVideoData+0x276
0000007ECABFFA20 00007FF8CB4FD7AA 000001E4B3DAB810 000001E4DB780C70 000001E4B3DAB780 0000000000000000 win-dshow.dll!DShow::HDevice::SendToCallback+0x8a
0000007ECABFFA90 00007FF8CB4FDB03 0000000000000000 0000000000000000 000001E4B3DAB8F0 0000000000000000 win-dshow.dll!DShow::HDevice::Receive+0x2e3
0000007ECABFFB30 00007FF8CB4FBC9E 000001E4DB780C70 000001E4DB780C70 0000000000000000 00007FF90D5559CD win-dshow.dll!DShow::CapturePin::Receive+0x3e
0000007ECABFFB60 00007FF8351D01CD 000001E4B3DAB780 000001E4DB780C70 0000000000000000 00007FF8351D2EA2 virtualcamclient.dll!0x7ff8351d01cd
0000007ECABFFBB0 00007FF8351D06A8 000001E4B3DAB780 00007FF90EAD6AD0 0000000000000000 0000000000000000 virtualcamclient.dll!0x7ff8351d06a8
0000007ECABFFBE0 00007FF8351D2EAC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 virtualcamclient.dll!0x7ff8351d2eac
0000007ECABFFC10 00007FF90EA1E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff90ea1e8d7
0000007ECABFFC40 00007FF90FFCC3FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff90ffcc3fc
...
I think, this "Unhandled exception: e" is ERROR_OUTOFMEMORY or "Not enough memory resources are available to complete this operation.". OBS was halted when it asked OS to get some RAM space (in your case it is more likely shared with video card, so VRAM). OBS needed this space to temporary store new video frame for processing from DrectShow device (camera, virtual device or capture card whatever it was), and OS didn't found any free space in RAM/VRAM. Consumption of the resources like RAM/VRAM can be monitored via the Task Manager of the Windows during the streaming/recording event. If RAM consumption grows infinitely and in a big steps - then you need to find the program/plugin/script that causing this. For example Browser sources usually greedy for RAM consumption. Also, the task can be too demanding for your PC.
 
Suslik V said:
Code: 
Unhandled exception: e
Date/Time: 2026-05-09, 12:34:20
Fault address: 7FF90D5679DA (c:\windows\system32\kernelbase.dll)
libobs version: 32.0.4 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8246; 64-bit)
CPU: AMD Ryzen 3 7320U with Radeon Graphics

Thread 237C: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000007ECABFF550 00007FF90D5679DA 0000000000000004 00007FF90FF5CD14 0000000000000002 0000000000000000 kernelbase.dll!0x7ff90d5679da
0000007ECABFF650 00007FF8CCA4B9C7 0000000000000000 0000000000000000 000001E4CE331400 0000000000000000 obs.dll!video_frame_init+0x467
0000007ECABFF770 00007FF8CCA06A35 000001E4CE331400 0000000000000004 0000000000000F00 0000000000000000 obs.dll!obs_source_frame_init+0x55
0000007ECABFF800 00007FF8CCA0454A 000001E4DC1D8AF0 0000007ECABFF9A0 000001E4DC1D8B20 000001E4DC1D8B20 obs.dll!obs_source_frame_create+0x5a
0000007ECABFF830 00007FF8CCA0EFF6 000001E400000004 0000007ECABFF9A0 000001E4DC1D8B20 000001E4DC1D8320 obs.dll!cache_video+0x226
0000007ECABFF8A0 00007FF8CCA0F4EF 000001E4DB780C00 00007FF8CB4FC937 0000000000FD2000 0000007ECABFFA3C obs.dll!obs_source_output_video2+0x1bf
0000007ECABFF9E0 00007FF8CB4F4876 000001E4E7520AD0 0000007ECABFFAF0 000001E4DB780C70 D1E5209F00000002 win-dshow.dll!DShowInput::OnVideoData+0x276
0000007ECABFFA20 00007FF8CB4FD7AA 000001E4B3DAB810 000001E4DB780C70 000001E4B3DAB780 0000000000000000 win-dshow.dll!DShow::HDevice::SendToCallback+0x8a
0000007ECABFFA90 00007FF8CB4FDB03 0000000000000000 0000000000000000 000001E4B3DAB8F0 0000000000000000 win-dshow.dll!DShow::HDevice::Receive+0x2e3
0000007ECABFFB30 00007FF8CB4FBC9E 000001E4DB780C70 000001E4DB780C70 0000000000000000 00007FF90D5559CD win-dshow.dll!DShow::CapturePin::Receive+0x3e
0000007ECABFFB60 00007FF8351D01CD 000001E4B3DAB780 000001E4DB780C70 0000000000000000 00007FF8351D2EA2 virtualcamclient.dll!0x7ff8351d01cd
0000007ECABFFBB0 00007FF8351D06A8 000001E4B3DAB780 00007FF90EAD6AD0 0000000000000000 0000000000000000 virtualcamclient.dll!0x7ff8351d06a8
0000007ECABFFBE0 00007FF8351D2EAC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 virtualcamclient.dll!0x7ff8351d2eac
0000007ECABFFC10 00007FF90EA1E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff90ea1e8d7
0000007ECABFFC40 00007FF90FFCC3FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff90ffcc3fc
...
I think, this "Unhandled exception: e" is ERROR_OUTOFMEMORY or "Not enough memory resources are available to complete this operation.". OBS was halted when it asked OS to get some RAM space (in your case it is more likely shared with video card, so VRAM). OBS needed this space to temporary store new video frame for processing from DrectShow device (camera, virtual device or capture card whatever it was), and OS didn't found any free space in RAM/VRAM. Consumption of the resources like RAM/VRAM can be monitored via the Task Manager of the Windows during the streaming/recording event. If RAM consumption grows infinitely and in a big steps - then you need to find the program/plugin/script that causing this. For example Browser sources usually greedy for RAM consumption. Also, the task can be too demanding for your PC.
Click to expand...
Thanks. Not as technology savvy as i used to be... Do you think this could be from my cameras? I have 2 insta 360 link 2c pros. The one for my overhead shot (art stream) is a hardware set up but the second for my face cam is a virtual cam because I couldn't get it to use both as hardware...a problem i didn't have with 2 different brands.

Any thoughts or suggestions are welcome.

Additionally, it seems one one crash report was generated but obs quit mid stream on me more than once as mentioned. I used the log analysis tool but all it told me was that I'm using wifi but my wifi is stable and nothing about what happened seems to be related to that
 
wltedflwr said:
Do you think this could be from my cameras?
Click to expand...
Have no idea. This should be tested by you. You may launch Task Manager and make test recording (you may set encoder to "same as stream" instead of running true live event) and time to time look at the RAM/VRAM consumption for each application. If some program "forgets" data in the memory, and thus memory consumption rapidly grows, then it is called "leakage" or "memory leak". Only option here is to restart such application before memory ends. Also, look for updates for your lovely programs - there is chance that the problem was fixed already.
 
Last edited:
You must log in or register to reply here.
Back
Top