OBSが起動時にクラッシュします（ブラウザソース関連？） / OBS crashes on startup (possibly browser source related)

S

suralion

New Member
こんにちは。
OBSが起動時にクラッシュする問題で困っています。

症状
OBSを起動すると、起動直後または少ししてからクラッシュします。
クラッシュログを見ると、libcef.dll や browser 関連のプロセスが関係しているように見えます。

試したこと
・Windowsのクリーンインストール
・GPUドライバの再インストール
・OBSの再インストール
・OBSのバージョンをいくつか変更して試した
・フォルダからブラウザ関連のファイルをすべて削除 → この状態だとクラッシュしない
・ブラウザ機能を戻すと再びクラッシュする
・--disable-gpu オプションを試したが改善せず
・ASUS関連ソフト（Armoury Crateなど）を削除

環境
・CPU：Ryzen 9 9950X3D
・GPU：RTX 4070 Ti
・OS：Windows（クリーンインストール済み）

補足
QtWebEngineProcess や obs-browser-page.exe がログに出ていました。
ブラウザ機能を削除すると完全に安定します。

質問
このような症状は既知の問題でしょうか？
また、試せる対処方法や確認すべき点があれば教えていただきたいです。

ログファイルを添付します。
よろしくお願いします。

Hello,

I am having an issue where OBS crashes on startup.

Issue
OBS crashes immediately after launch or shortly after.
From the crash logs, it seems related to libcef.dll or browser-related processes.

What I tried

  • Clean Windows installation
  • Reinstalled GPU drivers
  • Reinstalled OBS
  • Tested multiple OBS versions (latest and older ones)
  • Delete all browser-related files from the folder → This prevents crashes.
  • Restored browser functionality → crash returns
  • Tried --disable-gpu launch option → no improvement
  • Removed ASUS software (Armoury Crate, etc.)
Environment

  • CPU: Ryzen 9 9950X3D
  • GPU: RTX 4070 Ti
  • OS: Windows (clean install)
Additional info
QtWebEngineProcess and obs-browser-page.exe appear in logs.
OBS becomes completely stable when browser functionality is removed.

Question
Is this a known issue?
Are there any troubleshooting steps or fixes I can try?

I have attached the logs.
Thank you.
 

Attachments

Thank you for providing those logs. It could be a known issue, so please update to version 32.1.1 or newer by going to Help -> Check for updates in OBS or by downloading the latest installer from the downloads page and running it.

1. In Windows, we recommend that "Game Mode" be enabled. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
2. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. We recommend disabling it via these instructions. Be sure to restart after disabling it.
3. One of your audio devices has a sample rate that doesn't match the rest. This can result in audio drift over time or sound distortion. Check your audio devices in Windows settings (both Playback and Recording) and ensure the Default Format (under Advanced) is consistent. 48000 Hz is recommended.
OBS Sample Rate: 48000 Hz
Line (AG06/AG03): 44100 Hz
[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]: 48000 Hz
4. Browser hardware acceleration is currently disabled. Enabling acceleration is highly recommended due to the improvements to performance and significantly lower CPU usage for browser sources. This can be enabled in OBS Settings -> Advanced.
5. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (全画面ゲーム). You can use the same Game Capture for all your games. If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.
6. Display, Window and Game Capture Sources interfere with each other. Never put them in the same scene (全画面ゲーム, 全画面ゲームモンハン, 全画面ゲーム, FF14 and 全画面マイクラ用).
7. Make sure you plugins are compatible with the newest version of OBS and that you're using the newest version of those plugins.

Crashes with libcef are generally (probably only) going to be caused by a browser dock or source. If you create a new blank scene collection and it stops happening, then it's a source issue (IMO). If still having issues, provide new logs.
 
返信ありがとうございます。
上記のいくつかに対して対策を実施しました。
少なくとも1~4については実施済みです。
結果は変わらず起動時にクラッシュした旨のメッセージが表示されています。
ログを添付しますので再度ご確認いただければ幸いです。

* Translation
Thank you for your reply.
I have implemented some of the measures mentioned above.
At least measures 1-4 have been implemented.
The result remains unchanged; the message indicating a crash during startup is still displayed.
I have attached the log for your review.
 

Attachments

Create a new profile with no browser docks. Close and restart OBS. It it's still happening, then it's caused by your browser sources.
 
ブラウザ周辺のドッグを削除したプロファイルを作成し、OBSを再起動たところ起動時のクラッシュメッセージは出ませんでした。
その後Youtube用のチャットドッグを追加したらやはりクラッシュメッセージが表示されましたので、ご指摘の通りこちらが原因のようです。

このドッグを使わなければブラウザソースを使用しても問題なさそうではあるのですが、このドッグを使用することが可能になる方法はありますか？

* Translation
I created a profile with the browser-related dock removed and restarted OBS, and the crash message on startup did not appear.
However, when I added the chat dock for YouTube, the crash message reappeared, so it seems that this is indeed the cause, as you suggested.

While it seems that using browser sources is fine if I don't use this dock, is there any way to enable the use of this dock?
 

Attachments

上記のクラッシュが発生していない状態でブラウザソースを使用した状態で配信を開始したところOBSがクラッシュしました。
こちらもログを添付します。

* Translation
When I started streaming using the browser source without the above crash occurring, OBS crashed.
I've attached the log as well.
 

Attachments

Code: 
Unhandled exception: c0000005
Date/Time: 2026-04-18, 21:55:43
Fault address: 7FF60F16A743 (c:\program files\obs-studio\bin\64bit\obs64.exe)
libobs version: 32.1.1 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8246; 64-bit)
CPU: AMD Ryzen 9 9950X3D 16-Core Processor          


Thread 1188: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000306C36B3C0 00007FF60F16A743 00000144ADD98760 000000000000000F 00000144AD5CC820 000000306C36B5E9 obs64.exe!YouTubeAppDock::DispatchYTEvent+0x33
000000306C36B520 00007FF60F11470E FFFFFFFF9F01164F 00000144237D5260 000001434461F410 000001434461F410 obs64.exe!OBSBasic::StreamingStart+0x5fe
000000306C36B650 00007FF60F0BEB2D 0000000000000000 00000144237D5260 0000000000000000 0000000000000000 obs64.exe!OBSBasic::qt_static_metacall+0x27ad
000000306C36BA30 00007FFECAEB7439 000001434461F410 00000144237D5260 0000014374232B10 00007FFF00020002 qt6core.dll!0x7ffecaeb7439
000000306C36BA70 00007FFECAEB527F 000001434069DC30 000001434461F410 00000144237D5260 000001434461F410 qt6core.dll!0x7ffecaeb527f
000000306C36BB50 00007FFECB405CF2 000001434069DC30 00000143406C8080 000001434069DC30 000001434069DC30 qt6widgets.dll!0x7ffecb405cf2
000000306C36BC30 00007FFECB3C2EE7 0000000000000000 000000306C36BD60 0000000000000000 0000000000000000 qt6widgets.dll!0x7ffecb3c2ee7
000000306C36BC60 00007FFECB3C2056 000000306C36F400 000001434461F410 00000144237D5260 0000014400000000 qt6widgets.dll!0x7ffecb3c2056
000000306C36BE90 00007FFECAE6E91F 000001434065F180 0000000000000000 000001434065F180 FFFFFFFFFFFFFFFF qt6core.dll!0x7ffecae6e91f
000000306C36BF00 00007FFECAE70FD1 00000144237D5260 00000143406D6BD0 000001448154F1D0 00000143406D6B00 qt6core.dll!0x7ffecae70fd1
000000306C36BFC0 00007FFEC933421F 00000000000000A4 000000306C36C0F0 000001448154F1D0 00007FFECB015CB0 qt6gui.dll!0x7ffec933421f
000000306C36BFF0 00007FFECAFF1CE9 0000000000000000 0000000000000000 000001448154F1D0 00000143406D6BD0 qt6core.dll!0x7ffecaff1ce9
000000306C36F140 00007FFEC9334189 00000000000000A4 000001448154F1D0 000001434069DC30 0000000000000080 qt6gui.dll!0x7ffec9334189
000000306C36F170 00007FFECAE75234 000000306C36F210 000001434065F180 000000306C36F7B0 0000000000000000 qt6core.dll!0x7ffecae75234
000000306C36F1F0 00007FFECAE6CE62 00007FF60F3E124C 000000E4BD96E7B2 0000000000000002 00007FF60F3E124C qt6core.dll!0x7ffecae6ce62
000000306C36F250 00007FF60F17C1DA 000000306C36F6F0 0000000000000001 0000000000000001 0000000000000001 obs64.exe!run_program+0xc0a
000000306C36F6B0 00007FF60F17CF02 0000000000000002 0000000000000002 0000000000000001 00000143406588DA obs64.exe!main+0x722
000000306C36F890 00007FF60F1F1C30 0000000000000001 0000000000000000 0000000000000000 0000000000000000 obs64.exe!qtEntryPoint+0x30
000000306C36F920 00007FF60F1F1342 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x106
000000306C36F960 00007FFF287DE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7fff287de8d7
000000306C36F990 00007FFF2A2AC3FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7fff2a2ac3fc
This is crash in the call to the YouTube dock pane inside OBS.

And this:
Code: 
21:53:03.875: YT: InitYTUserUrl() User is not signed
...
leads to the known issue: https://github.com/obsproject/obs-studio/issues/10420
There was suggestion to make user to log-in from inside of this dock too:
https://github.com/obsproject/obs-studio/issues/10420#issuecomment-2016210978 said:
...
That's expected. The YouTube Live Control Room dock requires its own separate login. It does not share an authenticated session with OBS.
Click to expand...
 
Suslik V said:
Code: 
Unhandled exception: c0000005
Date/Time: 2026-04-18, 21:55:43
Fault address: 7FF60F16A743 (c:\program files\obs-studio\bin\64bit\obs64.exe)
libobs version: 32.1.1 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 8246; 64-bit)
CPU: AMD Ryzen 9 9950X3D 16-Core Processor       


Thread 1188: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000306C36B3C0 00007FF60F16A743 00000144ADD98760 000000000000000F 00000144AD5CC820 000000306C36B5E9 obs64.exe!YouTubeAppDock::DispatchYTEvent+0x33
000000306C36B520 00007FF60F11470E FFFFFFFF9F01164F 00000144237D5260 000001434461F410 000001434461F410 obs64.exe!OBSBasic::StreamingStart+0x5fe
000000306C36B650 00007FF60F0BEB2D 0000000000000000 00000144237D5260 0000000000000000 0000000000000000 obs64.exe!OBSBasic::qt_static_metacall+0x27ad
000000306C36BA30 00007FFECAEB7439 000001434461F410 00000144237D5260 0000014374232B10 00007FFF00020002 qt6core.dll!0x7ffecaeb7439
000000306C36BA70 00007FFECAEB527F 000001434069DC30 000001434461F410 00000144237D5260 000001434461F410 qt6core.dll!0x7ffecaeb527f
000000306C36BB50 00007FFECB405CF2 000001434069DC30 00000143406C8080 000001434069DC30 000001434069DC30 qt6widgets.dll!0x7ffecb405cf2
000000306C36BC30 00007FFECB3C2EE7 0000000000000000 000000306C36BD60 0000000000000000 0000000000000000 qt6widgets.dll!0x7ffecb3c2ee7
000000306C36BC60 00007FFECB3C2056 000000306C36F400 000001434461F410 00000144237D5260 0000014400000000 qt6widgets.dll!0x7ffecb3c2056
000000306C36BE90 00007FFECAE6E91F 000001434065F180 0000000000000000 000001434065F180 FFFFFFFFFFFFFFFF qt6core.dll!0x7ffecae6e91f
000000306C36BF00 00007FFECAE70FD1 00000144237D5260 00000143406D6BD0 000001448154F1D0 00000143406D6B00 qt6core.dll!0x7ffecae70fd1
000000306C36BFC0 00007FFEC933421F 00000000000000A4 000000306C36C0F0 000001448154F1D0 00007FFECB015CB0 qt6gui.dll!0x7ffec933421f
000000306C36BFF0 00007FFECAFF1CE9 0000000000000000 0000000000000000 000001448154F1D0 00000143406D6BD0 qt6core.dll!0x7ffecaff1ce9
000000306C36F140 00007FFEC9334189 00000000000000A4 000001448154F1D0 000001434069DC30 0000000000000080 qt6gui.dll!0x7ffec9334189
000000306C36F170 00007FFECAE75234 000000306C36F210 000001434065F180 000000306C36F7B0 0000000000000000 qt6core.dll!0x7ffecae75234
000000306C36F1F0 00007FFECAE6CE62 00007FF60F3E124C 000000E4BD96E7B2 0000000000000002 00007FF60F3E124C qt6core.dll!0x7ffecae6ce62
000000306C36F250 00007FF60F17C1DA 000000306C36F6F0 0000000000000001 0000000000000001 0000000000000001 obs64.exe!run_program+0xc0a
000000306C36F6B0 00007FF60F17CF02 0000000000000002 0000000000000002 0000000000000001 00000143406588DA obs64.exe!main+0x722
000000306C36F890 00007FF60F1F1C30 0000000000000001 0000000000000000 0000000000000000 0000000000000000 obs64.exe!qtEntryPoint+0x30
000000306C36F920 00007FF60F1F1342 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x106
000000306C36F960 00007FFF287DE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7fff287de8d7
000000306C36F990 00007FFF2A2AC3FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7fff2a2ac3fc
This is crash in the call to the YouTube dock pane inside OBS.

And this:
Code: 
21:53:03.875: YT: InitYTUserUrl() User is not signed
...
leads to the known issue: https://github.com/obsproject/obs-studio/issues/10420
There was suggestion to make user to log-in from inside of this dock too:
Click to expand...
コメントありがとうございます。
上記のイシューを確認したところ最終的には古いバージョンであれば問題は起きなかった、という結論になっているようでした。
イシューに記載されているVer30.1.0では自分も試せていなかったので、試してみましたが、結果は変わらず、YoutubeLiveControlPanelのドッグを追加したところクラッシュした旨のメッセージが表示されてしまいました。
なので上記の問題とは別なのかもしれません。

そしてこれはもっと関係ない事かもしれませんが、もしかしたら関係するかもしれないので書き加えておきます。
前提条件としてこれまで書いていなかったのですが、以前CPU：Intel Core i9-14900K、マザーボード：ASUS TUF GAMING H770-PRO WIFIを使用していて、そこからクリーンインストールをせず、ドライバーの更新のみで現在PCを使用しています。
(前提にも書いていますが現在は、CPU：Ryzen 9 9950X3D、マザーボード：ASRock X870 LiveMixer WiFi)
これらの構成や相性は悪いとか、前のCPUの時点でのゴミが残っているとかも考えられるのかと思いこちらの情報も載せておきます。
(関係なさそうであれば無視してください。)

* Translation
Thank you for your comment.

After reviewing the issue mentioned above, it seems the conclusion was that the problem did not occur with older versions.
I hadn't been able to test version 30.1.0 myself, as mentioned in the issue, so I tried it, but the result was the same; a message indicating a crash appeared when I added the YouTube Live Control Panel dock.
Therefore, this might be a separate issue from the one mentioned above.

And this might be even more unrelated, but I'll add it in case it's relevant.
I haven't mentioned this before, but previously I was using a CPU: Intel Core i9-14900K, Motherboard: ASUS TUF GAMING H770-PRO WIFI, and I haven't done a clean install since then, only updating the drivers.
(As mentioned in the prerequisites, currently I'm using a CPU: Ryzen 9 9950X3D, Motherboard: ASRock X870 LiveMixer WiFi)
I'm including this information because I thought it might be possible that these configurations or compatibility issues, or leftover junk from the previous CPU, are causing the problem.
(Please ignore this if it doesn't seem relevant.)
 
No. In the issue it was mentioned that the problem occurred after the upgrade from the v30.0.2 to newer version. "Upgrade" was done by mixing the old files and new. When user launched backup version of the OBS (almost whole setup: OBS "config" folder + OBS executable) then everything worked fine.

So, in case the log-in from inside the YouTube dock not possible or do nothing for you, then you can:
  1. Make backup copies of OBS Settings in form of the screenshots. This needed in case you don't_know/don't_remember your perfect settings in OBS. Take in mind, that many Settings are unique to the selected profile in OBS (the Encoder or Video settings for example, while "enabled/disabled" Studio Mode settings are common for all profiles).
  2. Make sure that OBS Profile folder is cleared only then start OBS (delete the "obs-studio\basic\profiles\" folder - it usually lies in the "%APPDATA%" folder);
  3. Make all your settings manually again for each profile (you have screenshots of all Settings tabs and all pages, you did in p1).
Instead of deleting all Profiles (see p2) you can try to make new Profile from main menu entry and experiment with it. Take in mind, that Sources related settings (global Audio sources etc) stored in the Scene Collections (the "obs-studio\basic\scenes\" folder). Browser Source related temporary files may be stored in the "obs-studio\plugin_config\obs-browser\" folder. And so on. There are many places where data may mess up.

Or you can try to run OBS portable mode in different folder and import your Scenes and Profiles later (make sure that you have exported your Scene Collections and Profiles and make backups time to time). For portable mode of OBS, please read after the words "if it was not clear": https://obsproject.com/forum/thread...-when-opening-app-settings.82157/#post-346499 or in the OBS Help: https://obsproject.com/kb/portable-mode
 
You must log in or register to reply here.
Back
Top