OBS Crashing For No Reason

T

TippyBard29

New Member
For absolutely no reason, since a few days ago,. OBS has been crashing on me, and I have no clue why. Here's all of the crash reports from when it began up to now:
 

Attachments

I'm not as familiar with the Elgato 4K capture card itself. Is that something you changed recently? Logs look like it is trying to capture at 120FPS and your stream is 60fps. Have you tried changing that to match at 60 and making sure drivers are up to date?
 
Code: 
Unhandled exception: e
Date/Time: 2026-07-04, 17:36:14
Fault address: 7FFF9F171C0A (c:\windows\system32\kernelbase.dll)
libobs version: 32.1.2 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8737; 64-bit)
CPU: AMD Ryzen 7 5700G with Radeon Graphics        


Thread 6918: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000B4C27FF620 00007FFF9F171C0A 00007FFF9F259300 0000000000000000 0000000000000000 0000000000000008 kernelbase.dll!0x7fff9f171c0a
000000B4C27FF720 00007FFF195DBBE7 000000B4C27FF9A0 0000000000000000 00000232C7DF2940 0000000000000780 obs.dll!video_frame_init+0x467
000000B4C27FF840 00007FFF19596C75 00000232C7DF2940 0000000000000002 0000000000000780 0000000000000000 obs.dll!obs_source_frame_init+0x55
000000B4C27FF8D0 00007FFF1959478A 00000232FAB334D0 000000B4C27FFA70 00000232FAB33500 00000232FAB33500 obs.dll!obs_source_frame_create+0x5a
000000B4C27FF900 00007FFF1959F236 0000023200000002 000000B4C27FFA70 00000232FAB33500 0000000000000100 obs.dll!cache_video+0x226
000000B4C27FF970 00007FFF1959F72F 00000232C7E2C700 00007FFF0BA8C7F7 00000000002F7600 BA16CCC000000000 obs.dll!obs_source_output_video2+0x1bf
000000B4C27FFAB0 00007FFF0BA84886 00000232FAF320E0 000000B4C27FFBC0 00000232C7E2C700 D1E5209F00000002 win-dshow.dll!DShowInput::OnVideoData+0x276
000000B4C27FFAF0 00007FFF0BA8D66A 00000232FAF320E0 00000232C7E2C700 00000232C7E2C700 0000023200000000 win-dshow.dll!DShow::HDevice::SendToCallback+0x8a
000000B4C27FFB60 00007FFF0BA8D9C3 00000232F447B520 0000000000000000 00000232FAE68668 0000000000000000 win-dshow.dll!DShow::HDevice::Receive+0x2e3
000000B4C27FFC00 00007FFF0BA8BB5E 00000232C7E2C700 0000000000001000 00000232F447B6A0 00000232C7E2C700 win-dshow.dll!DShow::CapturePin::Receive+0x3e
000000B4C27FFC30 00007FFF2721AC9F 00000232C7E2A6C0 00000232C7E2C700 0000000000000000 00000232C7E2A6C0 ksproxy.ax!0x7fff2721ac9f
000000B4C27FFC60 00007FFF2721D5E0 0000000073BF741D 00000232C7F16600 00000232C7E2A6C0 0000000073BE2E98 ksproxy.ax!0x7fff2721d5e0
000000B4C27FFCD0 00007FFF272113E2 0000000000000000 0000000000000000 0000000000000080 000000B4C27FFD00 ksproxy.ax!0x7fff272113e2
000000B4C27FFDA0 00007FFF2721DB34 00000232FA60B640 00000232C7E29D40 00000232FA60B640 0000000000000002 ksproxy.ax!0x7fff2721db34
000000B4C27FFDD0 00007FFF27212724 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ksproxy.ax!0x7fff27212724
000000B4C27FFE30 00007FFFA140E957 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7fffa140e957
000000B4C27FFE60 00007FFFA1DEAD6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7fffa1dead6c
...
This and other reports (despite different modules in the log) shows that OBS are crashes because your system run out of RAM. The error itself "Unhandled exception: e" is ERROR_OUTOFMEMORY or "Not enough memory resources are available to complete this operation."

May be similar to:
W

Thread 'OBS Suddenly crashing during streams'

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...

Memory monitoring via Task Manager (memory consumption by process) and Resource Monitor (Resource Monitor > Memory tab > Hard Faults column) is the first step to find the cause of the problem. The Task Manager can show how greedy each of the processes you are running. And Resource Monitor may show to you how slow each request to the memory was (the Hard Faults is when it was too late, not malfunction).
 
RyeMoes said:
I'm not as familiar with the Elgato 4K capture card itself. Is that something you changed recently? Logs look like it is trying to capture at 120FPS and your stream is 60fps. Have you tried changing that to match at 60 and making sure drivers are up to date?
Click to expand...
How would I do that?
 
I think I have it all sorted out. I think using "Custom" for "Resolution/FPS Type" then setting those manually allow me to set up and manage how it goes, and then it means I have to resize the window each time I do that.
 
You must log in or register to reply here.
Back
Top