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!

[noam_weizman9905]

@Cunningcory And does this setting change not affect anything? In terms of quality?

[FlyingFourFun]

there is zero impact to quality.

Hardware GPU scheduling on allows the GPU to manage itself, which means your CPU is doing less work - in theory, this means you can get better performance in some cases.

Benchmarks however have shown mixed results, with same games show gains, others do not.

Its widely believed that this has a negligible effect on applications such as Adobe.   I have not tested it,  as my RTX 5090 is still in transit.

You can expect the same quality with the feature off or on - potentially a very minor performance impact, but there is no clear evidence for Adobe software.   If you are a gamer, you might want to turn it back on before playing games - but that requires a system restart.

[Cunningcory]

@noam_weizman9905 As far as I'm aware, there's no change to speed/quality when it comes to video editing with HAGS on versus off. The biggest tradeoff comes in gaming, where turning off HAGS also disables DLSS Frame Generation (a big feature of the 50 series cards). As a result, if you play a game where you want to utilize Frame Gen, you'll have to toggle HAGS back on and restart your computer. Then when you go back to video editing you'll need to toggle it off and restart your computer once more.

[pkirst]

Need to apologize again but NVIDIA Studio Driver and NVIDIA Game Ready Driver 581.29 does not contain all the required fixes for this issue.  

We will have all the required NVIDIA Driver changes to address this issue in our Sept 30th Studio & Game Ready Drivers. These drivers are expected to post to http://nvidia.com/drivers on the morning of Sept 30th (PST). 

To unblock any critical work, please install and utilize NVIDIA Driver version(s) 573.22 and 572.83 

[Daniel31572930sqvu]

So I'm finally going to be able to use my graphics card for the reason to why I spent £500+ on it 6 months later with no compensation? Fantastic.

[zachary_2720]

Wow. I thought I was going absolutely insane when this has been happening to me for the better part of 3-4 weeks. I am a brand new PC owner, my first ever build. I was about to haul this thing back to Microcenter before I found this thread. Wild. 

Adding more context, my exports are CONSISTENTLY stuck during the encoding phase. No heavy edits, Tik Tok length clips.. MAX 2 min. Regularly gets to 8-30% before it just loses its mind. Even after I end the task, the program cannot be closed, it continues to run in the background and does not respond to task master. 

Was vastly dissapointed, believed I effed up the build in some way shape or form. Will have to migrate my files onto my portable harddrive and try on my mac. REALLY HOPING this driver fix in 2 weeks is the solution. 

[MPEO]

Wow. So it appears that it's a driver issue. I'm having the same issue with RTX 5050. 

[MPEO]

How can I get these old drivers? It's not showing on the previous list of drivers. The oldest I can get is 577.

[MyerPj]

https://www.nvidia.com/en-us/drivers

When I go to the above, I put in my driver / windows info, and press Find, then it shows me the latest Studio and game driver, under that is View more versions.. That takes me backwards to 03/18/25 and driver 572.83

[kylied42404115]

Very glad to hear a potential fix is coming.  I've been having this same issue with my new RTX 5080.  Doesn't happen on every project but the symptom persists on once it starts happening. The only workaround I found useful was switching to software encoding which seems to fully bypass the problem so driver issue makes sense.  Before I found the solution this had me so frustrated I was watching Davinci tutorial videos, ready to jump ship.

[Exodus-FL37970569tuvz]

My render keeps getting stuck randomly, when my render gets stuck CPU and GPU usage drop from the perfomance tab and when I cancel the render my premiere pro gets frozen and after force quit it does not open again until I restart my whole PC

sometimes it crashes my PC

Im just rendering a raw video file with out any animation, I also tried it with different projects, all projects are doing the same thing which were running fine back then

My drivers are all updated
Windows Updated
Windows Activated
Adobe Cloud Purchased
also there is a lot of space in all drives
also deleted media cache
changes the location of media cache files

at this point IDK what to do either than burning my PC

System Requirements are:
Intel Core i7-9700K
5060 8GB
32GB Ram Corsair
Samsung EVO 980 1TB
my whole system information are attached below

[jamieclarke]

Hi @Exodus-FL37970569tuvz - There is a known issue with the 50 series GPUs where exports are freezing.  Please fall back to Studio driver version 573.22 or 572.83.  I will merge your post with the primary thread so you are notified of updates.

[Exodus-FL37970569tuvz]

thankyou so much, I thought I was going insane that's a huge relief to atleast identify the problem

[Exodus-FL37970569tuvz]

how to revert my drivers to specifically this version? because at nvidia website the oldest versions is 576.52

[MyerPj]

I answered this above, but if you click <Find> then the Studio driver (tab), under the current Studio driver is 'View More Versions'. Driver Versions still to: 572.83

[Dmitriy36779285gov2]

Hey, @jamieclarke 

I've tried installing these drivers. There are really no freezes and artifacts with them. But the new transitions that appeared in Premiere 25.5 (Film Impact) don't work with them. 

Therefore, the only working way is to disable GPU scheduling.

[FlyingFourFun]

I finaly got my 5090FE and installed it today;  managed to render out the same project that was about 40 min long in 3 different ways, log file below for details, but here is the specs and versions used for the software for your referance, spoiler, it rendered without any issues.  Id be open to downloading a project someone has issues with, and testing to see if I also run into issues.

Video started as a Iphone HDR H265, converted to PRORES for the first test, and exported back to H265 in 4K

Second test, used the original H265 HDR footage, and exported it from 4K H265 to 1080P (Seq size) H265, also no issues

Third Test, used the original H265 HDR footage, exported it from 4K H265 to 1080p (Seq size) H265, also no issues (I think this matches the settings of the OP, if I read thier post fully/correct.

There was not a single blip, and the 5090 had lots of head room;  I was running the new masking tool in the over all three export tests,  the 5090 doesnt seem to speed up the new mask took in any way, but none the less it was running within premier 25.6 Beta, and also watchign youtube videos at 3x speed.

And now, the important part, Drivers/software versions:

Windows 25H2 Build26200.6584 (This is a REALLY new offical version, if you want it, I can tell you how to trigger the download/install).

Adobe Premier Pro Beta 25.6.0.78 2025-09-23

Media Encoder Beta 25.6.0.074 2025-09-25 (I used Media encoder to export with)

Nvidia Studio Driver 581.29 Sept 10, 2025

Hardware GPU Scheduler was confirmed enabled.

09/25/2025 08:35:31 PM : Queue Started

- Source File: C:\Users\XXXX\AppData\Local\Temp\Stampede Wagons PRORES v26.prproj
- Output File: H:\YOUTUBE READY\TEST RTX5090 Stampede PRORES.mp4
- Preset Used: H265 Export 
- Video: 3840x2160 (1.0), 60 fps, Rec. 709, 100 (63% HLG, 51% PQ), Hardware Encoding, Nvidia Codec, 00:38:04:51
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 50.00 Mbps
- Encoding Time: 01:00:53
09/25/2025 09:36:24 PM : File Successfully Encoded

- Source File: C:\Users\XXXX\AppData\Local\Temp\Stampede Wagons H265_1_1.prproj
- Output File: H:\YOUTUBE READY\1080p H265 to H264 Test HBIT Stampede Wagons H265.mp4
- Preset Used:
- Video: 1920x1080 (1.0), 60 fps, Progressive, Rec. 709, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:38:05:03
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 40.00 Mbps
- Encoding Time: 00:24:38
09/25/2025 10:25:50 PM : File Successfully Encoded

09/25/2025 10:25:50 PM : Queue Stopped

09/25/2025 10:39:25 PM : Queue Started

- Source File: C:\Users\XXX\AppData\Local\Temp\Stampede Wagons H265_1.prproj
- Output File: H:\YOUTUBE READY\H265 to 264 Test Stampede Wagons H265_1.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 60 fps, Rec. 709, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:38:05:03
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 50.00 Mbps
- Encoding Time: 00:20:55
09/25/2025 11:00:20 PM : File Successfully Encoded

09/25/2025 11:00:21 PM : Queue Stopped

I still have the non-beta software installed, I was going to try that also and report back.

Not sure why I am not running into what appears to be a very consitent issue, if someone wants to share a project that fails, I would not mind trying it to see if I can render with Hardware.

[Cunningcory]

The newest Nvidia driver released today claims to fix this bug. I'll test it tonight when I get home, but hopefully the newest driver fixes it for everyone!

[Witold3607716889yl]

Well unfortunately...

 

[Hoczo]

The new drivers on our computers didn’t fix this issue.

[jamieclarke]

Hi @Hoczo and others please be patient the studio driver has not been released yet.  We will update the thread when the driver is available.

[MeDocs374947182vbx]

Can also confirm - new driver installed, same issue as before, the new driver fixed nothing ...

[FlyingFourFun]

@Hoczo @MeDocs374947182vbx @Witold3607716889yl 

What version are you installing?  the update utility only shows the Sept 10 one still, and the Adobe says the new driver is not even posted yet?   can you confirm the driver your using Studio vs game and the version numbers please...

Referances to "latest" driver lead to only confusion.   Please clarify the versions your using.

The driver update utility doesnt have anything newer than Sept 10, and the manual driver download only shows Sept 10 version as per screen grab below:

I would really like to know and confirm what version you are using as no one else is claiming the Sept 30 driver is out yet (which is expected to correct it).

[FlyingFourFun]

@Cunningcory can you confirm you have the Sept 30th Driver and not the Sept 10th driver?  I have nto been able to find the Sept 30 driver for download.  Nvidia sites still onyl show me Sept 10th:

[FlyingFourFun]

There might be confusion as apperently there is a "game ready" driver dated Sept 30, but there is no signs of a Studio driver for Sept 30th.....