Skip to main content
mandicreally
mandicreally
Inspiring
December 30, 2017
Question

GPU Render Error. Yea another post from another person.

  • December 30, 2017
  • 1 reply
  • 652 views

Ok I'm pulling my freaking hair out.  I constantly run into GPU Render Errors, but usually a reboot fixes things.  Today I have been trying for about 3 hours to get a project to export, with no luck.  I can fully Render the timeline in the project, but when I head to Export, it fails in a matter of minutes.  I cleared my cache files and attempted again.  Shut down and let the computer sit.  Checked for drivers updates.  Checked for Premiere updates.  This has been a constant issue for me lately and it is really getting old. Today is just worse than it has been in a while.  I had read somewhere to open AME before Premiere and export via Queuing to AME.  However I have found that to be FAR WORSE for this GPU Render error. 

System Specs:

AMD Ryzen 5 1600
16GB GSkill DDR4 Ram 2800mhz

Geforce GTX 660 2GB GDDR5

Windows 10 Home 64 Bit

Geforce Drivers 388.71 (latest release)
Premiere Pro 2018

I know the graphics card is a little old, but it should at least function, even if slowly.  I've seen plenty of statements of "roll back drivers", and I have done so to all kind of revisions, none of which make any difference.  Nvidia lists the latest driver as THE drive for the GTX 660, so I don't want to hear about how the drivers aren't compatible for this old card.  I have a newer video card but I cannot install it just yet unfortunately.  I'd love to speed up my workflow I just cannot put it in yet.

The Timeline isn't a simple one but it is by no means the most complex.  It has some warp stabilizer and has Lumetri color on basically all of the clips.  Footage is 4k downscaled to 1080p via Sequence settings and scale adjustment on clips.

Error:

After I took this screenshot I went through and manually rendered the incomplete sections then once the entire timeline was Rendered, I saved, attempted Export and it failed again.

It seems like this is such a massive, common problem with not much in the way of official response.  Unless I am missing something. 

This topic has been closed for replies.

1 reply

mandicreally
mandicreallyAuthor
Inspiring
December 30, 2017

Oh and Export settings "YouTube 1080P HD" Preset with the following changes:

-Render Maximum Bit Depth

-Use Maximum Render Quality

-VBR 2 Pass

-Target Bit Rate: 18

-Max Bit Rate: 22

R Neil Haugen
R Neil Haugen
Legend
December 30, 2017

Sorry to say you might do better especially for reliability by turning Mercury Acceleration to software only. Not sure it would really add much time even.

Next, go through your Lumetri instances on each clip and turn off  (uncheck) every tab/section you aren't using. This removes those from wasting processing effort so if you're not using say HSL and Vignette sections on a clip, uncheck the boxes.

Those warp sections: I would advise doing a render and replace on those with JUST warp applied, then do Lumetri on the replacement media.

Any clip you have multiple Lumetri on, consider doing a render/replace also, and all render/replace do in the same format/codec settings of your final file, and turn on "use previews" in the export box.

Neil

Everyone's mileage always varies ...
mandicreally
mandicreallyAuthor
Inspiring
December 30, 2017

I tried going over to Mercury Software Acceleration through AME and even that failed.  So I may have some major issues I don't realize.  This is the first time I've worked on a sequence where I downscaled from 4k.

I cannot Render and Replace the Warp Stabilized clips as they are all on Nested Sequences and Render and Replace doesn't work on a Nest.  Had to Nest as I was downscaling clips and Warp won't apply to a downscaled clip (for some reason).

Working my way through the project and disabling any unused portions of the Lumetri settings now.  Also I deleted a couple clips and with the Warp on them and reimported them, trying to start fresh on the ones that I felt were likeliest to be an issue.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices