Crash without a crash report?

[StefenTower]

Since yesterday, I've experienced a repeatable problem with a plugin (already reported to its developer) where OBS crashes, but I am not presented with a crash report, nor is a crash report stored in the crashes folder.

This is happening with OBS 31.0.3 on Windows 11.

Is there an alternative way to show what happened to cause the crash, beyond discussing what steps I took as a user leading to the crash?

 

[prgmitchell]

Since yesterday, I've experienced a repeatable problem with a plugin (already reported to its developer) where OBS crashes, but I am not presented with a crash report, nor is a crash report stored in the crashes folder.

This is happening with OBS 31.0.3 on Windows 11.

Is there an alternative way to show what happened to cause the crash, beyond discussing what steps I took as a user leading to the crash?

Can you describe "crashes" in more detail? If it is closing without any error you should still see an entry as an event viewer log.

 

[StefenTower]

A crash here is OBS appears to freeze for a couple seconds, then vanishes off the screen as the app just quits, and there's not the usual presentation of a crash report.

 

[prgmitchell]

Is there anything in event viewer?

 

[StefenTower]

In this case, there is an Application Error in the Event Viewer, with this data (personal parts redacted):

+

System

- Provider [ Name] Application Error [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

EventID 1000

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x8000000000000000

- TimeCreated [ SystemTime] 2025-04-11T20:35:57.5581991Z

EventRecordID 22824

Correlation

- Execution [ ProcessID] 17060 [ ThreadID] 21788

Channel Application

Computer {redacted}

- Security [ UserID] {redacted}

-

EventData

AppName

obs64.exe

AppVersion

31.0.3.0

AppTimeStamp

a9a5d959

ModuleName

ntdll.dll

ModuleVersion

10.0.26100.3775

ModuleTimeStamp

5e4be250

ExceptionCode

c0000374

FaultingOffset

0000000000115f55

ProcessId

0x428c

ProcessCreationTime

0x1dbab214ac17e50

AppPath

C:\Program Files\obs-studio\bin\64bit\obs64.exe

ModulePath

C:\WINDOWS\SYSTEM32\ntdll.dll

IntegratorReportId

2e51fb10-eac6-4f5c-abd5-8733369bc885

PackageFullName

PackageRelativeAppId

 

[prgmitchell]

Sorry I am just re-reading your message and realizing you said "with a plugin". If you have no issues without the plugin then yeah, there is nothing to solve here on our side you would need to continue your conversation with the plugin developer.

 

[StefenTower]

Sorry I am just re-reading your message and realizing you said "with a plugin". If you have no issues without the plugin then yeah, there is nothing to solve here on our side you would need to continue your conversation with the plugin developer.

That conversation is happening. But a crash without an expected crash report seems problematic on its own, which is why I bothered to post about it.

 

[PaiSand]

If there's no crash report then OBS didn't crashed. A freeze isn't a crash and is commonly caused by a plugin or GPU driver or other third party app.
As described on the pinned post on this forum, a log file from the moment the issue was present is needed too.

Just make sure the plugins you use are updated and compatible with the OBS version you're using. On the GPU driver, keep them updated, unless an issue is present due to the newer nvidia drivers.

 

[prgmitchell]

No there is no log file needed, seems like it is already known which plugin is causing this issue so nothing left to troubleshoot on the OBS side of things.