Need Help Understanding How To Analyze A Crash Report

FinalisOmega

New Member
As the title says, I'm very new to being on a PC in general and sometimes struggle with the basics. I have NO idea what I'm looking at here. I see that it's crashing, and I see "what" is crashing. I just have no idea as to what it actually is. Any information as to what is, or if there is some guideline as to how I can figure these things out for myself in the future would be appreciated!
 

Attachments

  • Crash 2024-09-02 22-16-35.txt
    150 KB · Views: 14
  • Crash 2024-09-03 22-08-31.txt
    150 KB · Views: 18

Suslik V

Active Member
Code:
Thread 6CE8: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
0000004C95FCFBA0 00007FFB391352B7 0000000000000000 00007FFB2C1931D0 0000018DE57A3600 0000000000000000 w32-pthreads.dll!pthread_mutex_unlock+0x27
0000004C95FCFBE0 00007FFB2C20EEE7 0000000000000001 0000018DE57A3600 00007FFB2C1B0620 0000000000000001 obs.dll!audio_output_disconnect+0xd7
0000004C95FCFC10 00007FFB2C19041E 0000018DE57A3600 0000000000000001 00007FFB2C1B0620 0000000000000001 obs.dll!remove_connection+0x3e
0000004C95FCFC60 00007FFB2C1B2B62 0000000000000001 00007FFB2C1B0620 0000018E1005E220 0000004C95FCFD49 obs.dll!stop_audio_encoders+0x122
0000004C95FCFCA0 00007FFB2C1B2EC5 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.dll!end_data_capture_thread+0x85
0000004C95FCFCE0 00007FFB391314A7 0000018E360B3E60 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x1b7
0000004C95FCFDB0 00007FFB584D9333 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffb584d9333
0000004C95FCFDE0 00007FFB5966257D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffb5966257d
0000004C95FCFE10 00007FFB5AE0AF28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffb5ae0af28
the crash right after the "mutex_unlock" means either wrong logic (threads "intersections") or ... I actually don't know. There is no traces of 3-party plugins that may set theirs locks on the thread, so
I think this should be reported to:
 
Top