Reinstalled OBS and now drops frames in my recordings.

wreith

New Member

Hey everyone. (tl;dr at the bottom)

I've been using OBS to record footage from my PC for over 5 years now. I'd got my settings perfect and had been smooth sailing. However, after disconnecting and reconnecting the cables to my PC, OBS started to rapidly degrade and I was faced with an encoding error when I stopped recording.

Long story short, I experimented with a bunch of stuff and ended up reinstalling OBS to it's newest version, while keeping my old settings intact. I even screenshotted my settings and replicated them as closely as I could. However, since the reinstall, recording any gameplay footage creates a .mp4 with inconsistently choppy footage (it does not effect the footage I record directly from browsers though). The preview is not choppy.

I've done a lot of forum searching and setting changes (changed video encoder from NVIDIA NVENC H.264 (deprecated) to NVIDIA NVENC H.264, changed Preset to P5 and below, turned Multipass from qp to sp, changed my scene to just have one Display Capture, "optimised" the OBS application in the NVIDIA App (changed simple and advanced encoder to NVIDIA NVENC H.264), scanned PC with Malwarebytes to see if there was any malware (there wasn't), and changed FPS from 60 to 30 (it was better, but not a lot)). My OBS already runs on admin mode. I haven't updated my drivers, but I'm always extremely hesitant to do that as I've found it always creates new problems elsewhere on my PC whenever it's trying to solve another problem, and I end up having to roll them back. They were also updated within the last few months, so they're not extremely outdated.

I know my PC can record this footage, as before I disconnected and reconnected my PC's cables, I recorded the exact footage that my PC now struggles to record with no problem.

I've managed to fine tune it to where it can record some stuff, but really struggles with other stuff.

Unsure if related (since this issue only effects recording gameplay), but my Game Capture and Window Capture are black screens too. I use Display Capture, so it doesn't affect me, but I'm unsure if it might indicate another problem that also effects how my recordings come out.

Further context: I'm recording Yakuza 0 footage with a freecam mod. Before moving my PC it recorded all of it fine. Afterwards it was choppy on both non-freecam gameplay and freecam gameplay. I've managed to get it to run fine on non-freecam gameplay so long as I don't look at the sky, which tanks the recording.

Anyone know what's up?

tl;dr - OBS has been good for recording for years until I unplugged and replugged my PC cables, then suddenly OBS can't encode Display Capture for games well anymore. I end up reinstalling OBS, but encoding is still bad for games on Display Capture. I try a bunch of solutions but they only make it a bit better. Manage to get it the best it can be but still produces choppy footage, so I came here to get help.
 
9900k & you're running 280HZ while using OBS? Good luck with that. Try 120 or 60HZ

Color Range should be Partial not Full

Sample Rate mis-matches, OBS is @ 44k, all else looked like 48k

Bugged Scenes, there should only be (1) Display, Game or Window capture per Scene to avoid interference.

I would update the Nvidia driver, current driver is old & Nvidia was pushing crap drivers back then.

Test

 
Game Mode can be enabled

I'm not sure about Malwarebytes, I have it on my system but never running when using OBS. I would run Defender, as I know it won't interfere in any way.
 
I get your hesitance to update the driver. 566.36 Studio driver is still running on my system (12900k/3090). It's vetted & as stable as it's gets. Rollback to it, it will perform better than what's in there now.
 
@rockbottom thanks for the suggestions! I will implement them now and see what comes out. Still v surprised my rig worked fine with these setting for half a decade and then suddenly didn't. Will update and see how it is.
 
@rockbottom It was the monitor refresh rate. I had no idea it pushed the system that much but logically it makes a lot of sense and I'm surprised I didn't realise sooner. I need to remember 9900k isn't top of the line anymore. Tried with 120hz and 60hz and 120 was choppy but 60 was as expected! Unsure why my OBS wasn't choppy for so many years, but it's now resolved. Thanks so much for the help!
 
@rockbottom apologies for coming back, but I've encountered the same error on a recording and would like some more help with it.


Choppy output for the recording started at 18:38:06.996, all other recording came out with no issues. All prior suggestions had been implemented by the time of recording, so unsure why it's done this.

NB: Still using a free-cam mod. I have no idea if this would affect whether the recording output is choppy or not, but it created no issues beforehand and the other two recordings you see in the log before 18:38:06.996 was free-cam footage that came out with no issues. No freecam footage went out of bounds.

Any thoughts?

Edit: further context - I used "Main Scene" as my scene to record from.
 
Your system appears to be running on your iGPU at least the monitors are connected to it.......

18:08:22.853: Initializing D3D11...
18:08:22.853: Available Video Adapters:
18:08:22.855: Adapter 0: Intel(R) UHD Graphics 630
18:08:22.855: Dedicated VRAM: 134217728 (0.1 GiB)
18:08:22.855: Shared VRAM: 34276433920 (31.9 GiB)
18:08:22.855: PCI ID: 8086:3e98
18:08:22.855: HAGS Status: Disabled (Default: No, Driver status: Unsupported)
18:08:22.855: Driver Version: 31.0.101.2135
18:08:22.856: output 0:
18:08:22.856: name=VG279QM
18:08:22.856: pos={0, 0}
18:08:22.856: size={1920, 1080}
18:08:22.856: attached=true
18:08:22.856: refresh=60
18:08:22.856: bits_per_color=8
18:08:22.856: space=RGB_FULL_G22_NONE_P709
18:08:22.856: primaries=[r=(0.646484, 0.340820), g=(0.306641, 0.639648), b=(0.150391, 0.047852), wp=(0.313477, 0.329102)]
18:08:22.856: relative_gamut_area=[709=1.105803, P3=0.815166, 2020=0.584827]
18:08:22.856: sdr_white_nits=80
18:08:22.856: nit_range=[min=0.000000, max=400.000000, max_full_frame=400.000000]
18:08:22.856: dpi=96 (100%)
18:08:22.856: id=\\?\DISPLAY#AUS278F#4&3623efdd&1&UID224795#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
18:08:22.856: alt_id=\\.\DISPLAY6
18:08:22.857: output 1:
18:08:22.857: name=BenQ GL2460
18:08:22.857: pos={-1920, 0}
18:08:22.857: size={1920, 1080}
18:08:22.857: attached=true
18:08:22.857: refresh=60
18:08:22.857: bits_per_color=8
18:08:22.857: space=RGB_FULL_G22_NONE_P709
18:08:22.857: primaries=[r=(0.641602, 0.333984), g=(0.333984, 0.624023), b=(0.152344, 0.049805), wp=(0.313477, 0.329102)]
18:08:22.857: relative_gamut_area=[709=1.023304, P3=0.754350, 2020=0.541196]
18:08:22.857: sdr_white_nits=80
18:08:22.857: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
18:08:22.857: dpi=96 (100%)
18:08:22.857: id=\\?\DISPLAY#BNQ78CE#4&3623efdd&1&UID198195#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
18:08:22.857: alt_id=\\.\DISPLAY5
18:08:22.857: Adapter 1: NVIDIA GeForce RTX 2070 SUPER
18:08:22.857: Dedicated VRAM: 8377073664 (7.8 GiB)
18:08:22.857: Shared VRAM: 34276433920 (31.9 GiB)
18:08:22.857: PCI ID: 10de:1e84
18:08:22.857: HAGS Status: Disabled (Default: No, Driver status: Supported)
18:08:22.857: Driver Version: 32.0.16.1062
18:08:22.857: Loading up D3D11 on adapter Intel(R) UHD Graphics 630 (0)
18:08:22.890: D3D11 loaded successfully, feature level used: b000
18:08:22.890: DXGI increase maximum frame latency success

Things go sideways here, GPU is throwing errors, encoding lag ensues

18:15:52.393: [obs-nvenc] init_session: nv.nvEncOpenEncodeSessionEx(&params, &enc->session) failed: 1 (NV_ENC_ERR_NO_ENCODE_DEVICE)
18:15:52.609: [obs-nvenc: 'advanced_video_recording'] settings:
18:15:52.609: codec: H264
18:15:52.609: rate_control: VBR
18:15:52.609: bitrate: 16000
18:15:52.609: max_bitrate: 24000
18:15:52.609: keyint: 120
18:15:52.609: preset: p5
18:15:52.609: tuning: hq
18:15:52.609: multipass: disabled
18:15:52.609: profile: high
18:15:52.609: width: 1920
18:15:52.609: height: 1080
18:15:52.609: b-frames: 2
18:15:52.609: b-ref-mode: 0
18:15:52.609: lookahead: true (8 frames)
18:15:52.609: aq: true
18:15:52.609:
18:15:52.686: ---------------------------------
18:15:52.687: [FFmpeg aac encoder: 'Game Audio (System & Games)'] bitrate: 320, channels: 2, channel_layout: stereo, track: 2
18:15:52.687:
18:15:52.687: ---------------------------------
18:15:52.687: [FFmpeg aac encoder: 'AT2020 Condenser Microphone'] bitrate: 320, channels: 2, channel_layout: stereo, track: 3
18:15:52.687:
18:15:52.695: ==== Recording Start ===============================================
18:15:52.695: [mp4 output: 'adv_file_output'] Writing Hybrid MP4/MOV file 'S:/tbc footage/Haunted House Level Footage/2026-06-24 18-15-52.mp4'...
18:16:05.360: Stopping recording due to hotkey
18:16:05.639: [mp4 muxer: 'adv_file_output'] Flushing final fragment...
18:16:05.640: [mp4 muxer: 'adv_file_output'] Number of fragments: 7
18:16:05.640: [mp4 muxer: 'adv_file_output'] Full moov size: 13 KiB
18:16:05.640: [mp4 muxer: 'adv_file_output'] Final mdat size: 24541 KiB
18:16:05.640: Output 'adv_file_output': stopping
18:16:05.640: Output 'adv_file_output': Total frames output: 762
18:16:05.640: Output 'adv_file_output': Total drawn frames: 777
18:16:05.640: [mp4 output: 'adv_file_output'] Waiting for file writer to finish...
18:16:05.641: [mp4 output: 'adv_file_output'] File output complete. Finalization took 2 ms.
18:16:05.641: ==== Recording Stop ================================================
18:16:05.783: warning: 2 frames left in the queue on closing
18:16:05.783: warning: 2 frames left in the queue on closing
18:17:50.708: Starting recording due to hotkey
18:17:50.733: [obs-nvenc] init_session: nv.nvEncOpenEncodeSessionEx(&params, &enc->session) failed: 1 (NV_ENC_ERR_NO_ENCODE_DEVICE)
18:17:50.861: [obs-nvenc: 'advanced_video_recording'] settings:
18:17:50.861: codec: H264
18:17:50.861: rate_control: VBR
18:17:50.861: bitrate: 16000
18:17:50.861: max_bitrate: 24000
18:17:50.861: keyint: 120
18:17:50.861: preset: p5
18:17:50.861: tuning: hq
18:17:50.861: multipass: disabled
18:17:50.861: profile: high
18:17:50.861: width: 1920
18:17:50.861: height: 1080
18:17:50.861: b-frames: 2
18:17:50.861: b-ref-mode: 0
18:17:50.861: lookahead: true (8 frames)
18:17:50.861: aq: true
18:17:50.861:
18:17:50.937: ---------------------------------
18:17:50.937: [FFmpeg aac encoder: 'Game Audio (System & Games)'] bitrate: 320, channels: 2, channel_layout: stereo, track: 2
18:17:50.937:
18:17:50.937: ---------------------------------
18:17:50.937: [FFmpeg aac encoder: 'AT2020 Condenser Microphone'] bitrate: 320, channels: 2, channel_layout: s
18:38:01.420: ==== Recording Stop ================================================
18:38:02.666: Video stopped, number of skipped frames due to encoding lag: 5959/24751 (24.1%)
18:38:02.813: warning: 2 frames left in the queue on closing
18:38:02.813: warning: 2 frames left in the queue on closing
18:38:06.746: Starting recording due to hotkey
18:38:06.769: [obs-nvenc] init_session: nv.nvEncOpenEncodeSessionEx(&params, &enc->session) failed: 1 (NV_ENC_ERR_NO_ENCODE_DEVICE)
18:38:06.899: [obs-nvenc: 'advanced_video_recording'] settings:
18:38:06.899: codec: H264
18:38:06.899: rate_control: VBR
18:38:06.899: bitrate: 16000
18:38:06.899: max_bitrate: 24000
18:38:06.899: keyint: 120
18:38:06.899: preset: p5
18:38:06.899: tuning: hq
18:38:06.899: multipass: disabled
18:38:06.899: profile: high
18:38:06.899: width: 1920
18:38:06.899: height: 1080
18:38:06.899: b-frames: 2
18:38:06.899: b-ref-mode: 0
18:38:06.899: lookahead: true (8 frames)
18:38:06.899: aq: true
18:38:06.899:
18:38:06.988: ---------------------------------
18:38:06.989: [FFmpeg aac encoder: 'Game Audio (System & Games)'] bitrate: 320, channels: 2, channel_layout: stereo, track: 2
18:38:06.989:
18:38:06.989: ---------------------------------
18:38:06.989: [FFmpeg aac encoder: 'AT2020 Condenser Microphone'] bitrate: 320, channels: 2, channel_layout: stereo, track: 3
18:38:06.989:
18:38:06.996: ==== Recording Start ===============================================
18:38:06.997: [mp4 output: 'adv_file_output'] Writing Hybrid MP4/MOV file 'S:/tbc footage/Haunted House Level Footage/2026-06-24 18-38-06.mp4'...
18:44:12.472: Stopping recording due to hotkey
18:44:15.409: [mp4 muxer: 'adv_file_output'] Flushing final fragment...
18:44:15.411: [mp4 muxer: 'adv_file_output'] Number of fragments: 183
18:44:15.415: [mp4 muxer: 'adv_file_output'] Full moov size: 342 KiB
18:44:15.415: [mp4 muxer: 'adv_file_output'] Final mdat size: 684455 KiB
18:44:15.415: Output 'adv_file_output': stopping
18:44:15.415: Output 'adv_file_output': Total frames output: 21930
18:44:15.415: Output 'adv_file_output': Total drawn frames: 22105
18:44:15.415: [mp4 output: 'adv_file_output'] Waiting for file writer to finish...
18:44:15.416: [mp4 output: 'adv_file_output'] File output complete. Finalization took 6 ms.
18:44:15.416: ==== Recording Stop ================================================
18:44:15.475: Video stopped, number of skipped frames due to encoding lag: 20012/21957 (91.1%)
 
@rockbottom I did have to change my graphic settings for OBS from High Performance (running RTX 2070) to Power Saving (GPUi) for my Display Capture to appear. Would that be the cause? Changing back to High Performance turns Display Capture to a black screen.
 
Your first log had the correct configuration. Regression

13:05:27.040: Initializing D3D11...
13:05:27.040: Available Video Adapters:
13:05:27.042: Adapter 0: NVIDIA GeForce RTX 2070 SUPER
13:05:27.042: Dedicated VRAM: 8377073664 (7.8 GiB)
13:05:27.042: Shared VRAM: 34276433920 (31.9 GiB)
13:05:27.042: PCI ID: 10de:1e84
13:05:27.042: HAGS Status: Disabled (Default: No, Driver status: Supported)
13:05:27.042: Driver Version: 32.0.15.7688
13:05:27.043: output 0:
13:05:27.043: name=VG279QM
13:05:27.043: pos={0, 0}
13:05:27.043: size={1920, 1080}
13:05:27.043: attached=true
13:05:27.043: refresh=280
13:05:27.043: bits_per_color=8
13:05:27.043: space=RGB_FULL_G22_NONE_P709
13:05:27.043: primaries=[r=(0.646484, 0.340820), g=(0.306641, 0.639648), b=(0.150391, 0.047852), wp=(0.313477, 0.329102)]
13:05:27.043: relative_gamut_area=[709=1.105803, P3=0.815166, 2020=0.584827]
13:05:27.043: sdr_white_nits=80
13:05:27.043: nit_range=[min=0.000000, max=400.000000, max_full_frame=400.000000]
13:05:27.043: dpi=96 (100%)
13:05:27.043: id=\\?\DISPLAY#AUS278F#4&3623efdd&1&UID224795#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
13:05:27.043: alt_id=\\.\DISPLAY6
13:05:27.044: output 1:
13:05:27.044: name=BenQ GL2460
13:05:27.044: pos={-1920, 0}
13:05:27.044: size={1920, 1080}
13:05:27.044: attached=true
13:05:27.044: refresh=60
13:05:27.044: bits_per_color=8
13:05:27.044: space=RGB_FULL_G22_NONE_P709
13:05:27.044: primaries=[r=(0.641602, 0.333984), g=(0.333984, 0.624023), b=(0.152344, 0.049805), wp=(0.313477, 0.329102)]
13:05:27.044: relative_gamut_area=[709=1.023304, P3=0.754350, 2020=0.541196]
13:05:27.044: sdr_white_nits=80
13:05:27.044: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
13:05:27.044: dpi=96 (100%)
13:05:27.044: id=\\?\DISPLAY#BNQ78CE#4&3623efdd&1&UID198195#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
13:05:27.044: alt_id=\\.\DISPLAY5
13:05:27.044: Adapter 1: Intel(R) UHD Graphics 630
13:05:27.044: Dedicated VRAM: 134217728 (0.1 GiB)
13:05:27.044: Shared VRAM: 34276433920 (31.9 GiB)
13:05:27.044: PCI ID: 8086:3e98
13:05:27.044: HAGS Status: Disabled (Default: No, Driver status: Unsupported)
13:05:27.044: Driver Version: 31.0.101.2135
13:05:27.045: Loading up D3D11 on adapter NVIDIA GeForce RTX 2070 SUPER (0)
13:05:27.209: D3D11 loaded successfully, feature level used: b000
13:05:27.209: DXGI increase maximum frame latency success
 
@rockbottom I see. Changing graphic settings in Windows settings and restarting PC didn't revert it back and OBS still loads Intel for some reason. Am I gonna have to dive into an .ini file and change how it loads or is there another method?
 
I was getting an encoding error before I updated my OBS. My guess is that it switched the primary GPU from 2070 to GPUi after I unplugged and replugged everything
 
PC was moved & now has issues, maybe something got knocked loose?

On my rig, I set the GPU order in BIOS. 3090 is Primary, iGPU is active but that's it. I only use the iGPU to encode outgoing streams.
 
Might have defaulted back to the iGPU as Primary. Maybe the battery on your mobo is toast & the settings weren't saved when the power was killed to the rig.
 
Potentially? If the mobo battery was toast I feel like it would reflect in other areas but its not out of the question (games ran fine with no lag, Premiere Pro has been running fine with no lag, non-game recording have come out fine). I'll dive into BIOS and see how the GPU order is configured. Will report back what I find.
 
Back
Top