Skip to main content
goju
goju
Participant
November 10, 2016
Answered

Premiere Pro CC (2017) crashes at export

  • November 10, 2016
  • 20 replies
  • 48990 views

Hello

I've just started a Premiere Pro trial a few days ago and edited a video which I'm unable to export.

The export fails over and over again for the most part at the same point (34%..) The error code is 1609629690.

I'm using a Surface Pro 3 Core i5 running Windows 10. I tried to export at least 30 times with no success while changing parameters etc. As part of the mitigation I tried the following steps: Restarted my Surface Pro, rendered smaller segments in order to identify segments that may be causing this issue, removed suspicious still photos, tried different output types and tried to export based on previews.

I've worked with other editing software before and never had these problems.

Would appreciate any advice.

This topic has been closed for replies.
Correct answer Kevin J. Monahan Jr.

Goju has not returned since 2016, so this thread has become a proverbial dumping ground for all people having trouble exporting video from Premiere Pro.

A good number of solutions are given to this issue, so unfortunately, there is no one "magic bullet" to solve all export issues. Sorry.

Some things to try if you get an "Error Compiling Movie" error dialog box.

  • Delete Media Cache
  • Export to an intermediate codec like Cineform or ProRes instead of H.264
    • Create H.264 files from this master
    • Use smart rendering to make this process go much faster
  • Choose Project Settings > General > Renderer and choose "Software Only" — slower but bypasses the GPU which could be the source of your issue.
  • Remove GPU accelerated effects, like Lumetri Color effects.
  • If you have lots of large still images or 4K video in a HD timeline, consider
    • resizing photos in Photoshop to a smaller size
    • resize 4K video to HD in Media Encoder
  • Remove odd characters or punctuation marks in the naming of the file.
  • Make sure there is enough drive space available on the target hard drive for the export.
  • Copy/Paste clips from the problem sequence to a brand new sequence.
  • Delete any preview files.
  • Replace clips that seemed to have caused problems at the timecode indicated in the warning. It's possible that the clip is corrupt.

Hope these tips will help those finding this "dead thread" in search of a solution for exporting problems.

Thanks,
Kevin

20 replies

T
tooviikara
Participant
September 16, 2020

I had the same issue and I tried a lot of things as others did. But nothing happens It continuously crashed the whole time when exporting videos. Finally what happened was I add a new 240 SSD for the OS and the SW that I used(premiere) From there there is no crash.. still the rushes everything is in the HDD but I export and save the final out to SSD. I think all of the crashes people can try this. I think our old HDD can't transfer much data at a time or rendering time. I think a  bottleneck problem has happened that's why it crashed all time..

Kevin J. Monahan Jr.
Community Manager
Kevin J. Monahan Jr.Community ManagerCorrect answer
Community Manager
January 2, 2019

Goju has not returned since 2016, so this thread has become a proverbial dumping ground for all people having trouble exporting video from Premiere Pro.

A good number of solutions are given to this issue, so unfortunately, there is no one "magic bullet" to solve all export issues. Sorry.

Some things to try if you get an "Error Compiling Movie" error dialog box.

  • Delete Media Cache
  • Export to an intermediate codec like Cineform or ProRes instead of H.264
    • Create H.264 files from this master
    • Use smart rendering to make this process go much faster
  • Choose Project Settings > General > Renderer and choose "Software Only" — slower but bypasses the GPU which could be the source of your issue.
  • Remove GPU accelerated effects, like Lumetri Color effects.
  • If you have lots of large still images or 4K video in a HD timeline, consider
    • resizing photos in Photoshop to a smaller size
    • resize 4K video to HD in Media Encoder
  • Remove odd characters or punctuation marks in the naming of the file.
  • Make sure there is enough drive space available on the target hard drive for the export.
  • Copy/Paste clips from the problem sequence to a brand new sequence.
  • Delete any preview files.
  • Replace clips that seemed to have caused problems at the timecode indicated in the warning. It's possible that the clip is corrupt.

Hope these tips will help those finding this "dead thread" in search of a solution for exporting problems.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
A
AmySueJames
Participant
January 2, 2019

I know this was posted a while ago, but i figured my input would help anybody having the same problem. i have been dealing with the same problem for a while now, and i just fixed it. the problem isn't your computer, or the software. its the files, they are probably corrupt

A
AVI_Headache
Participant
August 15, 2018

This "Export Crash" issue has been around for a decade. I still use Premiere Pro CS5, and I occasionally get "unhandled" crashes (app disappears with no error message) when I attempt to open the Export Settings dialog.

Windows 10 updates seem to cause increasing instability with the legacy Adobe software.

My Fix:

  1. Open Premiere Preferences and clean the Media Cache Database.
  2. Open Project Preferences, set the Video Rendering mode from GPU Acceleration, to Software Only.
  3. Delete Previews when prompted.
  4. Reset the Video Rendering Mode back to GPU Acceleration.
  5. Delete Previews when prompted.
  6. Close and re-open the project.

Sequence(s) can now be exported.

F
FANX
Participating Frequently
August 10, 2018

I have a desktop PC  with 3770K OC 4.5G,  I had the same issue before, when exporting H264  Pr crashs all the time. But today i found that the problem is solved!   Just like i said, my 3770K was Over clocked, the voltage was set to 1.95 V.  I ran linx for 20 minutes and it reported a error. Then i set  the voltage to 1.23V and it works perfectly. After that i can export to H264 fast and stable!

H
harveyw
Participant
July 24, 2018

Export kept crashing at around 34% - 35% tried creating new sequences etc. The error message gave me a rough timecode where there was an issue in the error report. Exported that section and it was indeed the bit that was crashing. Re-imported & replaced those clips and now export seems to work.

V
ValdemarsHUN
Participant
May 29, 2018

Hello Guys,

I have a problem with premiere pro cc 2017 export. I started the render as Match Source - High bitrate, when the exporting around 80%, the normal render getting so f... slow. It has takes more than 10 minutes / percent. Anyone has a same problem?

System: Win 7

hp workstation z800

Xeon 2,67Ghzx2

96gb ram

gtx titan 980 6gb

Thanks

S
SergeiBoutenko
Participant
April 4, 2018

Guys and gals, I had the same problem and it was driving me nuts. Then I figured out that Premiere Pro CC 2017 doesn't like color corrected iPhone videos (or .m4v files). Once I deleted all my color effects from the .m4v files and saved my project, premiere stopped crashing instantly and I was able to export.

Hope that helps!

N
ND Strong
Participant
March 16, 2018

Okay everyone, I just talked to support (03/16/18) and the problem has an EASY fix (for Windows). Please follow the description below:

Open "File Explorer" > Go to "This PC" > Go to "Documents" > Go to "Adobe" > Locate "Premiere Pro" folder > Rename the folder to "Premiere Pro (old)" > Open Premiere Pro

This resets the preferences, but instantly fixed my crash issue. Your projects and files ARE NOT affected by doing this. Hope this helps!

Cheers!

    z_bird
    z_bird
    Participant
    March 14, 2018

    Yo I have been struggling with this problem all day trying tons of different things and finally found a true solution!

    I selected my entire project in the timeline and moved it about 30 minutes in. I changed my in and out to correspond with my project and hit export- it worked!

    Super simple solution to an incredibly frustrating glitch, just move your whole project way the heck down the timeline, if it worked for me it could work for you!

    Good luck ya'all <3

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