Premiere Pro CC 2014 (8.0.1.21) crashes when opening or creating a project

I just downloaded the trial for Premiere Pro CC (2014), and the program keeps crashing every time I open or create a new project. I can idle at the "Startup Screen" but as soon as I open a project the program closes without warning. I've re-installed all Adobe products I have, re-installed the Microsoft Visual C++ Redistributable 2012 and 2013 to get new MSVCR110.dll files (which seems to be the file causing the crash) but nothing is helping. I've also looked in every thread I've found on this forum and a lot of people seem to be having the same problem, but no one had got any answers for how to solve the problem.
Anyone have a clue on what to do? According to others formatting the hard drives don't seem to solve the problem either.
Here's the crash log:
Problem signature:
  Problem Event Name: APPCRASH
  Application Name: Adobe Premiere Pro.exe
  Application Version: 8.0.1.21
  Application Timestamp: 53c7b17f
  Fault Module Name: MSVCR110.dll
  Fault Module Version: 11.0.51106.1
  Fault Module Timestamp: 5098826e
  Exception Code: 40000015
  Exception Offset: 00000000000740da
  OS Version: 6.1.7601.2.1.0.256.48
  Locale ID: 1053
  Additional Information 1: dac8
  Additional Information 2: dac844fabf0ae09d193ac750f70263ad
  Additional Information 3: 6e8b
  Additional Information 4: 6e8b89b059d1639bd5ba176e9f652c56
I'm running a:
Intel i7-3770K, not overclocked
ATI Radeon 7850, not overclocked
16gb RAM
64-bit Windows 7 Professional with Service Pack 1

Me too with this one have it randomly when just opening the same project and begining to edit
had it happen about 4 times now.
Latest update
Microsoft Visual C++ Runtime Library
Program C:\Program Fi...
R6025
- pure virtual function call
[ok]
Adobe Premiere Pro CC 2014.1 has stopped working
roblem signature:
  Problem Event Name: APPCRASH
  Application Name: Adobe Premiere Pro.exe
  Application Version: 8.1.0.81
  Application Timestamp: 5426694c
  Fault Module Name: MSVCR110.dll
  Fault Module Version: 11.0.51106.1
  Fault Module Timestamp: 5098826e
  Exception Code: 40000015
  Exception Offset: 00000000000740da
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 2057
  Additional Information 1: a22a
  Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
  Additional Information 3: 9245
  Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Similar Messages

  • Premiere Pro/After Effects CC on Mac OSX crashes when moving media

    I have Premiere Pro CC and After Effects CC, in both programs whenever I attempt to move any media (any format) to the timeline from the media browser window Premiere (and After Effects) crashes immediately.
    I'm using a MacBook Pro w/ retina, running latest OS, and I have the Microsoft Office suite of apps installed.
    Customer service had a go fixing it but to no avail, apparently it has something to do with fonts if that helps anyone, i've reverted all the fonts on my Mac back to the default but still nothing. 
    Any help would be greatly appreciated!

    Hi Matt,
    Try the following:
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe folder preferences are set to read/write in all 3 locations.
    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

  • Photoshop CC 2014 crash when opening or creating new files when running with Cintiq 13HD.

    I have a problem where Photoshop CC 2014 crashes when trying to open or create a new file while the Photoshop window is being displayed on my Cintiq 13HD.
    When Photoshop is being displayed on my main monitor it doesn't crash.
    I'm running Windows 7 (64 bit) and have updated my graphics and wacom drivers to their latest versions and Photoshop is completely up to date. (I'm running the 30-day free trial)
    Here's the event log of the crash:
    Faulting application name: Photoshop.exe, version: 15.2.1.257, time stamp: 0x543dbc5e
    Faulting module name: atig6txx.dll, version: 8.14.1.6398, time stamp: 0x54176130
    Exception code: 0xc0000005
    Fault offset: 0x00000000000122b7
    Faulting process id: 0x23dc
    Faulting application start time: 0x01d0030b1092334e
    Faulting application path: D:\Program Files (x86)\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
    Faulting module path: C:\Windows\system32\atig6txx.dll
    Report Id: 61680f48-6efe-11e4-aeeb-bc5ff45851ea

    As you can already see, your ATI/AMD video card drriver is crashing.
    Update the driver from AMD's website to pick up all the bug fixes you are missing.

  • Pro CC 2014 constantly has "serious error" crashes - forces me to make new projects

    Since upgrading to PP CC 2014 - doing the most basic operations (dragging a clip from source to timeline) the app shuts down - gives "Serious error, will attempt to save current project" dialog, then on relaunch prompts to "open previous project," then I get "opening recovery project, but we make no guarantees, please save to a new file."
    Which I do, but it happens all over again after. Super frustrating, as you can imagine. I'm on a 2014 iMac 16g ram, 3.2 Intel core i5 OSX 10.9.4

    Adobe support has been a catastrophe for me today. Had a chat with a rep, they said they'd call me to talk it through, hours passed, no call. I called them, and had a tech try to fix my issue for almost 2 hours. Finally "fixed" it. Turned out it was one of the mouse pointer icons that is used by PP was missing in my prefs file, so every time I did certain mouse actions, when that pointer icon was needed the whole app crashed. Um, ok.
    But now the issue is back.
    Also when he took over my computer, he zeroed out a ton of my other user settings on my computer - a time killer for me. Add to that I get auto support emails from a "do not reply" account saying that if my issue isn't resolved to reply to the email. Plus today CC login was just screwed, so my TypeKit fonts were all inaccessible.
    How is it possible for your support to be this bad, Adobe?

  • Satellite Pro C50-A - Microsoft Office 2013 apps crash when opened

    I recently purchased a Satellite Pro C50-A PSCG7A-01X01V. I installed Windows 8.1 and then installed Office 2013. Unfortunately when I start one of the Office 2013 apps it immediately crashes with an error message eg: "Microsoft Word has stopped working". I have tried starting the applications in safe mode (eg excel /safe) however the same error occurs. Is anyone able to assist with this problem?

    I have managed to resolve the issue by using Microsoft's facility to 'Repair Office Programs'. Refer to http://office.microsoft.com/en-us/project-help/repair-or-remove-office-2010-HA010357402.aspx
    I also found this article useful
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/office-2013-wont-start/0269c763-7a03-4a6f-81cb-6522ef7d3ea3?msgId=41d5ad9f-6b30-4771-822d-e93369e6311b

  • Premiere Elements 9 crashes when trying to create new project?

    I dont seem to be able to get this application to work..... it was fine a few months ago, but when I went to create a new project it continually crashes out when you try and open an existing or new project file.
    can anyone suggest a possible rememdy please?\

    dudleythedog
    What computer operating system is your Premiere Elements 9 running on? And, are you running it from the 9.0.1 Update?
    Does the problem exist with and without the antivirus and firewall(s) disabled?
    Then the usual
    1. Running program from an User Account with Administrative Privileges plus Run As Administrator applied to program's desktop icon?
    2. Last version of QuickTime installed on same computer with Premiere Elements?
    3. Video card/graphics card driver version up to date according to web site of manufacturer of the card? According to the Device Manager/Display
    Adapters, how many video cards/graphics cards does your computer use - 1 or 2?
    As a first pass at this, let us delete the Adobe Premiere Elements Prefs file, and, if necessary, the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists.
    Assuming Windows 7, 8, or 8.1 64 bit computer....
    Local Disk C
    Users
    Owner
    AppData
    Roaming
    Adobe
    Premiere Elements
    9.0
    and, in the 9.0 Folder, is the Adobe Premiere Elements Prefs file that you delete. If necessary, delete the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the whole path cited.
    We will be watching for your results and then decide what next.
    Thank you.
    ATR

  • Premiere Pro CC 2014 not optimized for iMac 5K graphics card?

    I have the new iMac 5k with the AMD Redeon R9 M295X 4 GB GDDR5 graphics card. In Premiere Pro CC 2014 (updated to the latest version), when I go to "project settings" and select "Mercury Playback Engine GPU Acceleration," I get a pop-up window that reads: "the selected renderer hardware has not been certified." Does this mean that Premiere Pro is not optimized for these video cards? If I still choose to select GPU acceleration, will I see any performance boost?
    Thanks in advance for any responses.

    It means Adobe has not tested the card.
    If you can select the card you are OK.

  • Premiere pro cc 2014 update failed

    Couldn't move a project from desktop to laptop. Laptop showed premiere pro cc 2014 up to date. But when I tried opening project it said it was created on a newer version. Chat support said I should downoad an update from a link they provided. Tried installing but says Update Failed. Tried cc cleaner too. No luck.

    U44.. update error http://forums.adobe.com/thread/1289956 may help
    -more U44.. discussion http://forums.adobe.com/thread/1275963
    -http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
    -http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html
    or
    Creative Cloud chat support (all Creative Cloud customer service issues)
    http://helpx.adobe.com/x-productkb/global/service-ccm.html

  • New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball

    Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
    Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
    Some specs:
    Processor  2.5 GHz Intel Core i7
    Memory  16 GB 1600 MHz DDR3
    Graphics  Intel Iris Pro
    NVIDIA GeForce GT 750M GPU PCie
    Intel Iris Pro GPU Built-in
    8 GB DDR# 1600 MHz (x2) = 16 GB RAM
    350 GB of 499 GB left on drive
    Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
    Any suggestions would be greatly appreciated.

    >NVIDIA GeForce GT 750M GPU PCie
    >Intel Iris Pro GPU Built-in
    Dual graphics adapters are a bane on civilization!!!
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
    -Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

  • 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

  • What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

    I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
    Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it  to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
    I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
    My system configuration is Intel Core I7   950@  3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
    For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!!  and during the 20 days mentioned above it crashed once.
    The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
    I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
    I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
    Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
    Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
    Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

    Hello Ashraf,
    Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
    Thanks,
    Kevin

  • Multi Cam Flicker Issue - Premiere Pro CC 2014

    Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

    We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
    Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
    In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
    Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

    Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
    Mylenium

  • Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    It can occur even in the parts without filters !!! But no all time.
    ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
    ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
    ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
    MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
    When waiting for fixes this bug?

    Hi Aleksey,
    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
    Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
    Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
    When waiting for fixes this bug?
    If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug.  If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
    Thanks,
    Kevin

  • 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

Maybe you are looking for