Help with NV_ENC_ERR_INVALID_PARAM

violentmnky

New Member
Howdy!
I've used OBS for a good while now with no hiccups, but here recently every time I try to record I get hit with a pop up that states:
NVENC ERROR: Encode API Internal Error. (NV_ENC_ERR_INVALID_PARAM)
This does not produce a crash report so I have nothing to offer there.

Things I have tried: Restarting OBS, Restarting my PC, Running OBS with Admin perms, Uninstalling and Reinstalling OBS.
Log File: https://obsproject.com/logs/UspumXVw0j8cDram

Any assistance would be greatly appreciated.
 

rockbottom

Active Member
All of the 3000 series have 7th gen encoders & support B Frames. There might be something up with the driver/conflict or GPU itself. Did the trouble start when the driver was updated to the latest?

20:32:23.022: [obs-nvenc] Max B-frames setting (2) is more than encoder supports (0).
20:32:23.022: Setting B-frames to 0
20:32:23.022: [obs-nvenc] init_encoder_base: nvEncGetEncodePresetConfig failed: 8 (NV_ENC_ERR_INVALID_PARAM): EncodeAPI Internal Error.
20:32:23.022: [obs-nvenc] init_specific_encoder failed, trying again with compatibility options
20:32:23.022: [obs-nvenc] init_encoder_base: nvEncGetEncodePresetConfig failed: 8 (NV_ENC_ERR_INVALID_PARAM): EncodeAPI Internal Error.
20:32:23.153: [NVENC encoder] nvenc_create_internal failed, trying again without Psycho Visual Tuning
 

violentmnky

New Member
All of the 3000 series have 7th gen encoders & support B Frames. There might be something up with the driver/conflict or GPU itself. Did the trouble start when the driver was updated to the latest?

20:32:23.022: [obs-nvenc] Max B-frames setting (2) is more than encoder supports (0).
20:32:23.022: Setting B-frames to 0
20:32:23.022: [obs-nvenc] init_encoder_base: nvEncGetEncodePresetConfig failed: 8 (NV_ENC_ERR_INVALID_PARAM): EncodeAPI Internal Error.
20:32:23.022: [obs-nvenc] init_specific_encoder failed, trying again with compatibility options
20:32:23.022: [obs-nvenc] init_encoder_base: nvEncGetEncodePresetConfig failed: 8 (NV_ENC_ERR_INVALID_PARAM): EncodeAPI Internal Error.
20:32:23.153: [NVENC encoder] nvenc_create_internal failed, trying again without Psycho Visual Tuning
It started two or three updates ago. I was only half working on fixing this until very recently.
 

Harold

Active Member
For recording:
settings - output
output mode at the top: simple
recording quality: indistinguishable
Recording encoder: nvenc h264
recording format: matroska (mkv)
 

rockbottom

Active Member
Nothing changed, NVENC failure again. The Keyframe Interval was set to -1 & it should have been 250 in simple mode. I highly doubt it's OBS. Try a new Profile, if you get the same result, it may be time to DDU the graphics driver & get a fresh start.
 

violentmnky

New Member
Nothing changed, NVENC failure again. The Keyframe Interval was set to -1 & it should have been 250 in simple mode. I highly doubt it's OBS. Try a new Profile, if you get the same result, it may be time to DDU the graphics driver & get a fresh start.
I'm a novice here, pardon my ignorance. What do you mean by a "new profile"?
 

rockbottom

Active Member
Here you go. Since you're just starting out, the current Profile is most likely OK. But, we're going to test it anyway to rule out OBS as the source of the failure. When you create the new Profile, add just 1 Scene with 1 Source.

 

violentmnky

New Member
Here you go. Since you're just starting out, the current Profile is most likely OK. But, we're going to test it anyway to rule out OBS as the source of the failure. When you create the new Profile, add just 1 Scene with 1 Source.

Okay, can confirm the new profile didn't do the trick. I'll figure out the DDU and report back.
 

violentmnky

New Member
Here you go. Since you're just starting out, the current Profile is most likely OK. But, we're going to test it anyway to rule out OBS as the source of the failure. When you create the new Profile, add just 1 Scene with 1 Source.

Whelp. I did my research and DDU'd the drivers.
Still getting the exact same error from OBS when attempting to record.
Current log:
 

rockbottom

Active Member
That stinks, tried a different driver too. The log cut off as the Scenes were loading. It won't help with the encoder error but remove 1 of those captures from Scene 2. Create Scene 3. They can Interfere with each other. Give it another shot, see if it happens again.

On the bright side, the UHD 770 looks like it's ready to rock & roll if the 3060 needs to be serviced.
 
Last edited:

violentmnky

New Member
The stinks, tried a different driver too. The log cut off as the Scenes were loading. It won't help with the encoder error but remove 1 of those captures from Scene 2. Create Scene 3. They can Interfere with each other. Give it another shot, see if it happens again.

On the bright side, the UHD 770 looks like it's ready to rock & roll if the 3060 needs to be serviced.
This is off of a fresh and clean install of OBS with 1 Scene, 1 Source and the same graphics driver as post-DDU: https://obsproject.com/logs/NifQPt0xnSqZe85q


This is exactly the same, except using the most up to date graphics driver:
 

rockbottom

Active Member
The Keyframe Interval should not be set @ -1 in the Simple Mode. Are you attempting to record or stream? If you're recording, change the quality from "Same As Stream" to HQ Medium File Size.

23:10:13.323: [FFmpeg NVENC encoder: 'simple_video_stream'] settings:
23:10:13.323: encoder: NVIDIA NVENC H.264 (FFmpeg)
23:10:13.323: rate_control: CBR
23:10:13.323: bitrate: 2500
23:10:13.323: cqp: 0
23:10:13.323: keyint: -1
23:10:13.323: preset: p5
23:10:13.323: tuning: hq
23:10:13.323: multipass: qres
23:10:13.323: profile: high
23:10:13.323: width: 1280
23:10:13.323: height: 720
23:10:13.323: b-frames: 2
23:10:13.323: psycho-aq: 0
23:10:13.323: GPU: 0
23:10:13.323:
 
Top