Robtiel is correct. When you run an application as admin it gives it priority when resources are being allocated. If this alone does not work you can try and use a program like Process Explorer to increase the priority of OBS.
This is not strictly accurate. Running as Admin allows OBS to implement a GPU-priority workaround developed in conjunction with Microsoft to ensure that OBS gets first access to GPU time to handle its housekeeping tasks before other applications can use it all. This is NOT an effect of simply running any process as Admin.
The kind of stutter this can fix is when 'frames skipped due to rendering lag' shows up in the logs. It is not present in this case, and while still a good idea to do, does not really apply here.
20:19:05.414: [jim-nvenc: 'recording_h264'] settings:
20:19:05.414: rate_control: CBR
20:19:05.414: bitrate: 16000
Do not record locally using CBR. CBR is required for use while livestreaming due to the infrastructure needs involved, but is a TERRIBLE option in any other case (like recording locally). Use CQP or CRF, which are quality-target based encoding methods that use as little or as much bitrate as is needed to maintain a given image quality level, which you can do while recording to a local disk instead of having to deal with the livestreaming network bandwidth bottleneck.
20:19:05.414: lookahead: true
20:19:05.414: psycho_aq: true
THIS is very likely the actual culprit. DISABLE both Lookahead and Psychovisual Tuning. They use CUDA cores, and from my experience just cause problems in many cases when using NVENC, most commonly causing 'frames skipped due to encoding lag'. Which IS present in the logfile, though in very small numbers.
20:19:05.445: [ffmpeg muxer: 'adv_file_output'] Writing file 'C:/Users/User/Videos/2021-01-10 20-19-05.mp4'
NEVER RECORD DIRECTLY TO MP4 FOR ANY REASON.
It is NOT a recording-safe format, so if ANYTHING goes wrong during the recording or finalization, it will become irrecoverably corrupted. Only thing you can do is delete it, there is NO working option to recover or reconstruct a failed MP4. As an added bonus, most video editors have major problems with the native-mp4 recordings that OBS produces, but work fine if you record to MKV and then use the 'Remux Recordings' option under the File menu to remux them to MP4s.
There's a reason it pops up an orange warning message when selected, which everyone ignores.
