OBS crashing

T

techguypaul

New Member
So I've been having issues with OBS crashing after I've been streaming for a few hours. I have monitored my system load and everything checks out more than ok there; no issues with CPU, GPU or RAM utilization. I'm not dropping any frames while streaming. I'm also recording at the same time, but I've also had it crash when I'm just recording. The few plugins I have are all fine. I've attached the latest crash log that I can't make sense of, if someone can decipher what's causing the problem. it's happened with 2 different GPUs too (AMD 5700XT and now 9060XT).
 

Attachments

Code: 
Unhandled exception: e
Date/Time: 2026-02-12, 02:47:10
Fault address: 7FFC99E05369 (c:\windows\system32\kernelbase.dll)
libobs version: 32.0.4 (64-bit)
Windows version: 10.0 build 19045 (release: 22H2; revision: 6809; 64-bit)
CPU: AMD Ryzen 9 3900XT 12-Core Processor           


Thread 6530: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000005EA61FF1A0 00007FFC99E05369 0000000000000780 00000000002F7600 00007FFC999F3A81 000000010000000E kernelbase.dll!0x7ffc99e05369
0000005EA61FF1A8 0000000000000101 00000000002F7600 00007FFC999F3A81 000000010000000E 0000000000000000 <unknown>!0x101
0000005EA61FF1B0 0000000000000780 00007FFC999F3A81 000000010000000E 0000000000000000 00007FFC99E05369 <unknown>!0x780
0000005EA61FF1B8 00000000002F7600 000000010000000E 0000000000000000 00007FFC99E05369 0000000000000000 <unknown>!0x2f7600
0000005EA61FF1C0 00007FFC999F3A81 0000000000000000 00007FFC99E05369 0000000000000000 000001DB90DDA430 ucrtbase.dll!0x7ffc999f3a81
0000005EA61FF1C8 000000010000000E 00007FFC99E05369 0000000000000000 000001DB90DDA430 00007FFC999F3496 <unknown>!0x10000000e
I think this is out of RAM error. More likely VRAM ended.
 
Suslik V said:
Code: 
Unhandled exception: e
Date/Time: 2026-02-12, 02:47:10
Fault address: 7FFC99E05369 (c:\windows\system32\kernelbase.dll)
libobs version: 32.0.4 (64-bit)
Windows version: 10.0 build 19045 (release: 22H2; revision: 6809; 64-bit)
CPU: AMD Ryzen 9 3900XT 12-Core Processor          


Thread 6530: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000005EA61FF1A0 00007FFC99E05369 0000000000000780 00000000002F7600 00007FFC999F3A81 000000010000000E kernelbase.dll!0x7ffc99e05369
0000005EA61FF1A8 0000000000000101 00000000002F7600 00007FFC999F3A81 000000010000000E 0000000000000000 <unknown>!0x101
0000005EA61FF1B0 0000000000000780 00007FFC999F3A81 000000010000000E 0000000000000000 00007FFC99E05369 <unknown>!0x780
0000005EA61FF1B8 00000000002F7600 000000010000000E 0000000000000000 00007FFC99E05369 0000000000000000 <unknown>!0x2f7600
0000005EA61FF1C0 00007FFC999F3A81 0000000000000000 00007FFC99E05369 0000000000000000 000001DB90DDA430 ucrtbase.dll!0x7ffc999f3a81
0000005EA61FF1C8 000000010000000E 00007FFC99E05369 0000000000000000 000001DB90DDA430 00007FFC999F3496 <unknown>!0x10000000e
I think this is out of RAM error. More likely VRAM ended.
Click to expand...
Neither RAM or VRAM is close to being used up.
 
Then it's strange. GUI and D3D OBS libs unloaded (at least Qt and D3D names not visible in the threads). Unhandled exception, truncated to one letter "e", this previously was mentioned only in the crash logs where frame from directshow device was attempted to load into the memory and fails. The "win-wasapi: reconnect thread" is present (I don't remember if I even seen this thread before). There are few opened issues related to the memory leakages: https://github.com/obsproject/obs-studio/issues?q=is:issue state:open leak So, this all was on my mind.

Are there other crash reports with more clear sequences (without "<unknown>" sections)?
 
Suslik V said:
Then it's strange. GUI and D3D OBS libs unloaded (at least Qt and D3D names not visible in the threads). Unhandled exception, truncated to one letter "e", this previously was mentioned only in the crash logs where frame from directshow device was attempted to load into the memory and fails. The "win-wasapi: reconnect thread" is present (I don't remember if I even seen this thread before). There are few opened issues related to the memory leakages: https://github.com/obsproject/obs-studio/issues?q=is:issue state:open leak So, this all was on my mind.

Are there other crash reports with more clear sequences (without "<unknown>" sections)?
Click to expand...
Here's another recent crash report. Memory leak has been something I suspected, but unsure of what I can do about it. Sometimes (not every time) the crash is preceded by a couple of my Chrome tabs crashing like it's out of RAM (even though there's still 15+GB available out of 48GB).
 

Attachments

It is normal for Browser to crash before memory ends. OS manages memory allocation, so application with admin rights may get some advantages in memory allocation, but that is all. If OS decided that application already reached some limit - nothing will stop application from termination (crash).

As for the last crash report - it is same, and even truncated, no memory table listed and <200K (not enough RAM left?). If the Video memory is the case - it is worth to try to minimize hardware acceleration for the browser pages (sources) and see if crash happen less frequently or not .

For users who running a lot of Media sources - better to rebuild the scenes and reduce number of the sources (some also may use hardware acceleration that can be switched off in the Properties of the source; unlike the Browser source where corresponding option is global and is in the Settings > Advanced ).
 
Suslik V said:
It is normal for Browser to crash before memory ends. OS manages memory allocation, so application with admin rights may get some advantages in memory allocation, but that is all. If OS decided that application already reached some limit - nothing will stop application from termination (crash).

As for the last crash report - it is same, and even truncated, no memory table listed and <200K (not enough RAM left?). If the Video memory is the case - it is worth to try to minimize hardware acceleration for the browser pages (sources) and see if crash happen less frequently or not .

For users who running a lot of Media sources - better to rebuild the scenes and reduce number of the sources (some also may use hardware acceleration that can be switched off in the Properties of the source; unlike the Browser source where corresponding option is global and is in the Settings > Advanced ).
Click to expand...
But again, I'm not actually running out of RAM or any system resources. Not even close. I've literally watched it crash with 50% or under utilization of CPU, RAM and VRAM.
 
Please provide the log file from the same moment the crash happened.
The crash happens on the system level, not OBS itself. This could be for an out of RAM like was already suggested (not what Windows may show you), a faulty GPU driver, an issue on the operating system, or other issues.
A SSD or HDD almost full may be another cause. Maintaining system drive occupancy below 70% ensures optimal performance and prevents system slowdowns or failures.
 
You must log in or register to reply here.
Back
Top