Opencl acceleration makes premiere crash

I was really excited about premiere pro since I installed the evaluation version a few days ago, but today I'm just disappointed in Adobe and here is why.
This week-end, I switched to mercury openCL accelerated rendering, only to find out that premiere would crash without any error message as soon as some video or picture is to be displayed. After hours of searching websites and forums for a solution, uninstalling and reinstalling my amd graphics driver, I finally tried to contact a adobe premiere expert by chat. The guy answered me right away: no chat or phone support for evaluation versions.
I can understand the decision not to spend work effort on non-paying maybe customers, but the more I think about it, the more it makes me wonder if Adobe really understands what an evaluation software is all about... namely convincing people to buy their stuff:
I, the customer, find a neat piece of software, start evaluating it in order to decide whether or not it is worth my money. Starting to understand how it works, I try to get the most performance out of it, switch a setting and find out that the product actually is quite unstable on my setup (which is far from being exotic). My positive feeling about the product starts to wobble, but since I am quite convinced I don't put it away without searching for a solution. Used to get my hands dirty when computer issues arise, I put a few hours of effort into finding a workaround. Without success. Taking a closer look at Adobes support service, my positive impression is back: I can contact a premiere expert by chat.
And here it comes, counterproductive and just so... let's say it, stupid: Unfortunately, we don't provide chat or phone support to evaluation version users.
Come on, that can't be serious? I'm evaluating this software, and they make me understand: oh, it does not work? well, buy it, and then maybe we will make it work for you!
I love software business... It tries to make people accept the unacceptable. Imagine looking for a sports car. You find a very nice one which has a city mode which limits the engine to 50HP, and a much more exciting sports mode which unleashes all the 450HP it packs. They let you take a ride, you fall in love with the car, think about buying it for real. You want of course to know exactly what you're buying. Unfortunately, when switching from city mode to sports mode, the engine stops. Ok, bad impression... but you like the car and give them a second chance: you ask the dealer to check it out, so that you can try the other mode. How would you react to the dealer answering you: No, if you want to see what it's like, you must buy it first.
What the hell?! Who would not just walk away?
And here, I am supposed to pay for a piece of software that does not run properly on my PC?
How ... disappointing!

Hello Vinay,
Thank you for your answer.
I updated my version of permiere to 7.2.2 (33) today, unfortunately it still crashes as soon as opencl acceleration is activated.
My operating system is windows 8.1
I have 2 amd graphic cards in my rig:
R9 280x
HD5870
When I select mercury opencl, premiere crashes as soon as anything has to be displayed. It is independent of the type of material (pictures or videos) I browse in the media explorer and display in the source window. It crashes also as soon as I play the timeline, whether there are effects or not.
The videos and pictures I'm processing are all taken with a gopro hero3 and a galaxy note 3.
Regards,
Severin

Similar Messages

Mercury playback engine makes Premiere crash after cs6 update

Hi there everyone,
I have been working with Premiere cs5 for over a year without any serious errors. Since I upgraded the entire Creative Suite to cs6 however, I am forced to use the software playback method instead of the GPU accelerated one. Using the last mentioned causes Premiere to crash immediately when trying to drag any sort of video on the timeline. This happens in new projects as well as in cs5 ones; and all of the footage involved in both cases was ingested in the wellknown Matrox i-frame codec that always worked fine before. Specs:
Windows 7, 24 gB RAM (not sure whether DDR3 or 5), NVidia Quadro 4000, dual six-core CPU, several terras of HD @ 7200 rpm, Matrox MX02 LE, CS6.
I tried every possible combination and order of uninstalling an reinstalling Premiere, the Matrox drivers and the nVidia drivers, including older versions of the last two mentioned, but to no avail. Though it looks like an NVidia issue (I read somewhere about CS5 and 5.5 certified NVidia drivers but not CS6 yet) this problem manifested right after the upgrade to CS6.
The error reported is about the graphics card being reset, it stops and then recovers, leaving Premiere to hang. The card's hardware reacts with a noisy cooling fan acceleration sound that slowly falls back to its normal rpm.
-Sigh- I am sorry to bother you with this, but does anyone have any idea or experienced something similar? Does the combination of the mentioned elements ring a bell...?
Any help is utterly appreciated !

Hi Harm,
I couldn't find anything in the logs about temperature, but I did find some other logs. However: when I re-install a newer NVidia driver version, the PC will not crash, only Premiere crashes in that case, which lets me believe this is not just a hardware defect. The hardware however does play a role.
What I found in the event viewer are messages like:
A request to disable the Desktop Window Manager was made by process (4)
The Desktop Window Manager was unable to start because composition was disabled by a running application
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available ETC ETC.
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0 Problem signature:
P1: Adobe Premiere Pro.exe
P2: 6.0.1.0
P3: 4fac933f
P4: e05a
P5: 1 ETC ETC
The program Adobe Premiere Pro.exe version 6.0.1.0 stopped interacting with Windows and was closed.
The NVIDIA OpenGL driver lost connection with the display
driver due to exceeding the Windows Time-Out limit and is unable to continue.
The application must close. Error code: 7
Visit http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=3007 for more information.
Most of all I saw this:
Activation context generation failed for "C:\Windows\system32\vsnpstd3.dll".Error in manifest or policy file "C:\Windows\system32\vsnpstd3.dll" on line 2. The value "X64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
This report pops up hundreds of times... but I don't think the vsnpstd3.dll file, dating back to 2009, could be a problem all of a sudden.
It looks more like a Windows Time-out thing causing to reset the graphics card because the load of graphic data is too big to handle. The only strange thing is that the time-out action is taken by Windows before the usual two seconds have passed, it takes just a fraction of second. This leads me to believe that, during the demand from the Mercury Playback Engine to the NVidia card, "false information" is passed to Windows... i.e. a software problem.
I am thinking about rolling back to Premiere CS5 to see what happens... if this version would be working flawless again, that would be pretty steady proof for doubting the MPE of CS6.
To be continued...

CS3: MFX makes premiere crash down

When trying to open MFX-files in Premiere Pro CS3.2 I get this message: "sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project"
Does anybody know what I should do?
Best wishes,
Hallgrim

>1080p25
1 - do a test of filming at 1080i and see if that works
2 - convert to another format/codec and see if that works

Does Premiere CC 2014 use OpenCL acceleration in H.264 encoding or just for rendering?

It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?

Kenneth Badertscher wrote:
It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?
Transcoding is entirely CPU-bound. It's not something that can easily be parallelized, so there's no win in trying to send it to the GPU. The GPU can be used in exporting if you've added accelerated effects, or if you scale the video to a different resolution. Things that can be parallized fairly easily. Changing from one video format to another isn't one of those things, unfortunately.

Is Adobe Premiere Crashing on you??? - Solution to almost every cause...

I've been trying to fix this problem of mine, and I've found that countless people have had the same problem with previous versions of premiere and still do with even the more recent versions. I'm going to be posting this on multiple forums to help out. Well, I might be being a little cocky saying that I have a solution to every case of Adobe Premiere not working, but I will give as many solutions as I know starting with my problem, which I've had happen multiple times, and then go through the possible solutions to other countless people's errors that I've seen while trying to fix my problem.
It might almost seem like it's not worth it to go through all of my steps and instead just format your hard drive, but some people have too much stuff to have to copy off the drive to do that so that is why I'm posting this. For example, I myself have over a Terabyte of music on my computer =/.
PREMIERE PROBLEM CRASHES
When I would click on Premiere, no matter what version ( I only tried Adobe Premiere 6.5, Pro 7, and CS3 but I'm sure it would've been the same for all ) it would pop up as it usually does and then it would crash ( for search provider purposes I'm going to put every word I can think of ) lock up, freeze, shut down, close out, not work, wouldn't start, doesn't open, won't run, can't load, etc. Premiere 6.5 for example would say "Initializing" and then give a send or don't send error message. Similar thing for CS3 except it didn't say "Initializing" it said something else, but it would only say the first thing it would try to do and then the same error messages every time. This seemed to be an unfixable problem I've had multiple times with adobe premiere and I've tried the following possible fixes but none worked: System restores, uninstall and reinstall, uninstall all audio and video codecs I can find, Delete every adobe premiere file that exists on my computer including documents and settings / my documents / windows / program files / temp files / prefrence files / application data / etc., also going into my regestry editor and going to HKCU... as well as HKLM / Software / Microsoft / Windows / CurrentVersion / RUN and RUN Once and deleted any proccesses I knew I didn't need on startup, I've also tried unchecking Load Startup Items under the Selective Startup section using "msconfig" in the run command and then restarting without those background programs running and then tried Premiere, and I've even tried to do a repair install of Windows XP, but not a single one of those things in any combination would do the trick!!!
POSSIBLE CAUSES
The problem actually started after doing a system restore, maybe undoing something I wasn't aware of even though the system restore itself was only created a few days back so I'm not sure how that could be, none-the-less the problem started just after. It might have also had something to do with a new program I had installed to clean my registry. I don't believe that was the problem because after cleaning my registry and before the system restore the program worked just fine, but maybe the combination of the two things caused the problem this time. A few other problems I've heard of as possible causes / solutions are...
· Conflicts with Audio Codecs such as - Lame Mp3 / Ra-Audio codec12 / RC3 / etc.
· Conflicts with Video Codecs such as - Ligos, ffdshow, Darim Vision, Moonlight WinDivX, WMP DVD Playback, Core Video, Matrox, Fraps, etc. etc.
· Malware, Viruses, Spyware, bogus Registry Cleaners like RegCure, Pirated Software ( big no no), and other vulnerabilities.
· Prefrence files that needed to be deleted like: Prem60.prf, Premiere 6.5 Prefs - in C:\Documents and Settings\YourUserNameHere\Application Data\Adobe\Premiere, and a few other pref files I can't really remember.
· QUICK TIME, you should uninstall quicktime (which might have been my problem) and delete all files associated with it including Apple Software.
· Start Up proccess conflicts. Use Msconfig in the run command line to bring up msconfig, then under General / Selective Startup, uncheck Load Startup Items and restart your computer. If after restart Premiere doesn't work read on...
· Ace Mega Codecs Pack: This one can cause a lot of conflicts... Here's a screenshot of what your Ace MCP settings should be on through a Custom install, or you can use your control panel to modify an already existing install... http://frankreu.ipower.com//AceSettings.jpg
MY SOLUTION ( to possilby every case of Premiere crashing )
This is a very good solution to have so that you don't have to try all the other things first, I guarantee this is the best solution and it will take a little courage on your part but does the trick without having to format your Hard Drive. The first thing I did was uninstall all versions of Premiere, then Ace Mega Codecs pack v5.93.8971, I also uninstalled all extra audio codecs I could find, and uninstalled any extra software I didn't need on my computer while I was at it which might be causing the conflict such as Fraps, Growler Guncam, and any other little programs I didn't need and could reinstall. Even going as far as looking through the Program Files for things I didn't recognize, and if I were anyone else I would google it to make sure it is not a necessary file, and then delete all the folders to programs I had already uninstalled that were left over or other folders to things that I didn't need. If you're going to do this make sure you go into your My Computer folder, then at the top select the Tools tab and click on Folder Options, then on the view tab make sure that Show Hidden Files and Folders is selected and click apply. Then I went into C:\Documents and Settings\ (Every different account there was) and looked through the Application Data folders and the Local Settings folders for left over Adobe Premiere files and folders and deleted them all. I also cleaned out every temp folder I could find by selecting the files and pressing shift + delete to skip the recycling bin proccess. If you come across any files that say "cannot delete" due to file permissions just look on google for the program called Unlocker 1.8.7 and download it for free, here's the current link http://ccollomb.free.fr/unlocker/unlocker1.8.7.exe. After installing it, should only take seconds, you can right click on any file or group of files and click unlocker, then select the delete option and press the Unlock All button. If the process winlogon.exe or svchost is in the list of processes you are going to unlock do not do it, this will freeze up your computer. After deleting all those left over files you should use your Search command in your start menu to look for anything with the name Premiere in it, make sure you select Advanced Options and then put checkmarks next to Search System Folders, Search Hidden Files and Folders, and Search Subfolders. Delete all those files, but make sure they are related to Adobe Premiere and not something else. Then, and this may not be a necessary step so don't panic, I ran Uniblue Registry Booster to clean out my registry files of all unecessary entries and also did a registry defrag. Uniblue is software you have to pay for though so you might want to fish around on the internet for a good free registry cleaner, do not use RegCure though that one's a scam.
Then, and this is where you have to be kinda brave, I went into the registry editor by pressing the start button on my tastbar and opening the run command I then typed regedit.exe, or just regedit, to open the system registry editor. First you should make a backup of your registry before going any further by clicking the File / Export button, and saving the registry to your My Documents folder or somewhere else you will be able to find it. I would then use the Find command with all options checked to look for Adobe and then Premier seperately to make sure I found every place that had Premiere entries in it and then deleted those entries. Make sure you start from the top by having My Computer selected. Some would only say Prem~.exe and things similar to that, so that is why you have to look for Adobe as well to find all the entries. Once you click find, you can press F3 to do a find next and continue the seach after each value you delete. If a folder contained only a value with an Adobe Premiere property in it I deleted the whole folder. I then searched for the following words and began the same proccess with them: Ligos, Matrox, Fraps, Quicktime, and during the search if I saw any values I wasn't sure of because they didn't seem to be what I was referring to I left them alone. I also deleted any entries that I knew I nolonger needed in there such as Apple Software, and refrences to game demos or other programs I knew I had already uninstalled. Be carefull with that though, you should be absolutly sure before deleting anything from the registry. You have a back up so don't get too scared if you damage it, just double click your backup of the registry, then reboot and start over. Worst case is that you might have to do a windows repair install if you mess up.
Anyway, after you're done in the registry create a system restore point and then restart your computer. Once it loads up again try reinstalling Adobe Premiere and make sure you cross those figers, that's the most important part. Viola, that's my solution. If it doesn't work for you, well, most likely you have some serious malware or a trojan that just doesn't like Premiere. I myself use Panda Titanium 2009 as well as Uniblue PowerSuite to keep my system clean. If you can't afford that try Lavasoft Adaware freeware + Microsoft Malicious Software Removal Tool and see if they don't catch anything. Good luck, and I really hope that I help at least one person with all of this lol.

Jeff:
I have had both good and bad experiences with Acronis True Image. I got the recent copy of ATI via a Newegg.com bundle. I haven't tried it yet on any Windows 7 editing systems. ATI installs some services that I would rather not have running in the background.
What made you change from ATI to ShadowProtect Desktop Edition?
Are you running Windows 7?
What do you see as advantages to running ShadowProtect Desktop Edition as opposed to Acronis True Image?
Thanks

Premiere crashes every time I try to copy a Sequence that contains a nested sequence

I'm working a project that has a lot of multicam sequences in it and I'm having a problem with Premiere crashing. I want to be able to iterate my sequences for versioning as I go through and make changes requested by my client for final approval but don't want to get rid of the old versions in case I need to go back for something later. I use the as a general practice because I've learned the hard way that it's much easier to save everything and need it rather than start making changes that I might want to get back later
Most of the items don't have any issues; footage, gfx .movs, stills, etc. all copy and paste fine as do my 'source' sequences which have 3 video tracks (cam 1, cam 2, and a gfx track). I am then dragging those sequences into a new sequence and 'Enabling Multicam' on that clip so I can use the multicam function of the Program monitor (a great feature I might add). However, I am now going back and making changes and want to create new iterations of my 'Multicam Sequences' and when I go to Copy them Premiere crashes. I also tried right-clicking and selecting 'Duplicate' but this also causes a crash. Does anyone have any suggestions as to why this is happening? I think I'll need go ahead and submit a bug report because I really can't think of why this should be the case.
The only workaround I have thought of is to create new sequences and drag the contents of each of my old timelines into new, revisable sequences while still retaining my old originals.
I'm on a PC with Windows 7 Professional and have all the updates for the newest version of Premiere CC

Sounds similar to what's happening to me. I'm on a Mac with Premiere CC.
When I try and duplicate audio tracks, crashes almost every time.

Adobe CS4 (64bit) Potoshop, InDesign, Premiere crashes on startup

I am in need of some major help. I have a user who only on his profile Adobe Potoshop, InDesign, and Premiere crash on startup. I've tried most of the basic trouble shooting but still not working. Any Ideas?
Computer Specs:
HP z400 Workstation
Intel Xeon W3520 2.66 8MB/1066
6GB of RAM
ATI FirePro V5700 512MB Graphics

I was going to suggest resetting application preferences, but with multiple applications crashing, perhaps the problem is with the system...
First, I think I'd look to see if there are any updated display drivers available for the user's system, from the web site of the maker of the display adapter (video card).
You can try to see if disabling OpenGL support in Photoshop restores operation: Edit - Preferences - Performance, uncheck [ ] Use OpenGL Drawing.
If you do want to try to reset Photoshop preferences back to defaults, which is known to correct a lot of problems, have the user do this:
1. Press and hold Control - Shift - Alt immediately after starting Photoshop from its shortcut or menu item.
2. When the prompt "Do you want to set preferences back to defaults" comes up, confirm.
Best of luck.
-Noel

Premiere Crashes Upon Opening Project

Note: I'm using the newest version of Premiere Pro CC on a (maxed out) Retina Macbook Pro 2012.
This just started happening. When I open a project, Premiere crashes and gives me the below pop up, blocking me from doing anything within the project. It just keeps happening every time I open the project file, even if I make a copy of the original.
I uninstalled Premiere and installed it again - without the latest update - and it worked fine. But I want this to work with the latest update because I'm not paying a subscription to have the ability to update taken away.
Note that I also experienced this pop up recently when playing back MTS files within Premiere in the same project file. I used the built-in Media Explorer and it worked. Dragging and dropping the files from Finder to Premiere was causing it to act up. Not sure why this happens b/c D&D worked in previous versions.
Here's the error:
Thanks.

Hi Emoral7,
.mts files are avchd files having metadata which is required by premiere pro to read and interpret those files. When you browse the files through media browser, premiere pro reads the folder structure and the metadata of those files and imports them accordingly. If you drag and drop it directly in the project panel the folder structure of the files are damaged and premiere pro does not interprets them correctly because of missing metadata. CS6, was not so strict about the folder structure and sometime interprets the files correctly, but CC is little more strict aboit the folder structures and metadata files. For more information about folder structure of .mts files you can check help file of premiere pro.
Regards,
Vinay

Just installed Quadro 4000 Mac, now Premiere crashes when I try to open existing project

Mac Pro 4,1
Premiere Pro 5.5
OS X 10.6.8
I just replaced the stock ATI card with a PNY Quadro 4000 for Mac.
Via CUDA Preferences, have updated CUDA driver to 4.0.50
GPU driver is 1.6.37.0 (256.02.25f01)
When I try to open any existing Premiere project, Premiere crashes.
This happens whether I'm running the OS X 32-bit kernel or the 64-bit kernel.
If I launch Premiere and create a new project, Premiere seems to run OK. (I haven't yet tried adding any content or working with the content.)
As you can imagine, the only reason I shelled out for the CUDA-capable card was to take advantage of the hardware acceleration in Mercury. So ... not a very satisfying "upgrade" so far.
Any clues?

There are four sequences in all. Two are super-simple, with only one clip in each. A third has only a single clip plus four titles. The main sequence has multiple clips, two stills and three titles plus one extra audio track.
When the crash occurs, there's no error dialog box. What I see is this:
After I double-click the project file -- or open Premiere and choose the project from the splash screen -- the "loading" progress bar appears and seems to complete loading.
Premiere starts to draw the window for its workspace. It creates a solid white rectangle, the wristwatch "wait" icon appears briefly, then Premiere crashes.
The log captured by the Apple and Adobe crash reporters shows (among much else):
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
The last few lines captured for Thread 0 are:
77 com.adobe.premiere.frontend
0x000000010c7b4aa4 FE::MacApplication::RunSelf(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 164
78 com.adobe.premiere.frontend
0x000000010c7621a7 FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 2503
79 com.adobe.premiere.frontend
0x000000010c7b7c1d AppMain + 253
80 com.adobe.premiere.startup
0x000000010c9343e8 (anonymous namespace)::LaunchFrontendFramework(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 232
81 com.adobe.AdobePremierePro
0x0000000100003540 (anonymous namespace)::CallStartupFramework(int, char const* const*) + 288
82 com.adobe.AdobePremierePro
0x0000000100003ac7 main + 167
83 com.adobe.AdobePremierePro
0x00000001000033a8 start + 52

Analyze Content in batch send from Premiere Crashes

When selecting all video files in bin and sending to AME for batch analyze content, AME partially completes the first file and crashes every time. This leads to Premiere crashing as well. Unable to process even 1 file through analyze content for speech recognition, adobe story script synchronization or face recognition.
Files: Canon 5D Mark II H.264
AME version 6.0.2.81 (64-Bit)
Windows 7 Professional 64 Bit
i7 930
24 GB Ram
dual GTX 460 1GB GPU's

I talked to Adobe Tech support earlier however and decided to uninstall then reinstall Premier Pro and not update it. It has worked perfectly since, so if anyone else id having this problem I'd suggest trying John/Bill's approach first and if that doesn't work, reinstall withough updates. (or at least not the update prior to today)
Hmm... this makes me think that maybe you got bit by the "revert to trial when updating" bug that pops up every now and then, seemingly inexplicably. The problem is that when your installation reverts to trial mode, most MPEG-based assets become unusable. I can't recall if MP3s (which are MPEG-based) fall into the "unimportable" category or not. Had you updated to 5.0.3 just before this happened?
You almost certainly want to update--simply because of the numerous bug fixes and stability improvements--so if it happens again, be sure to deactivate the software, uninstall, run the Adobe CS5 Clean Tool a couple of times (rebooting each time), and then reinstall and update. You should be in good shape then.

Missing Mercury Playback Engine GPU Acceleration after computer crash. How can I get it back

Hi, I'm missing Mercury Playback Engine GPU Acceleration after computer crash. How can I get it back? I had my husband update my graphic driver. How what do I do? When I check the project settings > general, it still has the field of Mercuy Playback software only grayed out.

restart your computer and retry.
if that fails and you have a mac and premier, How to Enable Premiere Mercury Playback GPU Acceleration CUDA on iMac

Premiere crashed, my project won't open because of an "unknown error," and my autosave apparently stopped working 6 hours ago... Any solution?

I'm working in Premiere Pro CC 2014 on an early 2014 iMac. I started to notice my session was getting kind of buggy - audio clips started missing from my timeline, effect controls on some of my video clips had set themselves to the defaults. So I was trying to fix some of these things as I was editing. I save compulsively (like after every couple of edits), so I had not noticed that my session was no longer auto-saving.
Suddenly Premiere crashed. The recovery file will not open "due to an unknown error." The original file that crashed will not open either (same message), and I notice the file size is about half of what it should be. When I tried to open an auto-saved version, I discovered that the last auto-save was last night at about 10 p.m. (I quit working last night at about 1 a.m., so it just spontaneously stopped autosaving midway through my edit session.)
I followed all the suggestions I could find in forums. I trashed preferences, and I moved all my media into other folders. But the session won't open even far enough that it starts asking for media. When I create a new project and try to import my old edit sequence, dynamic link won't even get to the point where it asks me to select what sequences I want to import. It just sits there forever trying to open the file and can't.
Any suggestions?

Additional info - As I look further into the problem, it's even worse than I thought. The autosave files that say they're from last night are actually referencing work from days ago. So evidently, my auto-save is either putting incorrect time stamps on the files, or the project files are referencing old sequences. Either way, I cannot seem to locate a project file that contains a reasonably recent version of my cut, even though the time/date stamps on the files indicate they shouldn't be that old.

Premiere crashes constantly after update to CUDA Driver Version: 7.0.35

I have had troubles with the dreaded garbled screen bug, it occurs after working with premiere for more than an hour or working with 4K material or large graphic files.
But since updating to CUDA Driver Version: 7.0.35 premiere crashes immediately after starting the same project that worked the previous day. Only switching to open CL stops premiere from crashing.
Please advise!
yosemite 10.10.2 (14C1514)
Identifier:            com.adobe.AdobePremierePro
Version:               8.2.0 (8.2.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Adobe Premiere Pro CC 2014 [544]
NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f175

I moved from Version 5.. to 7.0.36 and the crashes started. Also strange pixelating on some screens. Is there a way to go backwards on the drivers or do I use Open CL until CUDA or Adobe or Apple comes up with a fix?

Premiere crashing if using other applications

I'm having problems with Adobe Premiere crashing on me.
It seems to happen whenever I use another application (like Chrome or Windows Explorer) while Premiere is open, then go back to Premiere. It pretty much instantly crashes as soon as I click inside the Premiere window.
This is the error message I get in Event Viewer:
Faulting application name: Adobe Premiere Pro.exe, version: 7.2.1.4, time stamp: 0x52aed7f3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000005
Fault offset: 0x0000000000018e5d
Faulting process id: 0x530
Faulting application start time: 0x01cf3baa978a06e0
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e214e2e5-a79d-11e3-a90b-bc5ff4488183
My system:
Intel i7 3770 @ 3.5 GHz
8GB RAM
Nvidia Geforce GTX 670 (Driver: 334.89)
Windows 7 Pro 64bit
*edit*
I've done a little more testing and found out that it doesn't have anything to do with using other applications. It happens if I minimize Premiere as well.
Another thing which might help pinpoint the problem: if I open a new empty project, it's fine, but if I add a new sequence and minimize Premiere it crashes instantly.
Message was edited by: machinemade
*edit 2*
I seem to have figured it out. I did a reset of the prefrences (by holding ALT while starting Premiere) and it hasn't crashed since.
I also installed the newest Quicktime. Not sure which of these changes fixed my problem, but it seems to have done it.
Message was edited by: machinemade

hi rutra!
hmmmmm. let's just check through the possibilities here:
How to troubleshoot "Cannot lock iPod" error message
let's try making sure that "terminate and stay resident" programs like antivirus packages are also shut down prior to trying the update. this InstallShield article might be of some help with that:
Close Applications Running in the Background
love, b

Premiere Crashes when sending Audio File to Audition

On OSX Lion, 12-core Mac Pro...
Premiere crashes whenever I attempt to EDIT a file to Audition from timeline. Happenes everytime. Fully updated on all programs...

Best to post specific product questions in that product's forum
http://forums.adobe.com/community/premiere/premierepro_current?view=discussions

Opencl acceleration makes premiere crash

Similar Messages

Maybe you are looking for