Random Crashes Any Help Appreciated

R

rockbottom

Active Member
All of it, Audio, Graphics, Video Encode Threads, Median & 99th percentile are what I look at.

The current results are excellent.
 
K

Kiwi_White

New Member
yea i dont quite know how to fix those SE java errors but its seems to be alot more stable now though so honestly mate your a life saver thank you so much man
 
R

rockbottom

Active Member
YW! I don't even have Java on my system let alone SE but check with SE support. Common theme....

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'none'".
 
R

rockbottom

Active Member
Nope

Something bugged in your scene collection. A media thread crashed so maybe one of the media sources. After start-up, your log is mostly websocket & SE errors.

Unhandled exception: 80000003
Date/Time: 2025-02-28, 19:16:03
Fault address: 7FFBF8B01152 (c:\program files (x86)\obs-studio\bin\64bit\obs.dll)
libobs version: 31.0.1 (64-bit)
Windows version: 10.0 build 26100 (release: 24H2; revision: 3194; 64-bit)
CPU: AMD Ryzen 9 7900X3D 12-Core Processor

Thread B48C: mp_media_thread (Crashed)

obs.dll!os_breakpoint+0x2
 
K

Kiwi_White

New Member
i had a look and couldnt see mcuh wrong apart from SE errors tbh but after doing some digging i found a setting in the advanced tab for obs under sources i had hardware acceleration turned on for browser sources could this of cause alot of this?
Screenshot 2025-02-28 211927.png
 
K

Kiwi_White

New Member
well i go live again today and we can see if this helps resolve the issue or not and if not ill remake my scene colletion bit by bit
 
R

rockbottom

Active Member
Your nerfed system was doing fine when the collection was small. Keep adding stuff & you see what happens. Your issue is the rig not OBS.
 
Suslik V

Suslik V

Active Member
Code: 
Thread B48C: mp_media_thread (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000012460FF7E8 00007FFBF8B01152 000001DBDD83ABA0 0000000000000000 0000000000000000 0000000000000107 obs.dll!os_breakpoint+0x2
00000012460FF7F0 00007FFBF8AD4CEA 000000007FFFFFFF 000001DC41F5A3C4 000001DC46C64AC0 0000000000000000 obs.dll!video_frame_init+0x4aa
00000012460FF920 00007FFBF8A906FC 000001DC459AB980 0000000000000000 0000000000000000 00000012460FFAE0 obs.dll!obs_source_frame_init+0x5c
00000012460FF9E0 00007FFBF8A8ECAA 000001DBCA256230 0000000000000000 000000000000000D 431BDE82D7B634DB obs.dll!obs_source_frame_create+0x5a
00000012460FFA10 00007FFBF8A98B81 000001DB0000000D 0000000000000000 000001DBCA2561F0 000001DBCA2561F1 obs.dll!cache_video+0x291
00000012460FFA90 00007FFBF8A98C92 00000000000000C8 000000000000000D 0000000000000000 000001DC4695D5A8 obs.dll!obs_source_output_video_internal+0x82
00000012460FFAC0 00007FFBF8A98E96 0000000000000048 0000000000000001 0000000000000000 0000000000000000 obs.dll!obs_source_output_video+0x136
00000012460FFBD0 00007FFBE845576D 00000012460FFD00 0000000000000001 431BDE82D7B634DB 0000000000000000 obs-ffmpeg.dll!mp_media_next_video+0x4cd
00000012460FFC40 00007FFBE84562D5 000001DC4695D5A8 0000000000000000 000001DC47053800 0000000000000000 obs-ffmpeg.dll!mp_media_thread+0x245
00000012460FFCA0 00007FFBE84563DE 0000000000000000 000001DC470538B0 00000012460FFD30 000001DBCCDC43B0 obs-ffmpeg.dll!mp_media_thread_start+0xe
00000012460FFCD0 00007FFC14251461 000001DC470538B0 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x171
00000012460FFD40 00007FFCDAE537B0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffcdae537b0
00000012460FFD70 00007FFCDC60E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffcdc60e8d7
00000012460FFDA0 00007FFCDD21BF2C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffcdd21bf2c
Means that OBS was unable to allocate memory for the video frame. You run out of the free RAM (or RAM available for OBS). You may try to monitor RAM usage in the Task Manager. Running OBS as admin and giving application higher priority in the Advanced setting may help a bit. But, as already said, better to simplify the scenes.

Here is OBS function that was called right before the breakpoint reached.
github.com

obs-studio/libobs/media-io/video-frame.c at 0bcf881ae9ca6cf5bd6d4f0e4395ee70100dae68 · obsproject/obs-studio

OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio
github.com github.com
 
K

Kiwi_White

New Member
Whats you mean my systems nerfed?? Tane a load of things out of each scene and have stream for 2 days each about 5-6 hours and no crashes so seams to have helped a load after i also changed that setting i am looking to get more ram soon too always thought 32gb was more than enough to be fair
 
R

rockbottom

Active Member
Not performing as expected or up to spec. Soft

Good

I would only touch the RAM if it's defective. I don't think adding more is going to solve anything.
 
K

Kiwi_White

New Member
Is there any way i can test as to why its not performing as it should like a ram test or cpu test or something? Its not the best of ram tbf i bought it when ddr5 just released and its only 5600mhz instead of the higher speeds that are available today
 
R

rockbottom

Active Member
RAM tests. Use whatever is easier for you. Memtest86 came pre-loaded on my mobo so that's what I used when I finished my build.

www.memtest86.com

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.
www.memtest86.com

www.techpowerup.com

TechPowerUp

MemTest64 is a free system memory stability and error detection software for all Intel and AMD processors. It runs on 64 bit Windows without installation.
www.techpowerup.com www.techpowerup.com
 
You must log in or register to reply here.
Top