Premiere Pro CC 2014 Crashing with rendering, freezing system, and more

Hello,
I'm having some serious issues with Premiere pro on my late 2013 iMac.
OSX 10.9.5
3.2GHz Intel Core i5
16GB 1600 MHz DDR3
NVIDIA FeForce GT 755M  1024MB
I'm working in 1920x1080 23.976fps. Media files are from sony FS700 .MTS and Cannon 5DmkIII .mov
Multiple times per day, PP crashes on me. It all started when I was getting really choppy playback which would be accompanied by this error message:
A Low Level Exception has occurred in ImporterMPEG (Importer)
This would soon after lead to the program freezing and me having to force quit the program. After contacting Adobe the first time about this persistent issue, the tech explained to me that it was a "Memory Leak" issue and that there was nothing that could be done. After the support team member ended our chat online before helping me solve my issue, I called support. I provided my case number and this person picked up where the helplessly left me and did the typical Adobe one fix all: He went into the hidden library and cleared all of my preferences, removed any third party plugins, and cleared the files in the root applications Adobe folder, renamed a folder "Adobe.Old" etc.
As I explained to the support team member on the phone, this is not a solution but rather a bandaid until it happens again.
Low and behold it has happened again. This time the support team member had me create a new System Administrator account on my computer thinking that there was a permissions problem with my other account which was conflicting with PPCC2014. While this was a major pain to switch between the new account and any other program that I had set up for day to day work, it allowed me to continue editing and at least (at a less efficient rate) get things done.
Now, while using my new System Administrator account, I am getting terrible crashes that not only stall the program, but force me to hard re-boot my computer. These crashes are accompanied by a terrifying looking screen that I was only able to capture once.
They've only become more intimidating as now I cant even see the program when this happens, but this is the only screen capture that did not turn out completely black.
I'm looking to see if anyone has had any extreme issues like this and if so how they were able to fix it. I've now spent 6+ hours with support and after the last one was told I would receive a personal email follow up by the end of the day (never happened) to take further actions based on the performance after the new account creation.
I need help. Now.
-John

Hi John,
First of all, try this: Re: A low level exception occured in: Importer MPEG (Importer)
Next, make sure that if you updated OS X to 10.9.x, or later, you must check the following each time you update: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Other things to try:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Delete media cache
Remove plug-ins
Repair permissions
Disconnect any third party hardware
Remove QT components from Mac HD > Library > QuickTime
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin

Similar Messages

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Premiere Pro CC 2014 crashing constantly

    Premiere Pro CC was great. Premiere Pro CC 2014 is not so great!
    Constantly crashing every time I go to render after a while.
    It happens so inconsistently I cannot explain.
    I wish Adobe would see this post and contact me to resolve.
    We pay for 5 seats every month and should not have to deal with software crashing constantly.
    Thanks,
    J

    Hi, I have the same problem too.
    Premiere pro cc 2014 crash constantly. I found problem in the overflow of RAM when I quickly scan (review) my clips on the timeline or resize the clips.
    My configuration:
    Premiere pro cc 8.1; 16Gb RAM; SSD 120(where i store and work with my video); CPU Intel i72700K; Windows 7 Pro x64

  • Premiere Pro CC 2014 crash when I Click and Drag

    Hi All, I have a problem with Premiere CC 2014 that is driving me crazy!
    The issue is as follows:
    If I try to drag a clip, sequence, effect or transition anywhere within the premiere, it will crash - with "Sorry, a serious error has occurred" message. The program will crash, quit and the saved recovery project is usually healthy (luckily!). BUT, as soon as I've re-started the program, and reloaded the project - or any project for that matter - the problem persists. As soon as I click and drag, Premiere crashes!
    In order to 'reset' this, I have to restart my machine. Once I have done so, I can continue editing as normal for a while (not long, perhaps up to an hour, or so) but eventually, it WILL crash again. I've not been able to work out what I have to do in order to trigger this - it seems random. But once it's happened, only restarting my computer will resolve it - and then only temporarily.
    Here are all the facts:
    The crash ONLY happens when I drag something... This can include moving a clip on the timeline, dragging a clip form the source viewer or project window, dragging an effect or transition.
    The crash happens after I have clicked, as soon as I start to move my mouse.
    I CAN click and drag to extend in and out points on the timeline, and I can do 'insert' edit using the button on the source monitor. No crash here.
    The footage plays fine.
    I am trying this on a CLEAN OS X install, with only Adobe packages installed, to eliminate any potential of interference from other programs. There are no third party plugins or drivers installed. No user data installed either (preferences, photos, documents, etc) - as fresh as it comes!
    I am not running Time Machine in the BG
    My system is: Macbook Pro 2011, 16GB Ram, 1tb SSD, OS X Yosemite 10.10.1. Intel Graphics card, so no option to turn on or off hardware acceleration. It is set to software only.
    I have tested this with projects and footage on an external drive, as well as internal, same issue.
    I noticed the issue had started on, or around 25-27th November 2014.
    Interestingly, I have noticed that once this crash has occurred in Premiere, a similar problem will occur in After Effects as soon as I drag a file or layer... doesn't matter what the layer is. The crash seems less elegant here, I don't get an error message, it just freezes and I have to 'force quit'. Again, the problem persists until the machine is restarted.
    I have been using my macbook and premiere pro cc 2014 on Mavericks for a long time, and had no problems - so I know it should work fine! The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups, I installed a few new fonts and any CC updates that happened in the background... I can rule out most of these because of my fresh install, with no user data, fonts plugins or time machine to confuse matters... It must be an Adobe bug with Yosemite!
    Any ideas?
    Thanks so much in advance!!

    Hi Vince,
    vince_email wrote:
    ...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
    Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
    Thanks,
    Kevin

  • Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

    After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
    Believe me, there's hardly a thing I haven't tried.
    It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
    Also I know I'm not the only one who's having these problems.
    My specs are:
    OS X Yosemite 10.10.1
    MacBook Pro (Retina, Mid 2012)
    2,3 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    NVIDIA GeForce GT 650M 1024 MB

    Hi JJ,
    JJ Millen wrote:
    It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
    One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
    Now that we have that sorted out...
    JJ Millen wrote:
    I checked that and it says 8.2.0. (65) build.
    Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
    JJ Millen wrote:
    Here are all the checkpoints mentioned in that thread, applicable to my project:
    - Version 8.2.0;
    - My Creative Cloud says Premiere Pro is up-to-date;
    - Operating system is OS X Yosemite version 10.10.1 (14B25);
    Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
    JJ Millen wrote:
    Type: MPEG Movie
    File Size: 4,0 GB
    Image Size: 1920 x 1080
    Frame Rate: 25,00
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:12:35:16
    Pixel Aspect Ratio: 1,0;
    So is this H.264? What is the camera that you are working with? DSLR?
    JJ Millen wrote:
    - I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
    What kind of drives are the media files stored on?
    Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
    Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
    JJ Millen wrote:
    - The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
    When you import clips, are you using File > Import, or are you importing via the Media Browser?
    JJ Millen wrote:
    - Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
    Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
    JJ Millen wrote:
    - The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
    - I currently have no third-part effects or codecs installed in Premiere;
    - I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
    - The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
    I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
    Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
    JJ Millen wrote:
    Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
    So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
    JJ Millen wrote:
    Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
    I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
    For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
    Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
    It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project

    We have been working in Premiere on this documentary film for months.
    As we reach completion it is beginning to really bog down and crash a lot.
    Equipment is
    iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
    Apple Cinema HD Display
    32 GB 1600 Mhz DDR3 RAM
    NVIDIA GeForce GTX 780M 4096 MB Graphics Card
    1TB internal SSD Drive
    We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
    The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
    We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
    Any advice on how we can manage this crashing and freezing problem would be much appreciated.
    We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
    Here are things we have done:
    Made a smaller timeline because we were working on one that was the entire movie.
    Turned off the secondary monitor and unplugged it.
    We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
    Any recommendations would be greatly appreciated.

    Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
    Tweaker's Page ...
    http://ppbm7.com/index.php/tweakers-page
    And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
    I think this would be good for you right now ... you need to get stuff done, not guess & try things.
    Neil

  • Premiere Pro CC 2014 crash and crash, and crash....

    Kevin and all you other Premiere Pro CC people out there.
    How long before Adobe will solve the problem of Premiere Pro crashing over and over again.
    I guess there is no one reading this that could tell me "it works for me".
    So Kevin (staff),
    Here is the 36-line-report you requested from me.
    For your information. Premiere Pro CC 2014_2 and back paddling to 8.0, they all crash.
    Most crashes are freeze on timeline. Thats is, nothing moves, sometime the music track
    just keep going and you can't stop it, so you have to hard quit.
    My power: Mac Pro 2014, 6 core, dubble graphic card, 64 GB memory, 1 TB SS storage
    This is my latest report:
    Process:               Adobe Premiere Pro CC 2014 [717]
    Path:                  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:            com.adobe.AdobePremierePro
    Version:               8.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    Hi,
    Sorry to hear about the experience. Can you please try this:
    Go to the following locations:
    Location 1: When in Finder, click on Go > Go to Folder > ~/Library/Application Support/Adobe
    Location 2: Go > Go to Folder > ~/Library/Preferences/Adobe
    Location 3: Documents > Adobe
    In all the locations, rename the 'Adobe' folders to 'OldAdobe'
    Launch Premiere, accept the License Agreement and see if it works.
    Note: You will lose your customized workspaces and keyboard shortcuts. Wait for Premiere to generate the media cache the first time you launch the project.
    Also i would suggest you to make this change if the playback issue continues and see if it works better:
    Under File > Project settings > General, change the Video renderer to Mercury Playback Engine software only. Click OK and select "Delete Previews"
    Thanks,
    Rameez

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • Premiere Pro CC 2014 Crashing on Start Up

    After installing Premiere Pro CC 2014 on my mac i opened the app but with in seconds of opening its crashed with this message '[/cloudroom/releases/2014.09/shared/adobe/MediaCore/Utilities/QTParser/Src/QTTrack.cpp-5 08]'
    It does this every time i open the app. Any ideas?

    Hi Nerd03, I have a similar problem on Windows which could relate to the issue discussed here:
    https://forums.adobe.com/message/7026671#7026671
    Do you get a starting screen or does it crash before you are asked to create a new project or open an existing one?
    I filed a bug report for mine on the Adobe bug form. Maybe worth monitoring the other thread for any news on this.

  • Premiere Pro CC (2014) crashing when making a sequence

    I just did a clean install of OS X Yosemite and installed Creative Cloud on my 2008 MacPro. Every time I make a new sequence or open a saved Premiere Pro CS6 project, Premiere Pro CC 2014 always crashes. I am not sure what is going on because before I updated OS X from Mavricks, I used Premiere Pro CS6 with no issues at all. Please help! Thanks!
    Here are my MacPro settings:
    Here are the errors I am getting:
    That blank space usually says this:

    Ok I have seemed to "fix" the problem. I have two video cards on my MacPro:
    I have a three monitor setup with two monitors on the 2600 XT and a single monitor on the 6870. I unplugged the two monitors on the 2600 XT and created a new sequence and it didn't crash. Not quite sure what is going on with this because this was never an issue while I was running Adobe Premiere Pro CS6. I still do want to run a three monitor setup but the 6870 doesn't want to support three monitors. Hopefully there is an update from Adobe that will fix this issue.
    Is there a way that Premiere will not try to use the other video card?

  • Premiere pro cc 2014 crashing my system

    I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
    it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in.  Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
    and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
    angry and frustrated here.
    Sean

    Somewhat figured it out and extremely frustrated.
    I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
    administrative priviledges.  On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
    I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
    I was very angry and upset with the Adobe technical support for this issue.
    On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
    However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away.  Not too interested in working on 2 different accounts either.
    Not sure what to do now and i am extremely frustrated.

  • Premiere Pro CC 2014 crashing on app startup, solutions exhausted??

    I've seen similar fixes offered for this but I've tried all to no avail.
    PPro CC 2014 version crashes on startup, right after the splash screen.  Doesn't get to the actual application, just instantly whites out with "Adobe Premiere Pro CC 2014.0 has stopped working".   Here's the problem details log from Windows:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.1.21
      Application Timestamp: 53c7b17f
      Fault Module Name: dvaui.dll
      Fault Module Version: 8.0.1.21
      Fault Module Timestamp: 53c76970
      Exception Code: c0000005
      Exception Offset: 00000000002f4e39
      OS Version: 6.1.7601.2.1.0.256.48
      Locale ID: 1033
      Additional Information 1: 4d34
      Additional Information 2: 4d34d3a7ae19b5763432cd60b19af792
      Additional Information 3: 0fe8
      Additional Information 4: 0fe86a744bc3a8e89178eceb53cd1d4c
    I've taken the advice of others and uninstalled PPro CC 2014, restarted, updated my Nvidia drives, restarted, reinstalled PPro CC 2014, restarted, attempted to run application but same crash persists.  Others also said something about changing permissions to "something";  I tried changing permissions to the cache folder I use but not sure how relevant that is, nor what to EXACTLY change for permissions, IF that's the problem.
    Any advice, experience with this problem, or discussion would be appreciated.  Thank you!
    UPDATE 7/27/14
    Uninstalled ALL Creative Cloud components / applications completely,  used Adobe CC Cleaner Tool to clean out remnants of cloud.  Reinstalled only PPro and Media Encoder 2014 and same thing happens for PPro, crashes instantly on startup.  I did, however, get some interesting weird Encoder errors and failures during its installation via Creative Cloud desktop.  Here are some photos of the error log:
    I feel that something is wrong from the very start, perhaps something within dynamiclink that crashes PPro / also gives install errors for Encoder. 
    Any help or thoughts are appriciated!!!

    UPDATE 7/28/14
    The preferences suggestions is indeed where the problem was. In my case, there was a Premiere Pro preferences folder that was in conflict with an earlier PPro pref folder under the Windows 7 Sync Center. I guess thats the Windows equivalent of Mac preferences issues, so be sure to check if you have any syncing conflicts, I suppose, lol. Hope this helps anybody with similar problems out there!

  • Adobe Premiere Pro CC 2014 crashing

    Hello,
    I'm using MBP with OS X 10.9.4, 16GB of RAM with two hard drives, 480GB Sandisk SSD and the stock 750GB HDD.
    My MBP is Early 2011 (8,2) model with AMD Radeon HD 6750 graphics card along with Intel HD 3000. I'm using external 27" Thunderbolt display with a resolution of 2560x1440. My project is set to use the OpenCL Mercury acceleration.
    The video files I'm editing are Apple ProRes 444 sitting on the HDD drive.
    My Premiere Pro CC 2014 keeps crashing all the time. Today it crashed 3 times, telling me a serious problem occurred and that Premiere must shut down. It managed to save the work. On the fourth crash, the application simply refused to play any clips, I tried to quit it, but it wouldn't, forcing me to force quit the application.
    Another thing I noticed is that once I click on "open project" from the start screen it takes something like 5 sec. before the project appears. It's a small project so it should open immediately, the way it used to open in the past.
    If it's relevant, I have only one installed plugin for Premiere and it's Neat Video Pro.
    I don't know what's going on but Premiere Pro (CC, the one before CC 2014) used to be rock solid on this machine.
    I'd appreciate any help with this issue since obviously something bad is going on.
    All best,
    Goran

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • Premiere Pro CC (2014) Crashes if I try and locate footage/scrub/create a blank sequence, please help

    Hello, this is my first time asking for help on here, I've been going round the forums and web in general for hours and can't seem to find a solution to this. I really hope someone can help me sort this.
    Every time I try and open a project in Pr CC 2014 on my Mac Pro  I get the "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will try and save your current project."
    People usually ask for as much detail as possible, so to that end: This is a project that I started on my MacBook Pro Retina, so when opening on my desktop it prompts me to locate the footage. Once I find the first file, as soon as my mouse moves over the clip (at the point that scrubbing would be evoked) I get the warning and it shuts down. I tried to open a blank new project, which does not shut down, until I go to import the footage and again, it only crashes when the mouse moves of the clip to scrub. I tried locating the footage in the finder to sidestep the Media Browser, and that allowed me to select the clip, but crashes once I tried to import it. I thought it may be the footage was corrupted, so I tried other clips with the same result. It also crashes if I just try to create a new sequence, with no footage at all in the project.
    All my other Adobe apps (AME, Pl, Ae, Br, Ai, Ps, Lr, Id, Mu) are working fine. I have uninstalled and reinstalled Pr and AME twice now. I have followed the advice of other posts and renamed/reset/deleted the preferences, plugins in the Library, and adobe folder in users/username/Documents. I have ensured that I have read/write access in all folders. I am running Yosemite on my desktop, but so is my laptop and Pr is running flawlessly on that. I never had this problem with Pr CC pre 2014, so I'm hoping it's not a hardware issue.
    I've also tried turning it off and on again!
    I have reached the end of my tether and consider myself well and truly defeated by this problem. I really hope that someone out there can figure what on earth is going on!
    Mac Pro (Early 2009)
    2 x 2.26 GHz Quad-Core Intel Xeon
    11 GB 1066 MHz DDR3 ECC
    ATI Radeon HD 5770 1024 MB
    and
    MacBook Pro (Retina 15-inch, Early 2013)
    2.7 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    Intel HD Graphics 4000 1024 MB

    Hi Man0fst331,
    Try the following:
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe preference files are set to read/write
    Delete media cache
    Remove plug-ins
    If you have AMD GPUs, make sure CUDA is not installed
    Repair permissions
    In Sequence Settings > Video Previews, change the codec to one that matches your footage
    Disconnect any third party hardware
    If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
    Disable App Nap
    Reboot
    Report back if anything here worked for you.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 (8.1.0) freezes while scrubbing timeline

    Using a Mac Mini (late 2012 model), running Mavericks 10.9.5
    Processor: 2.6 GHz Intel Quad Core i7
    Memory: 16 GB
    Graphics: Intel HD Graphics 4000 1024MB
    I am also using a 2TB Fantom G-Force Megadisk external HD to store all my media. It is connected via a Firewire 800 cable
    I've been having a lot of trouble with Premiere Pro CC 2014. While scrubbing through a project, a frame will all of a sudden freeze in the program monitor. I have my processors displayed on my menu bar and I've noticed that whenever I run into lag time or freezing the 8 processors won't all be firing, usually just one is actually working at that time. I am also only running one program at a time as to not tie up my processor.
    All of my source files are usually AVCHD. Most of my work is under 10 minutes long, so they are just short corporate videos not feature length movies.  I understand that editing native files can really slow your processors so with my latest project I consolidated and transcoded in the Project Manager to Apple ProRes in order to test that. Even with that I'm still having the exact same problem.
    These are some other steps I've taken to correct this:
    I've contacted Adobe several times and they told me that the Graphics Card is known to have problems and to contact Apple. I contacted Apple and they said there are no known problems with that Graphics Card it sounds like a software issue. I ran a disk permissions test and uninstalled and reinstalled the software. Same problems. Nothing has worked.
    I've trashed my preferences as well
    Really it seems that both Adobe and Apple are pointing the finger at each other. All I want to do is edit my videos without having to restart Premiere Pro every 10 minutes.

    This seems to be an issue for me A LOT too. I can't keep Premiere open for more than 2 minutes at a time right now. The Customer Service rep from India did a "Team View" on my computer before and after 45 minutes finally fixed the issue. But I can't seem to get a hold of customer support right now. I hope you and I both find a solution soon. Good luck!

Maybe you are looking for

  • Runtime Error when installing Adobe Creative Suite 5.5 Production Premium

    I am trying to install Adobe Creative Suite 5.5 Production Premium, but I keep getting a 'Runtime Error!':  This application has requested the Runtime to terminate it in an unusual way.  Please contact the application's support team for more informat

  • Where to find the performance counter information?

    Code: class Program static void Main(string[] args) if(CreatePerformanceCounters()) Console.WriteLine("Created performance counters"); Console.WriteLine("Please restart application"); Console.ReadKey(); return; var totalOperationsCounter = new Perfor

  • Internal excise invoice no.

    hi, Can anyon tell where internal excise invoice no. range defined. Actually in my case for three GRN posted with same excise group it is showing same excise internal no for all 3 GRN.. Thanx and regards, SAGAR

  • Do we need a cdrw frontend?

    Do we need a cdrw frontend? I tend to like a quick simple CD/DVD Tool. Would a cdrw frontend for Solaris Community be useful? Comments? Edited by: jhawk on Oct 28, 2007 2:41 AM Omit image

  • ORA-06502: numeric or value error: character string buffer too small

    I have a stored proc with a parameter pio_med_rec_nbr patient.med_rec_nbr%TYPE where patient.med_rec_nbr is a varchar2(12) . character set is we8mswin1252 semantics are bytes the stored proc retrieves max(med_rec_nbr) into nTmp( number) from a refere