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 Fixed
TOPICS
Export
31.7K
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 , 6 hours ago 6 hours ago

Fixed with Studio driver 581.57 released on October 14th.

Status Fixed
Translate
replies 310 Replies 310
310 Comments
New Here ,
May 24, 2025 May 24, 2025

Hi,

 

I have recorded footage that is about 1 hour in length and have made some edits in premiere pro, simple things such as a watermark and a few cuts and the start of the video.

 

Now when it comes to exporting it, I have tried both quick exporting and AME and the process is still the same, it exports up to 99% with 10 seconds remaining and then just freezes. I have left this for upto 1 hour and its does not seem to budge. 

 

I have tried almost everything i can think of or what i have found on the internet. From clearing the media cache, disabling one drive, making sure all the settings are the same as what the footage was recorded in, tried making copies of the document and saving to my desktop and importing that way, exporting it in a different format and making sure it is saved on either my external HD or my actual PC , I have tried unistalling adobe PP and restarting both my PC and App, I have tried creating a new sequence and changing the name of the exported file to something completely different and nothing seems to make a difference.

 

The export video and export audio files are both checked and have been unchecked to see if it made difference, I have broken down the footage to see if there was any specific frame that was causing this issue and apparently there is no problem.

 

I can not figure this out and need help, the file obviously auto creates a M4V and an audio AAC file and then compresses them both into the final MP4 file and the end of exporting but instead it just gets stuck and the the M4V ends up being around 15 - 20GB and the MP4 file is usually no more than 3KB. This is when my PC tells me that file can not open and is corrupt, but when I open the original file its plays no problem, can it be getting corrupt from the edits I have made? 

 

I have a pretty decent PC and have used both Software and Hardware encoding settings and nothing changes.


Processor AMD Ryzen 7 9700X 8-Core Processor 3.80 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
Graphics Card - NVIDIA RTX 5070 Ti

 

Any help would be appreciated, thank you.

 

 

Translate
Report
Community Expert ,
May 25, 2025 May 25, 2025

Hi @joshua_0607 
Have you tried exporting your video to a different set of compression/format? I'd try export to a different preset - like say YouTube 720p. This can test if it is particular format settings that is causing the problem.

Translate
Report
Community Expert ,
May 25, 2025 May 25, 2025

Do you have more than one hard drive? If so maybe try exporting to your desk top to make sure that there isn't some kind of communication issue between drives.

Translate
Report
Adobe Employee ,
May 27, 2025 May 27, 2025

Hi joshua_0607,

 

Sorry about the poor experience. Do you have sufficient storage space on the drive you're trying to export? Have you tried exporting in QuickTime > ProRes 422 LT to see if it's exporting properly? Also, have you checked whether you're able to export just the audio?

 

Thanks,

Sumeet

Translate
Report
Adobe Employee ,
May 27, 2025 May 27, 2025

Hi @AL-Shami - 
Thanks for submitting your bug report. We need a few more details to try to help with the issue.

 

Can you let us know the exact driver version you are using? 

 

What effects are you using?

If you remove the effects does the export complete?

Sorry for the frustration.

Status Needs More Info
Translate
Report
Community Beginner ,
May 27, 2025 May 27, 2025

Hi @jamieclarke -
Thanks for getting back to me and for looking into this. I appreciate the help!

To answer your questions:

  • Exact driver version: The NVIDIA Studio Driver version I am currently using is 576.52.

  • Effects used: Initially, the only effect I had applied to the clips was Lumetri Color (for basic color correction). With Lumetri Color applied, the export froze as described in my original post.

  • Export without effects: To troubleshoot, I then removed all effects from the timeline entirely. Unfortunately, even with no effects applied, the export still freezes at a random point when using CUDA hardware encoding.

So, to confirm, the freezing issue occurs both with Lumetri Color applied and with no effects applied at all when using CUDA hardware encoding.

Please let me know if there's any other information or logs I can provide that would be helpful.

Thanks again for your assistance!

Translate
Report
Community Expert ,
May 27, 2025 May 27, 2025

Keep working with @jamieclarke .

One thing you can try if you'd like is export to a visually lossless codec, like ProRes, LT or even ProRes Proxy format. Then you can make an h.264 from the ProRes. Something to try... 🙂

Translate
Report
Participant ,
May 28, 2025 May 28, 2025

"RTX 5000 series now support 4:2:2 10bit H.265 natively"

Pr 25.3 Beta +
There is currently no optimization for this architecture in 25.2.

Translate
Report
Community Beginner ,
May 29, 2025 May 29, 2025

I'm having the exact issue with the same card, drivers, Prem version - everything.

 

Incredibly frustrating.

 

I really do hope Adobe fixes this issue as soon as physically possible with the amount of money we're spending each month on this.

 

One way I've found is to go back to version 25 and render via mercury software rendering. Not ideal in the slightest.

Translate
Report
Community Beginner ,
May 30, 2025 May 30, 2025

I'm having the exact issue!

 

Card: RTX 5070 Ti
Driver: NVIDIA Studio Driver 576.52

Premiere Pro: 25.2.3 (tried latest Beta as well)

Occurs when exporting H264/H265 with hardware accelaration. Exporting with "software only" works.

Translate
Report
Community Beginner ,
May 31, 2025 May 31, 2025

 

The same problem was encountered in the RTX 5090, which has been going on for at least a few weeks. 

Translate
Report
New Here ,
May 31, 2025 May 31, 2025

Also having the same problem. Stuck after processing a bit and need to terminate via task maanger. Using an  RTX 5070 Ti, but I installed the Game Ready driver in Nvidia App. Thanks!

Translate
Report
Participant ,
May 31, 2025 May 31, 2025

@donm11979746 Game Ready driver fixed Premiere Pro?

Translate
Report
Adobe Employee ,
Jun 03, 2025 Jun 03, 2025

Hi @AL-Shami @crasso @donm11979746 - Would you be able to send a link with project and media that you are having this issue with to jamiec@adobe.com

 

Can you right click your media files and select "Media File Properties" and post a screenshot, please

Translate
Report
Community Beginner ,
Jun 03, 2025 Jun 03, 2025

It weirdly rendered out (using CUDA) in After Effects with the Game Engine, very slowly, and it crashed right at the end but it did render out.

Translate
Report
New Here ,
Jun 03, 2025 Jun 03, 2025

Same issue here!!

 

Card: MSI VANGUARD RTX 5070Ti 16GB

CPU: Intel Core i9-13900KF

Premiere:25.2.3 (build 4), beta 25.4

Driver: NVIDIA Studio 576.52

 

Translate
Report
Adobe Employee ,
Jun 03, 2025 Jun 03, 2025

Hi @AL-Shami @crasso @donm11979746 @Handbro  - Would you be able to create a memory dump in task manager of Premiere Pro when you are experiencing this issue.  You can email a link to jamiec@adobe.com

 

Please see this article: how to create a memory dump using task manager

 

Translate
Report
Community Beginner ,
Jun 04, 2025 Jun 04, 2025

Please check your inbox, I sent you an email.

Translate
Report
Community Beginner ,
Jun 09, 2025 Jun 09, 2025

I also got the same error, GPU was running at 70% but suddenly it dropped to 3%. Also stopped exporting video. After closing the render panel Premiere crash.

Translate
Report
Community Beginner ,
Jun 09, 2025 Jun 09, 2025

Hi Jamie, I see Adobe had the same issue with supporting the 40 series.

 

Any idea you may know when the 50 series will be supported with Adobe software?

 

Thanks,

Dan

Translate
Report
Community Beginner ,
Jun 09, 2025 Jun 09, 2025

I tried exporting a video of more than 2 hours with LUT Delog Slog3 and it worked. Previously, if I didn't have this LUT, I would get the error as mentioned. The solution is to add an adjustment layer and add LUT SGamut3CineSLog3_To_LC-709TypeA (you can try another LUT). How to download: search for the keyword "Software: Sony Look Profile (3D LUT)".
Continue to reduce the Intensity in the Lumetri color section to 0.1 so as not to affect the original color. Render and enjoy the results with the power of RTX 5000 series

Translate
Report
Community Beginner ,
Jun 09, 2025 Jun 09, 2025

I fixed it, read the instructions above

Translate
Report
Adobe Employee ,
Jun 11, 2025 Jun 11, 2025

Hi Community,

Sorry for this issue. Is it possible to try exporting using OpenCL? That is the workaround listed in the internal bug report. Let us know.

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
New Here ,
Jun 12, 2025 Jun 12, 2025

Hi,

I'm getting the same issue, both Adobe Premiere and Media Encoder become unresponsive during an export with Hardware Encoding, and they cannot be killed by Task Manager but only by restarting the computer.

 

CPU: AMD Ryzen 9 9950X

RAM: 96GB DDR5 5600MT/s (2x48)
GPU: NVIDIA GeForce RTX 5070ti

OS: Windows 11 24H2 26100.4061

Driver: 576.52

Translate
Report
Community Beginner ,
Jun 13, 2025 Jun 13, 2025

@LjnKao306948457o7m Your Solution WORKS!

@Kevin-Monahan I am not able to turn this on, because "We made a change with Premiere Pro and Media Encoder version 25.2 so that you can no longer manually choose the renderer in the Project settings."

Translate
Report