Question / Help OBS Studio crashing constantly when switching scene collections or exiting

Status
Not open for further replies.
S

Swizzle

New Member
This has been happening for a few months but I've just been dealing with it.

Whenever I switch to a different scene collection, as well as exiting OBS, the client crashes. I dunno what it is, but it seems to happen more and more after each OBS update.

Here is the log from my most recent crash:

https://gist.github.com/anonymous/e217ceed7bf1572626431549cedbfef6


If anyone has any idea what it could be please, for the love of all that is holy, let me know what I need to do to fix it.

Thanks!
 
S

Swizzle

New Member
Yes. In one instance. But still crashing for the past 6 months with different "causes." Elgato was installed a week ago. Did you look at the second crash report?

95% of the crashes occur with this error:

Fault address: 7FEF79FCCEB (c:\windows\system32\msvcp120.dll)

And yes, I already searched this issue on google and the only responses are if you are missing the msvcp120.dll, which I am not.
 
Last edited:
Harold

Harold

Active Member
Your two crashlogs show crashes in either elgato software or being caused by one of your browser sources.
 
Suslik V

Suslik V

Active Member
Anybody knows why crash log produces so high addresses: Fault address: 7FEF79FCCEB ? (~2^43) is this real address?
 
S

Shadowst

Member
I always have the same problem when closing the program.

(on 2 comps : processor - intel, video - radeon 280x and nvidia 1070 with fresh drivers Win7 64 bit (with the latest updates) + visual c++ 2005-2015 x64 and x86+net framework 4.6.0 or 4.6.2)

Fault address: 7FEF6C3CADB (c:\windows\system32\msvcp120.dll)

If there are no browser sources, then there are no errors. Errors often occur when browser sources are added.

Has anyone found a solution?
 
Last edited:
S

Shadowst

Member
The man wrote about the error Fault address: 7FEF79FCCEB (c:\windows\system32\msvcp120.dll).

I have the same error when closing the program.

How to solve it?
 
Simes

Simes

Member
The fact that the error is occurring in the same DLL is not an indication that it is the same error. Generally speaking, when you have no idea what's happening, and you're trying to get help from people who might know, it's best to provide them with the information they ask for.

Please post the full crashlog, as requested.
 
S

Shadowst

Member
Harold

Harold

Active Member
And it's NOT the same issue as the original poster in this thread. So you need to post your OWN thread and stop using someone else's thread for a different issue.
 
Status
Not open for further replies.
Top