Constant crashing while rendering in Premiere Pro CC

Am trying to export a video from this sequence, Premiere Pro CC (latest) crashes every time after about 1-2mins of rendering.
"Error compiling movie.
Unknown error."
Premiere project is located on system SSD (late model Macbook Pro Retina), with source files on external USB3 HDD and cache set to external thunderbolt SSD. Have tried targeting all drives, same issues. Tried flattening all the multicam sequences, same issue.
No special plugins or anything used, just the baked in effects and settings.
Have tried rendering to h.264 and ProRes, both have the same error.
Aiming for a release of this project in the next few days, please help if you can! Thank you so much!!

After trying many many things, I ended finding two problems:
1. an image file CC didn't like, which I removed
2. some other error, unknown, but I rendered the entire sequence in premiere (pressing enter), and then exported to a file after it was fully rendered, and used the "use previews" option to export.
Very strange but so far this has worked.

Similar Messages

Premiere Pro and Media Encoder crash while rendering H.264

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!

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.

Premiere Pro CC Crashes While Rendering With Mercury OpenCL

Hi guys!
Every time I try to render a ~2 min video in H.264 using the OpenCL renderer which is fully supported on my 7970 (2x Crossfire) the program crashes while rendering. (Usually around 28%)
If I switch to Mercury Software renderer, it renders perfectly.
I am currently using AMD 13.6beta2 drivers, and PPCC is fully updated, any suggestions?
Additionally, for the half minute that it tries to render with OpenCL before crashing, by checking the GPU utilization % in AMD catalyst overdrive, it seems to not be utilizing the gpu at all... And then promtly crashes of course...
I hope I can fix this problem soon... Really dissapointed with this adobe product.
Thanks a lot!

Rendering without any effects ----------> Still Crashes
Disabling Crossfire ----------------------- > Still Crashes
Reinstalling Premiere ---------------------> Still Crashes
Physically Removing the 2nd GPU -----> Works
So, is there any way I can get this to work while having both GPUs physically installed in the computer?
It would be quite a hastle to remove the 2nd one each time I need to use PP!
One odd thing also is that from watching the gpu utilization while rendering H.264 1080p, the GPU is only being used to about 30%, and very intermittently.... I would imagine things would accelerate quite a lot if it actually utilized the whole GPU!
Thank you very much guys!

CS6 crash while rendering

Hi,
recently CS 6 crashes while rendering, this happens at the beginning (ca. 800 frames), i change from GPU to CPU, deletet the cache files, try a different sequence
with other videos, all the same
in task manager i can't kill the premiere prozess
after crashing only the power/reset button helps
the strange is, at the same time my complete network crashes to ??
Windows 7 pro
16GB RAM
Genforce GTX570 Driver 340.52
Intel i7-2600K
With Media Encore there are no problems.
can someone help me ?

The problem with PP CS6 crashing during render has increased from once in a while to where it cannot complete any renders.
---->>> Encoding to H.264 MP4. Seems to do fine on AVI renders. H.264 MP4 is the key to the problem. <<<---
The error that it is reporting says that the "output directory could not be found", but the problem is the same when rendering to a different (not RAID) drive. Does not crash with AVI render. Replaced H.264 Codec -->> No change. Crashed at 90% of a 50 second file render to lowest level MP4 file.
It is not the motherboard - Replaced Gigabyte with ASUS Sabertooth 990FX
It is not the CPU - Replaced AMD 6 core with AMD 8 core FX
It is not heat. Cabinet is cool, all fans are running, no dust, no blockage.
It is not power supply - Replaced 750 W power supply with 850 W power supply.
It is not memory - Increased memory from 16GB to 32 GB, Computer repair shop rotated and tested memory.
It is not virus (no email on this machine, current virus protection and security software).
It is not drive space - Increased RAID from 2TB to 8 TB - Problem actually got worse - (crashes sooner)
It is not the video card - drivers verified correct by Nvidia - (Quadro 4000) - tested by installing a different video card - No change.
It is not software install - Uninstalled total CS6 package and reinstalled.
It is not a specific render file - It will not complete any renders now.
It is not a recent software install - The only software that has been updated is Adobe but that was ruled out by the total uninstall/reinstall. Backup install on a laptop is able to complete renders on the files that crash on the "big" machine. Nothing new has been installed. Virus and SpyBot show "clear".
It is not the CUDA or Mercury setting - Tested with CUDA on and off.
It's not the Playback settings - Tested for GPU Acceleration and Mercury Playback Engine Software only.
It is not the C: drive - Replaced with SSD.
Ran while watching Performance Monitor - No hint of problem before crash point. (video available).
So, what are we missing?
Windows 7 Pro
64 Bit
32 GB Ram
8 TB RAID
ASUS Sabertooth 990FX
AMD FX8350 (8 core)
Performance Score: 7.1
Power Supply 850 W.

Media Encoder crashes when exporting from Premiere Pro

Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?

Try turning off GPU acceleration.

An error has occurred while opening the Premiere Pro CC 2014: Premiere Debug Event

An error has occurred while opening the Premiere Pro CC 2014: Premiere Debug Event
[c: \ cloudroom \ releases \ 2014.9 \ shared \ adobe \ mediacore \ mediafoundation\API\in
I don't know what to do, any help?

Delete the Effect Presets and Custom Items.prfpset, located in
C:\Users\<username>\Documents\Adobe\Premiere Pro\8.0\Profile-<username>
when succesfull make new project and import old one into new one.
Might need to reset current workspace and pull down the audiotracks first to reveal videotracks.

After Effects crashes while rendering

Hi all,
We have been experiencing regular crashes while rendering on 9 different Mac systems.
We would start the render and then, all of a sudden, AE would crash.
Trying to restart, AE hangs at MediaCore initializing.
We actually need to do a hard shutdown to get the machine to reboot.
So my question is:
Could AE not release the media cache upon crashing thus blocking us to restart the app without having to reboot the machine?
We are running AE in multiproc mode with 4 GB memory allocation, which actually uses 3 procs.
I have tried bringing the memory allocation down to 3 GB on some of the systems, but it doesn't seems to make much difference.
Finally, we do not crash every time we render. It is very random.
Any ideas?
Thanks,
Rene

Hey Todd,
Sorry for the late reply, answers below:
What exact version of After Effects? 12.2.0.52 but we also use CS 5.5 (mainly for the feature where you can send your camera information to C4D, something that is not in the CC version... pitty)
Have you installed the recent updates? This is the latest update...
What operating system? Mac OSX 10.8.5
Tell us about your computer hardware. 2 x 6 cores CPUS, 24 Gb RAM, ATI Radeon HD 5870 GFX, 5 internal drives (4 of them are part of internal hardware raid with internal raid controller)
What versions of drivers for your graphics hardware do you have installed? No CUDA since it is ATI, 01.00.436
Do you have any third-party I/O hardware : AJA Kona 3G with either driver 1.47 or 1.49
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. It is a combination of a bunch of them: Animation codec into .mov wrapper, tga sequences, png files, we render to uncompressed .mov files for air.
If you are getting error message(s), what is the full text of the error message(s)? No, just the beach ball of death...
What were you doing when the problem occurred? They mainly occur when rendering sequences.
Has this ever worked before? It is very intermittent and does not happen every day. Plus, since we are in crunch time, AE is being used 24/7, so that may not help either.
What other software are you running? C4D, Photoshop, Illustrator, both in the CC and CS6 or CS5.5
Do you have any third-party effects or codecs installed? We have sapphire and Knoll lens flare, but crashes happens if we use them or not.
Are you using OpenGL features in After Effects? Not to my knowledge.
Does the problem only happen with your final output, RAM preview, or both? Render
Are you using Render Multiple Frames Simultaneously multiprocessing? Yes we do, most of the machines have it set with 4Gb memory allocation, but others have it set to 3 Gb.
Are you using the ray-traced 3D renderer? No, we are not.
If the problem is with output, give your exact output settings (both render setting and output module settings). Unfortunately, I do not have this as our artists are working and I cannot really stop them as we have things to get out to air for early morning. I will get this info next time we have the issue.
What is the exact sequence of steps that you are taking? Just sending the render out to the queue and starting and it will either crash to desktop or stay there doing nothing.
My biggest concern is why can't we just restart the app. It will always lock up while initializing MediaCore. We have our mediacaches set for 42 Gb on our main bootup drive, which is big enough to handle it. And after the crash, when we try to reboot, the machine will get to the grey Mac screen and just sit there. Have to hard shutdown the machine to have it come back up...
Let me know if you need more info.
Thanks,
Rene

Dreamweaver CS6 crashes while coding on Mac Pro with Yosemite OS

dreamweaver CS6 crashes while coding on Mac Pro with Yosemite OS
CS6 updated to latest
OS updated to latest 10.10.2
Java updated to latest
removed preferences
Still crashes continuously while coding without any alerts
Any suggestions

zayedhd wrote:
dreamweaver CS6 crashes while coding on Mac Pro with Yosemite OS
CS6 updated to latest
OS updated to latest 10.10.2
Java updated to latest
removed preferences
Still crashes continuously while coding without any alerts
Any suggestions
That could be the problem. If you actually mean DWCS6 and not DWCC 2014.1.1 when you say "latest" (check out Help > About Dreamweaver for your actual version) it requires the older Java SE 6 to be installed on the Mac. See if reinstalling it helps...
Java for OS X 2014-001
If you're using DWCC 2014 and updated your OS after having DW installed, you may need to reinstall to work out the kinks. Using the Cleaner Tool from Adobe to reinstall will give you a completely fresh installation...
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

Adobe Premiere Pro CC - Computer Crashes While Rendering/Exporting.

My computer crashes when exporting/rendering. I don't know why it is doing this. Please help!

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Adobe Media Encoder pausing rendering while working in Premiere Pro

Hello everyone,
So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
Has anyone ever seen that?
I use Windows 8 and Adobe CC.

Hi Rallymax,
Yes I do queue footage by having an Autowatch set up on the directories where the video is written to. I rarely do a direct export unless testing new settings.
Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export. Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
Adobe Media Encoder
The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
I will try the same test as Jason, if I can find any AVHCD video and see what the results are. Will be interesting.

Premiere CS5 crashes while rendering the timeline

Hello
I recently moved to CS5 Premium Production Suite and a new HP Eltie 8100 PC i750 8 GB RAM and the graphic card is a Nvidia FX-580. In addition I work with a Blackmagic Design Multibrigde Eclipse. When I work in project, it doesn't matter what kind of resolution HD or SD, in most cases when I render the project a failure message appears on the screen "Microsoft Visual C++ Runtime Error Program:c\Program... R6025 pure virtual function call". After that windows 7 64 Bit looks for a solution but can't find anything and the application Premiere Pro CS5 will be quited!
I tried to installed an older version of the Nvidia card driver coming originally from HP. Driver Version 8.16.11.9189. But also this made no changes in result. So the question is, do CS5 Premiere anything wrong in calling some forbidden code? Or is it a Win 7 OS bug?
Do anyone know something about this failure? I also have updated to the latest Abobe software 5.01 for Premiere but no changes.
Thanks for help

Yes it's a legal copy. Everything I have on the computer is legit here at work. I've never liked building an editor on my Dell machine. I always seem to have various errors no one else seems to have. I don't use security software on it, no email and limited internet activity except to update programs. Most of the time the machine and Premiere behaves well. Even editing goes great, but the time line render is impossible. I use the most Current Cineform plugin and edit both HDV and converted Canon 7D footage. In either fashion, rendering doesn't work. Even without the Cineform plug-in, just using the presets from Adobe, I can't render out a file. Very Frustrating.

Rendering in Premiere pro

I'm on a mac 10.6.8 CS5
three times now while working on a project I get a unknown error compiling message when rendring the work area in a sequence. The only way I can solve this is to open a new project and cut and paste the edit from the sequence. and starting a new project involves doing more unnecassary work
I've tried deleting rendered files, I cant change the mercury setting in renderer- its not slectable. I've tried cut and pasting onto a new seq in same project.
what am I doing wrong?
thanks

I have NO idea if anything here will help with a Mac... but some links I've saved
Error Compiling Movie http://kb2.adobe.com/cps/906/cpsid_90670.html
-and http://premierepro.wikia.com/wiki/Error:Error_compiling_movie
-and http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-rendering-or.html
-and nested sequences http://forums.adobe.com/thread/955172

FinalCut Studio crashing while rendering

On 2 different machines, a 2007 MacPro (6gb ram) and a 2008 Macbookpro (2gb ram) I am converting Go2meeting wmv files into h264 files for posting to brightcove.
While rendering the movies, at completely random intervals, I'll get an error message as below:
"Codec not found. You may be using a compression type without the corresponding hardware card."
This will happen while it is in the middle of rendering one of the WMV files. (no cmyk files in the wmv file)
On the Macpro desktop, I'll be able to save before Fincalcut completely crashes, on the Macbook Pro, the program will crash as soon as I hit the 'ok' button.
It takes a huge amount of time to render these sequences, and is irritating when I lose an entire night to one of these crashes. Any idea what may be causing them?
Addition info: running 10.6.4 on the desktop, 10.5.8 on the laptop, Flip4Mac, perian on both.
Message was edited by: rick knecht

The Liberator wrote:
I says every time it was due to the Perian plug-in. ..
.. I spoke with the IT guy, and he thought that is was just a simple thing of not having the video in NTSC H.246 and instead having it in PAL in DV.
you get a specific error-message, naming perian as source of error? never heard of that!
what do you try to accomplish, I assume Exporting with QT-conversion.. what settings?
perian adds a few codecs to the QT-engine, which are 'Mac-exotic', mostly divx ..
when you install other, addiional divx-plugins, e.g. for Flip-camcorders or the 'free' XviD, you get a conflict => errors.
your 'ITguy' should quit his job ... - in video editing, you don't switch standards & codecs 'like the wind'.
example: a 30fps/h264 is by many factors smaller than a 25fps/dv .. aside, you have (dramatic) losses of pic quality, by scaling the framerate ..
tell your 'ITguy', in which standard you're working, and for sure you want to export with corresponding settings.. it is HIS job, to make things done flawless .. he should 'clean' the QT-plugins to the few needed ones, not all he could get from the internet.
... The usual Admin-from-****-behavior to tell the user, s/he should change settings, not him..
your Mac/FCE DOES export in many standards.. just to mention that..
what are your sequence' settings, by the way... ?

Premiere cc 2014 crash with message "Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again."

I updated to Premiere Pro CC 2014, all the other Adobe CC 2014 software works great, but Premiere doesnt even load. The starting page (frame) comes up - my whole computer slows down and after a minute or two it crashes completely and comes up with the message : "Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again."
I'm running a macbook Pro 15" (2014) with 16GB RAM and 760GB SSD.
PLEASE HELP!

Hi Delarey,
Please go to the following location and rename the folder to old_folder name
User/user library/Application Support and rename Adobe folder
User/user library/Preferences and rename the Adobe folder
Then go to Documents folder and Go to Adobe/Premiere pro/8.0 and rename 8.0 folder
Make sure that you are in user library if you are not sure check the link below.
Access hidden user library files | Mac OS 10.7 and later
Regards,
Vinay

Bridge CC crashes when opened in Premiere Pro CC

Bridge CC tends to crash regularly when open in Premiere Pro CC. Sometimes it takes longer to crash than other times. sometimes it doesn't crash at all but it appears if I leave both programs open for an hour and then come back to work on a job it will crash in the middle of looking at footage to import into premiere. Is this a bug or is there some way to fix it on my computer?

Need more info. What OS and ram?
Bridge is a processor intensive program and if processing video in Pro CC it could starve computer for resources.

Constant crashing while rendering in Premiere Pro CC

Similar Messages

Maybe you are looking for