OBS crashes with Hardware Acceleration enabled on fresh Windows

L

Legasi

New Member
Hi everyone,

I am experiencing persistent OBS crashes caused by the built-in browser source on a clean Windows installation.

System Specs

  • CPU: AMD Ryzen 9 9950X3D
  • Motherboard: ASUS ROG Crosshair X870E Dark Hero with BIOS 1002
  • RAM: G.Skill 96GB 2x48GB F5-6800J3446F48GX2-TZ5RK running at stock JEDEC
  • GPU: ASUS ROG Strix GeForce RTX 4090 OC Edition 24GB GDDR6X
  • OS: Windows 11 Pro 25H2 build 26200.9168
  • GPU Driver: Nvidia 610.88 dated 28.07.2026
  • System Status: Completely stock, zero overclocking, all drivers updated
Scenario and Crash Details

  • Fresh Windows installation with only essential drivers, OBS Studio, and Hunt: Showdown 1896 installed.
  • Scene collection was built completely from scratch.
  • Crashes occur consistently after playing Hunt: Showdown 1896 for about 30 minutes on Ultra settings at 4K resolution with uncapped framerate, holding around 80 to 120 FPS.
  • The crash log explicitly points to an error in the built-in OBS browser component.
  • Turning off Browser Hardware Acceleration completely prevents the crashes, but I would prefer to keep it enabled on an RTX 4090.
Troubleshooting Already Attempted

  • Running OBS Studio as Administrator did not help; crashes still occur around the 30-minute mark.
  • Toggling Twitch Enhanced Broadcast makes no difference. The crash happens both with Enhanced Broadcast active streaming at 2K60 in HEVC, and with it disabled streaming at 1080p60 H.264 at 8000 kbps.
Questions for the Community

  1. Could this behavior indicate a physical hardware issue with the GPU, and what is the best method to test or rule this out?
  2. Is Hunt: Showdown 1896 consuming 100% of GPU resources at 4K Ultra, leaving no overhead for the Chromium Embedded Framework browser process and forcing it to crash?
  3. Could this be related to HAGS, a specific bug in Nvidia driver 610.88, or a compatibility issue with Windows 11 25H2 build 26200.9168?
I have attached both the OBS log file and the crash log to this post.

Thank you for your help!
 

Attachments

Code: 
Unhandled exception: 80000003
Date/Time: 2026-08-24, 17:48:26
Fault address: 7FFCCBF1FB20 (c:\program files (x86)\steam\steamapps\common\obs studio\obs-plugins\64bit\libcef.dll)
libobs version: 32.2.2 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 9168; 64-bit)
CPU: AMD Ryzen 9 9950X3D2 16-Core Processor         


Thread 4ED8: CrBrowserMain (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000BB84DFDB80 00007FFCCBF1FB20 00000C880070F7A0 000000BB84DFE130 000000BB84DFE130 000000BB84DFE080 libcef.dll!0x7ffccbf1fb20
000000BB84DFE000 00007FFCCBF1F785 000000BB84DFE130 00000C8800CD9490 1FFFFFFFFFFFFFFF 0000000000000000 libcef.dll!0x7ffccbf1f785
000000BB84DFE0E0 00007FFCCBF1FB39 000000BB84DFE2C8 0000000000000030 0000000000000000 0000000000000030 libcef.dll!0x7ffccbf1fb39
000000BB84DFE110 00007FFCCA58999E 000000BB84DFE6E0 00000C88000168C0 0000000000000001 00000C8800CD1560 libcef.dll!0x7ffcca58999e
000000BB84DFE270 00007FFCCA5864B4 00000C8800F4A540 000000BB84DFE6E0 00000000C0000005 00000C88008F6370 libcef.dll!0x7ffcca5864b4
000000BB84DFE2A0 00007FFCCA5849CB 000000BB84DFE4C0 000000BB84DFE3A8 00000C8800F4A540 00000C8800F4A540 libcef.dll!0x7ffcca5849cb
000000BB84DFE2E0 00007FFCCA591FD6 00000000000036C8 00000C8800521498 00000000000036C8 00000C8800521490 libcef.dll!0x7ffcca591fd6
000000BB84DFE450 00007FFCCA5935E0 000000BB84DFE6E0 0000301C00261350 00000C880009B738 00007FFCC8720176 libcef.dll!0x7ffcca5935e0
000000BB84DFE5D0 00007FFCCA3AE2C4 000000BB84DFE601 00007FFCC86AE3CD 0000000000000000 00000C8800905DD0 libcef.dll!0x7ffcca3ae2c4
000000BB84DFE6C0 00007FFCC74D8C1D 00007FFCD1C3B9AB 00000C8800905D18 00000C88000168C0 00000000E834A3EE libcef.dll!0x7ffcc74d8c1d
000000BB84DFE730 00007FFCC86BE5AB 1FFFFFFFFFFFFFFF 00000C8800905C00 00000C88000168C0 00007FFCC86B2C43 libcef.dll!0x7ffcc86be5ab
000000BB84DFE8C0 00007FFCC734DB5F 000000BB84DFECF0 00007FFCCBF97D20 00000C8800A3AC80 00007FFCC7FAB40B libcef.dll!0x7ffcc734db5f
000000BB84DFE950 00007FFCC734E828 0000000000000000 AAAAAAAA000174AD 000070E416B1C0BA 0000000000000000 libcef.dll!0x7ffcc734e828
000000BB84DFEA30 00007FFCC86C06C0 AAAAAAAA000174AD 0000301C002AD400 00000000000174AD 00007FFCC8726E79 libcef.dll!0x7ffcc86c06c0
000000BB84DFEAA0 00007FFCCBF98F37 0000000000000000 00000000000000E9 000000BB84DFED28 00007FFCC86A07BA libcef.dll!0x7ffccbf98f37
000000BB84DFEC80 00007FFCC7F96B15 0000000000000000 0000000000000004 0000301C00221330 000000BB84DFED28 libcef.dll!0x7ffcc7f96b15
000000BB84DFECB0 00007FFCC86C4D2C 000070E416B1C64A 0000000000000001 0000301C00221330 000000BB84DFEF30 libcef.dll!0x7ffcc86c4d2c
000000BB84DFED40 00007FFCC869F03D 000000BB84DFEE48 00007FFCC8699250 0000301C00221270 000000BB84DFEFA4 libcef.dll!0x7ffcc869f03d
000000BB84DFEDE0 00007FFCC8725D07 0000301C00221258 00000C880009AF40 0000301C002211A0 00007FFCC74B0228 libcef.dll!0x7ffcc8725d07
000000BB84DFF020 00007FFCCBEE2E05 000000BB84DFF180 00007FFCD1C31B28 0000000000000008 0000000100000000 libcef.dll!0x7ffccbee2e05
000000BB84DFF0E0 00007FFCC72B11CE 000000BB84DFF240 00007FFCC8AE594F 0000000000000000 0000000000000000 libcef.dll!0x7ffcc72b11ce
000000BB84DFF150 00007FFCC74AE916 0000000000000008 000000BB84DFF2F0 0000000000000038 000000BB84DFF2F0 libcef.dll!0x7ffcc74ae916
000000BB84DFF1D0 00007FFCC72CA37F 0000024F9DC1AAC0 0000024F9DC1AA20 00000045442D6564 0000000000000000 libcef.dll!0x7ffcc72ca37f
000000BB84DFF2A0 00007FFCC66E06E6 0000024F3894EF70 0000024F9E7EC170 000000BB84DFF370 000000BB84DFF340 libcef.dll!0x7ffcc66e06e6
000000BB84DFF340 00007FFCF69EF5EC 0000024F00080001 0000024F9E8647A0 0000000000000000 0000000000000000 obs-browser.dll!BrowserManagerThread+0x113c
000000BB84DFF7F0 00007FFCF69F347B 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs-browser.dll!std::thread::_Invoke<std::tuple<void (__cdecl*)(void)>,0>+0xb
000000BB84DFF820 00007FFCF6A3EF57 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs-browser.dll!thread_start<unsigned int (__cdecl*)(void *),1>+0x4f
000000BB84DFF850 00007FFD7E3ACCB7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffd7e3accb7
000000BB84DFF880 00007FFD7FA4AD6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffd7fa4ad6c
...
This is surely crash in the Browser source. I think, it was out of RAM.

Legasi said:
Turning off Browser Hardware Acceleration completely prevents the crashes...
Could this behavior indicate a physical hardware issue with the GPU... ?
Click to expand...
By taking into account the crash report and mentioned behavior (>30 minutes), I think, It is rather software problem. I think that VRAM was full (or RAM was full). Likely leakage ("forgotten" objects in the RAM). The Windows Task Manager can be used to monitor VRAM (and RAM) consumption. In OBS, Hardware Acceleration usually pre-loads all into the Video RAM, thus there may be the problem (for example, tens of the Media sources with hardware acceleration enabled may fill out all available video memory in matter of seconds).

What is not clear (for me) - is your Browser source was empty during the tests? (there is no single trace in the log that the Browser was loaded with some web page, or maybe I missed something, so there is the question)

For the test purposes, you may try to make copy of the current Profile and Scene Collection in OBS, and then change the recording encoder to the "Same as stream". This way you'll be able to test it locally without starting actual streaming session. Start recording instead.

What is strange (for me) that is in the posted logs the Browser crashed and OBS was running few minutes after the moment of the crash. In the crash report I see "Date/Time: 2026-08-24, 17:48:26", while the casual log ends by the "18:01:37.342: [game-capture: 'Spielaufnahme'] shared texture capture successful" message or ~13 minutes later.

Such crash reports are not very informative (no symbols present for the browser libs to track the functions calls, and complex structure of the 3rd party lib "libcef.dll" itself, makes it hard to analyze). Here, on the forum, developers rarely responds to the threads with the "Unhandled exception: 80000003" errors, especially when the crash points to the 3rd party lib. So, you may cross the fingers and monitor resources usage.
 
You must log in or register to reply here.
Back
Top