Premiere Pro CC 2014.2 Crashing while loading project...

When trying to open Premiere project the program opens and looks like it will load and then crashes.
If I create a new project Premiere opens and I can import footage but as soon as I try to play footage in the preview window or drop it in the timeline the program crashes as well.
I am working on a Windows 7, 64-bit, i7, 8GB ram, 1TB multiple partitioned hard drive. My Graphics card is, Intel(R) HD Graphics 4600 - Driver Version: 9.18.10.3204
My Error Log is:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: MXF_SDK_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d772c
Exception code: 0xc0000005
Fault offset: 0x00000000000bdc55
Faulting process id: 0x378c
Faulting application start time: 0x01d02c3625e455c1
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_4.4.33_vs10.dll
Report Id: b1b66e81-9829-11e4-95ce-c4346b64bc4f
I can't figure out what the faulting module is.
I just installed CC 2014.2 3 days ago. It all worked fine until yesterday when Premiere started crashing. I restarted the system - same issue. I uninstalled and reinstalled Premiere2014.2 - same issue. Premiere seems to be the only faulting application. Everything else (Ps, Ae, Lr, Id, Au, Ai) appears to still be working.
My version of CS6 (Purchased before getting a creative cloud membership not downloaded through CC) is also still working properly.
Thanks for the help.

Update: I updated my Graphics Card Driver to a more recent version. Restarted computer and reopened Premiere and similar crash happened. I went through to get some more crashes and had different crash reports. The faulty module is not always the same.
Problem Event Name:                        APPCRASH
Application Name:                             Adobe Premiere Pro.exe
Application Version:                           8.2.0.65
Application Timestamp:                     5486db4a
Fault Module Name:                          devenum.dll
Fault Module Version:                        6.6.7600.16385
Fault Module Timestamp:                  4a5bded7
Exception Code:                                  c0000005
Exception Offset:                                00000000000016a0
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  ec5a
Additional Information 2:                  ec5adb2545b190cc19da7bdfa78d5bf1
Additional Information 3:                  6e59
Additional Information 4: 6e59168cf9de1a4a9616903b4a4ba1e1
Problem Event Name:                          BEX64
Application Name:                             Adobe Premiere Pro.exe
Application Version:                           8.2.0.65
Application Timestamp:                     5486db4a
Fault Module Name:                          OpenCL.dll_unloaded
Fault Module Version:                        0.0.0.0
Fault Module Timestamp:                  50eb1a5b
Exception Offset:                                000007fee84516a0
Exception Code:                                  c0000005
Exception Data:                                   0000000000000008
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  a527
Additional Information 2:                  a527a6af76c2b04cfd1fc255c66e5364
Additional Information 3:                  21c7
Additional Information 4:                  21c71ffc516aa3806e495b8080bd51fe
Both of those are different from the original posted report.
I did have some success following these instructions.
Premiere Pro CC 2014.1 has stopped working - Win 7 64 bit
It appears I do not have a graphics card that is compatible with the mercury engine. I have had three successful tests and one crash since I selected Renderer: "Software only"
I plan to upgrade to a Nvidia card or the supported Intel Iris Card.
This seams to be the issue but I am hesitant to use CC 2014.2 for the time being because I don't know if it will crash randomly and CS6 is working fine. The second error code with "Fault Module Name: OpenCL.dll_unloaded" seems to be directly related to the graphics card and rendering processes. I will update as I learn more.
Please comment with any suggestions or resolutions you have had.

Similar Messages

Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC

Hi everyone,
I'm reporting this issue in case someone else would have the same problem.
I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
Cheers,
Vincent

Hi Vincent,
I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
iMac - 27" Late 2013
Processor 3.4 GHz Intel Core i5
Memory 12 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GTX 780M 4096 MB
Software OS X 10.9.4 (13E28)
I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
Resetting permissions on Adobe Preference Folder...
This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
Is there anyone at Adobe that can offer some advice??

Premiere Pro CC 2014.2 crashes when "locating media"

The problem;
Premiere Pro CC 2014.2 crashes when "locating media". I am working on a project that has not given me any problems for the last 200 hours. About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs. I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail.
Project workflow
- 700gb of 5d footage
- 20 sequences under 5 minutes
- Dynamically linked files with AE
- Warp Stabilized about a dozen clips of under 5 sec
- On every sequence color correction adjustment layer with RGB Curves, Three way color corrector and sharpen filter
- I kept old versions of the sequences (I was in version 5 before the crash)
What I have tried;
- Unsuccessfully tried to open auto-save files for this project.
- Successfully opened other older non relevant project
- Removed Mercury playback engine in the project settings
- Cleaned out media cache database through pp in media Preferences
- Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
- Tried importing sequences into new .proj file; it would crash as a result.
What "worked".
I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client. I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
Questions.
- What the hell happened? Why could I open it on one computer and not on the other?
- Is there a way to fix a corrupted .proj files on a PC?
- What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
Windows 8.1 64bit
Premiere 2014.2
Intel Quadcore i7-4770 3.40GHz
16gb Ram

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B

Dear Sir,
I'm in a big ****. I've directed and edited 1h documentary for Finnish television, also, the technical specs requested by the TV Channel is all production Broadcast masters must be encoded with Apple ProRES codec or MJPEG A or B.
As i'm working on PC (win7), the ProRES codec doesn't exist on PC system, so i've done the export to MJPEG. The problem is i have a different gamma level when i watch the final export with Quicktime or VLC. Of course i can adjust the level in those players, but it doesnt effect the file. When i import the Qt file into a Premiere sequence, the gamma level is still **** and different from my original level i have from my timeline and preview window. If i export the project to H264 1920x1080p25, then the gamma is perfect with Qt, VLC and WinMedia player. But the TV station don't wanna work with H264. Deadline is on next monday, and i can't send a Qt MJPEG file with wrong gamma !!!Any chance to find a solution to fix it ??? After reading different forum, i can see this problem exist since many years and never been solved.
What can i do ??
Denis.

Things is my prpject includ few effect plugins i bought, so what ever i could find a mac, not your i could export xml project to finalcut with plugins it dont have
Denis
Sent from my iPad.
Le 31 mai 2013 à 15:20, Fuzzy Barsik <[email protected]> a écrit :
Re: PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B
created by Fuzzy Barsik in Premiere Pro - View the full discussion
If it were me, I wouldn't encode to MJPEG.
So as to encode to ProRes on Windows you can utilise any solution based on ffmpeg/ffmbc or better yet find a Mac with Final Cut or Compressor installed for delivering critical work.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5368019#5368019
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5368019#5368019
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5368019#5368019. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Adobe premiere pro cc 2014 - constantly crashing

Naturally, my project is under deadline..
My system is running OS X 10.9.4 (13E28)
late-2012 MacBook Pro Retina
2.6 GHz Intel Core i7
16GB 1600 MHz DDR3
Intel HD Graphics 4000
NVIDIA GeForce GT 650M
768Gb Flash Hard Drive
My project consists of DSLR footage (h.264 compressed files) and Zoom H4N Audio (.WAV files)
Even after spending most of Thursday and Friday on the phone with Adobe support; deleted all files from media cache, re-imported project, waited for premiere to re-conformed footage, etc..
...I still find my project loading sluggishly.. like it takes 15 minutes until video clips in the sequence will fully loads & appear in the project window... it becomes momentarily operable before quickly becoming inoperable as the video and audio no longer playback or respond to the cursor.
At that point (when playback no longer works) I can still save the project.
It seems as though the software loses the dynamic link between the footage as it completely goes black.
Then when I try to exit Premiere CC 2014.. the program locks up and crashes with no report.
The crash reports I have are from a few days ago when they first began and before they stooped generating reports.
Majority of the errors were:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
It also crashed a few times with the following errors:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fbfdef0
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Any help would be greatly appreciated!

First I must say.. ADOBE PREMIERE PRO CC 2014 is glitchy as hell (and in my three weeks editing a documentary or rather two weeks bc I lost an entire week due to this issue) I have come to learn and identify some workaround solutions..
Here is what I originally wrote after speaking to five different Adobe engineers...
It is only an issue with PrCC2014 and the temporary solution before the upcoming update is to...
1) Go into Preferences... Audio... and UNCHECK the box next to "Maintain pitch while shuttling."
[this is a new feature in PrCC2014 that is processor intensive, causes audio dropouts, and is a major player in why the playback suffers]
2) Go into your sequences settings for each sequence you have for DSLR footage and change the Editing Mode preset to "CUSTOM"
3) Next scroll down to Video Previews and change the preview file format to "QuickTime" and the codec to "Animation."
4) Uncheck the box next to "Composite in Linear Color (requires GPU acceleration or max render quality).
[this is another new feature that is also processor intensive & is also a key suspect to the problem]
THE KEY TO FIXING (temporarily) THE BEHAVIOR
When your computer begins to show signs of the glitchy - sluggish playback behavior..
Stop.. go back into your SEQUENCE SETTINGS and change it to a different EDITING MODE (only temporarily) and click OK.
You could change yours from ProRes to CUSTOM (as indicated in step #3)
Next a prompt will pop up asking you...
Click okay then immediately go back to SEQUENCE SETTINGS and change it back to your original setting, in your case, ProRes.
Somehow, by DELETING those PREVIEW FILES it essentially resets the issue... until the dreaded glitchy behavior returns.
I have had luck with this trick and hopefully you will too..
Cheers!

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 2014 is crashing due to after effects plugins being installed in the mediacore. Is there a solution to this issue?

The title honestly says it all. I recently purchased CC 2014 and have been updating and transferring plugins from prior versions of adobe after effects. When installing those plugins as I did in previous versions of after effects none of the plugins were recognized/loaded. I eventually found a solution to this issue by simply installing the plugins into the media core. They have all successfully loaded, but due to their presence in the media core premiere pro is now crashing upon start up. Does anyone know a work around for this?
Image showing crash:
Specs:
OS: Windows 8.1
RAM: 8GB
CPU: Intel 5 4670k
GPU: GTX 980 sc
Premiere Pro CC 2014 and After Effects CC 2014 are both updated to their most recent versions

First ... have you checked that these are all updated to work with the CC versions? I'd check with the makers of each plugin, the software has MANY differences.
Next ... if say you removed all but one, do any of them work? It might be worthwhile to remove them from the folder, then add one by one until you find one that is crashing things. That would at least get you part way forward.
And ... you might list which ones you have, in what versions. Folks around here might be able to help just seeing that.
Neil

Premiere Pro CS 5.5 Crashes on Load

I've had the CS5 Master Suite installed and working just fine for the past year or so, and today compltely uninstalled it all (including searching for all Adobe files/dirs through my hard drive and deleting them). Then installed the new CS5.5 Master Suite - the installation went fine.
I began opening each of the apps from the suite a few times to ensure they all worked, and all do, except for Premiere Pro 5.5. The first time I opened it, it loaded fine and I was shown the Open Project screen. I close the app, tried to re-open it, and it crashed while it was loading the dependency files.
From that point on, even after several computer reboots, PP5.5 continues to crash while loading.
Anyone have any suggestions? Any Adobe tech reps I can troubleshoot with please?
Thanks in advance.

Thank you gents for the responses. After some fiddling last night, I discovered that the nVidia drivers were the cause of the crashes.
I had the latest GeForce drivers installed (270.61), which caused the crashes. When I downgraded to the last set (I believe 266.xx or 267.xx - I'm at work right now, can't recall), the crashes went away.
Then I saw someone else's thread about the new 270.73 Quadro drivers, I installed them using the .inf "hack", and again, no more crashes.
So, once nVidia releases the GeForce drivers equivelent to the Quadro 270.73, everything will be great.

Premiere Pro CC 2014.2 crashes frequently when switching between programs

I've started to frequent program crashes in Premiere Pro CC 2014.2 in Mac OS 10.10.3 on my 2013 Mac Pro. The issue occurs when I switch from another program, say word or Adobe Audion back to Premiere Pro. I get the 'we're sorry' dialogue box and the application crashes. About 50% of the time when this happens - when I reopen the application it crashes again - and then on the 2nd re-open it's successful. It's really hampering my workflow to worry about a crash every time I move into AE or Audition. I've uninstalled all plugins, uninstalled and re-installed PP, cleared the media cache, and reset preferences. Still happening every day on this machine. FYI i have a 2013 iMac running the same OS which has been opening the same project files without this issue - so it seems like it's specific to this machine for some reason...

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

Premiere Pro CC 2014 very unresponsive while rendering on background with Adobe Media Encoder

Usually while I eddit videos on Premiere, I'm rendering on the background with AME. Or at least I used to. Some time ago, this process suddenly stopped working, as rendering on the background bagan to make Premiere really unresponsive, and quite impossible to work with. I couldn't think of any change I made other than switching my HDD, and I blamed it on that (it made sense because new HDD is one of those WD Green ones, a little worse than my old Seagate one). So I adapted to just queueing everything and start rendering when I was done edditing. But yesterday I installed a 240gb Kingston HyperX SSD, re-installed Windows and the main apps on it, and tried again, hoping to see an improvement. Now I was storing the original media on the HDD, running OS, Premiere and AME on the SSD, and rendering to the HDD. It did not work. Premiere still became slow while I rendering with AME. So I thought it might get better if the HDD was not reading and writing at the same time, and I switched the original media to the SSD, while still rendering to the HDD. Also didn't help. I don't know why this setup suddenly does not work, and I really need to fix it.
My setup:
Windows 7 Home Premium 64bit
Intel Core i7 2600 @ 3.4GHz
12GB of RAM
nVidia GeForce GTX 560 (yes, drivers are up to date)
Dual monitors (one for Premiere workspace and one for a bigger program monitor)
2TB WD Green HDD where I keep most of my junk (and media files)
240GB Kingston HyperX SSD where I run the OS and important apps (Premiere and AME included)
I'm running Adobe Premiere Pro CC 2014 (8.1.0 build) and AME CC 2014 (8.1.0.122 build)

Hi chriscorrell,
Thank you for posting on Adobe forums.
Upgrading your OS might be a good idea because Premiere CC 2014's OS requirement is OS X 10.8.
See here: System requirements | Adobe Premiere Pro
Thanks,
Rameez

Premiere Pro CC 2014 TickTime Crash FIX (in some cases)

In my experience so far, Premiere Pro can return a TickTime.ccp error in several different situations. In some instances (too much Warp Stabilizer) just clicking okay a gazillion times is a usable workaround. In a case I had recently, Premiere Pro CC2014 crashed completely every time I tried opening the project file and all its autosaved versions. Here's a description of what I figured out to be the problem and how I solved it.
My project file was created in CS6, then edited in CC2014 on a Mac, then Windows. After this the crashing started on both Mac and Windows version of Premiere Pro CC 2014.
Symptoms:
An error message pops up on opening project [..\..\src\TickTime.ccp-290]. Clicking okay brings up another more serious one about a Serious Error and PP needing to close. Then it dies.
The problem:
Somewhere between CS6 and CC2014, Adobe seems to have changed their XML file structure from using a comma as decimal separator to instead using a period. Somewhere within my project file, Premiere left one as a comma.
My fix:
1. Make a copy of your project file and change the extension from ".prproj" to ".gz"
2. Use something like 7zip and extract the file, this should give you a new file with no extention.
3. Edit this file in a text editor (I'd reccomend Notepad++ or TextWrangler, but Notepad and TextEdit will also do).
4. Search for the term <PlaybackSpeed>. Most of your clips would have a numerical value of 1 directly after this, referring to a playback speed of 100%. Click Find Next a few times and look at the numbers following the selected bits. Anything that is not a multiple of 100 will be a decimal number, that should look like "0.5" or "1.2759984", (referring to speed values of 50% and 127.59984% respectively). If you see a comma, replace it with a full stop. My project had a value of "0,8845" I had to change it to "0.8845"
5. Save the file, and using 7-Zip, compress it into a new gz file.
6. Change the ".gz" extension to ".prproj" and you should be set to continue your edit.
If you didn't change the speed of any of you clips, chances are this is not your problem.

Hi Karel,
Thanks very much for writing this up. I hope this helps others having this issue.
Thanks,
Kevin

Premiere Pro CC 2014.2 - Crash when dragging videofile into timeline

Hey guys,
when I try to drag a image or videofile (doesn't really matter which fileformat, codec or length) into a sequence Premiere Pro CC 2014.2 will crash immediately, without a warning. Just the usual "Adobe Premiere has stopped working" in Windows 7.
I'm using Windows 7 64-bit with 4GB RAM, Intel Core i3-4130 COU @ 3,40 GHz and a Intel HD Graphics 4400. Premiere Pro worked seamlessly just days before, without any change to the system. The error occured in Premiere Pro CC 2014.1 too. Maybe it's a problem with the video preview? Music files are no problem.
Thanks in advance! Need help asap. customers are waiting

Solution:
My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
Thanks Michaela from the Adobe Support Chat!

Premiere Pro CC 2014 Startup Crash "Quit Unexpectedly"

This morning, I take a look at Creative Cloud and there was 2 updates called "Adobe Premiere Pro CC 2014" and "Adobe Photoshop CC 2014". So, I figured, "Sure. Why not?" I updated them. So far, Photoshop still works. After Effects works too. But when I open Premiere Pro CC 2014, I get the pop-up screen, loading stuff and it just quit unexpectedly. I cleaned all of the Adobe products with the Cleaner Tool, uninstalled it, reinstalled it, opened it and it still happens. This is where it stops loading every time and quits. Also, love the artwork.
After that, it quits unexpectedly. Here is an image of that error.
I'm using a MacBook Pro. I don't know what to do. I really need help, guys.

Solution:
My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
Thanks Michaela from the Adobe Support Chat!

Premiere Pro CC 2014.2 Crashing on Startup

Hi guys,
My Premier Pro keeps crashing when it starts up. It only started happening a couple of days ago. I've pulled the below out of the event viewer.
I have already tried the following;
1) Disabled intel graphics to leave just my AMD Radeon Graphics active
2) Complete Uninstall and reinstall of CC and all app
3) Ditched the OOBE db file
4) Created a new user profile.
The event logs
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: dvaui.dll, version: 8.2.0.65, time stamp: 0x5486b61b
Exception code: 0xc0000005
Fault offset: 0x00000000001871a8
Faulting process id: 0x220c
Faulting application start time: 0x01d04085edc807fd
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\dvaui.dll
Report Id: 50b6f6fd-ac79-11e4-9e82-a0a8cd78aa54
Fault bucket 92314328, type 20
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Adobe Premiere Pro.exe
P2: 8.2.0.65
P3: 5486db4a
P4: dvaui.dll
P5: 8.2.0.65
P6: 5486b61b
P7: c0000005
P8: 00000000001871a8
P9:
P10:
Attached files:
C:\Users\charlotte.hallas\AppData\Local\Temp\WERF328.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\charlotte.hallas\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Adobe Premiere P_e7eb58a966a9f59d2bdeb4a4f8248ebb48a03a_1af72f9c
Analysis symbol:
Rechecking for solution: 0
Report Id: 50b6f6fd-ac79-11e4-9e82-a0a8cd78aa54
Report Status: 0

I am having the same issue. I have a time-sensitive project that I can no longer work on because this program continues to crash. I would revert to a previous (stable) version if I could find the download link for it, but i can't seem to find that.
Come on, Adobe...this is a MAJOR flaw.

Premiere Pro CC 2014 keeps crashing on startup.

So, I just had a fresh Windows 7 install because for the last 3 days I've been having a problem with Premiere Pro CC 2014 and this was my last resort, even so, it didn't work.
Everytime I try to start Premiere Pro CC 2014 this happens:
I know this has been a problem to a lot of people, but I've tried every solution I've seen so far: tried the Premiere Pro CC version, reinstalled Premiere Pro CC 2014, updated Intel Graphic card, disabled Intel Graphic card, renamed Adobe's AppData folder, tried running in compability mode, reinstalled Quicktime, unistalled Quicktime. And I just formatted my computer, so I really don't know what else can I do.
I'm running Windows 7 Ultimate with a Intel Core i3-4330 CPU @ 3.50GHz, Sapphire Radeon R7 260x, 8GB RAM.
My Event Viewer logs:
"Faulting application name: Adobe QT32 Server.exe, version: 8.0.1.21, time stamp: 0x53c7afcc Faulting module name: ImageRenderer.dll, version: 8.0.1.21, time stamp: 0x53c76485 Exception code: 0xc000001d Fault offset: 0x001e5353 Faulting process id: 0x114c Faulting application start time: 0x01cfbfc08ce68291 Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\32\Adobe QT32 Server.exe Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\32\ImageRenderer.dll Report Id: cb4f1cdb-2bb3-11e4-82a4-97822361737e"
"Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Adobe QT32 Server CC 2014.0 because of this error.
Program: Adobe QT32 Server CC 2014.0" "Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f Faulting module name: ImageRenderer.dll, version: 8.0.1.21, time stamp: 0x53c7659e Exception code: 0xc000001d Fault offset: 0x00000000001f5382 Faulting process id: 0xc70 Faulting application start time: 0x01cfbfc086d5619d Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\ImageRenderer.dll Report Id: cb4a3ac9-2bb3-11e4-82a4-97822361737e"
"Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Adobe Premiere Pro CC 2014.0 because of this error. Program: Adobe Premiere Pro CC 2014.0"
Thank you.

Hi zerebelo,
Please install Windows 7 Serivce Pack 1 and that should fix it.
Let me know if that helped.
Thanks!!!
Rameez

Premiere Pro CC 2014.2 Crashing while loading project...

Similar Messages

Maybe you are looking for