Skip to main content
Participant
May 24, 2025

P: Premiere Pro Freeze During Export Using Hardware Encoding (NVIDIA RTX 5070)

  • May 24, 2025
  • 302 replies
  • 36371 views

Hi Adobe Community,

I'm experiencing consistent freezes when exporting projects using CUDA acceleration with my new NVIDIA GeForce RTX 5070. This occurs in both Adobe Premiere Pro and Media Encoder.

 

Bug Report Details:

  • Product(s) Affected:

    • Adobe Premiere Pro (25.2)

  • Operating System: Windows 11 Pro

  • GPU: ASUS Prime GeForce RTX™ 5070 OC Edition 12GB GDDR7

  • GPU Driver: NVIDIA Studio Driver (Latest version available at the time of this report)

Issue Description:
Since upgrading to the ASUS RTX 5070, Adobe Premiere Pro freeze during export when CUDA acceleration is enabled. The application becomes completely unresponsive at a random percentage of export progress. No error message is displayed, and no crash logs seem to be generated. The application process cannot be terminated via Task Manager, forcing a full PC restart.


Project & Export Settings (Typical Scenario):

  • Source Footage: H.265

  • Sequence Resolution: 1080p

  • Sequence Duration: Approximately 40 minutes

  • Effects Used: Minimal (no heavy effects or LUTs)

  • Preview Rendering: Not used

  • Export Format: H.264

  • Renderer: Mercury Playback Engine GPU Acceleration (CUDA)

  • Encoding: Hardware Encoding

 

Steps to Reproduce:

  1. Open a project in Premiere Pro (e.g., a 40-minute timeline with H.265 footage, simple edits, no heavy effects).
  2. Go to File > Export > Media.
  3. Set Export Format to H.264.
  4. Ensure "Performance" is set to "Hardware Encoding."
  5. Under Video > Encoding Settings (or similar, depending on version), ensure the Renderer is set to "Mercury Playback Engine GPU Acceleration (CUDA)."
  6. Start the export (either directly from Premiere Pro or by queuing to Media Encoder).


Expected Result:

The export completes successfully(New RTX 5000 series now support 4:2:2 10bit H.265 natively)

Actual Result:
The application (Premiere Pro) freezes at a random point during the export. It becomes unresponsive, and the system requires a hard restart as the application cannot be closed via Task Manager.

 

Additional Notes:

  • The problem is reproducible in both Premiere Pro direct export and Adobe Media Encoder.

  • Switching to "Software Eng" rendering allows exports to complete, but this is not ideal.

 

I would appreciate any insights, troubleshooting steps, or guidance on whether this is a known compatibility issue. Please let me know if further information is required.

Thank you!

302 replies

Participant
July 22, 2025

I bought the same model of Graphics card GeForce 5070. Also facing the same issue for more than 40 mins video.

Big Disappointment from Adobe.

randyw54437024
Participating Frequently
July 21, 2025

Any updates yet? Getting ready to build my new video editing PC with a 5080 and would love some assurance

danm32376722
Known Participant
July 21, 2025

I just upgraded my 4080 super to a 5090 and cannot complete an export in Premiere or Encoder using the GPU to encode. Latest studio drivers. 

Known Participant
July 19, 2025

@Tsimdux Try turning it on.

Known Participant
July 19, 2025

@MyerPj I was answering zionb76063611, not you.

FlyingFourFun
Inspiring
July 19, 2025

@Tsimduxthat's too bad its already disabled.   If one didn't turn on the global setting there should be no reason for it play a role then.   That also explains the crazy stuff I was seeing when I forced the global setting to on - PP probably doesn't work well with the setting enabled which is why the driver profile says to keep it off.

 

I still think we will see an nvidia driver update paired with an adobe PP update that will correct this for the 5000 series cards.  I look forward to when they release the update and maybe give some insight in how ti was corrected.   But like others, I hope this fix comes very quick now.

 

Thanks for taking a stab at looking at it.

Participating Frequently
July 19, 2025

@FlyingFourFun I will say I looked at the Adobe profile in Nvidia Profile Inspector and it does say REBAR is DISABLED, so I'm not very optimistic.

Participating Frequently
July 19, 2025

@FlyingFourFun Interesting theory. Basically Resizable Bar is turned on in the bios. Nvidia's driver automatically toggles it off unless a game supports it. If the game supports it, Nvidia's driver turns Resizable Bar on to take advantage of it.

 

The issue MIGHT be that Adobe products, for some reason, are being flagged on the 50 series cards as supporting Resizable Bar and activating when using Adobe products. But since Adobe doesn't support rebar, the memory freaks out and the app locks up.

 

When I have time I might try this theory out and report back. Currently REBAR is ON in the bios and OFF in the global settings of Nvidia.

FlyingFourFun
Inspiring
July 18, 2025

@pentian 

they did offer the one know workaround, which is to turn off HW encoding when exporting.... confirmed its not ideal, empathy was expressed.   They will never tell you when a fix might happen because no one knows until they solve it, that it’s fixed or thought to be fixed.  This is standard in the software dev world.  As as aside, I was just reading that Divinci didnt have support for the 5000 series either when the cards first starting appearing, it was held back at the start...   not sure if they have support now.  But that might speak to the idea tha maybe these 5000 cards have something different about them... 

 

The issue may not even be Adobe's at this point.  The 5000 series card have all sorts of issues, including defective GPU processors that are not know until you use tools like GPU-Z and confirm the missing video processors....  which most people don’t even know is a problem with these cards unless you are watching the game review channels.

 

If you want to try and trouble shoot something with your 5000 series cards, I have a hunch based on something I saw when testing another system related to resizable bar.

This setting gave us HUGE performance gains!! Check yours now!

 

I think the advice in this video is bad for content creators, it specifically tells you to force on the feature so its active 100% of the time.  I tried this with the expectation Premier would be faster, but what it did was memory got way out of hand, and the GPU would lock up.  Putting the setting back to normal allowed the same system to run fine.

 

My hunch I wanted to test, was if turning off resizable bar fully, would allow premier to run properly with the 5000 series cars.  Based on my interpretation of the complains people have had, and what I saw when I turned this feature fully on - they struck me as similar.  I had plans to try it when I got my 5090, but today I still can’t find an available founders edition in Canada.

 

If you have time and ambition, maybe give it a try and report back on what happens.  I know you probably want to focus on your work and not bother with this BS testing, but when in a pickle sometimes trying something leads to an answer.  It’s a long shot, so your call - if I had a 5090 I would be testing it myself.

Participating Frequently
July 18, 2025

The lack of any community engagement on this issue is really disappointing. At least demonstrate some accountability, provide some work arounds, and some tentative timelines. At this point I don't recommend Adobe Premiere if you've bought a new computer within the last year. Adobe Premiere is officially legacy software. Time to move to Davinci Resolve everyone.