OBS crashes after starting an existing scheduled YouTube broadcast — YouTubeStreamCheckThread / Qt6Core.dll

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

32.2.1

OBS Studio Version (Other)

32.2.1 64-bit

OBS Studio Log URL

https://obsproject.com/logs/V3hUBjeVxctBGSC3

OBS Studio Crash Log URL

No response

Expected Behavior

OBS should remain open after connecting to the selected scheduled YouTube broadcast and should allow the broadcast to continue normally.

Current Behavior

OBS intermittently closes approximately 2–4 seconds after starting a previously scheduled YouTube broadcast through Manage Broadcast → Select Existing Broadcast.

The RTMPS connection succeeds and streaming begins, but OBS then exits without generating an OBS crash report. The final log line is:

QThread: Destroyed while thread 'YouTubeStreamCheckThread' is still running

Windows Reliability Monitor records:

Problem Event Name: BEX64
Fault Module Name: Qt6Core.dll
Exception Code: c0000409
Exception Data: 0000000000000007

The YouTube account remains connected after reopening OBS.

Steps to Reproduce

1. Connect a YouTube account in Settings → Stream.
2. Create and schedule an upcoming unlisted livestream in YouTube Studio.
3. In OBS, select Manage Broadcast.
4. Choose Select Existing Broadcast.
5. Select the scheduled broadcast.
6. Click Start Streaming.
7. OBS connects successfully, then closes approximately 2–4 seconds later.

Anything else we should know?

No OBS crash report is generated.

Windows Reliability Monitor recorded two identical failures:

Faulting Application: obs64.exe
Fault Module: Qt6Core.dll
Fault Module Version: 6.11.1.0
Exception Offset: 000000000001c898
Exception Code: c0000409
Exception Data: 0000000000000007
Bucket ID: c9051fb32575d6bb30aea4abdc896b63

The OBS logs consistently show that the encoder initializes, YouTube RTMPS connects successfully, and the stream starts before the fatal QThread message appears.

Additional logs:

https://obsproject.com/logs/TOCFzOfITxru3ezg
https://obsproject.com/logs/nE2Ka6HxdCnCyC04
https://obsproject.com/logs/ZqZzOGZqbgfyXQI4
https://obsproject.com/logs/UAtgBgWzoSBo2BmF

The issue also reproduced in Safe Mode, with a newly created clean profile, on OBS 32.1.2 and 32.2.1, after Windows and NVIDIA driver updates, and with all audio monitoring disabled.

Start at the Manage Broadcast → Select Existing Broadcast flow and compare the linked OBS logs, focusing on the final YouTubeStreamCheckThread message and the Qt6Core.dll failure. Reproduce with an existing scheduled YouTube broadcast in a clean profile; done means OBS remains open and streaming continues without the thread-destruction failure.