Rendering/Encoding Bug "Error Retrieving frame..."

[Blade283694466fq1]

Videos failed to render in media encoder (same thing happens when trying in premiere). According to my logs, this first started happening in February. This time, it happened on 3 different renders, using two seperate video files. I swear I reported this bug before. Of course it's not fixed. Here is exactly what media encoder says.

" - Preset Used:
- Video: 3840x2160 (1.0), 29.97 fps, Progressive, Rec. 709, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:25:02:17
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 35.00 Mbps
- Encoding Time: 00:10:13
10/19/2025 03:12:36 PM : Encoding Failed
------------------------------------------------------------
Error retrieving frame 82549 at time 06;50;29;12 from the file: E:\Temp\Tyler Smith\RAW\MVI_9710.MP4, substituting frame 82548" 

The workaround for this was just chop about 20 frames off and render in premiere, not encoder. I'm going to attempt my workaround this time. Please fix this bug, it has gone on far too long.

CPU: AMD Ryzen 7 7700X

GPU: 4060ti 16gb

RAM: TForce Delta DDR5 64GB

Source video: CLOG3 .mp4

Premiere 25.5

[IanB_360]

Hi @Blade283694466fq1 
Can you share the project and media that has been giving you this issue? You can file share your .prproj file and media if you would like by direct messaging me. 
here to help 
Ian

[DigitalxxKnife]

Any update on this? 

I am having this SAME issue and I have to keep rolling back to old versions of premiere to get certain projects to load and to work at all, I also cant export without error codes using both Hardward AND Software encoding options. 

[Blade283694466fq1]

Sorry I cannot share this media, it's a client's. I don't have any wild settings. 4k, 1 Pass VBR 35mbps. I rendered other parts from the same file but for some reason Premiere arbitrarily picks parts of my big files and gets stuck on them. I got it to work  forcing it through Premiere. I decided to give it a shot since Encoder was giving me the wrong frame and timecode information. Premiere had the same error, but basically skipped past the issue by replacing the ~20 frames. It also gave the correct timecode information allowing me to to adjust it if I had to. No one is going to freakout about half a second in an hour long video, but it does seem very unprofessional. So on that point, this is not an issue unique to me, Adobe needs to, if not fix, at least address this issue. It could possibly be something on Nvdidia's end and they need to help,. they are notorious for making developer's go around their issues. In short, this sucks. 

[Blade283694466fq1]

Oh man, the software encoding recomendation online as a solution to this issue is obnoxious. Imagine trying it and finding out 4 hours later it didn't work. All I really did to get it to go through was encode it through Premiere, not Encoder. Why it works I don't know, but Premiere did what encoder started to do but bailed on. It replaced the problem frame with the previous frame it could use. So about 20 frames. Hope this helps. Been almost a year since I encountered this issue so hopefully something gets done.