Premiere Pro CC (2014 version) crashes (beach ball) when trying open certain large Projects

Hi,
I'm currently editing for a TV channel using the latest version of Premiere Pro CC and certain projects (it seems to be with ones with a lot of footage) crash when I open it. Basically, it doesn't even load all the footage up, one that crashed just now said it had around 140 files left to load, but the beach ball arrives and I sat there waiting for half an hour and nothing happen, apart from the beach ball spinning.
Now, we're on an high spec iMac 3.5Ghz i, 32GB ram, 512gb Flash Storage, 4GB Geforce Graphics card, so I don't think the issue can be the mac, unless the macs faulty, but seems to work fine, when I create new projects etc.
Also, their workflow uses USB 3.0 drives, could this be the bottle-neck making them crash? That being said I've edited lots off my USB 3.0 drive at home and my desktop is a lot weaker then this iMac.
Any ideas what the issue may be?
Thank you,
Matt

Hi Matt,
Please mention the exact version of Premiere Pro. Assuming you are using 2014 version, please try some steps mentioned below.
1. Clean the media cache files by navigating to /Users/User Name/Library/Application Support/Adobe/Common
2. Check the version of the drivers of your NVidia card. So, go to Apple Menu>System Preferences and check if you have a CUDA Preference pane if it is not there then go to the below link and update the Card to latest drivers.
CUDA Drivers for MAC Archive | NVIDIA
3. Also, please mention if you have any third party plugins used in the project. If yes, then try to update those Plugins or copy and paste those plugins to some other location and Trash them from MediaCore of Premiere Pro. The location of third party plugins is mentioned below.
Startup Drive or MAC HD /Library/Application Support/Adobe/Common/Plug-ins/7.0
Hope it helps.
Regards,
Vinay

Similar Messages

Mountain Lion Finder "unresponsive" (Beach balls) when trying to copy large amount of files

Before Mountain Lion, using Lion - transfering 999 files from my compact flash card to my SSD hard drive via a FW800 reader was SO easy. Select all, drag and drop and the transfer would begin immediately.
Now, after upgrading to Mountain Lion, I experience at least 60 seconds of beach balls and an "unresponsive" finder. Sometimes it starts to transfer, sometimes I have to relaunch finder.
I've reset the PRAM (although I didn't hear 4 beeps), the SMC, I did verify and repair disk permissions.
Any thoughts on this?
Thank you,
(Late 2011 15 in MBP)

Scott Oliphant wrote:
iomega, lacie, 500GB, 1TB, etc, seems to be drive independent. I've formatted and started over with several of the drives and same thing. If I copy the files over in smaller chunks (say, 70GB) as opposed to 600GB, the problem does not happen. It's like finder is holding on to some of the info when it puts it's "ghost" on the destination drive before it's copied over and keeping the file locked when it tries to write over it.
This may be a stretch since I have no experience with iomega and no recent experience with LaCie drives, but the different results if transfers are large or small may be a tip-off.
I ran into something similar with Seagate GoFlex drives and the problem was heat. Virtually none of these drives are ventilated properly (i.e, no fans and not much, if any, air flow) and with extended use, they get really hot and start to generate errors. Seagate's solution is to shut the drive down when not actually in use, which doesn't always play nice with Macs. Your drives may use a different technique for temperature control, or maybe none at all. Relatively small data transfers will allow the drives to recover; very large transfers won't, and to make things worse, as the drive heats up, the transfer rate will often slow down because of the errors. That can be seen if you leave Activity Monitor open and watch the transfer rate over time (a method which Seagate tech support said was worthless because Activity Monitor was unreliable and GoFlex drives had no heat problem).
If that's what's wrong, there really isn't any solution except using the smaller chunks of data which you've found works.

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

I get the spinning beach ball when I open preview, it wont go away, can i somehow stop the process its trying to do?

I get the spinning beach ball when I open preview, it wont go away, can i somehow stop the process its trying to do?

You can quit Preview by selecting it in Activity Monitor and then clicking on the red octagon 'Quit Process'. That does not solve the issue of the beach ball' as such. Perhaps. a reinstall of the OS might sole the problem. That is simply a guess on my part.
Ciao.

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 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.

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 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 C 2014.1 Crashing as soon as video is imported

Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.1.0.81
Application Timestamp: 5426694c
Fault Module Name: vidcap.ax
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5be085
Exception Code: c0000005
Exception Offset: 00000000000016a0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Information 1: 4e58
Additional Information 2: 4e585bbb5de0374ebb122afe33680fb4
Additional Information 3: 2bf0
Additional Information 4: 2bf0dfd7878ba2e9e99f058666e5c5f5
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
Any suggestions? The app crashes as soon as video is imported or a project is opened that already has video files in it.

Thanks Mark!
Switching to Software only render worked!
The graphics drivers are for the Intel HD Graphics 4400 card, Driver version: 10.18.10.3496
The full report is:
Intel(R) HD Graphics 4400
Report Date: Thursday, December 18, 2014
Report Time [hh:mm:ss]: 1:52:16 PM
Driver Version: 10.18.10.3496
Operating System: Windows* 7 Professional(6.1.7601)
Default Language: English (Canada)
Installed DirectX* Version: 11.0
Supported DirectX* Version: 11.0
Shader Version: 5.0
OpenGL* Version: 4.2
OpenCL* Version: 1.2
Physical Memory: 7879 MB
Processor: Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz
Processor Speed: 2494 MHz
Vendor ID: 8086
Device ID: 0A16
Device Revision: 0B
* Processor Graphics Information *
Processor Graphics in Use: Intel(R) HD Graphics 4400
Video BIOS: 2175.0
Current Resolution: 1600 x 900
* Devices connected to the Graphics Accelerator *
Active Displays: 1
* Built-in Display *
Display Type: Digital
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: Embedded DisplayPort
Device Type: Built-in Display
Maximum Image Size
Horizontal Size: 12.2 inches
Vertical Size: 6.69 inches
Supported Modes
1600 x 900 (60p Hz)
1600 x 900 (50p Hz)
Power Management Support
Standby Mode: Supported
Suspend Mode: Supported
Active Off Mode: Supported
Hope that helps, and thanks again!

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!

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!

Can't get GeForce GTX 560 Ti card CUDA to work with new Premiere Pro CC 2014 version

In the past I've been able to get CUDA on my GeForce GTX 560 Ti card to work with Mercury Playback engine by adding "GeForce GTX 560 Ti" to the cuda_supported_cards.txt file. But with the new CC 2014 version of Premiere, that file isn't in the Premiere Pro directory anymore. Is there a way to get my GTX 560 Ti to be listed as a CUDA-supported card with CC 2014?

Okay, I figured it out. I installed the latest graphics driver and then opened the NVIDIA control panel. In there I selected "Manage 3D settings" and went to the "program settings" tab. I selected Adobe Premiere (adobe premiere pro.exe) from the list and under the "CUDA - GPUs" feature, I changed it to "Use these GPUs" and selected my GTX 560 Ti (which was the only one listed).
After doing that, I opened Premiere Pro CC 2014 and selected "Project Settings - General" and was then able to choose "Mercury Playback Engine GPU Acceleration" under Renderer (which had previously been unavailable).
Hopefully this will help someone else if they encounter the same problem.

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 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 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 version) crashes (beach ball) when trying open certain large Projects

Similar Messages

Maybe you are looking for