Premiere Pro Performance Issues with RTX 3060 and RTX 3080 12GB

[T - Sal]

Description:

Hello ,

I'm encountering some performance issues with Premiere Pro and my new RTX 3060 and RTX 3080 12GB GPUs. Previously, I was using an ADM W9100 and Premiere Pro was working fine. However, after switching to the RTX GPUs, I'm experiencing the dreaded "Media Pending" screen and sluggish performance.

I've tried importing a file from the source, which displayed a picture, but Premiere Pro is not playing or performing smoothly. I attempted to change the CUDA settings in the project settings, which improved the situation slightly, but I'm still unable to complete any real work.

System Specs:

RTX 3060 and RTX 3080 12GB GPUs
64 GB RAM, kingston Fury Beast DDR5 RGB 32GB 5600MT/s DDR5

Intel Core i7-12700F is a 12th generation
Deepcool LE720 ARGB AIO Liquid CPU Cooler is a 360mm radiator
Steps Taken:

Imported a file from the source, which displayed a picture but did not play smoothly.
Changed CUDA settings in the project settings, which improved performance slightly.
Issue:

"Media Pending" screen
Sluggish performance
Inability to complete real work
Request for Assistance:

I'm seeking advice and guidance from the Adobe Community on how to resolve these performance issues. Any help or suggestions would be greatly appreciated.

Thank you in advance for your assistance.

Best,

[R Neil Haugen]

Have you tried removing the 3060 and just using the 3080?

[T - Sal]

I've tested both the 3060 and 3080 individually, and the same issue persists. When I uninstall the latest driver, Premiere Pro works fine. However, when I install an older driver like 466.47 and 472.84 , Premiere Pro gives me a message that the driver is not supported, but the software still works fine.

[R Neil Haugen]

Go one driver back from the current one, that newest one is a pain in the posterior.

[T - Sal]

I tested all drivers from 2023-2024,, none of the drivers have resolved the issue.

[Peru Bob]

Make sure to use a Studio driver, not a Game driver.

[MyerPj]

<<when I install an older driver like 466.47 and 472.84>>

Why so far back, just use a 530/540 range, even 551.23 was working ok for me. I have the latest version 551.61 and it's working OK, but I know there has been some problems with it.

You're not using them installed in the machine at the same time? If so, pick one or the other, but not both. The days of dual GPUs is past, at least as far as video creation software goes.

[T - Sal]

I tested both the game ready and the studio drivers 

[T - Sal]

Hello, I've attempted to install the GPUs separately and also tried the 551.61 driver version, but I'm still facing the same issue.

[MyerPj]

It might be time to look at some other components. Any overclocking going on? HUD are notorious, trying to measure frame rates, temps, etc...

[T - Sal]

I have Gpu Tweak III

[MyerPj]

Yes, remove that from starting with Windows. Those are the kind of things to look for / remove.

[R Neil Haugen]

I have an Acer Triton, with their GPU monitor and tweaks applet. If that's open, Premiere isn't as responsive as when it's closed. It eats just enough resources of the wrong kind to interfere with Premiere.

[T - Sal]

I've discovered a workaround, if I import just one clip into a new project from the same path before opening the original, and then open the original project, everything works fine. It's an odd behavior, but at least there's a temporary solution.

[T - Sal]

You can see it over here!

[T - Sal · Accepted solution]

Exciting news, everyone! I've successfully resolved the persistent issues I was facing with Premiere Pro, all thanks to the amazing support from Nvidia and the helpful members of the Adobe Community.

When I reached out to Nvidia about the problems I was experiencing, they promptly provided me with their CleanupTool_1.0.20.0 utility, which I ran as an administrator to clean up any remnants of old drivers. After that, they guided me through the process of downloading and installing the latest driver version, 551.86-desktop-win10-win11-64bit-international-dch-whql. And it worked like magic! Everything is now running seamlessly.

[R Neil Haugen]

Thank you for a great detailed post about resolving this!

That bit about their driver cleanup tool is news to me, so thanks for that especially.

[T - Sal]

You're welcome! 🙂