Skip to main content
New Participant
September 4, 2013
Question

Premiere Pro and Media Encoder crash while rendering H.264

  • September 4, 2013
  • 13 replies
  • 51057 views

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.

It's only while rendering H.264 - other formats seem to work fine.

And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.

It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.

I've tried disabling CUDA and my overclock to no avail. Please help!

This topic has been closed for replies.

13 replies

lucasp40979045
New Participant
May 14, 2017

I'm having the same issue. I've tried all (not all actually) the tricks written on this page and nothing...

It's interesting that some who had this problem could solve it with a "weird solution", such as removing or downsizing a JPG or something. I could find on Youtube a guy who disabled his Bluetooth device before start the export process and it worked for him.. I mean... it seems that everyone has to find it's own way to make it work. All this information makes me think that i'll have to pick another SW editor to work =( because it looks like a lottery.

The only thing i did not try was change my power supply.... I have a 500w real.

Here's my settings:

Intel i7 4771 3.50ghz

4 GB RAM

Windows 10 Pro 64 bits

GTX 1050 2 gb

And i'm not going to change my power supply bcause I can barely see any solution coming from it, just like many others...

Well, it's more about a vent instead of a helping ask... but if someone has the another solutions pls tell me.

----------------------------EDIT-----------------------------

I Found out that I can export my video choosing the option AVI (Uncompressed). This generates an extremely huge file. My 14 minutes long video was transformed into a 72GB avi file. For now it doesn't matter. After that I opened the avi on Media Encoder and tried to convert it with H.264. For my surprise it worked better, it reached about 70% of the process, but then again, it crashes the computer. Everything stops.

Could it be a problem with codecs or something? Should I install a package?

----------------------------EDIT2--------------------------

So, Here's the thing.

I Continued trying export from Premiere, without Media Enconre. I'm making some tests with different length videos.  I could get some information from it.

In tiny length videos, the export process goes with no problem I tried many times 30~80 seconds video. With videos above 1 minute it goes bad. Then i repeated with a long video but this time I increased the velocity of my GTX 1050 fans with the MSI Afterburner and also increased the fan of the CPU cooler, the intel processor cooler with SpeedFan both over 100%. Doing that made the export process go further, I got 40%, then it crashed again. Does it has to do with the problem?  I don't think that my GTX 1050 is a bad Card, or even my i7 processor, but why they lead the process go longer then? After changing the speed of the fans I got a 23 C° on my CPU, which is super cold. The normal is between 40~48Cº.

Thanks

lucasp40979045
New Participant
May 16, 2017

Hey! I finally could solve my problem!!! I've just installed a codec. H.264 | DivX.com

Even with CUDA, with a lot of files on Media folder and many other, i finally could get this done with this codec. I don't know actually what to think... Should I still belive it's a lottery or I'm too naive to miss the packages of codecs that are necessary to do so?

Bye

Participating Frequently
October 8, 2017

None of this works for me. I installed H.264/DivX.com. but I can't find it in premiere pro export codecs.

Known Participant
September 15, 2016

I have had this problem on and off since starting to use PPro Creative Cloud.  I was very hopeful that the latest version (Sept 2016) would solve this problem, but it has not.  My work-around is to render in two steps.  The first step is to render to QuickTime 422, and the second step is to render the QuickTime file as H.264.  Of course this makes it impossible to publish to YouTube in a single step, which is extremely annoying.  And it means I need 5x more space on my render drive for intermediate files than for my final renders, which is also extremely annoying.

New Participant
February 5, 2016

I'm not sure if everyone has found this issue to be resolved, but I wanted to let you all know that the above fixes did not work for me, however I finally figured out a solution that did.


My timeline would render through just fine, but would crash while exporting to H.264 (I did not try other file types) and every time it crashed it was at 46% (or 92% if I did single pass VBR).


I realized the problem was a JPEG I was using at the end of the video. The resolution was too big and it was crashing Premiere. I brought the file into Photoshop and changed it from 600dpi to 300dpi. Re-imported to premiere, exported and presto!


Not sure if this will be the solution anyone was looking for, but figured I'd still share.


Take care,


Tim

New Participant
February 6, 2016

Had same issue with a large PNG, reduced the image size, solved the issue.

Thanks for the tip.

New Participant
September 11, 2015

I was having the same issue exporting a 45 second video with the latest version of Premiere Pro CC 2015 running on a new iMac w/ OS X Yosemite 10.10.5 and a Nvidia graphics card. No video plug-ins installed.

Tried many of the steps above: cleaning cache, exporting via Adobe Media Encoder, etc without any luck (although at one point, by some miracle, I was able to export the project successfully, though the export failed after I tested the export a second time.)

I finally phoned Adobe support and was connected with someone almost immediately.

I shared my screen with the support agent, and after about 45 minutes of adjusting a number of settings, we successfully exported the project without any freezes.

A lot of what we changed was a little over my head, but basically he somehow determined that some effect I had used was not cooperating with my graphics card.


He saved my project as a new project and then made sure my sequence settings used Quicktime + Apple Pro Res 422 under Video Previews.

Next he re-rendered the project from in to out. This took about 5 minutes. (45 sec project, 1080p, mostly MTS files, one .MP4 file, and a .mov file that had been rendered out from AE).

He then went to File/Preferences/Memory and changed "Optimize rendering" from "Performance" to "Memory."


Finally, he exported the project using the Apple Pro Res 422 codec.


I apologize that this answer is a bit vague, but I think it's safe to say that this is a graphics card issue that can be resolved. Call Adobe support!

Jian3672
Participating Frequently
October 7, 2015

Apple Pro Res 422 codec isn't listed on my PPCC2015

New Participant
October 11, 2015

I believe you may be able to download the codec from Apple, though I'm not entirely sure.

After my original post on 11 September, I actually began to encounter the errors again in the same project. While the constant freezing is incredibly annoying, I figured the following work around:

1. Any clips or media that are on your timeline but are outside of your in/out points should be moved over to a new sequence. In other words, remove anything from your timeline that won't be included in the final export. Just duplicate your sequence then remove the excess media from the original.

2. Render out everything left on your timeline.

3. Save your project and close/quit Premiere.

4. Open Premiere. Re-open your project if Premiere does not do this for you automatically.

5. Export your media as you usually would.

This solution may not work for everyone, but basically I've found that rendering everything and restarting Premiere before going to export does the trick.

jeff4083402
New Participant
September 3, 2015

I also will reply, if this helps others.

I was able to solve the issue of Premiere Pro.  After spending hours working with Adobe support, they were not able to identify what was wrong.

I am running a newer 8core 4.6ghz AMD processor with 2gb video card and 32gb RAM, but why was PP crashing when editing a video?

I figured out that if I copied all my project files to the local SSD drive, and did not have any working files on a local standard harddrive or usb drive, then it worked fine.

So now I just move all my project files off of usb and regular drives to the local SSD drive before I start a new project, which is the same drive where Windows and PremierePro is installed, and then it works fine without crashing or other issues.

Just wanted to share, and hope that helps.

Participating Frequently
December 14, 2015

THis was the answer for me and I knew better but was being lazy!

Keep all your files in the same directory on the same ssd drive!   TY

Participating Frequently
December 14, 2015

‌ANd export to a different sad drive too if possible!! ;-)

New Participant
August 4, 2015

Oop! Whadya know!

New Participant
August 4, 2015

Well that ROYALLY messed up my project! Now most of my footage is unlinked, when I try and link it up it tells me that the audio is not detected and that if I continue the deletion of the audio track cannot be undone. Then there is the whole crashing every time I try and relink it up anyway to try and build everything back up. So what on earth am I supposed to do NOW!

CBCreator
New Participant
May 27, 2015

I was running into a similar problem - fortunately cleaning the media cache database and trashing the preferences worked for me. Hope others who this doesn't work for can find a fix.

thnord
Adobe Employee
Adobe Employee
June 3, 2015

So I'd like to take a crack at getting to the bottom of these issues. To do that, I'd like to gather some more information. Please be as thorough as possible as it will help us better understand what's going on so we can investigate any bugs.

  • What version of Premiere Pro/AME are you using?
  • What type of system are you on? Hardware, OS (please be as specific as possible)
  • What is your source? Is it a Premiere Pro sequence?
  • Have you ever reproduced with anything other than a Premiere Pro sequence (ie. just a single file being transcoded in AME)?
  • What type of media is in your sequence?
  • Are you using any 3rd party effects in your sequence?
  • Does the problem go away if you export to another format? If so, a possible workaround for the time being would be to export to an intermediary format then transcode that file to h.264.
  • It is also helpful to distinguish between rendering and exporting. Please let us know if you see the crashing when rendering your timeline or exporting either through Premiere or Adobe Media Encoder (or both).

As noted above, trashing your preferences may resolve the issue:

1. To trash preferences, hold down the Shift key while launching Adobe Media Encoder.

2 (mac). To delete the Media Cache on the Mac, navigate to: (your user directory) > Library > Application Support > Adobe > Common > Media Cache Files, and delete the contents of that directory.

2 (win). To do it on Windows, go to: (your user directory) > (your name) > AppData > Roaming > Adobe > Common > MediaCache and do the same thing.

One other possible solution: Look at your sequence and find any gaps between clips and replace them with black video. This has caused issues for some users in the past. Please let us know if that resolves the issue.

Participating Frequently
July 20, 2015

I am also having this problem. I had no issues at all using Premiere CC 2014 but after the upgrade, it closes when I try to export.

I will try some of these suggestions but I am disappointed that this is sucking up so much of my time.

InterimAD
New Participant
May 21, 2015

Hi All,

I have exactly the same behavior - Premiere Pro CC crashes during rendering and export. I have a iMac 27" with:

Model: iMac14,2, BootROM IM142.0108.B02, 4 processors, Intel Core i5, 3.4 GHz, 8 GB, SMC 2.15f2, TOSHIBA 512GB SSD

Graphics: NVIDIA GeForce GTX 775M, NVIDIA GeForce GTX 775M, PCIe, 2048 MB

• The Adobe Premiere and all other CC Programs are all updated

• I tried it with CUDA, without (per Software and OpenGL rendering)

• I erased the Premiere cache and started with Shift + Alt

• I make a complete new project and sequence and tried to export old films, that I exported before

• I deinstalled CUDA

• The Adobe folder inside the preference folder (Library) is set to read&write for me 

• The hard drives are all checked with disk utility

• The OS X is Mavericks and started several times with cmd + alt + p + r for cleaning the processor ramm

• My iMac is clean and stays cool during rendering and exporting

What else can I do?

analytical_solution157F
New Participant
April 11, 2015

I just started having this happen, and I may need to re edit a whole f-ing project in the next day if Adobe doesn't take care of their problem. Not happy.

humanbeing00
New Participant
April 12, 2015

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?

I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).

Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.

I cant even

If I find a way to fix either of these problems, I will post straight away.

humanbeing00
New Participant
April 12, 2015

So Adobe has updated the cross-same-version compatibility problem. Projects can now be opened on other systems on Windows or AppleOS. Might have helped that I logged in at the create project screen and transferred my settings across to the system I am on at Uni.

As for the rendering problem, I will try to figure out an answer to the problem beyond just saying that the highest you can render is H.264 720p 25.

Good luck to you all