Illustrator/indesign and premire pro cc 2014 crashes after splash screen

Hi, I can't figure out whats going on, I had CC running fine, the 2014 updates came and all software except photoshop crash after the splash screen. I have done everything I could think of. Verified fonts, I've uninstalled and re-installed creative cloud and the software. I ran adobe cleaner which get rid of the original CC software (I didn't want that to happen) I've deleted preferences, ran disk permissions and repair. CS6 software install and runs.
I am lost to say the least as to why photoshop CC 2014 works and yet, the others crash. Any Ideas?
Thanks.

Hi camdude,
Can you send the Adobe Illustrator CC 2014 crash logs to me at [email protected]
The steps to get the crash log are:
1) Open the finder app.
2) Press command +shift + g to open the "Go to the folder" dialog.
3) In the text edit field type "~/Library/Logs/DiagnosticReports".
4) This will take you the DiagnosticReports folder.
5) Please share the latest crash log file from this folder.
With Best Regards,
Raghuveer

Similar Messages

Premiere CC 2014 Crashes on Splash Screen

Hi there,
Running Premiere CC 2014 on Win7x64. A few days ago it began crashing on the startup screen right after attempting to launch the program. I have updated/rolled/back/changed my nvidia drivers (geforce 770) so many times at this point I cannot count...have removed ALL adobe programs and reinstalled, cleared cache, cleared prefs, emptied media cache....feels like I've tried everything.
Have been on the phone with both nvidia AND adobe, who have sent me back and forth a few times. I think it's a Premiere issue because the other cuda accelerated programs I try run just fine.
Help!

Thanks for the response, Mark. One of the crazier things about this is that windows update is also malfunctioning and its service will not initiate when told to do so...it's even set to Auttomatic Delayed start. So this leads me to believe that windows had a failed software update, and Premiere is feeling the effects of that. The only other thing on your list I could that seem logical would be a corrupt user pref setting (#1), however I deleted all prefs when uninstalling all the adobe programs before reinstalling. After 2 hours on the phone with Nvidia I have determined the graphics card is not the issue.
Here's the windows event log:
====================================
Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
Faulting module name: dvaui.dll, version: 8.0.1.21, time stamp: 0x53c76970
Exception code: 0xc0000005
Fault offset: 0x00000000002f4e39
Faulting process id: 0x1aa4
Faulting application start time: 0x01cfddacf2c64f1b
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: 32b540fc-49a0-11e4-9537-74d02b2a846b
=====================================
Every single time it crashes, dvaui.dll is the file being referenced. What is that DLL responsible for? Thanks for helping me resolve this.

MacBook Pro Hard Disk Crashed after Frozen Screen

Hi
Very unpleasant experience with my first MacBook. My MacBook Pro Book 13'' (late 2010 model) screen froze on start up. Realised that the battery was low and plugged the power adapter in, and let the frozen screen continue hoping for it to start in a while, only to realise that the entire laptop heated up significantly. I switchd the laptop off and let it simply recharge.
No luck on restarting after laptop was fully charged despite several attempts and following all instructions on Apple website, including SMC reset. I took the laptop down to the store and the Genius Bar team informed me that the hard disk had corrupted and they could not retrieve any data.
Wondering if this is a common problem, as I have never had a hard disk failure before and specially surprising as it is relatively new laptop (<1 year) old ? Seems like a technical fault with the laptop prima facie. Some data was not backed up recently, and now I need to look for a recovery specialist, with costs to bear despite Apple Care.
Any suggestions on recovery specialists in London who do not charge a fortune ?
Thank a Lot !
Deepa

www.apple.com/support/macbookpro
this is not laptop oriented forum

CS5 crashes after splash screen

Every time I load my CS5 Application it crashes right after the splash screen. The log says:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
*** error for object 0x10f1f6e00: incorrect checksum for freed object - object was probably modified after being freed.
Any suggestions on how to get past this?
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 12 GB
Bus Speed: 1.6 GHz
System Version: Mac OS X 10.6.3 (10D573)

Ok, so if this happens to you here is the solution:
The problem relates to the installed fonts you have. There is no way of knowing exactly which one it is without trial and error enabling and disabling. What worked for me was using a font-managing software like Font Book and having it validate all your fonts. From there delete or disable any questionable ones with errors. Not all fonts with errors create this problem, so it is possible to re-introduce fonts and isolate the one(s) that cause the crash.

After Effect CS6 crashes after splash screen

I cannot get After Effects to open. When I try to open the software, I get a splash screen, and then the window opens, but the it stops responding before the interface can appear. I thought the issue may have been my virus protection (norton), so I tried shutting down my firewall and restarting my computer. This seemed to work for me the first time I tried it; After Effect opened and everything seemed to work fine, but the next time I started the computer and opened the software it continued to crash, and what I thought was the solution no longer worked. Premiere, Photoshop,and Audition work fine. However, the trial version of FX Home's software, Hitfilm 2, gives me the same problem as well. I have tried alot to get both of these programs to work with no success. I would appreciate any suggestions as to how I might fix this.
Computer spec:
win 7 64-bit
intel i7 960 3.2ghz
12 gb ddr3
nvidia 560 ti

Updated to 310.7 from 306.97, but still no luck. When after effect stops responding there is sometimes a dialog box asking me if I want to send my information. This dialog box does not always appear every time I try to open after effects, but when it does, this is the additional information it gives me:
Files that help describe the problem:
C:\Users\Owner\AppData\Local\Temp\WER9F1C.tmp.WERInternalMetadata.xml
C:\Users\Owner\AppData\Local\Temp\WER193B.tmp.appcompat.txt
C:\Users\Owner\AppData\Local\Temp\WER19AA.tmp.mdmp
However I can't find these files on my computer. This is also the same information I get when trying to open FX Home's software, except when I try to open that software I do not get a splash screen or window, the .exe shows up for a few seconds in the task manager and disappears.

Captivate 5 crashes after splash screen

I've downloaded the trial version of Captivate 5 and every time I try to start the program, I can't get passed the splash screen.
I'm running:
Win7 Home Premium, 64-bit
i5 2.27 GHz
4 GB RAM
350+ GB memory available
Upon initial launch, program crashed and produced an error message: "Adobe Captivate is not responding." I changed the AdobeCaptivate.exe file properties to "Run this program in compatibility for: (tried all options)" and "Run this program as an administrator" and no luck. Making the file compatible to a previous OS version caused the file to simply freeze (rather than crash) but prevented the Trial Activation prompt when operating as compatible for versions earlier than Vista.
I've tried uninstalling and reinstalling 6 times, after following various recommendations on potential fixes. Have also tried:
Cleaner tool - http://www.adobe.com/support/contact/cs5clean.html
AdobeNotificationsDllFieldReplacementTool.exe
Deleting the "amt3.log" file from the temp folder (saw this in a previous post, I guess to look for process errors)
The only "error" message listed in the entire amt3.log file is "Sequence Error! PreValidate called after Validate!" towards the very end of the log sequence. I'm at the end of my rope here. I almost purchased Captivate 5 without downloading the trial version first. I'd still like to purchase it but not if I can't even get the trial version to work.
Someone please help. Thanks.

Hi and welcome to this forum.
It sounds like you've tried most of the usual fixes for this installation issue.
I'm only a regular user like yourself but I know that the Adobe developers watch this forum closely for any issues like the one you're having. They'll usually chime in pretty quickly to offer assistance via some kind of screen sharing session so that they can investigate what's happening.
Stay tuned and be patient. Help is on the way, but even developers need a weekend.

4 programs - photoshop, illustrator, indesign and premiere pro not updating?

any ideas why

Hi Tapani-Talo,
Updates can often fail because of additional language files from the existing installations have been removed. Run the uninstaller and then reinstall the application and try applying the update again. Complete the following steps to uninstall the software:
Mac OS:
Go to Applications/Utitlies/Adobe Installers.
Run the applicable uninstaller.
Windows Vista/7:
Go to Start > Control Panels > Programs and Features.
Locate the affected Adobe Creative software title and click Uninstall.
Windows 8:
Press Windows Key + R to open the run command. Type Control Panels and press OK.
Open the Program & Features Control Panel.
Locate the affected Adobe Creative software title and click Uninstall.
Try these steps and let me know if it helps.
Thanks!
Gurleen

Premiere Pro CS5 and After Effects CS5 crash after splash screen

Im am fed up with this ive done everything i can and no one seems to know whats wrong, i installed CS5 on my macbook and imac i7, and they both worked for a while but then suddenly my imac i7 cs5 stopped working and kept crashing, my macbook continues to work just fine, ive even done a system reinstally and reinstalled os x and yes it would work for a little and then stop, they both have the same programs, whats weird is when i create a new user with admin privileges on my imac it would work fine but i deleted some files in the main account trying to fix the problem and no it wont work in the second account so here i am doing a system reinstally one last time. i called adobe they were no help at all literally, i called apple they did as much as they could i mean apple really made me feel like they tried, so here i am can anyone help?

Ok so i figured it out, the problem is my downloaded fonts from the internet. What sucks is that adobe cs4 applications ran perfectly fine with them, but now cs5 doesnt . I uninstalled my downloaded fonts and guess what?! it worked! I wonder why cs4 starts up with no problems with the same fonts and cs5 cant, thats just stupid...

Encore CS3 crashes after splash screen

I have purchased a new computer and have installed Adobe Master Collection CS3 and am using the Windows 7 system. I created a movie project in Premier Pro CS3 and rendered the movie and received the message at the end of rendering that said "Application failed to retun a video frame". I assumed the program couldn't open the Encore program and so I tried to open it separately. It would start up then crashes when it gets to the loading of the blue ray part of the program. I don't know if I am looking at two separate issues or just one. Please help!

If Jeff's Roxio Fix does not solve the issue, then consider this: failure to return video frame is often a sign that there is a gap in the video.
Do you have ganged Assets on one Timeline?
Have you checked 100% that your Audio is EXACTLY (and I mean 100%) the same Duration, down to the Audio Unit, with the Duration of the Video, or shorter? One extra Audio Unit can get you a gap in a ganged Timeline.
Good luck,
Hunt

NEED HELP!! LOGIC CRASHES AFTER splash screen plss hel

hey i recently updated to osx 10.6.6 and since then my logic pro has been acting up. But it has come to the point to where now it doesnt even open it crashes right after checking midi drivers. here is the report if anyone can pleasee helpp
Process: Logic Pro [483]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier: com.apple.logic.pro
Version: 8.0.2 (1502.22)
Build Info: Logic-15022200~9
Code Type: X86 (Native)
Parent Process: launchd [410]
Date/Time: 2011-01-23 18:53:35.804 -0500
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report: 406669 sec
Crashes Since Last Report: 78
Per-App Interval Since Last Report: 367569 sec
Per-App Crashes Since Last Report: 59
Anonymous UUID: A3586FC6-6081-439D-A15C-C8042C0882EB
Exception Type: EXCBADACCESS (SIGABRT)
Exception Codes: KERNINVALIDADDRESS at 0x0000000049b45b69
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
abort() called
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x9128a176 __kill + 10
1 libSystem.B.dylib 0x9128a168 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x9131c89d raise + 26
3 libSystem.B.dylib 0x91332951 __abort + 124
4 libSystem.B.dylib 0x913329cd abortreportnp + 0
5 com.apple.logic.pro 0x002b37ff 0x1000 + 2828287
6 libSystem.B.dylib 0x9128f46b _sigtramp + 43
7 ??? 0x0000000b 0 + 11
8 com.apple.logic.pro 0x00020cff 0x1000 + 130303
9 com.apple.logic.pro 0x00021f94 0x1000 + 135060
10 com.apple.logic.pro 0x00032e0b 0x1000 + 204299
11 com.apple.logic.pro 0x002b741e 0x1000 + 2843678
12 com.apple.logic.pro 0x002b75e3 0x1000 + 2844131
13 com.apple.logic.pro 0x00012e8c 0x1000 + 73356
14 com.apple.logic.pro 0x0019534e 0x1000 + 1655630
15 com.apple.logic.pro 0x004d3c78 0x1000 + 5057656
16 com.apple.logic.pro 0x0051f9db 0x1000 + 5368283
17 com.apple.logic.pro 0x005205f9 0x1000 + 5371385
18 com.apple.AppKit 0x94753040 -[NSDocument readFromURL:ofType:error:] + 743
19 com.apple.logic.pro 0x00520410 0x1000 + 5370896
20 com.apple.AppKit 0x9463eddd -[NSDocument initWithContentsOfURL:ofType:error:] + 311
21 com.apple.AppKit 0x9463e981 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 383
22 com.apple.logic.pro 0x0053d6d3 0x1000 + 5490387
23 com.apple.AppKit 0x9463e739 -[NSDocumentController openDocumentWithContentsOfURL:display:error:] + 886
24 com.apple.logic.pro 0x004d8b79 0x1000 + 5077881
25 com.apple.Foundation 0x923d5588 nsnotecallback + 345
26 com.apple.CoreFoundation 0x9851f793 __CFXNotificationPost + 947
27 com.apple.CoreFoundation 0x9851f19a _CFXNotificationPostNotification + 186
28 com.apple.Foundation 0x923ca384 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
29 com.apple.Foundation 0x923d7789 -[NSNotificationCenter postNotificationName:object:] + 56
30 com.apple.AppKit 0x94423422 -[NSApplication _postDidFinishNotification] + 125
31 com.apple.AppKit 0x94423332 -[NSApplication _sendFinishLaunchingNotification] + 74
32 com.apple.AppKit 0x9457a4ed -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274
33 com.apple.AppKit 0x9457a10d -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101
34 com.apple.Foundation 0x9240a7a4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
35 com.apple.Foundation 0x9240a568 _NSAppleEventManagerGenericHandler + 228
36 com.apple.AE 0x92dc8f58 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
37 com.apple.AE 0x92dc8e57 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
38 com.apple.AE 0x92dc8d61 aeProcessAppleEvent + 197
39 com.apple.HIToolbox 0x97a07389 AEProcessAppleEvent + 50
40 com.apple.AppKit 0x943f39ca _DPSNextEvent + 1420
41 com.apple.AppKit 0x943f2fce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
42 com.apple.AppKit 0x943b5247 -[NSApplication run] + 821
43 com.apple.prokit 0x0210df5c NSProApplicationMain + 326
44 com.apple.logic.pro 0x00003942 0x1000 + 10562
45 com.apple.logic.pro 0x00003869 0x1000 + 10345
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9124f982 kevent + 10
1 libSystem.B.dylib 0x9125009c dispatch_mgrinvoke + 215
2 libSystem.B.dylib 0x9124f559 dispatch_queueinvoke + 163
3 libSystem.B.dylib 0x9124f2fe dispatch_workerthread2 + 240
4 libSystem.B.dylib 0x9124ed81 pthreadwqthread + 390
5 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 2: com.apple.CFSocket.private
0 libSystem.B.dylib 0x912480c6 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x98540c83 __CFSocketManager + 1091
2 libSystem.B.dylib 0x9125685d pthreadstart + 345
3 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x912290fa machmsgtrap + 10
1 libSystem.B.dylib 0x91229867 mach_msg + 68
2 com.apple.audio.midi.CoreMIDI 0x025090c1 XServerMachPort::ReceiveMessage(int&, void*, int&) + 155
3 com.apple.audio.midi.CoreMIDI 0x0252797a MIDIProcess::RunMIDIInThread() + 150
4 com.apple.audio.midi.CoreMIDI 0x0250a2d9 XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x02509ca6 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9125685d pthreadstart + 345
7 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 5:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 6:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 7:
0 libSystem.B.dylib 0x912570a6 _semwaitsignal + 10
1 libSystem.B.dylib 0x91282ee5 nanosleep$UNIX2003 + 188
2 libSystem.B.dylib 0x91282e23 usleep$UNIX2003 + 61
3 com.apple.AppKit 0x9455cfe1 -[NSUIHeartBeat _heartBeatThread:] + 2039
4 com.apple.Foundation 0x923d5bf0 -[NSThread main] + 45
5 com.apple.Foundation 0x923d5ba0 _NSThread__main_ + 1499
6 libSystem.B.dylib 0x9125685d pthreadstart + 345
7 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x913328e1 ecx: 0xbfffde9c edx: 0x9128a176
edi: 0x1ed7c800 esi: 0x251df830 ebp: 0xbfffdeb8 esp: 0xbfffde9c
ss: 0x0000001f efl: 0x00000286 eip: 0x9128a176 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x010b7818

Hi, ish1919.
Have you updated the drivers for your hardware? An OS update sometimes needs later drivers. Older ones can cause conflicts. Check the manufacturer website [eg. RME] for your hardware and get the latest version.
Hope this helps.
Scorpii.

[SOLVED] Amarok 2.0.1 crashes after splash screen

i have no clue what is going on here, but amarok 2.0.1 crashes every time i try to run it. so if someone could at least give me a little insite......
[nick@grim ~]$ amarok
amarok(15659)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-nick/ksycoca4"
amarok(15659)/kdecore (KLibLoader) kde4Factory: The library "" does not offer a qt_plugin_instance function.
amarok(15659)/kdecore (KLibLoader) kde3Factory: The library "" does not offer an "init_phonon_xine" function.
amarok(15659) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-mtpcollection.so"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-sqlcollection.so"
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090128 10:11:06 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-ipodcollection.so"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-daapcollection.so"
QDBusObjectPath: invalid path ""
Object::connect: No such slot MainWindow::showStatistics()
Object::connect: (receiver name: 'MainWindow')
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QLayout: Attempting to add QLayout "" to MainWindow "MainWindow", which already has a layout
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
<unknown program name>(15657)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "
[nick@grim ~]$ KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = amarok path = <unknown> pid = 15659
sock_file=/home/nick/.kde4/socket-grim/kdeinit4__0
also, i have no clue if this is related, but every time i start konsole from ALT+F2, it says "KDEInit could not launch '/usr/bin/konsole'.", but launches it anyways.
Last edited by grimrider (2009-01-28 21:44:54)

anrxc wrote:Don't worry about it too much because amarok crashes all over the place so you are not missing much
I built my own test a few minutes ago to avoid libgpod and mtp, one of the first problems is segfaulting at every exit so it looses many settings like the current playlist. Playlist importing from v1 is still broken, rtsp streams are not recognised (even though it is still the xine engine), there is no EQ, random crashes here and there... If you still want to try it check this build http://aur.archlinux.org/packages.php?ID=19633
haha wow. i guess ill stick w/ 1.4 untill they get this sorted out. was hoping for sumthin new but owell
thanks for the help

Lightroom 1.4.1 crashes after splash screen

Lightroom gets far enough to show the total number of pictures in the catalog (145024) and then quits. This is the message in the Application Event Log.
"Faulting application lightroom.exe, version 1.4.1.0, faulting module msvcr80.dll, version 8.0.50727.1433, fault address 0x00014584."
I reinstalled 1.4.1. I rebooted. I renamed msvcr80.dll in the lighroom folders and rebooted. I stopped all other programs.
Can I do anything like delete preferences or start with a different catalog? I backed up the catalog yesterday but I'm not sure how to revert to it if I can't open Lightroom.
Bill

Use this document to locate your preference file: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=333660
Start Lr with a different catalog by holding the Ctrl key while starting Lr.

Premire Pro CC 2014 and Media Encoder Crash During Launch

Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.0.169
Application Timestamp: 536f4f89
Fault Module Name: ImageRenderer.dll
Fault Module Version: 8.0.0.169
Fault Module Timestamp: 536f2c18
Exception Code: c000001d
Exception Offset: 00000000001f5382
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0b2d
Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
Additional Information 3: fa9f
Additional Information 4: fa9f59f642d335ee71c6667e52000d39

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Photoshop CC2014 in OSX Yosemite (Mac book pro retina 2014) crashes frequently and Merge to HDR does not work

My photoshop CC2014 on my Mac OSX Yosemite crashes all the time with random tasks. Now almost nothing works. Sometimes it stops working after doing random tasks like starting photoshop and i have to do a hard reset by putting the power off of my Mac pro retina (2014). After logging in again i got the message from Photoshop that graphics problem occurred with a Problem report I will post here. I also cannot merge to HDR from lightroom to photoshop & also in Photoshop in the file menu > automate merge to HDR pro. It 8 of 10 times it stops working and I won't select one of the brackets. I have to force quit photoshop. I think these instability problems started after updating to Yosemite but become worser everyday. I also disabled the graphics driver, put it on basic and enabled/disabled open gl, sometimes photoshop disables it automaticly. My osx is up to date so I don't have to update my graphic driver because these updates or done within the OSX update pane. I cannot add the Problem report file in this topic, How can I do this???

Have you installed all the Photoshop updates and MacOS 10.10 updates?
Disabling GPU usage in Photoshop should help with the video driver bugs in MacOS 10.10, until Apple can solve all the driver issues (yes, Apple knows about them and is working on solutions).
What does the long, detailed crash log say?
Also, anything that freezes, shuts down, or reboots the machine is not an application error - but caused by an OS bug, a low level driver bug, or faulty hardware. Applications simply cannot cause those symptoms on modern OSes.

Premiere Pro CC 2014 crash when I Click and Drag

Hi All, I have a problem with Premiere CC 2014 that is driving me crazy!
The issue is as follows:
If I try to drag a clip, sequence, effect or transition anywhere within the premiere, it will crash - with "Sorry, a serious error has occurred" message. The program will crash, quit and the saved recovery project is usually healthy (luckily!). BUT, as soon as I've re-started the program, and reloaded the project - or any project for that matter - the problem persists. As soon as I click and drag, Premiere crashes!
In order to 'reset' this, I have to restart my machine. Once I have done so, I can continue editing as normal for a while (not long, perhaps up to an hour, or so) but eventually, it WILL crash again. I've not been able to work out what I have to do in order to trigger this - it seems random. But once it's happened, only restarting my computer will resolve it - and then only temporarily.
Here are all the facts:
The crash ONLY happens when I drag something... This can include moving a clip on the timeline, dragging a clip form the source viewer or project window, dragging an effect or transition.
The crash happens after I have clicked, as soon as I start to move my mouse.
I CAN click and drag to extend in and out points on the timeline, and I can do 'insert' edit using the button on the source monitor. No crash here.
The footage plays fine.
I am trying this on a CLEAN OS X install, with only Adobe packages installed, to eliminate any potential of interference from other programs. There are no third party plugins or drivers installed. No user data installed either (preferences, photos, documents, etc) - as fresh as it comes!
I am not running Time Machine in the BG
My system is: Macbook Pro 2011, 16GB Ram, 1tb SSD, OS X Yosemite 10.10.1. Intel Graphics card, so no option to turn on or off hardware acceleration. It is set to software only.
I have tested this with projects and footage on an external drive, as well as internal, same issue.
I noticed the issue had started on, or around 25-27th November 2014.
Interestingly, I have noticed that once this crash has occurred in Premiere, a similar problem will occur in After Effects as soon as I drag a file or layer... doesn't matter what the layer is. The crash seems less elegant here, I don't get an error message, it just freezes and I have to 'force quit'. Again, the problem persists until the machine is restarted.
I have been using my macbook and premiere pro cc 2014 on Mavericks for a long time, and had no problems - so I know it should work fine! The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups, I installed a few new fonts and any CC updates that happened in the background... I can rule out most of these because of my fresh install, with no user data, fonts plugins or time machine to confuse matters... It must be an Adobe bug with Yosemite!
Any ideas?
Thanks so much in advance!!

Hi Vince,
vince_email wrote:
...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
Thanks,
Kevin

Illustrator/indesign and premire pro cc 2014 crashes after splash screen

Similar Messages

Maybe you are looking for