OBS constant and random crashes

LeftY_CRO

New Member
Hello!

I just made an account after weeks of searching (for a possible) solution for "my" constant crashes.
I've been using the Streamelements plugin, so after contacting them (I thought that the recent OBS update broke the plugin) they didn't have a clue what was going on.

Now I'm using the NDI plugin so I can stream from my 2nd PC, but that's not it... If someone can help me, that would be nice; since I don't have any more ideas about what to do.
The crashes started after updating to the latest version of the OBS, and they are completely random:
- sometimes after pressing the "Stream" button
- sometimes after 2 minutes
- sometimes after 1 hour
- you get the point

What I've tried:
- uninstall plugins
- uninstall obs
- clear registry traces
- revert to one of the previous versions (vent back a full year lol)
- change the audio from 48 to 44.1
- create separate sources so the display capture and game capture arent in the same scene
- update drivers
- reset bios
- using the default bios settings
- update bios
- repair windows (10)
- Upgrade Windows from 10 to 11
- reinstall a fresh windows (11)
- obs analyzer suggestions
- streamelements support

The reports indicates "Unhandled exception: c0000005" on the threads with the following addresses:
- libx264-164.dll
- kernel32.dll
- ntdll.dll

thanks,
Tom
 

Attachments

  • Crash 2024-09-03 20-57-45.txt
    232.3 KB · Views: 37
  • 2024-09-04 23-13-34.txt
    42.7 KB · Views: 35

Suslik V

Active Member
Code:
Thread 6090: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000E953BF7E00 00007FF86D1154FB 0000028D00000000 0000000000000001 00000000000008A0 0000000000000010 libx264-164.dll!0x7ff86d1154fb
000000E953BF7FE0 00007FF86D11F452 0000028D095F1040 0000000000000071 0000000000000010 0000028DFFFFFFFF libx264-164.dll!0x7ff86d11f452
000000E953BFDDC0 00007FF86D155191 0000028D095F1040 0000000000000000 000000000000095F 0000028D0ADF1380 libx264-164.dll!0x7ff86d155191
000000E953BFFDA0 00007FF86D15602F 0000028D14E544C0 0000000000000000 0000028D0ADF1380 0000000000000000 libx264-164.dll!0x7ff86d15602f
000000E953BFFDD0 00007FF86D15E5E4 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff86d15e5e4
000000E953BFFE00 00007FF86D0D4470 0000028D68D31AD0 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff86d0d4470
000000E953BFFE30 00007FF86D1FF76A 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-164.dll!0x7ff86d1ff76a
000000E953BFFE60 00007FF912BB257D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ff912bb257d
000000E953BFFE90 00007FF914ECAF28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff914ecaf28
Your PC is no longer stable. Try stress test it with x264-based encoders.
 

LeftY_CRO

New Member
What does that mean? Possible CPU issue?
Tried OCCT and memtest and it was fine, looks like I'll need to find something else..
Thanks!
 

LeftY_CRO

New Member
I can see that the issue is the same as mine...
Regarding the FFmpeg, I tried the code that you wrote there but I am getting some error which looks like the FFmpeg is not installed on my system.

Btw, I've tried prime95 today and didn't find any failures. I'm gonna try with Cinebench, Aida, prime and occt again
 

Attachments

  • ffmpeg_error.png
    ffmpeg_error.png
    38.7 KB · Views: 27

Suslik V

Active Member
FFmpeg is command line util. It doesn't require installation. Its main .exe and .dlls (shared build) should be unpacked to some folder on user's PC. By specifying full path to the .exe file it can be used as any other command line util.

For example, the "ffmpeg-4.3.1-win64-shared.zip" (has a bit older libx264 core 161) can be found in old archives, like: https://archive.org/download/zeranoe/win64/shared/ - I think, even this older core may crash your PC in case there is HW instability. You may give it a try.

As far as I understand, OBS 30.2.3 uses libx264 (core 164) same as in FFmpeg 6.0
 

LeftY_CRO

New Member
So this means that the issue is 100% in HW?
That is really strange, because any other APP works just fine, only the OBS is the problem...
 

DeathNation

New Member
Hello guys !
I have the exact same problem for a few days now. My computer suddenly crashes during my lives. I have an Intel processor and I still haven't updated the bios. Do you think that could be the problem?
 

Attachments

  • 2024-11-21 20-49-01.txt
    44.3 KB · Views: 21
  • Crash 2024-11-21 20-46-32.txt
    60 bytes · Views: 20

prgmitchell

Forum Moderator
Hello guys !
I have the exact same problem for a few days now. My computer suddenly crashes during my lives. I have an Intel processor and I still haven't updated the bios. Do you think that could be the problem?
This is not the same problem, this is your GPU driver crashing.
 

Suslik V

Active Member
@DeathNation
Code:
22:57:07.952: Device Remove/Reset!  Rebuilding all assets...
this is the evidence that graphics driver was restarted (usually display blinks/off at this moment).


...Do you think I should go back to an older version of my driver?
In your case, likely, not. You better look at stable clocks, temperature and power.

...and I still haven't updated the bios
Usually, new firmware releases has brief description of what was fixed/added.
 

DeathNation

New Member
Thanks Suslik.
I'm still surprised. I do intensive video editing, I play video games everyday and I've never had a crash. The only crashes I have occur when I'm streaming. Everything suggests that this is a problem that comes from OBS.

I forgot to specify but when I crash, my screens no longer respond, I have black screens but I still hear sounds and even people talking on discord.

"In your case, likely, not. You better look at stable clocks, temperature and power."
Sorry to ask but how do I do this ?
 
Last edited:

prgmitchell

Forum Moderator
Thanks Suslik.
I'm still surprised. I do intensive video editing, I play video games everyday and I've never had a crash. The only crashes I have occur when I'm streaming. Everything suggests that this is a problem that comes from OBS.

I forgot to specify but when I crash, my screens no longer respond, I have black screens but I still hear sounds and even people talking on discord.

"In your case, likely, not. You better look at stable clocks, temperature and power."
Sorry to ask but how do I do this ?

This is a good starting place for you but if running DDU and reinstalling the latest GPU driver does not resolve this you'd want to seek more general tech support as this falls outside the scope of OBS:


OBS is unique in the fact that you are doing real-time encoding which is a difficult task for your GPU. Either way, this wouldn't be something for you to solve within OBS as it is an issue with your GPU.
 

DeathNation

New Member
This is a good starting place for you but if running DDU and reinstalling the latest GPU driver does not resolve this you'd want to seek more general tech support as this falls outside the scope of OBS:


OBS is unique in the fact that you are doing real-time encoding which is a difficult task for your GPU. Either way, this wouldn't be something for you to solve within OBS as it is an issue with your GPU.
Thanks for you reply :)
I just cleaned my drivers with DDU. I will get back to you if there is any progress. Thanks again for your help.
 

Suslik V

Active Member
@DeathNation
by "stable" clocks I mean - remove overclock if any applied. Temperature of the components usually controlled by utils that can log sensors (such utils usually has "hardware monitor" in the name). Power - only by replacement of the power supply (of course, in rare cases, in search for cracks in soldering or vias, you can knocking with handle of the screwdriver on power supply box).

Driver crash is not good. If application is about to do something restricted (for example, making attempt to write to the part of the memory that is not allowed for this application) then OS should close this application before something bad happens. Everything that relays on the driver (for GPU it is: display device, game, OBS, overlay util etc) likely will not function properly or will crash too. Only imagine that OBS tries to capture image and encode it with GPU encoders from the device that itself is in the "reset" state at the moment - of course there is chance that something will go wrong!

Ideally, simple instructions from OBS (or any application) shouldn't crash the GPU driver itself. OS rather will abort OBS process than will allow something unpredictable to happen with the driver, that itself used by many programs on your PC (from Browser to File Explorer). It is main task of the OS - to manage hardware. So, if program that controls hardware (driver) suddenly not functioning normal, then I assume either hardware error (power loss, high temperature, overclock) or problem in the driver itself. For the mentioned driver, video card and the game - there are not so many reports on this forum.
 

DeathNation

New Member
Thank you very much for this precise answer. I have news since this evening... I had two crashes while I was not on OBS. So I can already eliminate OBS. I made a DDU but nothing changed. I updated my motherboard and my bios. Since then I have not had a crash. I am still waiting before confirming that it was indeed that. Because that is precisely the problem with these crashes. Sometimes they happen, sometimes not. I strongly suspect a connection problem (probably related to my screens). Or the Nvidia application that I use to record my games. I continue to proceed by elimination. Sorry for my English, I use a translator.
 
Top