Pro Crashed When Opening Project

Working in CS3.  I have a completed project, only need to export the final product, but when I now open the project file I get this message - 

sorry about that - 1/2 of my message didn't post...
message reads: Adobe Premiere Pro CS3 has encountered a problem and needs to close.  We are sorry for the inconvenience.
There isn't an error message assigned to help me understand what the issue is - it could be a corrupted file, but maybe there is another reason.
Thoughts?

Similar Messages

  • Premiere pro crashes when opening project

    Premiere pro project crashes when opening. I have an imac running OS 10.7.3 (8GB Ram, AMD Radeon HD 6970 2048mb) and have Premiere Pro 5.5.2. I have had 2 projects that I have worked on for hours and saved numerous times and then when I closed pp and tried to reopen the file the screen goes white and then crashes. Please help.

    Ann, THANKS for replying!
    If I open a brand new project, which I could do before, and then IMPORT a previous project, it works and I can edit and export the project.  However, it did crash upon trying to save it and I still can not just open a previously created project.  When I do I get an error message that Says: "Premiere has encountered an error and needs to close down.  We will attempt to save your project."
    Do you or anyone else have any ideas?

  • Frequent crashing when opening projects

    10.5.8, LP 9.0.2, Mac Pro 8-core 6GB RAM
    Logic frequently stalls/crashes when opening projects. This happens most often with projects that have lots of sampler instruments (primarily VSL), but some of the time with no samplers at all. The loading window generally hangs on Vienna Instruments with projects that have them, and on Space Designer with projects that don't.
    The project this happens most frequently with is an orchestral template I'm creating. It has about 25 instances of Vienna Instruments (totalling 1.34GB worth of samples), a few channel EQs and one instance of Space Designer. Other projects that have caused the crash include about 10 native software instrument plugins, 1 Akoustic Piano and 10-15 native effect plugins. I consulted VSL tech support who said the problem was most likely with Logic. I'm inclined to agree, since the problem happens with and without any Vienna Instruments, and Vienna Ensemble Standalone has no problem loading templates with a lot of samples.
    Does anyone have any suggestions to troubleshoot? Has anyone had similar experiences? Thanks.

    Well, this has happened to me too. To the point where I've lost all the work, because Logic can't open the original project or the "crashed" copy it creates. Happened again with a new project I'm working on, albeit on a much more modest laptop system.
    Annoying. Makes me think about switching DAWs...what else can you do if Logic can't be trusted.

  • PSE 6 on Mac Book Pro Crashes when opening a picture

    Whenever I try to open a picture PSE crashes. This is similar to another post but I should not be having RAM or generation issues. I have removed and downloaded from different DMGs all to no avail. Please advise.
    Thanks

    Thanks for the comment but I wasn't asking about viruses.  The thread I asked on solved the other user's issue because of the Norton incompatibility. I was referring to the original question which had nothing to do with viruses.  I open elements and try to open a picture from iphoto to work on and elements quits.  Since I don't have Norton or any other anti virus program, I was hoping there was another explanation which would apply to my situation.  Any ideas?
    Date: Tue, 4 May 2010 16:34:51 -0600
    From: [email protected]
    To: [email protected]
    Subject: PSE 6 on Mac Book Pro Crashes when opening a picture
    There's really no need for Norton on the Mac - because there is no such thing as a Mac virus.  I realize that this could change tomorrow, but as of today, there is no such thing as a Mac virus.  There hasn't been for about a decade.
    You can remove Norton.  I removed it from my Macs about a decade ago. 
    To prevent any future viruses from getting in, set up a new sub-user account on your Mac, and start using it.  Don't run your Mac as the Administrator.
    When you run as a lowly user, your Mac keeps an eye over what you do, and demands the Administrator's name and password whenever you do something suspicious.  That won't be a problem 99.9% of the time.  It's only a problem when you try to install an application or a utility. 
    Keep that limitation in mind, and use it to your advantage.  A virus is an application that pretends to be something else.  It lures you into installing that virus onto your computer.  Let's say in the future you download what you think is a photo.  It's really a virus.  You double-click on it to launch Photoshop Elements.  Instead, you launch the virus, which starts to install itself on your Mac. 
    At that point, everything comes to a screeching halt when the Mac operating system stops the installation, and puts a message on the screen.  That message will say something like, "Please type the Administrator's name and password to INSTALL THIS APPLICATION into the Applications Folder."  That is your tipoff that you aren't dealing with a photo.  You are dealing with an application. 
    At this point, you should ask yourself, "Why is a photo trying to install anything?"  Whenever the Mac operating system asks for the Administrator's name and password, you should ask yourself if you know exactly what is being installed.
    If you were running your Mac as the Administrator, then you wouldn't get this warning messages.  The Mac would say, "Well, I guess he knows what he's doing, so I'll install this application."  And the still-to-be-written virus would be installed on your Mac.  It's a lot easier to keep viruses off your computer than to try to remove them once they get in.
    This is why you don't need anti-virus software on the Mac - if you have an intelligent user operating the computer as a sub-user.
    >

  • Ae crashing when opening project

    Since of yesterday AE started crashing when opening a project which i worked on a few weeks ago.
    We opened it on a PC, saved, with a new name. and it would open just fine. When reconnecting the files (AI-drawing) it crashed again. Renamed the drawing and replaced the originals with the new ones, layer by layer. Everything worked ok.
    Just now, same thing, can't open any of the versions of the project. And it gives a warning saying that it crashed when opening windows. Do you want to open those windows again? Some versions of the project, i can open when clicking no. other crash anyway. What the heck is going on?
    Others open fine, but this not. It involves some puppet tools scripts that i bought from aescripts...
    I'm running a new Mac Pro, with the latest version of Mavericks, and latest version of AE.
    tried to open with preview off, tried trashing the prefs etc. nothing seems to help.
    /r
    Process: After Effects [488]
    Path: /Applications/Adobe After Effects CC/Adobe After Effects CC.app/Contents/MacOS/After Effects
    Identifier: com.adobe.AfterEffects
    Version: 12.2 (12.2)
    Code Type: X86-64 (Native)
    Parent Process: launchd [193]
    Responsible: After Effects [488]
    User ID: 501
    Date/Time: 2014-05-09 18:23:39.073 +0300
    OS Version: Mac OS X 10.9.2 (13C1021)
    Report Version: 11
    Anonymous UUID: 54D14E8C-AAA4-87E4-1B62-F54E0133DECE
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000845
    VM Regions Near 0x845:
    -->
    __TEXT 0000000100000000-0000000100004000 [ 16K] r-x/rwx SM=COW /Applications/Adobe After Effects CC/Adobe After Effects CC.app/Contents/MacOS/After Effects
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 BEE.dylib 0x000000010127e703 BEEp_FlattenLayerParamFunc(TDB_ParamLayerStream const*, bool) + 67
    1 TDB.dylib 0x000000010251fbbe TDB_ParamLayerStream::GetFlattenedReserved0() const + 62
    2 TDB.dylib 0x0000000102502ccf TDB_Stream::Write(SLU_File*) const + 1519
    3 TDB.dylib 0x0000000102517f30 TDB_StreamGroup::Write(SLU_File*) const + 992
    4 FLT.dylib 0x00000001019f9228 FLT_FCSeqSpec::Write(SLU_File*) const + 1688
    5 TDB.dylib 0x0000000102517f30 TDB_StreamGroup::Write(SLU_File*) const + 992
    6 TDB.dylib 0x0000000102517f30 TDB_StreamGroup::Write(SLU_File*) const + 992
    7 BEE.dylib 0x000000010124ba08 BEE_Layer::WritePlus(SLU_File*, BEEp_FileInfo*) + 168
    8 BEE.dylib 0x000000010125c615 BEE_ReattachAllItems() + 6517
    9 BEE.dylib 0x00000001011243fc int LIST_ForEachT > >(std::vector >*, long, int (*)(std::vector >*, long, int, std::vector >::value_type), int*) + 76
    10 BEE.dylib 0x000000010124c7c4 BEEp_WriteItemFunc(void*, BEE_Item*, BEE_FolderItem*, int) + 1988
    11 BEE.dylib 0x0000000101197995 BEE_ForEachItem(BEE_Project*, BEE_FolderItem*, int (*)(void*, BEE_Item*, BEE_FolderItem*, int), void*, int) + 261
    12 BEE.dylib 0x000000010124c40a BEEp_WriteItemFunc(void*, BEE_Item*, BEE_FolderItem*, int) + 1034
    13 BEE.dylib 0x000000010119f4b6 BEE_GetDefaultFolder(BEE_Project*, int, unsigned char) + 2038
    14 BEE.dylib 0x0000000101197995 BEE_ForEachItem(BEE_Project*, BEE_FolderItem*, int (*)(void*, BEE_Item*, BEE_FolderItem*, int), void*, int) + 261
    15 BEE.dylib 0x0000000101256a4e BEE_SaveProject(BEE_Project*, unsigned int, unsigned int, int, int, int, int, BEE_ActiveItemInfo const*, std::set, std::allocator > const*, FILE_Spec*) + 5198
    16 com.adobe.AfterEffectsLib.framework 0x0000000100707605 CPDir::SaveProjectToFileSpec(FILE_Spec*, int, bool) + 309
    17 com.adobe.AfterEffectsLib.framework 0x0000000100708ff7 CPDir::DoSave(int) + 55
    18 com.adobe.AfterEffectsLib.framework 0x0000000100709197 CPDir::DoSaveAs(FILE_Spec*) + 183
    19 com.adobe.AfterEffectsLib.framework 0x00000001002bb765 TestEmergencyUnhandledExceptionHandler() + 293
    20 com.adobe.AfterEffectsLib.framework 0x00000001002bb3de SetupEmergencyUnhandledExceptionHandler(bool) + 542
    21 U.dylib 0x0000000102f8071a Up_InvokeUnhandledExceptionOrHardwareErrorHandler() + 74
    22 U.dylib 0x0000000102fbe8a2 SetupHardwareExceptionHandling(bool) + 418
    23 com.adobe.dvacore.framework 0x00000001034f7041 (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 337
    24 libsystem_platform.dylib 0x00007fff8fd2b5aa _sigtramp + 26
    25 PIN.dylib 0x00000001021c99e1 std::vector<_t_PDOCG*, std::allocator<_t_PDOCG*> >::_M_insert_aux(__gnu_cxx::__normal_iterator<_t_PDOCG**, std::vector<_t_PDOCG*, std::allocator<_t_PDOCG*> > >, _t_PDOCG* const&) + 465
    26 PIN.dylib 0x00000001021c830b PDFLayerOCG::_GetBounds(_t_ASFixedRect&) const + 299
    27 PIN.dylib 0x00000001021be016 D_YMp_GetBounds + 1270
    28 PIN.dylib 0x00000001021bdb74 D_YMp_GetBounds + 84
    29 PIN.dylib 0x00000001021c3b27 D_YM_NewSeqSpecFromFile + 3847
    30 PIN.dylib 0x00000001021c4df2 D_YM_SynchSeqSpec + 1586
    31 PIN.dylib 0x0000000102086c38 PINp_SynchSeqSpec + 840
    32 PIN.dylib 0x000000010203c05e PIN_FinishPartialRead + 1166
    33 PIN.dylib 0x000000010203c4a5 PIN_ReadSeqSpec + 1013
    34 BEE.dylib 0x000000010124f357 BEEp_ReadItemChunk(BEEp_FileInfo*, SLU_ChunkInfo const*, BEE_FolderItem*, M_Ratio const*, BEE_Item**, unsigned char, BEE_Project*) + 2103
    35 BEE.dylib 0x00000001012516fc BEEp_ReadOneItem(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*, bool) + 140
    36 BEE.dylib 0x000000010125160a BEEp_ReadItems(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*) + 74
    37 BEE.dylib 0x0000000101250d9b BEEp_ReadItemChunk(BEEp_FileInfo*, SLU_ChunkInfo const*, BEE_FolderItem*, M_Ratio const*, BEE_Item**, unsigned char, BEE_Project*) + 8827
    38 BEE.dylib 0x00000001012516fc BEEp_ReadOneItem(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*, bool) + 140
    39 BEE.dylib 0x000000010125160a BEEp_ReadItems(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*) + 74
    40 BEE.dylib 0x0000000101250d9b BEEp_ReadItemChunk(BEEp_FileInfo*, SLU_ChunkInfo const*, BEE_FolderItem*, M_Ratio const*, BEE_Item**, unsigned char, BEE_Project*) + 8827
    41 BEE.dylib 0x00000001012516fc BEEp_ReadOneItem(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*, bool) + 140
    42 BEE.dylib 0x000000010125160a BEEp_ReadItems(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*) + 74
    43 BEE.dylib 0x0000000101250d9b BEEp_ReadItemChunk(BEEp_FileInfo*, SLU_ChunkInfo const*, BEE_FolderItem*, M_Ratio const*, BEE_Item**, unsigned char, BEE_Project*) + 8827
    44 BEE.dylib 0x00000001012516fc BEEp_ReadOneItem(BEEp_FileInfo*, SLU_ChunkInfo*, BEE_FolderItem*, unsigned char, BEE_Project*, bool) + 140
    45 BEE.dylib 0x0000000101253f48 BEEp_LoadProject(FILE_Spec*, BEE_FolderItem*, unsigned char, unsigned char, unsigned char*, BEE_ActiveItemInfo*, unsigned int*, BEE_Project*) + 8424
    46 BEE.dylib 0x0000000101251d1f BEE_LoadProject(FILE_Spec*, BEE_FolderItem*, unsigned char, unsigned char, unsigned char*, BEE_ActiveItemInfo*, unsigned int*, BEE_Project*) + 175
    47 BEE.dylib 0x000000010114804c BEE_Idle() + 476
    48 BEE.dylib 0x00000001013239f5 BEEp_DoTask + 69
    49 BEE.dylib 0x0000000101147a17 BEE_DoCommand(short, BEE_CommandInfo*) + 567
    50 com.adobe.AfterEffectsLib.framework 0x0000000100705e4a CPDir::OpenFileSpec(FILE_Spec**, unsigned char, unsigned char, unsigned char) + 474
    51 com.adobe.AfterEffectsLib.framework 0x000000010024afce CEggApp::OpenDocumentGuts(FILE_Spec**, unsigned char, unsigned char, unsigned char) + 414
    52 com.adobe.AfterEffectsLib.framework 0x000000010024b52f CEggApp::OpenDocument(FILE_Spec**, unsigned char, unsigned char, unsigned char) + 383
    53 com.adobe.AfterEffectsLib.framework 0x00000001000ab68a GetAECocoaApplication() + 5978
    54 com.apple.AppKit 0x00007fff9302c0e5 __69-[NSApplication(NSAppleEventHandling) _handleAEOpenDocumentsForURLs:]_block_invoke + 1651
    55 com.apple.AppKit 0x00007fff92e27c23 __78-[NSDocumentController(NSInternal) _autoreopenDocumentsWithCompletionHandler:]_block_invoke_2 + 140
    56 com.apple.AppKit 0x00007fff92e2780d -[NSDocumentController(NSInternal) _autoreopenDocumentsWithCompletionHandler:] + 746
    57 com.apple.AppKit 0x00007fff92c92b7b -[NSApplication _reopenWindowsAsNecessaryIncludingRestorableState:registeringAsReady:completionHandler:] + 323
    58 com.apple.AppKit 0x00007fff9302b9e9 -[NSApplication(NSAppleEventHandling) _handleAEOpenDocumentsForURLs:] + 306
    59 com.apple.AppKit 0x00007fff92c9243b -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 450
    60 com.apple.Foundation 0x00007fff8e8fef0a -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 294
    61 com.apple.Foundation 0x00007fff8e8fed7d _NSAppleEventManagerGenericHandler + 106
    62 com.apple.AE 0x00007fff9797ae1f aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 381
    63 com.apple.AE 0x00007fff9797ac32 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 31
    64 com.apple.AE 0x00007fff9797ab36 aeProcessAppleEvent + 315
    65 com.apple.HIToolbox 0x00007fff8dab7161 AEProcessAppleEvent + 56
    66 com.apple.AppKit 0x00007fff92c8e246 _DPSNextEvent + 1026
    67 com.apple.AppKit 0x00007fff92c8da2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    68 com.apple.AppKit 0x00007fff92c81b2c -[NSApplication run] + 553
    69 com.adobe.AfterEffectsLib.framework 0x000000010030d661 CApplication::Run() + 65
    70 com.adobe.AfterEffectsLib.framework 0x000000010027ec96 MainMain(bool, bool, bool, bool, bool, bool, unsigned short const*, bool, void**, int, int, int) + 918
    71 com.adobe.AfterEffectsLib.framework 0x000000010027e8cb EggMain(bool, bool, bool, bool, bool, bool, unsigned short const*, bool, int) + 59
    72 com.adobe.AfterEffects 0x00000001000038ae main + 1838
    73 com.adobe.AfterEffects 0x0000000100003174 start + 52

    Thanks, been trying hard to think what change could cause this, but can't.
    Switched to another hardrive at some point, though. But no software updates.
    Hid the ai-files, and opened up the project. Worked fine.
    Replaced the ai-layers with an jpeg. Seems to work.
    But, did the same thing a few days ago already. Opened up the project without the original ai-file.
    Renamed the ai-file and replaced all the layers with the layers from the new one.
    Worked well for a day or two, then started crashing again.

  • Premiere Pro CS6crashes when opening project files ...

    01
    02
    After I work on my videos for long time, now Premiere Pro crashing when i open my projects.
    It's hepen after I updated adobe softweres.
    Can some one help me?

    OS: Windows 8
    Operating System:        Windows 8 Pro 64-bit (6.2, Build 9200) (9200.win8_gdr.121023-1503)
    Language:                       English (Regional Setting: English)
    System Manufacturer:  ASUSTeK COMPUTER INC.
    System Model:                Z9PE-D8 WS
    Processor:                       Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (12 CPUs), ~2.0GHz
    Memory:                         32768MB RAM
    Available OS Memory:  32718MB RAM
    DirectX Version:             DirectX 11
    Adobe Premiere pro CS6
    I have Neat Video plug-in and I have used this plug in my videos projects.  I uninstalled this plug after I updated adobe software and I installed again. But still I can't open my project files.

  • LabVIEW Crashes when Opening Project

    Hey Guys,
    I'm running into an interesting issue where LabVIEW crashes when opening a project. This is the second time I've run into this issue, on the same project. To get around it the first time I simply deleted and re-made my project, but since it's happened again, I need to figure out how to debug it. The symptom is that LabVIEW will crash when opening the project (sometimes I can see the "vi loading" screen) without any indication that crash has occured. It doesn't even launch the error reporter, the process just dies. Anyone know how I can go about debugging this?
    Solved!
    Go to Solution.

    xkenneth86,
    What version of LabVIEW? Have you ever had previous versions of LabVIEW on your computer? Can you attach a screenshot of the crash?
    David H.
    National Instruments

  • FCP 6.02 Crashing when opening Project

    Hi,
    Going bananas trying to work out why a project I have been working on for 6months now causes FCP to crash when opening. I can open other projects fine, but when I try and open a project with all media offline I get the same issue.
    All drives are external and I have space on both local and external disks.
    I have tried opening the project from the autosave vault - which should work - to no avail.
    I have now reinstalled Final Cut Studio 2 with no change to the above.
    Any help would be appreciated.
    Thanks
    p

    Thanks Shane,
    I was running all the latest apps - Qt 7.3, FCP6.02 OSX 10.411, did all the updates etc.
    By erasing FCP and compressor I was able to get the project to open, but exporting through compressor kept crashing - which was an original fault that started happening before the project crash issue.
    Not wanting to waste any more time I did a complete erase and re-install of my computer, and after spending close to half a day doing it I think it's been worth it - though I'm going through the testing phase - although as it stands the project has been loading and compressor has been working properly (will test more though).
    I was using a couple of plugins that I downloaded from Apple's website: FX plugins manager of sorts, and I was using a filmic filter from that set which I think may have been corrupting the whole project.
    I will keep testing though...
    p

  • Soundtrack pro crash when open

    Soundtrack Pro crashes when I lunch it. The same Happens on my laptop, Powerbook G4 1.68 GHz 1.5 GB Ram 15". I have deleted all the related files and reinstalled and the same happens
    Anyone who can help?
    Process: Soundtrack Pro [363]
    Path: /Applications/Soundtrack Pro.app/Contents/MacOS/Soundtrack Pro
    Identifier: com.apple.soundtrackpro
    Version: ??? (???)
    Build Info: SoundtrackProProject-7030000~2
    Code Type: PPC (Native)
    Parent Process: launchd [104]
    Date/Time: 2008-07-08 23:20:04.278 +0200
    OS Version: Mac OS X 10.5.4 (9E17)
    Report Version: 6
    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000001, 0x000000008fe0105c
    Crashed Thread: 0
    Dyld Error Message:
    Library not loaded: /Library/Frameworks/ProMetadataSupport.framework/Versions/A/ProMetadataSupport
    Referenced from: /Applications/Soundtrack Pro.app/Contents/MacOS/Soundtrack Pro
    Reason: image not found

    Hi. I'm having the same problem. I just did a complete wipe and reinstall of my MacBook Pro and installed a fresh copy of Logic Studio. I've been using Logic Pro quite happily for a week or so but tried to open Soundtrack Pro for the first time last night and it barely bounced once in the dock then it said that Soundtrack Pro quit unexpectedly. I tried a couple of times including resetting the application but still no joy. I then reinstalled Soundtrack Pro only from the Logic Studio installer DVD but it still isn't opening. Any ideas would be much appreciated. My whole machine is up to date via software update and I have also run Disk Utility and there are no problems. There is basically nothing on my machine at the moment either having done a complete reinstall. Are there any library files that could be deleted to fool it into opening fresh again? Plists etc perhaps? My error log brings up the same thing at the bottom saying that no image was found.
    Will keep digging around the archives and see if I can come up with anything.

  • PE 8 crashes when opening project after loading Windows Live/Movie Maker

    Have a new HP computer with Windows 7 and plenty of RAM/ROM.  Loaded all the updates for Windows, PE 8.01, ATI, etc. but still crashed when I open a project.  It worked fine for the first 2 weeks, then I loaded Windows Live/Movie Maker and now PE 8 is unhappy.  Seems like lots of crashing issues but can't find this particular one.  Reload PE 8?  Remove Windows Live/Movie Maker?  Thanks if you have some help.

    The only thing I can think of is that Windows LIVE/Movie Maker is runnin
    g like messenger and Office LIVE and that would be disturbing for
    PE8... You can enter the pro
    ccesses with ctrl-alt-del and kill the Movie Maker proccess manually (in the handler) in that case and you would not need to uninstall it but repeat killing the proccess every time for PE8.
    Otherwise uninstalling LIVE Movie Maker should be fixing it if I take a guess, and I wonder doesn't you have Windows Movie Maker in the computer from start, why would you need/want Windows LIVE Movie Maker (at least my Vista has Movie Maker preinstalled)?

  • Premiere pro crashing upon opening projects

    Whenever I try to open a project I've previously been working on I get and error and Premiere pro crashes. I've found a workaround in the form of deleting my preferences, but I have to do this everytime which doesn't seem normal.
    First time using support so I'm not sure if I need to provide more
    This is the crashreport
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Adobe Premiere Pro.exe
      Application Version:          7.2.1.4
      Application Timestamp:          52aed7f3
      Fault Module Name:          aticfx64.dll
      Fault Module Version:          8.17.10.1230
      Fault Module Timestamp:          52540642
      Exception Code:          c0000005
      Exception Offset:          00000000000a1a4e
      OS Version:          6.1.7601.2.1.0.256.1
      Locale ID:          3081
      Additional Information 1:          3f3b
      Additional Information 2:          3f3bfa8c58092881edeecad35641e2c4
      Additional Information 3:          7bc3
      Additional Information 4:          7bc34bbf1df47809e434a387a1f71c12

    Hi justinB,
    Welcome to the Forums.
    Please go to the location of the mentioned aticfx.dll and move it to your desktop. This file might be a result of bad installation of Graphics Drivers. Please launch the Premier Pro and check if it works.
    Regards,
    Vinay

  • Premiere Pro crashes when opening the program. what to do

    Premiere Pro crashes every time when opening the program. Other creative cloud programs are functioning well. What to do?

    You may get more specific help in that forum http://forums.adobe.com/community/premiere
    When you go there, you need to provide a LOT more information for anyone to help
    -PPro Information FAQ http://forums.adobe.com/message/4200840
    Also, Go to http://forums.adobe.com/community/premiere and, in the area just under Ask a Question, type in
    crash on launch
    You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question

  • Photo app crashing when opening projects

    Every time I try to go into the projects I created using phot and its predecessor, the app crashes and closes

    Have you tried to repair the Photos library?
    Try to repair your Photos library using the First Aid Tools:
    Make a backup copy of your Photos Library  on an external drive.
    To repair hold down the  alt/option and the command key simultaneously while double clicking thePhotos application in the Applications folder  to launch the First aid tools. Hold down both keys firmly and long enough, until the First Aid panel will appear.
    The select "Repair ...".
    Can you create and open projects, if you create a new test library?  Launch Photos while holding down the alt/options key. Import a few photos and try to create a book or another project. Does that work at all, if you use a different library?

  • Soundtrack Pro Crashes when opening Audio File Project

    I am just starting to use Soundtrack Pro 2 with FCP 6. When I try to send an Audio File Project from FCP, Soundtrack Pro starts up, then closes. If I try to open the Audio File Project within Soundtrack Pro the program closes. Any Suggestions? Thanks.

    In trying workarounds, I exported the clip as a movie from FCP then tried to open it in Soundtrack Pro. STP closed. I also tried opening the (sent).stap file that FCP generated, and Soundtrack Pro closed again. Also, STP does not give me the error window saying the program closed unexpectedly and do I want to report it. It just stops. Any thoughts? Thanks a lot.

  • Logic crashes when opening projects

    I've just installed Logic 8 on my new Macbook Pro and installed a Focusrite LE interface. I created several projects yesterday (both MIDI and audio) without any problems but when I went back to them today, some open and close OK but others crash Logic when I've closed one project and then try to open another. Sometimes I launch Logic from the dock and it opens the previous project OK but other times it just launches the toolbar but the dropdown menus are locked and I have to force quit to get out of the software. It doesn't seem to happen on any particular file, nor does it happen every time (frustrating or what!!) but its certainly a major problem. Should I just reinstall Logic from the ground up or is there a bug or incompatibly issue with the software and the interface? HELP!!

    what a pain dude
    sounds like you tried all of the right things
    i assume you still get the same behavior even with no plugins, all new prefs, etc
    are you having issues with other programs?
    have you tried just creating a new project and see what happens when you open it repeatedly
    then try adding stuff and see what happens
    how is your drive?
    just brainstorming here
    i am a hobbyist so i don't have huge projects with tons of tracks, etc
    but even with a dual quad mac pro logic can take awhile to open
    it just sites there
    but there is no actual crash (unexpectedly quits)
    yeah i guess you might just try reinstalling it
    a minor pain but might be your best shot
    good luck!

Maybe you are looking for