Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
31

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

Community Beginner ,
May 25, 2025 May 25, 2025

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!

Bug Acknowledged
TOPICS
Export
31.6K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Participant , Oct 01, 2025 Oct 01, 2025

NVIDIA posted Game Ready Driver, 581.42 yesterday that includes all the required fixes for this issue. It is available here for desktop users : https://www.nvidia.com/en-us/drivers/details/257133/


Due to a recent plan of release change, we did not post a updated Studio Driver yesterday, the next Studio Driver to now pick up all the required fixes will be on Oct 14th. 

Please let me know if you have any further questions. 

Translate

correct answers 1 Pinned Reply

Adobe Employee , Jun 26, 2025 Jun 26, 2025

Please see this post for additional instructions: https://community.adobe.com/t5/premiere-pro-bugs/p-premiere-pro-freeze-during-export-using-hardware-encoding-nvidia-rtx-5070/idc-p/15444944#M53853 

 

The Studio driver will be available Oct 14th.

 

This issue will be fixed on Sept 30th, the Studio drivers will be posted on the morning of Sept 30th (PST).

 

Users have reported fall back to Studio driver version 573.22 or 572.83

 

Quick Update: We’ve been able to reprduce the issue. Thank you for y

...
Status Acknowledged
Translate
replies 309 Replies 309
309 Comments
Community Beginner ,
Oct 07, 2025 Oct 07, 2025

it started with premiere pro version 25.2 and all above. Still using 25.1 as the only working properly

Translate
Report
LEGEND ,
Oct 07, 2025 Oct 07, 2025

Are you using a 50 series Nvidia GPU?

Translate
Report
Community Expert ,
Oct 07, 2025 Oct 07, 2025

@Witold3607716889yl it may not be the same issue. 4090s have been around for quite awhile and there is not a lot of reports on the 4000 series. I'm on a 4070 and it works fine. You might want to look for other causes. Or try the same work arounds mentioned in this thread.

 

Translate
Report
Community Beginner ,
Oct 09, 2025 Oct 09, 2025

@pkirst I will add, with latest Gaming drived in some projects I got Freeze during export even with Turned OFF Gpu Scheduling!

Translate
Report
New Here ,
Oct 09, 2025 Oct 09, 2025

Try updating After Effects to version 25.5 and check the render.

Translate
Report
Enthusiast ,
Oct 14, 2025 Oct 14, 2025

New driver from Nvidia is out today: Oct 14, 2025 version 581.57

FlyingFourFun_0-1760453148276.png

 

Translate
Report
Community Beginner ,
Oct 14, 2025 Oct 14, 2025

Doing a stress test - so far so good... 3 shorts, 4 long forms. Will report back.

Translate
Report
Community Beginner ,
Oct 14, 2025 Oct 14, 2025

Just a follow up.

I've managed to successfully render out 3 shorts and 1 long form (approx 60 minutes long, 4K 60fps). Straight from Prem.

 

I did try it through Media Encoder but it did seem to take ALOT longer.

5070, Studio driver 581.57, latest Prem & ME versions.

 

Editing in Prem felt a lot smoother.

Still early days but things feel better.

Translate
Report
Enthusiast ,
Oct 14, 2025 Oct 14, 2025
LATEST

@Daniel31572930sqvu I think you should time the renders.  I have been noticing that there are at times 3x longer renders in ME vs Premier - but I have been running the beta, I posted about it in the beta group, but that thread is all but ignored by one other person.  I think there is significant difference, I rarely render within premier, as even if I exit premier, and wrap for the day, I like being to see where in the render it is (like in ME) - I wish Premier also did this - along with putting the exact timecode its processing on the screen.

 

Also; Glad to see your tests are holding up.  I was not having issues with the 5090,  but I will be running some tests later today to ensure no new bugs are introduced, and I will also run a test ME vs PR to see if the speed difference is still there, and by home much.

Translate
Report