OBS Watch Dog Violation

P

Padinn

Member
Hello,
Starting today I am getting watch dog violations causing my entire PC crash after streaming with OBS for 5-15 minutes. I have done a CPU, GPU, and RAM stress test with no errors. I have updated chipset and graphics card drivers. I was able to stream fine 3 days ago and as far as I know no significant changes were made to my PC since that time. I am on Windows 11 2025 H2. Has anyone else encountered something like this? I disabled some plugins and overlays on OBS without any success. My GPU and CPU temperatures appear fine.

AMD 5950
x570 steel legend ax
3060 TI
 

Attachments

  • 2025-12-06 21-39-27.txt
    34.5 KB · Views: 16
  • 2025-12-06 21-39-27.txt
    34.5 KB · Views: 9
qhobbes

qhobbes

Active Member
1. 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 as a troubleshooting step. Don't forget to restart.
2. Update OBS to 32.0.3 or newer.
3. Run updated OBS as Admin.
4. Disable multi-track video/enhanced broadcasting.

Post new log if still having issues.
 
R

rockbottom

Active Member
Watchdog Violations are generally caused by driver issues.

  • Double-check your drivers and remove unnecessary peripherals to fix the DPC Watchdog violation error.
  • The DPC Watchdog error can be caused by outdated or incorrectly installed drivers. Software conflicts are less common culprits.
  • Solve the DPC Watchdog violation error in Windows 10 and Windows 11 by checking IDE ATA/ATAPI controllers, removing external devices, updating SSD drivers, and scanning system files for errors. If all else fails, try a system restore.
 
R

rockbottom

Active Member
Installed Nvidia driver was released 3 days ago, 12/4. I personally have not vetted this driver. Maybe it's good but there's a conflict on the system?
 
R

rockbottom

Active Member
I found at least (1) bad driver in the log. Update your network driver. Go to your Mobo's support page

21:46:02.229: [rtmp stream: 'rtmp multitrack video'] Interface: Intel(R) I211 Gigabit Network Connection (ethernet, 1000↓/1000↑ mbps)
21:46:02.230: [rtmp stream: 'rtmp multitrack video'] Interface has non-zero error counters (125/0 errors, 250/0 discards)
 
R

rockbottom

Active Member
I'm not aware of this option:
21:46:01.785: user opts: lookaheadDepth=4

gist.github.com

ffmpeg -h encoder=h264_nvenc

ffmpeg -h encoder=h264_nvenc. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com gist.github.com

-lookahead_level <int> E..V....... Specifies the lookahead level. Higher level may improve quality at the expense of performance. (from -1 to 15) (default -1)
auto 15 E..V.......
0 0 E..V.......
1 1 E..V.......
2 2 E..V.......
3 3 E..V.......
 
P

Padinn

Member
I will try these options. A new wrinkle: this will happen without streaming at all. I just let OBS sit in my game scene idle and it starts fine, then after a few minutes starts getting choppy and cpu usage jumps a lot. It continues in this way until pc freezes. I was able to close obs and chopping continued, but I couldn't get task manager to reveal anything due to how sluggish pc was.
 
R

rockbottom

Active Member
Yep, it really could be any driver/device. OBS isn't causing it so you'll need to troubleshoot your rig. Hit the most recent stuff first & try to work backwards if possible.
 
P

Padinn

Member
Tried rolling that back, no fix. Here is an updated crash log that happened in safe mode for OBS. I am trying a new scene now.
 

Attachments

  • 2025-12-07 12-11-01.txt
    19.6 KB · Views: 7
P

Padinn

Member
rockbottom said:
Yep, it really could be any driver/device. OBS isn't causing it so you'll need to troubleshoot your rig. Hit the most recent stuff first & try to work backwards if possible.
Click to expand...
Been aiming to do that but the thing is this is a dedicated stream PC and I haven't really made changes to it since 12/3 when it was working. I just made a scene with nothing but capture card and camera, still froze. I am at a loss.
 
P

Padinn

Member
So what happens is after a seemingly random amount of time the CPU usage increases to basically 100% until I force a reboot. Disabling hardware GPU scheduling did not impact this.
 
R

rockbottom

Active Member
Are you still get the Watchdog Violations?

The log above is a session log. It ends here: There might be a bad browser source possible. Look at the crash log for more info.

2:11:10.354: DShow: Elgato GC4K60ProMK2 tonemapper enable=1
12:11:11.001: [obs-browser: 'Idle Alertbox'] Error: Uncaught SyntaxError: Identifier 'obsCSS' has already been declared (https://streamelements.com/overlay/...bHwo01sf4d9mAtQhXvq1oLSdQRwsCmybqoL7-hgyaJR:1)
12:11:11.266: [obs-browser: 'Chatbox'] Error: Uncaught (in promise) SyntaxError: "undefined" is not valid JSON (blob:https://streamelements.com/5e17485d-209f-4058-85fa-bf365dee8432:1)
12:11:30.314: User switched to scene 'Game Scene'
12:11:30.452: [obs-browser: 'Chatbox'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...bHwo01sf4d9mAtQhXvq1oLSdQRwsCmybqoL7-hgyaJR:4)
12:11:31.251: [obs-browser: 'Chatbox'] Error: Uncaught (in promise) SyntaxError: "undefined" is not valid JSON (blob:https://streamelements.com/e6410974-d205-451e-b18b-7eeaa79a9466:1)

Try a new Scene Collection, add just (1) Source & test. You'll have a clean slate with OBS, no Media Sources, no browser sources to muck things up, see if things improve.
 
R

rockbottom

Active Member
Save some resources, eliminate the upscale. Output 1080p not that

12:11:03.701: name=DELL U2412M
12:11:03.701: pos={0, 0}
12:11:03.701: size={1200, 1920}
12:11:03.701: attached=true
12:11:03.701: refresh=59
12:11:03.701: bits_per_color=8

12:11:04.524: video settings reset:
12:11:04.524: base resolution: 3840x2160
12:11:04.524: output resolution: 1536x864
 
R

rockbottom

Active Member
I think you're just running out of VRAM.

Upscaling, Hardware decoding is enabled on browser sources, every Media Source has it enabled. It all adds up quickly & the 3060 is thin.
 
P

Padinn

Member
rockbottom said:
Save some resources, eliminate the upscale. Output 1080p not that

12:11:03.701: name=DELL U2412M
12:11:03.701: pos={0, 0}
12:11:03.701: size={1200, 1920}
12:11:03.701: attached=true
12:11:03.701: refresh=59
12:11:03.701: bits_per_color=8

12:11:04.524: video settings reset:
12:11:04.524: base resolution: 3840x2160
12:11:04.524: output resolution: 1536x864
Click to expand...
This is a dedicated stream PC. I am not sure where you are seeing the upscaling. The capture card is set to 4k, which is why the base resolution is set that way.

This has worked fine for years with these settings - and as recently as 3 days ago. I do think you may be correct about corruption to the scene collection, I will test that next. I am also disabling the hardward encoding as a test.
 
Last edited:
R

rockbottom

Active Member
I would run everything @ 1080p at least until you get things sorted. Reduce the load, get it running correctly first, then add load.

The Scene you added on 12/3 may have been the breaking point. Nothing is free & there's only 8GB of VRAM.
 
P

Padinn

Member
rockbottom said:
I would run everything @ 1080p at least until you get things sorted. Reduce the load, get it running correctly first, then add load.

The Scene you added on 12/3 may have been the breaking point. Nothing is free & there's only 8GB of VRAM.
Click to expand...
I follow, to clarify, I did not add any scenes on 12/3. I made zero changes. It just stopped working properly.
 
You must log in or register to reply here.
Top