OBS won't open, appears in Task Mgr Details, then goes away

StrikeDaMic

New Member
Hi all

Pretty much what the title says is my issue: Without any previous sign of this, OBS Studio won't open. I give it admin rights, I tried holding Shift/Ctrl as it opens (I once had in my mind that this was a form of "safe mode"), I deleted all plugins marked problematic ... it won't open. It just appears in the details list of Task Mgr for a few seconds, then goes away. Rebooting PC does not work either.

Attached the log and crash reports. Anyone got an idea what's going on? Any support appreciated. Thanks!
 

Attachments

  • 2023-08-15 21-05-26.txt
    6.2 KB · Views: 5
  • Crash 2023-08-15 20-48-35.txt
    56.6 KB · Views: 5

StrikeDaMic

New Member
UPDATE: After checking for corrupted files (nothing), for a new version (nothing) and updating the Nvidia GPU driver (since I noticed that sometimes for a moment, OBS-nvenc-test also opens in the task mgr details list before disappearing again), I restarted the PC, tried to open OBS, and it started. But if I close it, it won't start again. I restarted the PC, it started up. Restarted PC, it didn't start up until I tried opening it again and again and again, random amount until it suddenly started. This is very weird behavior...
 

StrikeDaMic

New Member
the obs-midi-mg plugin is likely causing your crash.
Interestingly enough, I got OBS to run and tried to open OBS-midi-mg's settings. OBS crashed ...
Darn it. This is a very central plugin for me. I'll see if there's an update at all. Thanks!
 

StrikeDaMic

New Member
SOLVED

I researched and figured out that the plugin creator has recognized the issues (a while ago, apparently) in his V2.3.1 and suggests to downgrade to V2.3.0. Did so, OBS and the plugin manager now start every time. Couldn't set the title to [SOLVED] I'm afraid. Thanks again @Harold for your help! Could you let me, a noob, understand how you figured out that obs-midi-mg was the culprit from the log?
 

Harold

Active Member
it was the major module that wasn't a runtime component in the crashed thread in the crash report.
 
Top