Adobe AIR Debug Launcher has stopped working Error on Flash Builder 4.6

Hi,
Maybe you could help me out here as I’ve search the web and Adobe forum but could not find any answer.
I just installed Flash Builder 4.6 (after uninstalling 4.5.1), now when I run my app, the adl.exe crashes (error details below). I thought because I have an app that was created with 4.5, but then I created a new app with this version and it still crash. I have Windows 7 64-bit PC.
Thanks so much. Any help is greatly appreciated.
Error details:
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     adl.exe
Application Version:     3.1.0.4880
Application Timestamp:     4eb7612e
Fault Module Name:     Adobe AIR.dll
Fault Module Version:     3.1.0.4880
Fault Module Timestamp:     4eb75fb9
Exception Code:     c0000005
Exception Offset:     000a8a5b
OS Version:     6.1.7600.2.0.0.256.48
Locale ID:     1033
Additional Information 1:     0a9e
Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
Additional Information 3:     0a9e
Additional Information 4:     0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0×0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
And this is the crash log:
Version=1
EventType=APPCRASH
EventTime=129672424273270780
ReportType=2
Consent=1
ReportIdentifier=3f7d7727-1c55-11e1-a8fc-705ab656b183
IntegratorReportIdentifier=3f7d7726-1c55-11e1-a8fc-705ab656b183
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=adl.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.0.4880
Sig[2].Name=Application Timestamp
Sig[2].Value=4eb7612e
Sig[3].Name=Fault Module Name
Sig[3].Value=Adobe AIR.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.1.0.4880
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eb75fb9
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000a8a5b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
UI[3]=Adobe AIR Debug Launcher has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[15]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\msi.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\IMM32.DLL
LoadedModule[19]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[20]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[21]=C:\Windows\syswow64\NSI.dll
LoadedModule[22]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\runtimes\air\win\Adobe AIR\Versions\1.0\Adobe AIR.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\system32\WINMM.dll
LoadedModule[26]=C:\Windows\system32\OLEACC.dll
LoadedModule[27]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[28]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[29]=C:\Windows\system32\MSIMG32.dll
LoadedModule[30]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 5.82.7600.16661_none_ebfb56996c72aefc\COMCTL32.dll
LoadedModule[32]=C:\Windows\syswow64\WININET.dll
LoadedModule[33]=C:\Windows\syswow64\urlmon.dll
LoadedModule[34]=C:\Windows\syswow64\iertutil.dll
LoadedModule[35]=C:\Windows\system32\mscms.dll
LoadedModule[36]=C:\Windows\system32\USERENV.dll
LoadedModule[37]=C:\Windows\system32\profapi.dll
LoadedModule[38]=C:\Windows\system32\Secur32.dll
LoadedModule[39]=C:\Windows\system32\DSOUND.dll
LoadedModule[40]=C:\Windows\system32\POWRPROF.dll
LoadedModule[41]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[42]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[43]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[44]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[45]=C:\Windows\system32\WINNSI.DLL
LoadedModule[46]=C:\Windows\system32\DNSAPI.dll
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\system32\dbghelp.dll
LoadedModule[49]=C:\Windows\system32\uxtheme.dll
LoadedModule[50]=C:\Program Files (x86)\MMTaskbar\shellhook.dll
LoadedModule[51]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[52]=C:\Windows\system32\mlang.dll
LoadedModule[53]=C:\Windows\system32\dwmapi.dll
LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 6.0.7600.16661_none_420fe3fa2b8113bd\comctl32.dll
LoadedModule[55]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[56]=C:\Windows\system32\apphelp.dll
LoadedModule[57]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\DropboxExt.14. dll
LoadedModule[58]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCP71.dll
LoadedModule[59]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCR71.dll
LoadedModule[60]=C:\Windows\system32\EhStorShell.dll
LoadedModule[61]=C:\Windows\system32\PROPSYS.dll
LoadedModule[62]=C:\Windows\system32\ntshrui.dll
LoadedModule[63]=C:\Windows\system32\srvcli.dll
LoadedModule[64]=C:\Windows\system32\cscapi.dll
LoadedModule[65]=C:\Windows\system32\slc.dll
LoadedModule[66]=C:\Windows\system32\credssp.dll
LoadedModule[67]=C:\Windows\SysWOW64\schannel.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Adobe AIR Debug Launcher
AppPath=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe

Dear, I had the same problema.
Was the sandbox from firewall.
I disabled and worked.

Similar Messages

Adobe AIR Debug Launcher has stopped working in League Of Legends

I am a player of League Of Legends,and I always get the crash with a message of "Adobe AIR Debug Launcher has stopped working" in the game lobby .This is annoying and affect me so much.
As I found ,the LOL client is using the AIR of 3.1.0.4880. i have tried to update the AIR to 3.4 and copy the file to the LOL folder,but it is useless .can someone help me to solve it?

I think this thread is talking about the issue you are facing:
http://forums.adobe.com/message/4517944#4517944
Hitomi

Adobe Air debug launcher has stopped working

Hi htere
I am constantly getting this error "Adove Air debug launcher has stopped working" at times on my League of Legends client. I have updated Adobe Air to the latest version and I even went ahead and made sure everything is ran as administrator.
http://i47.tinypic.com/33usf8i.jpg
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     LolClient.exe
Application Version:     2.0.2.12610
Application Timestamp:     4c00573a
Fault Module Name:     Air.dll
Fault Module Version:     0.0.0.0
Fault Module Timestamp:     511c7eb4
Exception Code:     c0000005
Exception Offset:     00002e72
OS Version:     6.1.7601.2.1.0.768.3
Locale ID:     3081
Additional Information 1:     0a9e
Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
Additional Information 3:     0a9e
Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

This thread seems to have a lot of helpful answers: http://forums.adobe.com/message/5359944#5359944
specifically, a video recorded that covers most/all the issues: http://youtu.be/uX0mMgJUyG0
Hope this helps anyone else finding issues!

Infuriating 'Adobe InDesign CC 2014 has stopped working error' has lost me a day. Just got dumped by chat support...

Hi All,
I've taken a few deep breaths before writing this to try and avoid a hugely frustrated rant.
To summarise; since early this morning my previously healthy version of InDesign CC 2014 has been unable to open, crashing at the 'Executing startup services...' stage with the error message 'Adobe InDesign CC 2014 has stopped working'. I worked on it all day yesterday and use it extensively every day more or less, this problem came out of nowhere overnight. I didn't do any kind of system update in the interim period. I'm using a HP Envy dv7 Notebook PC running Windows 8.
I tried as much as I could based on my own very limited knowledge and some forum searching. I re-installed the software. Did that again using the Adobe CC cleaner .exe file in between un-install and re-install. I uninstalled older versions of the software (which all worked fine - as does the rest of the Creative Suite software I have installed. I deleted extensions. None of this helped.
I then went looking for Adobe support and got a guy via Adobe's chat controlling my PC from afar and trying some much deeper technical stuff. After two hours he said that it was an OS issue, sorry... after a bit of dismayed pleading he said OK, I'll try one more thing and made me a new user with administration power, told me to login in to that account and try again. I did, it worked! But it's still broken on my main account and he disconnected in the few minutes I was gone and I now seem to be frozen out of chat help. HELP!
What does this mean? All CS/CC software seems to be working fine on my normal account apart from InDesign CC 2014. I have a huge file, now very close to being overdue, which I was working on in 2014 CC and can't be opened by older versions. The software works on this other account - so I guess I can work there short term. But how do I get it fixed on my main account?
Hopefully someone out there has the answer?
Thanks!
Luke

First, see Replace Your Preferences and do it for the original account.
If that fails to solve the problem, rename the two Adobe folders that contain the prefs in the user profile for that account and copy the folders from the new account where it works. You want to be sure you copy the folders, rather than merge the contents, so you must rename the old folders first.

"Adobe Media Core CS6 has stopped working" error.

I have had Premiere Elements 11, Photoshop Elements and LR 4 installed for over a year on my Windows 7 computer. Over the last couple months, within a few minutes of turning on my computer I get an error that Adobe Media Core CS6 has stopped working. It seems like this might be related to Premiere but I have not been able to find a solution. This occurs even if I have not run any of my installed programs. Any suggestions what is causing this and how to fix it?

I had not saved the detail files earlier today (it appears they disappear on a restart), but did a shutdown/startup a short time ago and had a recurrence again. (Although two subsequent cycles did not generate the error.) I saved the files and the .xml file indicates the parent process was Elements 11 Organizer this time, not LR4.
I had been living with this problem for a while, one of the set of saved error file sets was from 5/1. I don't recall for sure if that was from the first occurrence of the error, but I decided to look for other programs installed just before that time. I see that Adobe Creative Cloud was installed the day before, 4/30. I don't recall how/why that was installed since I don't have any Cloud products. Also installed on 4/30 were three Microsoft Visual C++ Redistributable files, which show installation times one minute before the Creative Cloud installation, so I assume they are part of the Cloud installation. The next most recent (before 5/1) installed program was Smith Micro Anime Studio Pro 9.5, which was installed on 4/29.
The firewall settings have not changed. I was in a chat with my ISP when the problem occurred this afternoon, but not during the latest occurrence. I don't recall any updates since 6/24. I believe the error had occurred every time I started my computer before the Firewall changes, but it seems to be more sporadic now.
I will see what else I can come up with tomorrow since it is getting late. I wanted to get this all down before I lost my thoughts.
Update 7/5:
I have more information, but still no solution.
I found this thread Adobe Media Core CS6 has stopped working related to the same error, but it had no solution. The error did not occur when I exited PS Elements or Premiere Elements as it did for that person.
I also found Adobe media core cs6 stopped working......??? and tried the steps to rebuild the Photoshop Elements editor preferences file, but no success.
I had noticed that Adobe Creative Cloud was installed the day before, so I uninstalled it. Error still occurred.
I installed a different firewall (Zone Alarm Free) and disabled Windows Defender, error still occurs.
Uninstalled Anime Studio Pro (that had been installed a couple days before, error still occurred.
I will provide more updates as I try more changes.
Update 7/20:
More things I tried:
Repaired quicktime via control panel, did not fix
Uninstalled quicktime, error did not recur
I noticed that there remained a plug-ins folder in the quicktime folder, so I renamed it.
Reinstalled quicktime from Apple site on 7/12 and the CS6 error has not recurred.
Additional info not directly related to original question, but occurred afterwards.
I don't think it is related, but a few days later started getting a small blank MFC CTxfiHlp window upon windows startup. I haven't resolved that yet, but it is related to my Creative XFi sound card.
I also noted when I reinstalled Anime Studio Pro that the readme contains a warning that 64 bit windows does not support quicktime; that I should use the 32 bit version of their software.
I installed the latest Creative sound card software, but started getting lockups. Still working on this, but the original problem seems to be solved.
The only other thing I can think of is that iTunes software had been installed, but I removed it. It is possible that caused a problem with quicktime??
Anyway, the removal of quicktime (including the Plug Ins) and re-install did resolve my problem.

Adobe Premier Elements 10 has stopped working error message/Audio issues

I'm working on a project for about a week. I almost finished it, "shared" it to my computer, and watched it thru windows media player. I thought of something else that I could add to the audio, so I went back into the project in PE10 and put small (2-3 seconds) audio clips on audio track 3. Once I did that, PE 10 would not allow me to put any audio effects on that track. (I went into some older longer projects that I have and it allowed me to put effects on any audio track).
So, I moved my short audio clips to the Narration and Soundtrack tracks. It finally highlighted the App;y button for the audio effects. Now, the problem is that I can't play or click onthe timeline or move the timeline indicator without PE10 closing out of my video. As soon as I try to do anything, it says "Adobe Premier Elements 10 has stopped working" and it closes the program.
I can open my other projects and everything seems to work fine on those and it doesn't close out, but it won't allow me to do anything in this particular project.
Again, I have been going into and out of the project for a week and all of the sudden it won't let me work on it. It's only about a 3 minute project, so I don't know why it would have trouble.
Oh, and it also un-rendered everything.
Any thoughts?
Thanks!

LOTS more information is needed for someone to try and help
These questions below may be for a different product... but the information you need to supply is the same, for the products you use
-http://forums.adobe.com/message/4200840
-http://forums.adobe.com/thread/416679
-http://forums.adobe.com/thread/419406

Licensing has stopped working error durinng launch of Photoshop CS3

I cannot get rid of this error message during launch of PS CS3. I tried uninstalling running the CS3MacClean Script, reinstalling, ... same problem. The same installer and serial number works fine on a clean system so I know there must be a file or two that the cleanup script doesn't remove.
Anybody know what files to delete?

After installation, a system upgrade, machine migration, backup restore, or some other system event(s), trying to launch Adobe applications on Mac OS X results in the error "Licensing for this product has stopped working." You may see error numbers after this message, such as "150:30".
Solutions
Do one or more of the following solutions. Note, Adobe Trial Software that displays the error can not be restored to run.
Solution 1: Run the License Repair Tool
Close any Adobe applications.
Download the License Repair Tool:
www.adobe.com/support/contact/licensing.html
Run the License Service Update.
1. Double click the LicenseRecovery111.dmg
2. Double click the LicenseRecoveryLauncher.app.
3. Enter your administrator username and password when prompted and click OK.
4. Follow the on-screen instructions.
Start your Adobe application(s).
Important: The patch applies to Creative Suite 3 or 4 products, Acrobat 8 or 9, Photoshop Elements 6 or 8, Director and Technical Communication Suite. If your issue was not resolved on the first attempt, run the patch again and enter option 0, when prompted to do so.
Solution 2: Delete the FLEXnet Publisher preferences folder
Important: The path listed below refers to the Library folder that lives just inside your startup disk, not the Library folder inside your user home folder!
Quit all Adobe applications.
On your startup disk, locate and rename, or copy to the desktop and then delete, the following folder:
/Library/Preferences/FLEXnet Publisher/
Start your Adobe application(s).
Solution 3: Repair Disk Permissions
Launch the Apple Disk Utility:
/Applications/Utilities/Disk Utility.app
Select your startup disk.
Click Repair Disk Permissions.
Note: This can take considerable time. For more information about using Disk Utility, consult Apple's website.
Start your Adobe application(s).
Solution 4: Reset your permissions on the FLEXnet Publisher licensing service folder.
Important: The path listed below refers to the Library folder that lives just inside your startup disk, not the Library folder inside your user home folder!
Use the permissions instructions below to modify the permissions on the following folder on your startup disk:
/Library/Application Support/FLEXnet Publisher/
Solution 5: Reset your permissions on the Adobe PCD folder.
Important: The path listed below refers to the Library folder that lives just inside your startup disk, not the Library folder inside your user home folder!
Use the permissions instructions below to modify the permissions on the following folder on your startup disk:
/Library/Application Support/Adobe/Adobe PCD/
Permissions Instructions:
Close out of all Adobe applications. Follow the directions below to modify permissions to the folder.
Note: This solution requires administrative privileges on your computer. You will need to provide administrative credentials.
On Mac OS X 10.4
Using Finder, navigate to the folder to be modified.
Control+Click the folder, and then select Get Info.
Expand the Ownership & Permissions section.
Click the Details option to show the various owner and group options.
Verify that you have Read & Write permissions.
Click the lock icon next to the Owner field, choose yourself as the Owner, type in your administrator username and password when prompted, and click OK.
Change the Owner to system.
Change the Permission to Read & Write for Owner.
Click Apply To Enclosed Items and click OK to the warning dialog.
Type in your administrator username and password when prompted and click OK.
Close the Get Info dialog box.
Launch Adobe Acrobat 9 or an Adobe Creative Suite 4 product.
On Mac OS X 10.5
Using Finder, navigate to the folder to be modified.
Control+Click on the folder, and then select Get Info.
Expand the Sharing & Permissions section.
Click on the Details option to show the various owner and group options.
Click the lock icon in the lower right corner. Type in your administrator username and password when prompted and click OK.
Change your username to have Read & Write permissions.
Change admin to have Read & Write permissions.
Change Everyone to have Read & Write permissions.
Click the Gear icon and select Apply To Enclosed Item.
Close the Get Info dialog box.
Launch Adobe Acrobat 9 or an Adobe Creative Suite 4 product.
Solution 6: Remove the SQLite journaling file.
Important: The path listed below refers to the Library folder that lives just inside your startup disk, not the Library folder inside your user home folder!
The journaling file exists only under specific circumstances where a client is accessing the database file with certain options enabled. If the file does not exist, continue to the next solution.
Using Finder, navigate to:
/Library/Application Support/Adobe/Adobe PCD/cache
If present, delete cache.db-journal.
Launch Adobe Acrobat 9 or an Adobe Creative Suite 4 product.
Solution 7: (Acrobat 9 only) Reinstall on a non-case-sensitive file system.
Adobe applications are not supported on an OS formatted with a case-sensitive file system. If you attempt to install an Adobe application on a case sensitive volume such as a UFS, HFS+ case sensitive (HFSX) or SMB formatted drive, you get an error that the file system of the setup drive is not supported. Only Acrobat 9 doesn't display such error message and allows you to install the application, but attempting to launch Acrobat 9 results in the error "Licensing for this product has stopped working (error code 130:9)." The drive needs to be reformatted to a non-case-sensitive file system.
To check if MAC OS X is formatted with a case-sensitive file system :
From the Apple menu select About this Mac.
Click More Info and under Hardware select Serial-ATA.
Select the drive Acrobat 9 has been installed on and check the file system in the list. Note if the file system is case sensitive.
Alternatively, use the Disk Utility to check the file system:
From Applications > Utilities, launch the Disk Utility
Select the disk Acrobat is installed on and check its format.
Solution 8: Contact Adobe Technical Support
Adobe Technical Support can obtain logs from your machine to determine additional information about the failure. Contact Adobe Technical Support if the information provided has not helped to resolve your issue.
Additional Information
The Flexnet folders/files required to run Adobe applications can get corrupted, or have permission settings problems, if moved from one machine to another, or through a system restore from Time Machine. Flexnet service licensing failures can't be resolved by re-installating the appliaction, nor will the Adobe CS3 or CS4 Clean Scripts solve this problem. If permissions issues prevented the FLEXnet licensing service from launching, accessing its data, or communicating with Adobe processes, the licensing failure is expected.

Merge to HDR Pro from LR5. After applying preset and during conversion of file, Iget an error message "Adobe Photoshop CC 2014 has stopped working" and closing PS

In LR5 i do: Merge to HDR Pro. After I apply my preset and PS attempts to convert HDR file, I get an error message from PS: "Adobe Photoshop CC 2014 has stopped working". Then PS Closes.
My source files are 5 NEF files of 28 MB. I select 16-bit, I also tried 8-bit. No difference. Same error message.
I have a Toshiba Quosmio X870 with Intel i7 3610QM @ 2,30 GHz, 16 GB RAM, Windows 7x64 HP SP 1, 7,3 Performance Index
Any suggestions?

As the crash report says - your outdated video card driver is crashing. You need to update your video card driver from the GPU maker's website (AMD/ATI in this case).

Adobe reader has stopped working error message after installing reader XI on windows 7

Adobe reader has stopped working error message when loading reader after installing reader XI on windows 7.
Does anybody know why ?

Dear Pat,
Thank you for your reply.
It is Ver. 11.0.06 for Acrobat XI
No, I can't open the Reader at all. The error message box popped up immediately when I run the Reader

Windows 8 - Photoshop CS5.1 crashes upon startup. Error message: "Adobe Photoshop CS5.1 has stopped working.A problem caused by the program to stop working correctly. Windows will close the program and notify you if a solution is available."

Hello!
I've had the student version of the Adobe Creative Suite 5.5 Design Premium software for several years now.
When I received my Windows 8 computer I installed the software with no issue.
Last week when I tried opening Photoshop I get the following error: "Adobe Photoshop CS5.1 has stopped working.A problem caused by the program to stop working correctly. Windows will close the program and notify you if a solution is available."
I deactivated and uninstalled the entire Creative Suite then reinstalled it. I am able to open the other programs, but still receive the same message for Photoshop.
What can I do?

I found the issue was with the Nik Filters I was using. The filters were messing with Photoshop's initializing. I uninstalled and reinstalled the filters and now Photoshop works like a charm.
It appears this forum is dead?!
Thankfully, I was able to troubleshoot on my own and figured out the problem...

I downloaded Photoshop CC 2014 last week and every time I open the program, I get an error message that reads "Adobe Photoshop CC 2014 has stopped working" and it forces me to close the program. How to I resolve this?

I downloaded Photoshop CC 2014 last week and every time I open the program, I get an error message that reads "Adobe Photoshop CC 2014 has stopped working" and it forces me to close the program. How to I resolve this?

Hi Noel,
I'm wondering whether your comment addressed to Lmono was intended for me Tmono.
You ask: "So why didn't you provide the same?"
It just didn't occur to me to do so.
My intent was to report that there was at least one other user encountering a similar problem. It occurred to me that Adobe might be interested in determining the scale of a problem which causes one of their best known products to fail to run quite so completely after a clean install
I also see that I misreported the OS I'm running - its Windows 8.
If there is further information I can provide which might be helpful in determining a solution, if someone could be specific about what would be helpful, then I will try to respond appropriately.
Perhaps the following from the event log:
Faulting application name: Photoshop.exe, version: 15.1.0.148, time stamp: 0x53d97a8f
Faulting module name: igdfcl64.dll, version: 8.1.0.2875, time stamp: 0x507eff6d
Exception code: 0xc0000005
Fault offset: 0x0000000000809283
Faulting process id: 0x1f48
Faulting application start time: 0x01cfca332430f3a7
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\windows\SYSTEM32\igdfcl64.dll
Report Id: 659ea6c9-3626-11e4-bea1-9c2a70825e62
Faulting package full name:
Faulting package-relative application ID:
The X230 has Intel HD 4000 graphics support built in to the processor. Windows was pretty stubborn about refusing driver updates, but I just managed to get drivers from the Intel site to install and Photoshop is now running, so hopefully I need not try your patience any further.
In case anyone else has a similar problem and stumbles on this the way to install the driver that worked was to:
- download the zip version of the generic driver from Intel
- use the 'have disk' option in the windows dialog to install the driver - other paths in the UI did not work with windows refusing to install the driver.

Adobe Premiere CC"has stopped working error"

Ran an update on Adobe Premiere CC last night. Now this error occurs. I did a system restore to 1 hour before the update. Adobe worked fine this morning. After I closed the program and logged in tonight the "has stopped working error" displays. Also Adobe will not import and .MOV files and the .MOV files that are already on the timeline are no longer there. Any help would be appreciated thanks.

I have just had the same thing happen to me too. Everything has been working fine but today, Premiere has crashed/stopped working twice. I have managed to get back into it now, but it won't playback either the Source or Program Monitors, saying there is a 'Low-level exception in Adobe Player (Player)'.

Adobe Premiere Pro CC 2014.2 has stopped working error

Hello guys,
I have recently built a new computer with the following specs:
CPU: 4790k (stock speed)
Ram: Team Extreem 16 GB (2x8) (at 2400mhz)
Motherboard: Asus Ranger 7
GPU: Zotac 780ti Amp edition
Storage: 250SSD Samsung evo + Barracuda 1TB
PSU: 850 G2 EVGA
Operating System: Windows 7 Professional
All drivers are up to date.
So I have installed the creative cloud and then proceeded to install the applications in the following order: Media Encoder, Photoshop and Premiere Pro CC. Both media and photoshop have no problems but premiere pro CC crashes upon clicking on it.
I would click on the premiere pro CC button and the premiere pro loading screen will pop up but then the 'has stopped working error' will happen immediately.
I need to get this problem solved within the next couple of days because I need it for a very important video project. If this problem cannot be fixed in the next 2 days I will, unfortunately, have to refund my subscription with adobe (still within 28 days) and use Cyberlink or Vegas.
I tried searching the forums and google but haven't found a solution that works for me. Could someone please lend a hand?

Log Name:      Application
Source:        Windows Error Reporting
Date:          24/12/2014 02:24:37
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      TimothyNg-PC
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Adobe Premiere Pro.exe
P2: 8.2.0.65
P3: 5486db4a
P4: ImageRenderer.dll
P5: 8.2.0.65
P6: 5486b5ee
P7: c000001d
P8: 00000000001f5342
P9:
P10:
Attached files:
C:\Users\Timothy Ng\AppData\Local\Temp\WER1ADF.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Timothy Ng\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Adobe Premiere P_c9e978dddf5d58a2727a44f4be9bc974f52b65b_153e222f
Analysis symbol:
Rechecking for solution: 0
Report Id: ffe49cc7-8b13-11e4-9225-7824af362b95
Report Status: 1
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-24T02:24:37.000000000Z" />
    <EventRecordID>2146</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TimothyNg-PC</Computer>
    <Security />
</System>
<EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Adobe Premiere Pro.exe</Data>
    <Data>8.2.0.65</Data>
    <Data>5486db4a</Data>
    <Data>ImageRenderer.dll</Data>
    <Data>8.2.0.65</Data>
    <Data>5486b5ee</Data>
    <Data>c000001d</Data>
    <Data>00000000001f5342</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\Timothy Ng\AppData\Local\Temp\WER1ADF.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\Timothy Ng\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Adobe Premiere P_c9e978dddf5d58a2727a44f4be9bc974f52b65b_153e222f</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>ffe49cc7-8b13-11e4-9225-7824af362b95</Data>
    <Data>1</Data>
</EventData>
</Event>

Adobe Photoshop Lightroom has stopped working error

Updated to latest CC version - everything worked as expected for a couple of days - earlier this afternoon LR started (and continues) to crash. "Adobe Photoshop Lightroom has stopped working" error - I followed various bits of support instructions - uninstalling - re-installing - signing out and back in - downloaded and engaged "Adobe Creative Suite Cleaner Tool" - now, several hours later, the problem has not been resolved - I urgently need to get back to my project. Unfortunately, I even followed the thread that instructed to uninstall the previous 5.7.1 version.
Please assist asap - regards Kalli

Did not tinker with any of the setting options in the preference dialog. Just installed and worked successfully for a couple of days using the default settings.
Since the first crash some hours ago, LR has not stayed open making it impossible to try different settings.
The default install provided a fully working app - I tried out the new feature and soon after went back to my project.
Could the fact that I uninstalled the previous - 5.7.? version have anything to do with this?
How can I re-install the previous version at it was stable?
Do any of you have any answers?
And / or do you know how to engage Adobe?
Thanks - Kalli

Fresh Install Mac - Licensing for this product has stopped working Error: 6

We just got the new macbook pro refreshes at work and decided to make the switch to standalone CFBuilder.   We downloaded the trial and installed. On launch we get this error, "Licensing for this product has stopped working Error: 6". Every macbook had the same result.   All are running 2 Ghz Quad Core i7 with 8GB of ram.   All of them get the same error.    All have a fresh install of 10.6.6.   Other than installing Air before the CFBuilder install they have no other applications installed.   Other than Air, there are no other Adobe products installed. All CFBuilders were installed under an admin account.
We've tried all the troubleshooting.   Permissions, LicenseRecovery, Setting the clock back to 2010... we even tried reinstalling OSX, then installing acrobat, then air, then CFBuilder with the same result every time.   We even activated the root account on the system and installed under root. Same result every time.    The Flexnet service never gets created unless we use the License recovery tool.   If we install the updater it still makes no difference.
All options for CFBuilder are grayed out under help.   Registration, Deactivation, Updates...
Any suggestions?

Thanks for posting and letting me know. Yes, it is crappy to have to work-around it like that. I noticed when I installed
Builder that it over-wrote some newer files, but I said "Okay to All". I'm using CS4 not CS5 and my newer files were probably better. I'm glad you got your program working at least. My problem is I started my first Project at the wwwroot level, like all the instructions say. It wasn't until I saw Ben Forta's video of it that I realized I was supposed to start a new folder within the wwwroot folder as my Project folder. Now I can't get rid of my first Project folder without DELETING all of the files in wwwroot, WHICH I CANNOT DO. MANY OF THE FOLDERS THERE ARE WORKING WEB SITES! If you know of any way to detach that original Project, I'd sure like to know how to do it.
Thanks,
Tedra

Adobe AIR Debug Launcher has stopped working Error on Flash Builder 4.6

Similar Messages

Maybe you are looking for