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
August 5, 2025

I think I may have figured out a problem with what's going on, I had to reinstall windows, use my first driver from Nvidia and noticed the problem is not within the video codec, but the audio codec. For some reason the driver update messes with the Nvidia High definition audio codecs, once I used a known working driver, every export I tried with my RTX5090 worked fine and without hiccups. I would suggest trying to check when you update your drivers, if the HD audio part is corrupted or not installed, This was the previous problem I had. I hope this helps to someone having the same issue. 

Participant
August 5, 2025

@MyerPj Oh, I'm not using Premiere so can't say if it would work the same. Some additional info: I'm on a new laptop with a RTX 5070 TI card. Once I first got it and installed the drivers that came with it I did a test run in After Effects and as I remembered it, the etst run went well. A while later when I've updated all drivers to the latest versions I got the issues described here in both After Effects and Media Encoder. After trying basically EVERYTHING I decided to revert to the original drivers and now it all works like a charm. I don't know which NVIDIA driver version that broke it, just that v. 573.22 fixed the issue.

MyerPj
Community Expert
Community Expert
August 5, 2025

Cool! NVIDIA is now on the case (and this thread) 🙂

@pkirst 

MyerPj
Community Expert
Community Expert
August 5, 2025

@Johan33441262p7e6 , but not in Premiere?

Participant
August 5, 2025

@pkirst I've sent it to you as a private message.

Participant
August 5, 2025

exatly same issue here rtx5090, freezing during export. i've put the 4090  back and was flawlessy good...don't know what nvidia did!!! 

pkirst
Participating Frequently
August 5, 2025

May someone who is impated by this issue provide NVIDIA with a dmp file after the application becomes unresponsive. Here are the steps to provide the dmp file : 

Creating a manual crash dump file when a program freezes or is unresponsive
When you are using a program and it becomes unresponsive, you can manually create a dump file using the Windows Task Manager.  Choose from one of the two methods to access the Windows Task Manager.  
 
a) Right-click over the Start icon or Windows Taskbar and select Task Manager from the context menu.

 

b) On your Windows keyboard, press CTRL + ALT + DEL at the same time.  Then select Task Manager.  

This will bring up the Windows Task Manager.  Find the process for the program that is frozen or unresponsive.  Next, right-click over the app and select Create dump file (if you do not see the option, drill down on the app and find the process which is unresponsive from the expanded list).  It may take Windows a couple of minutes to complete writing the dump file. 
 


Once Windows notifies you that the file was successfully created, select
Open file location.  The DMP file will be too large to attach to an email.  You will first need to upload the DMP file to a file sharing service such as Google Drive or Microsoft OneDrive and then share the URL to download the file with us.  You may reduce the file size by compressing or zipping up the file before uploading it to a file sharing site

Participant
August 5, 2025

Downgrading the NVIDIA driver to v. 573.22 fixed the issue for me in After Effects and Media Encoder

Participant
August 5, 2025

I've had my 5070 Ti since March 31st, bought it used from a store. Gigabyte card with serial number starting with "SN2503" (2025, week 3(?)).

Participant
August 5, 2025

When did you buy this 5070? Someone else couldn’t take it anymore and ended up buying another 50-series card, and it worked without any problems. Could it be that the newer batches have already fixed this issue, while the older batches can’t be fixed due to a hardware problem?