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

[AL-Shami]

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!

[danm32376722]

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. 

[randyw54437024]

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

[amit_patwardhan8504]

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.

[satyajit kulkarni]

I am also facing the same issue for my premiere Pro with GeForce rtx5070 graphics.... I am very disappointed for investing lot of money in both graphics,new desktop ..... Hoping for the fixes soon....  

[Cameron39026970w4qk]

@jamieclarke Any updates!?!?!?

[Spankers]

Crazy to see the entire community crash out over a problem that should've been solved ages ago. This shouldn't have been an issue to begin with lol.

[R Neil Haugen]

As this has also happened to a number of Resolve users with 5060/70/80/90 cards, it isn't just an Adobe issue. There have been problems identified by Nvidia with some drivers by reports.

So we're all hoping Nvidia, Adobe,  and BlackMagic can get this sorted 

[FlyingFourFun]

@R Neil Haugen I believe the root of the export issues and possible a few others is a driver issue at its base, that will either get resolved by Nvidia, or in collab with adobe and blackmagic...    I saw in the release notes there was a cuda library update, OpenCL layer update and lots of changes in the driver that could be the cause (including some comments on NVENC response changes in the driver).  Hopefully we are not far from a fix, but I feel like this not 100% on adobe at this point.

[Jawad335818487twc]

I have the same issue with a new 5080 card while rendering / exporting to H264, its always getting stuck somewhere. Just updated to the new Studio Driver ver 577 today, same issue. Have a Z790 and i9 13900KS, 96 GB RAM.

Not sure how much the Adobe experts will help you here but, try this and it will work:

Instead of exporting to H264 or H265 export to another format. Since my recordings are from an iPhone and the files are MOV, so I just rendered them in ProRes, which is basically Quicktime (Apple ProRes 422). This method worked for me, because my source and output would be in the same format, and I upload on YouTube, which accepts this format. 

The render is a bit slow, and it consumes weirdly CPU, my Intel iGPU and 5080, and its not running continuously, but it doesn't get stuck. The time estimate on the render is not reliable though. But ProRes will work, guarantee, and you will thank me for it 🙂

[R Neil Haugen]

Great practical advice!

I'm a Resolve user also, and the same issues happen to many over 'there' with the 5060/70/80/90 cards at this time. Hoping Nvidia et al get this sorted quickly.

[FlyingFourFun]

I hav ebeen readign through a numner of other support forums, and even the gamers are seeing issues and they are deep diving into firmware.  The more I visit other forums, the feel its more likly a driver issue.  Hopefully its not a defect in the GPU design - which is not unheard of.  Could explain why the volume of 5000 series available is low...

Things like this, and maybe more we dont fulyl know about yet:

NVIDIA GeForce RTX 50 Cards Spotted with Missing ROPs, NVIDIA Confirms the Issue, Multiple Vendors A...

[FlyingFourFun]

@Jawad335818487twc thats good advice for a work around that may asisst a good deal of people, thanks for sharing.

[Tsimdux]

@Jawad335818487twc I tried this and it froze after an hour and thirteen minutes exporting a five minute video on a 5090...

[Tsimdux]

@Jawad335818487twc Nevermind. The UI froze up but the video completed. It took several hours.

[Chen292594190kp1]

Who’s unlucky? Me.

The school computer lab is getting an upgrade — we bought 32 RTX 5060 GPUs, and Premiere Pro is the main course in that lab. Damn it.

My current workaround is to roll back to Windows 10, install the Game Ready Driver (absolutely do not install any version of the Studio Driver), and make sure to use DDU to completely remove the old driver.

In the BIOS, set PCIe 5.0 to 3.0, and disable Resize BAR.

In the driver settings, change the Power Plan to “Maximum Performance” — otherwise, you’ll get a black screen. The PC hasn’t crashed, it just loses video output.

After all these tweaks, Premiere Pro becomes usable — exports and renders work fine.

BUT if you’re working with all 4K footage, the workload becomes too heavy, and the system might crash or reboot.

This batch of GPUs is killing me — I’ve taken the heat from the school and most of the teachers.

It’s clearly not a small issue, and I don’t know whether it can be fixed, or if it’s permanently broken.

Remember to keep evidence — send at least one email per month to the supplier, setting a deadline.

I told them: If it’s not resolved in 6 months, we’re returning them.

[R Neil Haugen]

The issue it seems to be is with those card's drivers ... I'm also a user of Resolve, and this has come up on the BM and other Resolve forums also. I've also seen a post where Nvidia recognizes some driver issues with some high-end uses. Which would be virtually all the pro video post apps, probably.

I would just note, as a general Nvidia practice ... I strongly disagree with your comments on the studio drivers/gaming drivers. As for over the last decade, gaming drivers have caused a tremendous amount of problems for many users ... that were simply resolved by going to the latest studio driver.

In over a decade, I know of only one other user who has suggested using gaming drivers. And a ton of posts where issues were solved by simply doing a clean install of the Studio driver.

[Chen292594190kp1]

I spent a week trying to solve this problem — Windows 10 combined with the Game Driver is the only way to get Premiere Pro running.

I’ve read almost every single post about this issue, searching for solutions, but nothing has worked. Adobe has known about this for two months already, and they even said fixing it was the top priority. But two months have passed, and it’s still unresolved.

This is no longer just a simple driver problem. Hundreds of engineers at Adobe and Nvidia haven’t been able to fix this in two months.

Now both Adobe and Nvidia have gone silent. Even the latest 577.00 Studio Driver doesn’t mention any fixes for the Premiere Pro issue.

As a long-time IT professional, I want to tell you: this is not a trivial issue. Even if they do “solve” it in the future, it will likely involve disabling some features, reducing performance, or not fully utilizing the capabilities of the RTX 50-series GPUs.

[R Neil Haugen]

This issue with the newer ... and very spendy Nvidia cards ... is a right royal pain for all users. Period. What a freaking mess!

There are a ton of users hoping this can get sorted without as you mention disabling some of the hardware you've already paid for. Dearly.

Total sympathies!

[SwanyPlaysGames]

I've had issues with this for over 3 months now. I haven't been able to properly export my videos due to all the crashing with my 5090. This is getting ridiculous.

[MyerPj]

Can you export to ProRes? It's a visually lossless format, and then you can make h.264/5 from the ProRes.

[FlyingFourFun]

Chen292594190kp11 there is some logic to your approach of using game drivers and windows 10.  Reading through hundreds of posts in the gaming community, gamers seem to have found acorrelation between a windows update from May of 2025 and the interplay with the newer nvidia drivers (they listed a version I just cant recall it right now).

Your solution aligns with avoiding both the windows cumulative update and nvidia driver that the gaming community is pointing to for issues.

With that said,  I am confident that the engineering teams involved understand the issue and are working on a solution, and I think this will be solved 'soon' - but that will not be soon enough, I think soon is 2 weeks.  For the record, this is my personal speculation I have no connections that could inform confirm or deny this - so take it as hope or fantasy....

[Tsimdux]

I've also found that Discord similarly locks up and stops responding while streaming to Discord using hardware acceleration. This makes me think it has something to do with the Nvidia/Windows drivers more than Adobe.

[R Neil Haugen]

Yes ... and in Resolve and other apps as well. It clearly is not an Adobe specific issue. Though so freaking frustrating.

And seems to affect many though maybe not all 5060 & higher number cards. 

[Tsimdux]

I THINK I've found the FIX!!!

Solution: 

1. Open the Registry Editor (press Win+R, type regedit, press Enter).

2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm

3. Right-click, select New > DWORD (32-bit) Value, and name it: OverlayMinFPS

4. Set its value to: 0

5. Open Task Manager, find "Desktop Window Manager," and end task. It restarts automatically.

6. Reboot your computer for good measure.

This registry tweak targets a problem with how Windows 11's Desktop Window Manager (DWM) interacts with Multiplane Overlay (MPO) when rendering Chromium/Electron-based apps (like Discord) and GPU-accelerated video apps (like Premiere Pro). The issue often results in application freezes, incomplete rendering, or UI elements not updating, especially after alt-tabbing or during certain GPU-heavy tasks. Setting OverlayMinFPS to zero removes the minimum frame rate requirement for assigning DirectX swap chains to overlays, which stabilizes how frames are presented and eliminates the freezing.

I'm currently testing with a few exports in Adobe Media Encoder. I was able to do an effect-heavy export that took an hour and a half with no freeze. I'm about to test a three-hour video export that doesn't have as many effects and so should rely on the GPU hardware encoding more. I've even been alt-tabbing out and using other windows, which would normally guarantee a freeze. Can other people test to see if this works? I'm not sure why this plagues the 50 series cards more than others if this is indeed the issue.

Here's where I found the fix: https://www.reddit.com/r/Windows11/comments/1kgp7ar/cause_and_solution_to_windows_24h2_related/

[FlyingFourFun]

@Tsimdux interesting discovery - lookign forward to seeign how this plays out.  I would like to test it, but I have a 3090 and none of the freezing issues expressed here.