First Pro CC crashes at launch

Similar Questions

• First Pro CC crashes on launch

  I was very excited to try new applications CC, especially Premiere Pro, but no more, he immediately blocked the launch, or I get this error message.

  "Adobe Premiere Pro has not found all the modules capable of video game. Please update your video display drivers and start over. »

  I've updated my video drivers to the latest version, and it still happens.

  I am running

  Windows 7 Professional 64 bit

  NVIDIA GTX 460, 320.18 pilot

  Intel Core i7-3770

  32 GB of RAM

  I'm a very sad panda. I hope this is resolved soon.

  Try right clicking on the launch icon and solvers compatiability. I lied and said that it worked on Vista, so he tried to open via the drivers etc and viola! It worked. Saved settings and will reopen its doors very well.

  So far.

• After effects CC accident leads to first Pro CC Crash

  Hello

  Major panic goes here...

  I was in the middle of a montage using first Pro CC 2015 and has decided to use After Effects to stabilize a clip... Still fails to load (crashes on loading MediaCore) and this in turn freezes first.  I use the Task Manager to close the two apps, then try to run that Premiere Pro but keeps locks even begin to load the usual elements that tend to see ((ExporterAVI, etc.))

  Tried to uninstall first using cloud creative but that no longer works!  He insisted I had the first running, but it was not...  THAT makes wonder if this was the cause behind it does not quite...  In any case, I've used the cleanup tool to remove the first and am currently download first Pro CC of the Cloud...

  While I hope it will work, is there a history of this debacle over there among the other sick CC?

  I'm running a Windows PC with 10 because the OS...

  See you soon

  Steve

  Please check if this helps First Pro CC Crash at startup

  Adobe Premiere Pro CC 2015 crashing in the fix for windows 10 - YouTube

  or you can contact our support for him is resolved.

  https://helpx.Adobe.com/support.html#/top_products

  Concerning

  Stéphane

• First Pro CC crashes on startup after upgrading Windows 8.1. All solutions?

  First Pro CC crashes on startup after upgrading Windows 8.1. All solutions?

  It was working fine until I updated my operating system. I tried to reinstall the software. I tried to update my graphic drivers.

  Hi P.Ava,

  Please also try to delete / disable any antivirus or firewall software installed on the system.

  Please update if it works.

  Thank you

  Sandeep

• Adobe first Pro CC crashes after update

  I have read similar discussions of crash during launch with Premiere Pro (cloud), but I've exhausted all the suggestions. Works on a Mac, I have downloaded the latest update, rebooted the machine, disconnected Adobe Cloud, recorded in Adobe Cloud, checked my read/write permissions in the (good) library, and restarted again. It seems that first will launch and will watch the window of loading on the screen, but it crashes. Adobe Photoshop and Lightroom start without problems. Any suggestions?

  Contact adobe during the time pst support by clicking here and, when available, click on "still need help," http://helpx.adobe.com/x-productkb/global/service-ccm.html

• First Pro CC Crashing on Mavericks - error message "cannot find capable video modules...". »

  Have tried all the adobe offers solutions, but also updates to the OS, uninstalled and reinstalled.  After effects also blocks.  What is going on?

  I spent the weekend trying to solve this problem: when I run the first Pro CC it crashes on the home screen with the message: "cannot find capable video game modules. Please update the drivers and try again.  I am running on a Macbook Pro 2014 10.9.4 Mavericks.  I updated the graphics/video drivers, made sure that all updates are underway on the OS, uninstalled and reinstalled the program and even changed the region/language settings as suggested on some forums online.  I've tried every suggestion to Adobe for the problem.  After Effects hangs before the splash screen.  What happens here?  When it comes to Apple they say is Adobe - I just need to program that I pay to work.

  Hello

  Please go to the following location to move the Adobe folder on the desktop,

  User library > Application support >

  User library > preferences >

  Make sure that you are in the library user not in the library system.

  Access the hidden user library files. Mac OS 10.7 and later versions

  Please rename the Adobe folder in the documents to old.adobe

  Now try and launch.

  Hope that helps.

  Thank you

  Mohd Naseem.

• First Pro CC crash at startup

  Hey guys,.

  ADobe Premiere Pro starts after the splash screen, as soon as it breaks down right!

  I have windows 8.1

  16 GB of Ram

  I7

  680M 4GB NVIDIA

  I reinstalled my graphics driver, who has not fixed anything.

  Also I tried reinstallng Adobe Premiere Pro, but that no longer works.

  Here is the error log says:

  Name of the failing application: Adobe first Pro.exe, version: 7.2.1.4, time stamp: 0x52aed7f3

  The failed module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

  Exception code: 0xc0000005

  Offset: 0x00000000002ade82

  ID of the process failed: 0 x 3468

  Start time of application vulnerabilities: 0x01cf156264fae44b

  Just for grins, try to press and hold the command key before (and that) you run the application. If still it crashes, try down option and do the same thing. There are keyboard options that can be used to rub and reset preferences and other settings that can make your app on launch accident. The other keys (ctrl, shift) have also reset functions at the launch. See if that helps.

• First Pro CC2015 crashes on opening

  just updated - 2012 retina macbook pro 1 gb vram - CUDA updated.

  PP has worked fine until today, now I get the message "'Premiere Pro could not find video playback capable modules" "

  crashes and impossible to force to leave without restarting.

  already tried:

  •Desinstallez and reinstall PP and ME (x 2)

  •turn all software and CUDA

  •Eteignez GFx CardStatus

  •Reinitialisez landau

  •a boot.

  •reparer permissions.

  anyone else with questions about a 2012 MBPr?

  Hi Rosco,

  See if this doc will help: first Pro CC, CC 2014, 20141 freeze at startup or crashing everything working (Mac OS X 10.9 and later)

  Thank you

  Kevin

• Adobe first Pro CC crash at startup

  Hello I have a problem when I open Adobe first Pro CC it crash and I get this error

  Signature of the problem:

  Problem event name: APPCRASH

  Name of the application: Adobe first Pro.exe

  Application version: 8.2.0.65

  Application timestamp: 5486db4a

  Fault Module name: ImageRenderer.dll

  Fault Module Version: 8.2.0.65

  Timestamp of Module error: 5486b5ee

  Exception offset: 00000000001f5342

  Exception code: c000001d

  OS version: 6.1.7600.2.0.0.768.3

  Locale ID: 1031

  Additional information 1: 0b2d

  More information 2: 0b2df4702c3fc6489bf922fb8e966350

  3 more information: 3e3d

  Additional information 4: 3e3dc964c555afa850b3ab3b520ac7e3

  Problem event name:	APPCRASH
  Name of the application:	Adobe QT32 Server.exe
  Version of the application:	8.2.0.65
  Timestamp of the application:	5486d9b1
  Name of the Module for error:	ImageRenderer.dll
  Fault Module version:	8.2.0.65
  Module Timestamp error:	5486b0a8
  Exception offset:	c000001d
  Exception code:	001e5343

  OS version:6.1.7600.2.0.0.768.3Locale ID:1031Additional information 1:0a9eAdditional information 2:0a9e372d3b4ad19135b953a78882e789Additional information 3:0a9eAdditional information 4:0a9e372d3b4ad19135b953a78882e789

  I have reinstall the first I turned off my hd 4600 graphics card and no effect I hope someone can help me

  Hello

  This error report occurs generally if you do not have Service Pack 1 installed. The SP1 installation and see if it is resolved.

  Thank you

  Regalo

• First Pro CC crash when you drag the project window media

  I had so many problems with the CC (2014) since the 8.1 update. The last problem is interacting with the media in the project window. In any version of PP (7, 8.0.1, 8.1), when I try to drag the media from the project to the timeline window, I get the crash 'first Pro CC met a serious error... ". ». I use a Macbook Pro i7, 16 GB of ram, Nvidia GT graphic map of 750 m, on OSX Yosemite. I tried to clear the cache of media and the parameters of compensation at the start with alt + shift. I've been using 8.0.1 due to previous problems with ui serious lag on 8.1. I had more problems with the PP in the last 3 months than in the previous 7 years, I have used.

  Hi Bryan,.

  You have the extension installed "Pushbullet" Chrome? If so, you and Baemon should try to remove and then see if the problem goes away. He worked for others: Re: Premiere Pro CS6 crashes when drag-and -

  Thank you
  Kevin

• First Pro CC crashing after the importation of the media

  I just built my first PC a few weeks ago for the sole purpose of editing with first Pro CC, but every time I have import any media and try to use the view, the program crashes. As long as I do not import, the program does not crash. After I imported, it will be crash without worrying if she still a picture or a video.  I even tried to load the project "Eagles_Doc_Final" which gives to Adobe, as practice and which will crash immediatelysince there is already media imported.

  
  

  I'm about to start an assistant job in editing my work and I need to start training at home with first since I've only used Final Cut in the past.

  My system:

  Trial version of first Pro CC - I really want to buy a subscription, but I can't even make it work.

  Windows 7 Home Premium - make all updates using the Update window.

  Processor - Intel Core i7 4790 K - updated drivers using version 2.0 driver Intel (r) update utility

  Motherboard - GIGABYTE GA-Z97X-UD3H -Bios is version F5. There is an update F6 and F7, but do not know if it would be necessary?

  GPU - no - I wait to see how fast first Pro CC is without using a GPU for acceleration. I read that I have doesn't have a GPU to run the program. Is this correct?

  This is the error I get...

  "Adobe Premiere Pro CC has stopped working"

  Signature of the problem:

  Problem event name: APPCRASH

  Name of the application: Adobe first Pro.exe

  Application version: 8.1.0.81

  Application timestamp: 5426694c

  Fault Module name: devenum.dll

  Fault Module Version: 6.6.7600.16385

  Timestamp of Module error: 4a5bded7

  Exception code: c0000005

  Exception offset: 00000000000016a 0

  OS version: 6.1.7601.2.1.0.768.3

  Locale ID: 1033

  Additional information 1: ec5a

  More information 2: ec5adb2545b190cc19da7bdfa78d5bf1

  3 more information: 52eb

  Additional information 4: 52eb6b5eb5247c23714f771b797ebaa7

  and this is the error in the event viewer application.

  General

  Name of the failing application: Adobe first Pro.exe, version: 8.1.0.81, time stamp: 0x5426694c

  Name of the failed module: devenum.dll, version: 6.6.7600.16385, time stamp: 0x4a5bded7

  Exception code: 0xc0000005

  Offset: 0x00000000000016a0

  ID of the process failed: 0 x 1114

  Start time of application vulnerabilities: 0x01d00202f06d1b2f

  The failing application path: C:\Program Files\Adobe\Adobe Premiere Pro 2014\Adobe first Pro.exe CC

  Path of the failing module: C:\Windows\system32\devenum.dll

  Report ID: 3bf56dba-6df6-11e4-9734-74d435e5c333

  If anyone can help point me in the right direction, I would gladly appreciate it. I don't want to jeopardize anything with this new job because I couldn't get this to work.

  -JR

  Hi jacobrivera68,

  Before importing anything, go to file > project settings > General and change the GPU acceleration for playback (software only) Mercury engine and see if that fixes the problem.

  Thank you

  Regalo

• First Pro CC crash at startup c:\sirreel64\releases\

  Since two months ago when I try to open the first Pro CC projects, the program crash and displays the message:

  "Premiere Pro has encountered an error"

  [c:\sirreel64\releases\2013.02\shared\adobe\mediacore\mediafoundatio\api\inc]

  

  If I open new projects it seems ok, I save, then I the reopen them and it failed again.

  I'm working on a Quad 4 GB RAM 64 bit Win8 IntelCore.

  Driver GPU are updated.

  I uninstalled third party plugins, try to open the application with the SHIFT key, but the question still.

  If I try to open an automatic record of the project, the only older work, but when I save it and open it again, it crash again.

  I don't really know what to do.

  Alberto C.

  Hello Alberto,.

  Uninstall iCloud. See this thread: f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe debug event

  Thank you

  Kevin

• First Pro CC crash

  Hi all

  I just made the switch to first Pro CC and at halfway through my latest project, the application has started to plant all the time, and when I present the crash report, Adobe says that they do not find a problem.

  I use version Premiere Pro 7.2.2 on a trash can Mac Pro (Mavericks 10.9.3)

  Here is the crash report.  I tried to delete the media Cache files and nothing seems to help. Can anyone help?

  Process: Adobe Premiere Pro CC [19717]

  Path: / Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe first Pro CC

  ID: com.adobe.AdobePremierePro

  Version: 7.2.2 (7.2.2)

  Code type: X 86-64 (Native)

  Parent process: launchd [796]

  Responsible for: Adobe Premiere Pro CC [19717]

  ID: 1736816378

  Date/time: 08:55:00.518 2014-09-26 + 0100

  OS version: Mac OS X 10.9.3 (13 D 65)

  Report Version: 11

  Anonymous UUID: 04113131-7041-30A7-6DC5-71A9B4D97D74

  Crashed Thread: the queue on the expedition 10: com.apple.root.default - priority

  Exception type: EXC_BAD_ACCESS (SIGSEGV)

  Exception codes: KERN_INVALID_ADDRESS at 0x000000012dc6d000

  VM regions near 0x12dc6d000:

  VM_ALLOCATE 000000012dc23000-000000012dc6d000 [296K] rw-/ rwx SM = PRV

  ->

  BATTERY GUARD 000000012dc83000-000000012dc84000 [4K]-/ rwx SM DRAW keeps stack for the thread 35 =.

  Thread 0: Dispatch queue: com.apple.main - wire

  0 com.apple.CoreFoundation 0x00007fff8992cc62-[objectsWithOptions:passingTest sets:] + 194

  1 com.apple.AppKit 0x00007fff88205db2-[NSView (NSInternal) _uninstallRemovedTrackingAreas] + 314

  2 com.apple.AppKit 0x00007fff8830f579-[NSView (NSInternal) _updateTrackingAreas] + 679

  3 com.apple.AppKit 0x00007fff8830f8e7-[NSView (NSInternal) _updateTrackingAreas] + 1557

  4 com.apple.AppKit 0x00007fff8830f8e7-[NSView (NSInternal) _updateTrackingAreas] + 1557

  5 com.apple.AppKit 0x00007fff88365e24 _handleInvalidCursorRectsNote + 994

  6 com.apple.AppKit 0x00007fff889438a1 __35-[NSWindow _postInvalidCursorRects] + 46 _block_invoke2988

  7 com.apple.CoreFoundation 0x00007fff89905e17 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

  8 com.apple.CoreFoundation 0x00007fff89905d87 __CFRunLoopDoObservers + 391

  com.apple.CoreFoundation 9 0x00007fff898f7468 __CFRunLoopRun + 776

  10 com.apple.CoreFoundation 0x00007fff898f6f25 CFRunLoopRunSpecific + 309

  11 com.apple.HIToolbox 0x00007fff8b50da0d RunCurrentEventLoopInMode + 226

  12 com.apple.HIToolbox 0x00007fff8b50d7b7 ReceiveNextEventCommon + 479

  13 com.apple.HIToolbox 0x00007fff8b50d5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65

  14 com.apple.AppKit 0x00007fff881c926e _DPSNextEvent + 1434

  15 com.apple.AppKit 0x00007fff881c88bb-[NSApplication nextEventMatchingMask:untilDate:inMode: dequeue:] + 122

  16 com.apple.AppKit 0x00007fff881bc9bc-[NSApplication run] + 553

  17 com.adobe.Frontend.framework 0x00000001000c684d FE: MacApplication::RunSelf() + 45

  18 com.adobe.Frontend.framework 0x000000010004642a FE::Application:Run(std::basic_string<unsigned_short,_std::char_traits<unsigned_short>,_dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned_short>_>_const&) + 4058

  19 com.adobe.Frontend.framework 0x00000001000c80c8 FE::AppMain (ASL::ObjectPtr < ASL::Module, ASL::AtomicValue > const &, std::basic_string < unsignedShort, std::char_traits < unsigned short > dvacore::utility:SmallBlockAllocator:STLAllocator < unsigned short > > const &, int, void *) + 296

  20 com.adobe.Frontend.framework 0x00000001000cf285 FE::Run (ASL::ObjectPtr < ASL::Module, ASL::AtomicValue > const &, std::basic_string < unsignedShort, std::char_traits < unsigned short > dvacore::utility:SmallBlockAllocator:STLAllocator < unsigned short > > const &, int) + 581

  21 main 0x00000001000018bc com.adobe.AdobePremierePro + 524

  22 com.adobe.AdobePremierePro 0x00000001000016a4 start + 52

  .

  Thanks in advance for the help of everyone in this discussion.

  I have now created a project that doesn't crash!  HOORAY!

  How do I...?

  I have all my original Quicktime (originally Pro-Res 1920 x 1080) items dragged in AE and rendered uncompressed 8-bit versions of all.

  Then I carefully replaced all subrenders in my project now use the uncompressed... and so far (touch my wooden desk)... it is not breaking.

  Note: I kept my clips that had alpha as Lossless with Alpha channels (the good old reliable Animation million + codec, God bless you!)

  Seems to me that first Pro CC has problems with clips of previously used Pro-Res, that were once quite happily in FCP 7.

  My advice to all those affected by the same mistakes is crashing, is to re-encode your source clips. Uncompressed 8-bit was maybe a bit drastic, but I wanted to make sure I had "wild" media to start with.

  So, Adobe - please take note. This must be fixed.  This is my reccomendation for the next update!

• Adobe first Pro CC crash

  I have recently upgraded to adobe Premiere Pro CS5.5 and some time CC, it was working fine, then all of a sudden a random crash appears saying 'Adobe Premiere Pro CC has stopped working' and no solution is then found by force, she leaves. I restarted my computer, and still the error occurs whenever I run the sequence that I'm working on. It is very furstrating!

  I use the first Pro CC

  I have installed the latest updates

  Windows 7

  I use Dxtory for my images and the codec is a Codec Dxtory video to 29.97 and .avi files

  

  Hey kids,

  I read through all of this, as I had the same problem. Robert has actually almost got the answer, but I did change my RAM and update the driver for my GTX780ti as he suggested.

  This is what worked for me. Automatic backup is the culprit. TURN IT OFF. I save anyway, and I suspect most of you save constantly as I do, most of the time unconsciously. It is not necessary for the automatic backup if you condition yourself to save all the time. When you go to restore, automobile except wants to crash this party during the party. Auto save every five minutes that means crash will be available soon. This especially happens when you use things like auto levels and shadow in light to pull up some Sun videos and you have the temporal smoothing detect way upward, with stage and automatic backup is just that you are going to make. DOH! It crashed again. I saw it will automatically record and I was just clicking an effect for my cuts just before turning back to make effect. Automatic backup just wants in the way of production.

  No more accidents because I close auto reduction.

  I had an i7 hexcore, 24 GB of ram, win 7, ASUS ROG RADR as my boot PC, 2 X 4 to drive 7200 RPM SATA III RAID0.

  I will be rebuilding my hackintosh with two 750 GB Samsung SSD RAID0 SATAIII EVO as boot drive and I think the same thing will happen with auto backup. Just turn it off and learn how to save on a regular basis. I have no idea why, I even use auto backup since I save almost all the time. (I'm brooding?) I was a bit paranoid, opting to save right after a record until I figured this out. I was going to clear the preview files and make them again, and then I realized, AutoSave is not necessary.

  If the first plant again regularly, I guess I'll be wrong but since I turned off auto save. no crashes.

  Also, FYI. Windows sucks and you better stop the updates and I finish a little annoying program which will choke first, AE and anything CPU and memory intensive. It is called "Trusted Installer". What to do after the updates. This computer stifles rarely and Yes, it was stuffy big time today. Windows will appear eventually your settings to download and install updates you don't want to, since they do it and you will have to cut them again. Can I change on either but Windows has some issues with hiccups over the playback head. I turned off all the antivirus/antispyware. This hiccups never goes away. I leave also all drives on because that Dreamweaver crashes all the time if you do not have a custom power profile. I have a little less total 17TB. I am now air conditioned myself to change the options for "diet" when I'm done for the day for if I have not, I will shorten the life expectancy of my hard drives nice.

  Adobe, this is the second program send me problems to the point that it costs me power time and serious brain. I had the brain power to spare, but I would rather put my job playing in games like this. For now, I work around your bugs. Everyone, stop automatic backup and learn to save, save, save even in your sleep. I will dream about the recording of tonight. I'll post the accident report but it's almost 05:00, and I would have done a few hours ago.

  I hope this helps.

• First Pro CC crashes every time that I tried to export!

  Hello

  I use a Macbook Pro 13 "with i7 2.8 Ghz and 4 GB of ram, using the Intel HD Graphics 3000."

  This laptop is now completely re-installed, and I only downloaded first Pro CC of my creative cloud subscription.

  I'm trying to make a small project that resides on my laptop computer, containing a few items.

  As soon as I try to export-> media, the software just crashes. Every time. I just installed first Pro CC with the default settings.

  Can someone please help?

  Kind regards

  Kurt

  Norway

  Salvation Front Media,

  Please follow these steps: open the window of finder, click go and choose go to folder and then follow the steps below.

  1. go to ~/Library-> preferences > Adobe
  2. Right-click on the Adobe folder
  3. Click on Get Info
  4. Click on the lock icon
  5. Click on + icon and select user (name of current user account)
  6. Give permission to read & write to it.

  Then try to export again.

  Thank you