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

You must log in or register to reply here.
Back
Top