Having random crashes when swapping scene.

Correalian

New Member
Hi, yesterday during my stream I switched to BRB scene and when I came back I found OBS Studio has crashed. I've never encountered this before and will include the logs. Then tonight went to feed my dog, hit BRB and came back and found it had crashed again.

I've not changed anything for months with settings or such. Till the last two days had zero issues.

Any ideas on the cause and what I can try to rectify it?
 

Attachments

  • 2025-05-19 20-49-00.txt
    115.5 KB · Views: 15
  • 2025-05-20 19-30-47.txt
    93.8 KB · Views: 8

prgmitchell

Forum Moderator
1747785986820.png
 

Correalian

New Member
Sure, there is just one for the first stream. None for the second time it crashed.

I'm going to test with no plugins and see if it will do it again in the meantime.
 

Attachments

  • Crash 2025-05-20 07-00-42.txt
    150 KB · Views: 11

Suslik V

Active Member
Code:
Unhandled exception: 80000003
...

Thread 3A74: mp_media_thread (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000006BF8CFF258 00007FFE15691732 0000000000000780 0000019B10850000 0000019B108502E4 0000000000000000 obs.dll!os_breakpoint+0x2
0000006BF8CFF260 00007FFE15664F50 0000000000000018 0000019B4FBBF670 0000019B4831F5C0 0000019B2F0B2300 obs.dll!video_frame_init+0x4a0
0000006BF8CFF390 00007FFE1562082C 0000019B27BC8410 431BDE82D7B63400 0000000000000000 0000019B27BC7C40 obs.dll!obs_source_frame_init+0x5c
0000006BF8CFF450 00007FFE1561EDDA 0000019B27BC8410 0000000000000000 0000019B27BC83D0 431BDE82D7B634DB obs.dll!obs_source_frame_create+0x5a
0000006BF8CFF480 00007FFE15628CF1 0000006BF8CFF5B4 0000006BF8CFF550 0000000000000000 0000019B27BC8440 obs.dll!cache_video+0x261
0000006BF8CFF500 00007FFE15628E02 0000019B577F9300 0000000000000001 0000000000000000 0000019B15D197A8 obs.dll!obs_source_output_video_internal+0x82
0000006BF8CFF530 00007FFE15629006 0000000000000048 0000019B00000001 0000000000000000 0000000000000000 obs.dll!obs_source_output_video+0x136
0000006BF8CFF640 00007FFE0160569F 0000006BF8CFF700 0000000000000001 431BDE82D7B634DB 0000000000000000 obs-ffmpeg.dll!mp_media_next_video+0x4bf
0000006BF8CFF6B0 00007FFE01606208 0000019B15D197A8 0000019B17BEA500 0000000000000000 00007FFEC4621910 obs-ffmpeg.dll!mp_media_thread+0x248
0000006BF8CFF710 00007FFE0160631E 0000000000000003 0000019B280D3020 0000006BF8CFF7A0 0000019B17BEA500 obs-ffmpeg.dll!mp_media_thread_start+0xe
0000006BF8CFF740 00007FFE3E851461 0000019B280D3020 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x171
0000006BF8CFF7B0 00007FFEC1E21BB2 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffec1e21bb2
0000006BF8CFF7E0 00007FFEC3BA7374 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffec3ba7374
0000006BF8CFF810 00007FFEC461CC91 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffec461cc91
No resources left (RAM) for OBS to complete the task.
 

Correalian

New Member
Hi thanks for the info. I am just curious on why this is happening after not being a issue for months though. Is there a way to automate the ram to be cleared as I thought 64GB + the pagefile was enough for my needs.

Any recommendations?
 

Suslik V

Active Member
You may try to look at the Task Manager ( like in this thread: https://obsproject.com/forum/threads/obs-studio-using-too-much-vram.185274/ ) and then make conclusion if something can be simplified.

Normally, the call to "obs.dll!video_frame_init" (allocation of the memory for a new frame) shouldn't result in a error like "obs.dll!os_breakpoint" (breakpoint reached).

Next two strings preset in the both logs:
Code:
07:00:40.492: error:   Failed to create D3D11VA video decoder
07:00:40.492: error:   Failed setup for format d3d11: hwaccel initialisation returned error.
these errors are from Media Source or sometimes Video Capture Device source.

In the mentioned thread (see above) browser acceleration was mentioned as a main reason of inadequate VRAM consumption. So, maybe it was the first and the Media Source playback (configured to use hardware acceleration) failed because of this.
 
Last edited:

Correalian

New Member
Hi, thank you for the link and info, will check it all out tonight. The media source in question is just a short looping video (a few mb) to use on the break message scene using VLC.
 
Top