RTX 3080 + OBS NVENC, smooth gameplay but recordings stutter

[Chiizukeeki]

I've been experiencing microstutters with my OBS recordings and I can't figure out the issue at all.

By microstutters, I mean normally frames would go in a sequential order like this:
1, 2, 3, 4, 5, 6, 7, 8, 9, 10

But at random parts, this is how some frames would present in my recordings:
1, 2, 2, 4, 5, 5, 7, 8, 8, 10

Example video: https://streamable.com/ty1x7k
The first part is the example, then in the second part I compared a smooth recording to the stuttered recording, both slowed down to 20% to show how the stuttered recording gets "stuck" on some frames.

I don't think this is related to my setup not being able to handle the task load because:

• I have a negligible amount of skipped/missed frames in OBS logs (<0.1%)
• I don't experience any stutters in-game as I'm playing
• this happens at random spots that don't seem to have to do with the graphical intensity of game scenes
• If I get stuttering in a particular part, I'm able rerecord that same part in the game and get a smooth recording this time
• I've tried even just recording a 60fps tester video I downloaded off YouTube, and I can see that frames are being missed

Specs:

• CPU: i7-10700k (no OC)
• GPU: RTX 3080 (no OC)
• RAM: 32 GB
• Windows 10 21H1 (after the update that fixed the multiple monitor/different refresh rates issue)
• Recording drive: 2TB NVME SSD
• Recording monitor: 1440p 144Hz (but usually running at 120 Hz)
• Side monitor: 1080p 60Hz
• Recording at 1440p 60fps

I've had this problem for nearly a year now and searched high and low, have already tried many usual suggested solutions:

• use admin mode on OBS
• update to latest drivers
• limit in-game fps to 60
• limit my recording monitor to 60 Hz or 120 Hz
• unplug my side monitor
• change recording drive
• change game install drive
• reinstall Windows
• disable OBS preview, minimize window
• turn on/off hardware accelerated graphics scheduling
• turn on/off adaptive sync

OBS log: https://obsproject.com/logs/ydEGHOxTOPmP5INk

Thanks for any help in advance.

 

[Kraezy]

This has been something that's been apparent since yonder years and much like yourself and others it has driven me nuts for such a long time with limited support from OBS devs themselves, even acknowledging the issue as previously it was pushed as a WDM Windows 10 fault etc between varying refresh rates of monitors ...

I've managed to resolve it on my NDI set up by using the following two programs in conjunction with some other things all running at the same time.

Spybot-Anti Beacon
Win10 Privacy
Add programs to Whitelists and Exploit protection
Turn off CFG (Control Flow Guard) to both OBS and your games/programs

Narrowed it down to being either a telemetry issue with Win10 or a WinDef scan of files or a combination of both. When WinDefender is enabled, monitor your Task Manager and you'll see MsMpEng.exe, every time you start a game and/or said program MsMpEng.exe will scan associated files.

Initially I went through the process of disabling Windefender all together, manually through GPEDIT.msc and registry, so MsMpEng.exe was never called on and it seemed to help , rather than every 15-40 secs of random stutter it delayed the stutter to around every 1m 15secs.

But as you said in the beginning it was random, you could watch the recording back and it would be smooth all the way through, re-watch the recording and it would stutter, that's why I took the idea of fully skeletonising Win10 as it doesn't seem right to me it was an OBS issue now.

By using Spybot-Anti Beacon (default settings) click Immunize
and using Win10 privacy (tick EVERYTHING) except for "allow usage of Cam / Microphone"
Though I suggest you read each info popup in Win10def as enabling some options will cause issues with various MS apps

I did this on BOTH gaming and Streaming PC's and it's been butter smooth ever since, both in Preview and in Recordings / streams. I'm on the latest version of Windows on both rigs (21H1)

I will eventually narrow it down to something specific but ultimately after spending 3 years trying to resolve the issue I'm not about to spend another inordinate amount of time tracking down which individual process / schedule service it is, I'll leave that down to OBS Devs.