RTX 5080 Codec Overload Error - Base 2160p to Out 1440p

CaBir

New Member
Hello everyone,

I purchased the Palit RTX 5080 Gamerock on July 14, 2025. My goal was to stream content on Twitch in high-quality resolution using the Nvidia codec.

I was using a Sapphire 7900xt Nitro+ Vapor-X just before. In my system only changed to the graphics card. I've been streaming on YouTube for about a year, and during that time, I was playing games and streaming at 2160p. I was using the AMD AV1 codec. However, as many of you know, the Nvenc codec provides better results for Twitch. After a while, one of my followers asked me to lower the resolution for faster chat, and I recently started streaming at 1440p.

During this time, I never experienced any codec overload errors. In fact, I didn't experience any such issues, even when streaming at 2160p. After replacing my graphics card, I was happy to get a more powerful one, but now, a few minutes after starting a stream, the camera freezes, and within a few minutes, I get a codec overload error. I've done a lot of checking.

The graphics card runs on PCie 5.0.
The graphics card driver is up to date and I've reinstalled it twice.
I've tried replacing the graphics card driver with the studio version.
I've enabled vertical sync in the game.
I've enabled DLSS in the game.
I've disabled the GPU of the CPU.

What I noticed is that when I start the game, the streaming stuttering starts when the graphics card usage reaches 99%. I don't get any errors in OBS when the graphics card usage is at 70-80-90-95%.

When I lower the in-game resolution from 2160p to 1440p, I don't experience any issues, and I don't get a codec overload error. (I'm not changing the graphics quality settings.)

My question is, while I don't get a codec overload error in OBS when playing the same games, at the same settings, and at the same resolution (2160p) with the 7900xt, or even when streaming at 2160p, why would I be experiencing these issues with the RTX 5080, a much more powerful graphics card?

Has anyone else experienced this issue with this graphics card? Or has anyone encountered a similar issue and been able to resolve it?

Since I can't figure out the exact cause of the issue, I first wanted to consult the OBS forum.

NOTE: While I was getting 70 fps at 2160p with the 7900xt, I'm now getting 120 fps with the same settings. I don't experience any freezing, stuttering, or lag in games. The problem only occurs when I'm streaming, and only in my streaming app, OBS. YouTube then gives an error, saying it can't receive enough data. In the meantime, I can continue playing my game without any problems, and even more comfortably than before.
 

Attachments

  • 2025-07-17 11-37-57.txt
    15.8 KB · Views: 24
  • Ekran görüntüsü 2025-07-17 102140.png
    Ekran görüntüsü 2025-07-17 102140.png
    19.8 KB · Views: 20
  • Ekran görüntüsü 2025-07-14 142959.png
    Ekran görüntüsü 2025-07-14 142959.png
    81.7 KB · Views: 19

PaiSand

Active Member
Please provide a log file where the issue happens. In this log file there's no active session in it.
 

Dasch

New Member
Hello

Ever since I bought a new computer with an RTX 5080 and 9800X3D, I've been experiencing the same issues.
I believe it's a driver issue. Since 572.83 drivers from March do not have the same anomaly. However, these drivers are outdated and VR performs poorly on them, so I prefer not to use them all the time.

What's more interesting, it doesn't matter if your GPU is maxed out, as most of the time it simply isn't. You can hover around 150-180W of power, but only if your GPU reach +95% at the current clock, the driver or the OS deprioritizes resources given to the OBS, causing the encoder overload.
I've tried making a post on Nvidia driver forum - no dice. It drives me mad and demotivates me from streaming PC games at all.
 

CaBir

New Member
Please provide a log file where the issue happens. In this log file there's no active session in it.
Hi, I don't understand, but the log files always seem to be the same. There are many different records, and they all have almost the same content. Am I looking at it wrong? I'll check and share again.
 

CaBir

New Member
Hello

Ever since I bought a new computer with an RTX 5080 and 9800X3D, I've been experiencing the same issues.
I believe it's a driver issue. Since 572.83 drivers from March do not have the same anomaly. However, these drivers are outdated and VR performs poorly on them, so I prefer not to use them all the time.

What's more interesting, it doesn't matter if your GPU is maxed out, as most of the time it simply isn't. You can hover around 150-180W of power, but only if your GPU reach +95% at the current clock, the driver or the OS deprioritizes resources given to the OBS, causing the encoder overload.
I've tried making a post on Nvidia driver forum - no dice. It drives me mad and demotivates me from streaming PC games at all.
Hello,
I agree.
When I play the game at 2160p resolution and the graphics card load exceeds 95%, the OBS app starts experiencing stuttering and codec overload errors. The game doesn't stutter or freeze at all.
When I lower the graphics settings in the game at 2160p resolution and the graphics card load drops below 95%, the OBS app error disappears and the problem is resolved.
It seems like there's an optimization issue here. Is the priority of the streaming cores changing? I don't understand.
My 4070ti Super had an 8th-generation encoder, and I wasn't experiencing any issues.
 

koala

Active Member
The log you posted just contains app start and exit. For analysis purposes it's essential you perform a recording resp. streaming session that exhibits your issue and post the log from that session.
 

CaBir

New Member
Hello everyone,

My tests revealed that the Nvidia Broadcast app is the source of the problem. If the app is installed and running in the background, and the camera app is in use, it causes a codec overload warning and a freeze in the OBS app.

I didn't encounter any issues when I closed the app, switched to the regular camera app, and used it on OBS.

I hope Nvidia resolves this issue with the Broadcast app immediately.

Thank you to everyone who responded and tried to help.
 

Dasch

New Member
Hello everyone,

My tests revealed that the Nvidia Broadcast app is the source of the problem. If the app is installed and running in the background, and the camera app is in use, it causes a codec overload warning and a freeze in the OBS app.

I didn't encounter any issues when I closed the app, switched to the regular camera app, and used it on OBS.

I hope Nvidia resolves this issue with the Broadcast app immediately.

Thank you to everyone who responded and tried to help.
That's not the cause of this issue. I don't even have Broadcast installed at the moment.
 

CaBir

New Member
Hello,

The problem has started again. I can't figure it out. Yesterday, when I disabled the Nvidia Broadcast app in the Dying Light 2 Ultra Ray Tracing settings, the codec overload error disappeared. Today, I turned on my computer and made sure the Broadcast app was disabled as yesterday, but when I tried to stream, I got the codec overload warning again.

Could you tell me where to get the OBS log files? Am I doing something wrong? I'm following the steps in OBS Help > Log Files > Upload Existing Log File, but when I click "Analyze," it says "no warnings." However, I get an error about codec overload, and the stream freezes.

Games I tested:

Dying Light 1 - 4K resolution - Ultra settings - 80-90% GPU usage - no game stuttering - no codec overload errors - no streaming issues
Dying Light 2 - 4K resolution - Ultra settings + DLSS quality - 99-100% GPU usage - no game stuttering - codec overload errors and streaming freezes
Forza Horizon 5 - 4K resolution - Ultra settings + DLSS quality - 99-100% GPU usage - no game stuttering - codec overload errors and streaming freezes
CS 2 - 4K resolution - game-recommended settings - 70-90% GPU usage - no game stuttering - no codec overload errors and streaming freezes

When GPU usage increases, the likelihood of me getting a codec overload error in OBS and experiencing streaming freezes increases.
 

koala

Active Member
Post the log here. The analyzer isn't fully aware of all existing issues. You find the logs in Help > Log files > Show Logfiles. Pick the one with the starting date+time matching your recording session.
 

CaBir

New Member
Something really funny is happening right now.

I disabled the "Hardware-accelerated GPU Scheduler" option, and now OBS is streaming with zero errors. It's meaningless, completely pointless, and incredibly strange.

My previous graphics card, the 7900xt, had this feature enabled, and I was live streaming to YouTube using the AV1 codec.

I think the streaming issue is resolved now, but now the video playback in the internet browser on my second screen has started stuttering and freezing.

We close one door, and another one opens right behind it...........

I selected the standard camera in the OBS app and checked the stream, and I had no issues.

I tried opening the Nvidia Broadcast camera in the OBS app. This time, there was no codec overload in the OBS app, and the game streamed clearly to YouTube, but there were obvious camera issues in both the OBS app and the live stream.

I had disabled the processor's graphics unit. I don't know if that will have any effect, but I'll enable it and try it out.

Dying Light 2 - 4K resolution - Ultra Ray Tracing - DLSS quality - No freezing, lag, or stuttering - No codec overload issues - Regular camera app - No camera stuttering issues - No issues with game and camera during live broadcasts

Dying Light 2 - 4K resolution - Ultra Ray Tracing - DLSS quality - No freezing, lag, or stuttering - No codec overload issues - Nvidia Broadcast camera app - No camera stuttering issues - No issues with game and camera during live broadcasts

Forza Horizon 5 - 4K resolution - 8x and Extreme+ resolution settings - DLSS off - No codec overload issues - Regular camera app - No camera stuttering issues - No issues with game and camera during live broadcasts

Losses per trial: "Frames dropped due to rendering delay" = 0.1% and "Frames dropped due to encoding delay" = 0%

WHO IS TO BLAME NOW?????????
 
Top