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!

[Peru Bob]

Try rolling back the Studio Driver to an earlier version.

[LjnKao306948457o7m]

@jamieclarke  it's been almost 2 months and adobe hasn't released any fix, it's terrible

[Daniel31572930sqvu]

I bought my 5070 in February with my new PC. Spent over £2k on it. Thought "what a fantastic investment. I can get so much work done, much quicker."

In perspective, they fixed the 40 series within 2 months. What a disappointment.

[randyw54437024]

I'm having the EXACT same issue. Please address it, thanks.

[Cameron39026970w4qk]

I also have the same issue with my new RTX 5090!!! Please fix these issues soon, any updates?!

[pentian]

Any updates on this issue? Sadly this is the 2nd hardware I bought for my wife this past year that now doesn't work with Adobe Premiere. First I got her a Surface Laptop with Snapdragon which was supposed to get a native ARM port by end of '24. That was a lie. So I figured I get her a desktop rig with a new RTX 50 series card for video editing. Also a terrible idea. Adobe cannot be trusted to be used on new hardware.

[Alex367466572b5i]

@pentian For some reason, Adobe engineers are not ready to share information about the hardware components of their software.
This is the only software manufacturer of this kind...
Some kind of 200% increase in productivity that no one can reproduce.
And buying different equipment for testing with your own money, and then posting the material for everyone, when Adobe doesn't care about it, there are no more people willing to do it...
Puget Systems with "free" access to hardware, also no longer tests Adobe Premiere Pro...

[MyerPj]

@Alex367466572b5i 

I just searched Puget's website and couldn't find anything that matches your statement: <<Puget Systems with "free" access to hardware, also no longer tests Adobe Premiere Pro...>>

In fact, from what I can see, they are modifying their benchmark software and are removing the HEVC test, due to a limitation of the API. That's the closest I can come to your statement, otherwise, nothing else seems to have changed.

I think your statement is wrong, or misleading at best.

[Tsimdux]

After checking some other threads in this community, it seems Adobe products are straight up incompatible with Blackwell 50 series cards. They should make an announcement and put up a disclaimer until the issue is resolved, especially as more and more people are able to get their hands on the newer hardware. The problem persists through Premiere Pro, After Effects, Media Encoder... Completely disabling the GPU (disabling hardware encoding) is the only way I've found to continue my workflow.

If it's going to take a while for an official fix, they should at least communicate what the issue is or a temporary workaround if one exists.

[randyw54437024]

After the 5060ti didn't work, I thought it's time to build a new PC anyway, I picked the 5080... But with this ongoing issue with the 5000s I'm thinking maybe a 4080 instead?

[FlyingFourFun]

I am not convinced there are wide spread issues with the 5000 series.  The forum is basicaly a collection of people who ahve issues.  I am confident there are many people without problems and the 5000 series.

Frankly, Id still buy (and I am hoping to secure) a 5090 FE - there is no way I would buy a 4090 right now if I had a choice,  if there is a glitch, I am sure it will be sorted soon.

As a matter of fact I decided to run the beta, and found that the latest beta solves a playback glitch I was having...  I dont thin its even documented that this glitch was resolved yet, but its fixed butterly smooth playback.

I am not convinced there is a wide spread issue with the 5000 series, and if there are a few glitches, I suspect they will be corrected shortly.

[Alex367466572b5i]

@MyerPj 
https://www.pugetsystems.com/blog/2025/05/21/why-pugetbench-for-premiere-pro-is-dropping-hevc-encodi...

Open the latest articles "for Content Creation" and there are only Ae & Resolve.
And the benches themselves are automatic, with all the downsides, and their equipment works with a bunch of disabled settings. I.e. there are a lot of questions for them about the hardware and the test.
They ignored iGPU for a long time, now as gaming sites have begun to use little memory, etc., etc.
But, there is simply nothing else, i.e. who wants to build something, they have to wait six months until they fix the benchmark, Adobe writes something about RTX 50? Maybe it's better to go straight to Resolve?

[Alex367466572b5i]

@FlyingFourFun So you're suggesting a lottery? There are no tests, so what if everything is fine, right?
And some enthusiast friend will spend a lot of money once again, buy Intel, AMD, old and new Nvidia video cards. And as before, he will do tests, and Adobe won't have to do anything...
Hire some bloggers already, let them write articles about hardware in their blog, even if they are bad, incorrect, but at least something. The company won't go bankrupt...

[zionb76063611]

Hello,

Yesterday, I purchased a powerful new laptop, the Lenovo Legion Pro 5i, which meets and even exceeds the specifications listed on your website for Adobe Premiere Pro. The computer's specifications are:

• Screen: 16-inch

• Processor: Intel Core Ultra 9 275HX

• Storage: 2x1TB SSD

• RAM: 32GB

• Graphics Card: Nvidia RTX 5060

Despite the advanced specifications, I encountered an issue immediately upon my first use of Premiere Pro after downloading and installing it. After just a few minutes of work, basic operations such as resizing internal program windows, or clicking the "Stop" and "Play" buttons, become significantly sluggish and seem to queue up. Shortly thereafter, the entire program freezes completely and becomes unresponsive.

It's important to note that I am currently working with proxy files while editing four cameras simultaneously, without any effects or additional elements that should burden the system. From my understanding, this system should easily handle such a workload.

I would appreciate your assistance in identifying the root cause of this problem. Is it possible that the new and advanced graphics card requires specific drivers that I need to download and install?

Thank you in advance for your help.

[Alex367466572b5i]

There may be problems with the RTX 50 graphics, there are many complaints. And you need to look in the Task Manager to see who is doing the hardware decoding and whether it works at all.

[ISBONNY]

To the Adobe Support Team,

I'm experiencing a critical issue with Premiere Pro: exports consistently freeze when I use my RTX 5090 graphics card. I've thoroughly tested this and can confirm it's an RTX 50 series GPU-specific problem, as switching back to an RTX 40 series card completely resolves the issue, allowing for normal exports.

I understand this problem has been brought up in other threads, but I urgently need to know Adobe's timeline for a fix. I just upgraded to the RTX 5090, and this bug is making it impossible to export any video. Premiere Pro locks up completely, can't be closed via Task Manager, and forces me to hard reboot my system every single time. It's ridiculous that I'm currently having to use my old GPU just to get any work done.

If a fix isn't coming very soon, can you please provide any immediate workarounds or temporary solutions that might allow me to export projects with my new RTX 5090 without these constant freezes? This situation is significantly impacting my workflow.

PLZ, I really hope it can be fixed as soon as possible .

[Tsimdux]

@ISBONNY For emergency exporting, the current only known workaround is to go to Edit - Preferences - Media and uncheck H264/HEVC hardware encoding (I also disable decoding). This will use your CPU for 100% of the export process. This will, unfortunately, be MUCH slower, so you may just have to let it run overnight. Obviously this is unacceptable for workflows that require consistent exporting. 

I'm not sure how this issue has gone under the radar for so many months. I think now more people are finally able to get their hands on 50 series cards. Either that or a recent update from Nvidia or Windows has broken support.

[MyerPj]

Uh, yeah @Alex367466572b5i , that's exactly what I referred to in my post, so you brought no new information to the table.

[pentian]

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.

[FlyingFourFun]

@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.

[Tsimdux]

@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.

[Tsimdux]

@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.

[FlyingFourFun]

@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.

[Alex367466572b5i]

@MyerPj I was answering zionb76063611, not you.

[Alex367466572b5i]

@Tsimdux Try turning it on.