Skip to main content
Participating Frequently
August 22, 2020
Answered

My After Effects started crashing on startup

  • August 22, 2020
  • 3 replies
  • 29675 views

My after effects was perfectly running fine yesterday. Today, one of my projects that I was working on crashed it and now the whole AE is not starting. 

I updated the graphic drivers to the latest, updated windows 10 and also made sure the  AE is also updated. 

 

I even uninstalled all of CC apps and CC and used the Adobe clean up and re installed it and still not working. 

I tried ALT+SHIFT+CTRL on launch and reset preferences, still the same. 

 

The crash report mentions the below. 

 

Process: AfterFX.exe [21640]
Path: C:\Program Files\Adobe\Adobe After Effects 2020\Support Files\AfterFX.exe
Product Version: 17.1.1.34
File Version: 17.1.1.34
Code Type: x64
Parent Process: Adobe Desktop Service.exe [10720]


Date/Time: 2020-08-23 00:35:14 AUS Eastern Standard Time
OS Version: 10.0.19041.292
Report ID:

 


Time Awake Since Boot: 1765 seconds


Crashed thread: 16 [4944] THREAD_PRIORITY_NORMAL


Exception Code: EXCEPTION_ACCESS_VIOLATION
Exception Parameters: User-Mode data execution prevention (DEP) violation at location 0x0000000000000000
Exception Message: 3221225477 The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Correct answer pablo1421

I have this same issue, and am also using the DisplayLink Plugable UD-3900... If anyone's found a work around please share.


Hello Everyone, I found a solution that worked for me with the UD-3900!!

I got this procedure from Microsoft: (I did have to also disable the Intel Display Adapter)

 

Try this:

  1. Right click on blank desktop>select Display settings.
  2. Scroll down and select Graphics settings.
  3. Click on browse and select the Application .exe from program files.

 For example - C:\Program Files\Adobe\Adobe After Effects CC (version number)*\After Effects.exe *Version number is whichever version you are using.

  1. Select the app>click on options> select high performance graphic card and Click on 'save'.
  2. Restart the computer.

Try launching AE. If this doesn't help then try the step below without changing the setting done above.

Go to Device Manager>Display adapters. Right Click on Intel and Disable it. Restart the machine and check if Intel is still disabled. If yes, launch the app and check.

 

3 replies

Participant
November 13, 2023

I fix this bug by deleting KeenTool Plugin folder at 
C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore

So problem can be because some of your plugin.

Try to find it at crush report here
C:\Users\{Username}|\AppData\Roaming\Adobe\After Effects\24.0\logs

Selim Rumi
Participant
February 13, 2024

My problem has been solved, thank you.

 
 
manojcn
Participant
October 8, 2021

I was facing a similar issue. After breaking my head for almost 3 weeks, I figured out that it was caused due to a plugin called AEJuice. Please try unintalling this plugin from the control panel and see if it works. Or try for other plugins that you see on control panel. Another solution might be to update your Windows if you're using it.

nishu_kush
Legend
August 24, 2020

Hi Neoassyrian,

 

Sorry for your issue.

How do you launch After Effects - by clicking its icon or by double-clicking the project file? What's the exact version of After Effects you're using? Have you tried launching it as administrator?

Let us know how it goes.

 

Thanks,

Nishu

Participating Frequently
September 3, 2020

I'm having an identical problem. Launching app via its Taskbar icon, and tried running as Administrator. All result in crashes while the splash screen still says "Initializing Required Components..."

Tried rolling back both After Effects and my GeForce GameReady Graphics Drivers to previous versions hoping to revert to a previous working environment. Can't get AE back and need to work...

Participating Frequently
September 4, 2020

I think I figured it out. I was using a docking station with 2 monitors and when I disconnect it it seems to work. Not sure if it is my NVIDIA/Intel graphics or the displayLink drivers.