OBS Crash unsure why

matchamalloww

New Member
Hi there, can anyone help me figure out why it crashed this time? The thread where it usually says it just says crashed. It was about an hour into stream with no issues, resolved the browser issue that was making it crash last time.
 

Attachments

  • Crash 2025-09-11 19-31-52.txt
    200 KB · Views: 10

Suslik V

Active Member
Code:
Unhandled exception: 80000003
...

Thread 6F18: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000094FC4FF058 00007FFE1DB25B52 0000000000000001 00007FFEE422F164 000001FC00000002 0000000000000000 obs.dll!os_breakpoint+0x2
00000094FC4FF060 00007FFE1DAF8CF7 0000000000000000 0000000000000000 000001FC3C8316A0 0000000000000000 obs.dll!video_frame_init+0x467
00000094FC4FF180 00007FFE1DAB4215 000001FC3C8316A0 0000000000000001 0000000000000780 0000000000000000 obs.dll!obs_source_frame_init+0x55
00000094FC4FF210 00007FFE1DAB24AA 000001FC33594270 00000094FC4FF3B0 000001FC335942A0 0000000000000000 obs.dll!obs_source_frame_create+0x5a
00000094FC4FF240 00007FFE1DABC7D6 000001FC00000001 00000094FC4FF3B0 000001FC335942A0 00007FFDFB351E9D obs.dll!cache_video+0x226
00000094FC4FF2B0 00007FFE1DABCCCF 000001FC30B627F0 0000000000038109 000001FC30B62A18 000001FC33926520 obs.dll!obs_source_output_video2+0x1bf
00000094FC4FF3F0 00007FFDF520458B 000001FC33782801 000001FC30B627F0 000001FC30FECAD8 000001FC05550000 win-dshow.dll!DShowInput::OnEncodedVideoData+0x11b
00000094FC4FF450 00007FFDF52046C4 000001FC30FEC9E0 00000094FC4FF560 000001FC33782880 D1E5209F00000002 win-dshow.dll!DShowInput::OnVideoData+0xc4
00000094FC4FF490 00007FFDF520D7AA 000001FC30FEC9E0 000001FC33782880 000001FC33782880 000001FC00000000 win-dshow.dll!DShow::HDevice::SendToCallback+0x8a
00000094FC4FF500 00007FFDF520DAA3 000001FC31030220 0000000000000000 000001FC31128EA8 0000000000000000 win-dshow.dll!DShow::HDevice::Receive+0x283
00000094FC4FF5A0 00007FFDF520BC9E 000001FC33782880 0000000000001000 000001FC310303A0 000001FC33782880 win-dshow.dll!DShow::CapturePin::Receive+0x3e
00000094FC4FF5D0 00007FFEC63E3B1F 000001FC5DFF5B80 000001FC33782880 0000000000000000 000001FC5DFF5B80 ksproxy.ax!0x7ffec63e3b1f
00000094FC4FF600 00007FFEC63E6460 00000006BCAD91D8 000001FC5717D180 000001FC5DFF5B80 00000006BCAC4C53 ksproxy.ax!0x7ffec63e6460
00000094FC4FF670 00007FFEC63E13E2 0000000000000000 0000000000000000 0000000000000080 00000094FC4FF6A0 ksproxy.ax!0x7ffec63e13e2
00000094FC4FF740 00007FFEC63EDED4 000001FC09450320 000001FC5DFF5460 000001FC09450320 0000000000000002 ksproxy.ax!0x7ffec63eded4
00000094FC4FF770 00007FFEC63E2724 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ksproxy.ax!0x7ffec63e2724
00000094FC4FF7D0 00007FFEE251E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffee251e8d7
00000094FC4FF800 00007FFEE425C34C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffee425c34c
This time no memory left, for sure. OBS was unable to initialize new frame for the Video Capture Device source. So, breakpoint reached. Did you monitored RAM and VRAM consumption during the event through the Task Manager? Try it next time. Hardware accelerated Media Sources are greedy (in case you have a lot of them VRAM will run out in a matter of minutes). A faulty driver for the capture device may cause memory leak (look for driver updates). Simplify scenes whenever possible.
 
Top