Adobe Elements 9 Crashing

Hi. I am trying to burn my completed movie to DVD and save a copy to my hard drive. When I try to do this Adobe Elements keeps shutting down. It usually gets to 99% and then stops working. I have tried reinstalling the program and I have deleted a lots of files to free up my hard drive. Does anyone have any ideas on how to fix this problem. Thank you

So its a JVC everio camcorder. I'm not too sure about format and resolution.
Yes used the get media tool.
My project settings are DV PAL, 25 F/sec, DV 25 720 x576i
My computer is an ACER aspire 5742G
Intel (R) Core (TM) i5 CPU
RAM 4GB
And I actually just 5 mins ago ran disk cleanup however problem is still there.
I'm not sure how I find out about defragmented disc space

Similar Messages

Adobe elements 10 crashing

Adobe elements 10 keeps crashing and it used to work. Why? Fix?

Hi,
Please try couple of probable solutions as mentioned below:
Solution 1:
1. Close Elements.
2. Launch the Photoshop Elements Welcome Screen and hold down ctrl + alt + shift as you click Editor.
3. Continue to hold the keys until you see a message box asking if you want to delete Photoshop Elements settings file; click Yes. Elements will open with default preferences.
Solution 2: In case any network printer is attached try to launch without network or printer uninstall or make different printer as default.
Solution 3: Try launching with anti-virus off or removing PSE from conflicting list.
Solution 4:
On the drive on which you have installed PSE,on my machine it is on C:
Go to C:\Program Files\Adobe\Photoshop Elements 10\Locales\<locale>\Plug-Ins\Import-Exportand you will find twain plug-in. Remove that plug-in from that location and copy it somewhere else.
Now launch PSE and check if it works.
For related post for Twain please see this:http://forums.adobe.com/message/2954743#2954743
Thanks,
Garry

Adobe Elements 12 crash

I have a new system since 2 weeks: Intel i7 4770, 16Gb, Windows 8.1 x64, SSD, AMD Radeon 9 270X 4GB. All drivers and software are the latest available versions.
I bought this system because my old system got a lot of crashes when using Adobe Elements Premiere 12 (AEP12).
But currently I am creating a movie and and do already have 2 crashes with my system. When the crash appears the video is corrupted and i only can kill AEP12 and then start the program again.
How can I find out what goes wrong here and find a way to fix this ?
Any ideas ?

For Windows, do NOT rely on Windows Update to have current driver information
-you need to go direct to the vendor web site and check updates for yourself
ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
Also, what are you editing?
Codec & Format information, read both links in reply #1 http://forums.adobe.com/thread/1270588
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
For PC (only?) http://www.headbands.com/gspot/
For PC/Mac http://mediaarea.net/en/MediaInfo/Download

Why is my adobe elements 11 crash right as it start the program?

i bought premiere elements 11 about 10 days ago, and its been working perfect until all of a sudden today it wont let me open the video editor, it keeps saying "adobe premiere elements has stopped woeking" it shows a status message like this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Elements.exe
Application Version: 11.0.0.0

if you have system backups, roll back your computer to a time before the crashes started.

My adobe elements keeps crashing and shutting down. How do i reinstall the software

cross posted
I have elements 9 - old program. It suddenly stopped working. How do i reinstall? I have the serial number. Thanks. I got a deadline tomorrow would really appreciate help.

reset your preferences -
acrobat: http://help.adobe.com/en_US/acrobat/X/pro/using/WS58a04a822e3e50102bd615109794195ff-7feb.w .html
adobe media encoder: https://forums.adobe.com/thread/1713540
after effects: http://helpx.adobe.com/after-effects/using/preferences.html
dreamweaver: https://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs6-cc.html
flash: http://helpx.adobe.com/flash/kb/re-create-preferences-flash-professional.html
illustrator: http://helpx.adobe.com/illustrator/using/setting-preferences.html
indesign: https://forums.adobe.com/thread/526990
lightroom: https://helpx.adobe.com/lightroom/help/setting-preferences-lightroom.html
muse (mac): https://forums.adobe.com/thread/1246022?tstart=0
photoshop: https://forums.adobe.com/thread/375776
photoshop elements: http://www.photokaboom.com/photography/learn/Photoshop_Elements/troubleshooting/1_delete_p references_file.htm
premiere pro: http://www.mediacollege.com/adobe/premiere/pro/troubleshooter/trash-preferences.html
if that fails, uninstall, clean (http://www.adobe.com/support/contact/cscleanertool.html) and reinstall.
Downloadable installation files available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4, CS4 Web Standard | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
Photoshop Elements: 13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
Lightroom: 5.7.1| 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5.5, 5 | 1
Contribute: CS5 | CS4, CS3 | 3,2
FrameMaker: 12, 11, 10, 9, 8, 7.2
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

Adobe elements 6 keeps crashing since upgrading iPhotos on Yosemite

Adobe elements keeps crashing every time I try to open a photo.
This seems to have started since I installed the Photos app on my Macbook Air.

Photos is not iPhoto and doesn't work at all the same way. You must export the photos from Photos, then open those copies in PSE. There is no external editor function in Photos at all.
How to use an external editor with Photos for OS X | iMore

Adobe updater is crashing with adobe photoshop elements 6 and mac os version 10.9.4 (on a brand new install) . How to overcome this ?

adobe updater is crashing with adobe photoshop elements 6 and mac os version 10.9.4 (on a brand new install) . How to overcome this ?

Maybe I typed it wrong ...it is unchecked.
This is the message I receive:
Process:         Adobe Updater
Path:            /Applications/Utilities/Adobe Utilities.localized/*/Adobe Updater.app/Contents/MacOS/Adobe Updater
Identifier:      "com.Adobe.ESD.AdobeUpdaterApplication"
Version:         Adobe Updater 5.1.0.1082 (5.1.0.1082)
Code Type:       X86 (Native)
Parent Process: launchd
Responsible:     Adobe Updater
User ID:         501
Date/Time:       2014-11-21 12:39:47.691 -0600
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 42CCAEE7-C520-BA70-4B27-711A184AB1A5
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
terminating with uncaught exception of type std::runtime_error: Unable to determine registration filepath!
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        0x93982952 __pthread_kill + 10
1   libsystem_pthread.dylib       0x96f15167 pthread_kill + 101
2   libsystem_c.dylib             0x940f029c abort + 155
3   libc++abi.dylib               0x99fe06c9 abort_message + 169
4   libc++abi.dylib               0x9a00147d default_terminate_handler() + 264
5   libc++abi.dylib               0x99ffec30 std::__terminate(void (*)()) + 14
6   libc++abi.dylib               0x99ffe64b __cxa_throw + 116
7   "com.Adobe.ESD.AdobeUpdaterApplication"0x0004e4a3 0x1000 + 316579
8   "com.Adobe.ESD.AdobeUpdaterApplication"0x00056f19 0x1000 + 352025
9   "com.Adobe.ESD.AdobeUpdaterApplication"0x00024499 0x1000 + 144537
10 "com.Adobe.ESD.AdobeUpdaterApplication"0x000139c0 0x1000 + 76224
11 "com.Adobe.ESD.AdobeUpdaterApplication"0x00002912 0x1000 + 6418
12 "com.Adobe.ESD.AdobeUpdaterApplication"0x0000282d 0x1000 + 6189
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        0x93983992 kevent64 + 10
1   libdispatch.dylib             0x96f1e899 dispatchmgr_invoke + 238
2   libdispatch.dylib             0x96f1e532 dispatchmgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib        0x93983046 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x96f15dcf pthreadwqthread + 372
2   libsystem_pthread.dylib       0x96f19cce start_wqthread + 30
Thread 3:
0   libsystem_kernel.dylib        0x93983046 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x96f15dcf pthreadwqthread + 372
2   libsystem_pthread.dylib       0x96f19cce start_wqthread + 30
Thread 4:
0   libsystem_kernel.dylib        0x93983046 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x96f15dcf pthreadwqthread + 372
2   libsystem_pthread.dylib       0x96f19cce start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa10e2c0c ecx: 0xbffff0dc edx: 0x93982952
edi: 0xa13a31a8 esi: 0x00000006 ebp: 0xbffff0f8 esp: 0xbffff0dc
   ss: 0x00000023 efl: 0x00000206 eip: 0x93982952   cs: 0x0000000b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x99fe3e46
Logical CPU:     0
Error Code:      0x00080148
Trap Number:     132
Binary Images:
    0x1000 -   0x24cff7 +"com.Adobe.ESD.AdobeUpdaterApplication" (Adobe Updater 5.1.0.1082 - 5.1.0.1082) <3D59867C-5698-4D46-AD1F-C357C48B75AA> /Applications/Utilities/Adobe Utilities.localized/*/Adobe Updater.app/Contents/MacOS/Adobe Updater
0x3ce000 -   0x3d9fff com.apple.CommerceCore (1.0 - 42) <D28DD970-4B69-3848-9BCC-3C67323B3D9C> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCor e.framework/Versions/A/CommerceCore
0x493f000 - 0x4964ff9 com.apple.framework.familycontrols (4.1 - 410) <A33A97EE-C735-38BA-9B49-5D78DAA3DEDA> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
0x8fea6000 - 0x8fed8417 dyld (239.4) <0F2176BD-4239-3506-BA41-3B885269520E> /usr/lib/dyld
0x90008000 - 0x90023ff5 com.apple.openscripting (1.4 - 157) <5C161A52-8D2F-3D56-A988-05727BED7A59> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework /Versions/A/OpenScripting
0x90024000 - 0x90025fff liblangid.dylib (117) <F18F76C6-7E4B-34AD-AE81-C1C031BF2F7D> /usr/lib/liblangid.dylib
0x90026000 - 0x90109ff7 libcrypto.0.9.8.dylib (52) <D3AB1D26-30BA-36D3-956C-EC7D7185C396> /usr/lib/libcrypto.0.9.8.dylib
0x9010a000 - 0x90135ff7 libsystem_network.dylib (241.3) <71EBA489-386D-3608-ADE6-CB50EBD1AB1B> /usr/lib/system/libsystem_network.dylib
0x90136000 - 0x9052effb com.apple.CoreGraphics (1.600.0 - 599.35.4) <2B46D887-CAED-30F3-B009-1EBF0C71DC2E> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x9069c000 - 0x906a5fff com.apple.audio.SoundManager (4.1 - 4.1) <68B7CEB7-AF09-3E24-8548-6ABF065B5186> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/V ersions/A/CarbonSound
...and it goes on and on.
Joy (Awbrey) Schichtl
[email protected]

Adobe Premiere Elements. Crash at transcode

Dear Adobe Community,
i got every time on ~66% a crash on transcoding. I will export (AVCHD/Bluray) my movie on a Disc/Computer but there is always the same problem with a movie longer than 1h. If i cut this movie to half. It works without a problem. I tried to export the 1st and the 2nd half that i can exlude errors in my files/jpegs. Both are export without an error.
Tried exports:
short/large movie with export option DVD. working.
short movie with export option AVCHD. working
short movie with export option Bluray. working
large movie with export option AVCHD. crash
large movie with export option bluray. crash
No entries in the event log. Only the message in elements with aborted transcoding.
I tested CPU/RAM with >5 hours Prime/OCCT stable.
What else can i try?
Sys:
Notebook: Sony VAIO VPCF11S1E (Vaio VPC-F Serie)
Prozessor: Intel Core i7 720QM
Grafikkarte: NVIDIA GeForce GT 330M
Thank you in advance

monchauer,
Thank you for that information.
Translation of the error log:
Name of misapplication: Adobe Premiere Elements.exe, version: 11.0.0.0, time stamp: 0x5041d43d
Name of the faulty module: mc_enc_avc.dll, version: 8.5.0.5184, time stamp: 0x4ff260b7
Exception code: 0xc0000005
Error Offset: 0x000000000002757c
ID of the faulty process: 0x874
Start time of misapplication: 0x01cf2ca939298336
Path of the faulty application: C: \ Program Files \ Adobe Elements \ Adobe Premiere Elements 11 \ Adobe Premiere Elements.exe
Path of the faulty module: C: \ Program Files \ Adobe Elements \ Adobe Premiere Elements 11 \ mc_enc_avc.dll
Report ID: 0dee2331-98AB-11e3-9023-5063139f3a94
The Faulting Module is mc_enc_avc.dll
Here is a PrPro thread on crashes on H.264 Export. In it, Jim Simon has a link to a MS Knowledgebase article, that might be useful: http://forums.adobe.com/thread/1141341
It appears that that .dll is likely part of the MainConcept Encoder: http://www.herdprotect.com/mc_enc_avc.dll-50f9fb58d88ab643d0199d77b79c2b9b4b12a8c7.aspx
As the MainConcept Encoder is installed along with PrE, if the MS article, or the Herd Project one does not help, it might be time to Uninstall PrE, run a Registry cleaner, like CCleander, then Reinstall. I am not a big fan of doing the Uninstall/clean/Reinstall, and usually hold that in the wings, until nothing else works, but then there are times, when an installation can become corrupt (in this case one of the MainConcept modules?), and that can fix some issues. I would try other remedies first, and maybe others will have some direct experience with the mc_enc_avc.dll, that will help, without that Uninstall/clean/Reinstall.
Good luck,
Hunt

Adobe Photoshop Elements 10 crashing on my Mac

HELP! My Photoshop Elements 10 keeps crashing on my Mac! Been using it for many years but have recently upgraded my Mac and now the program will run for about 15 mins and then crash! Very frustrating!

When you upgrade OS X over an installed copy of PSE it is critical to delete all existing preferences.
Go to your username>libary>preferences and delete:
com.adobe.PhotoshopElements.plist
Adobe Photoshop Elements 10 settings
Adobe Photoshop Elements 10 paths
com.adobe.Elements Organizer. 10.0.plist
com.adobe.ElementsOrganizer10.plist
and any lockfiles with the same names.
To see the user library in recent versions of OS X, click the Go menu in the Finder and hold down the Option key and it will appear below the little house for your user account. While you're in there also go to the Saved Application States folder and delete any for PSE.

Just installed Adobe Premiere Elements 10 - Crashes upon opening a new Project

I've just installed Adobe Photoshop & Premiere Elements 10 on one of our marketing user's PC, and while Photoshop works like a charm, Premiere Elements 10 crashes every time you try to create a new project. I have done a total uninstall and reinstall, but get the same results. Here is the crash report generated by Windows (7 Pro x64)
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Elements.exe
Application Version: 10.0.0.0
Application Timestamp: 4e791009
Fault Module Name: dvacore.dll
Fault Module Version: 8.0.0.0
Fault Module Timestamp: 4e78f08f
Exception Code: c0000005
Exception Offset: 000000000000154e
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7a8f
Additional Information 2: 7a8f433f52f6f9a5539b887f16e37397
Additional Information 3: 9ca8
Additional Information 4: 9ca8acafba7b6c4cf5e9fa78b17b0956

Thank you for trying to help, Bill.
I had read about the fingerprint problem in the forums and deactivated that before my first post.
I am reasonably proficient with CS6 web/design, but I don't have a lot of tech knowledge.
While working today, I had trouble with Acrobat X and had to uninstall/reinstall. I have done more restarts in the last 36 hours!
I uninstalled/reinstalled PrE ... in case something that I had done had helped! Organizer opens but not PrE.
I will put the EventViewer stuff at the end of the post. I didn't know there was an EventViewer until today!
It says something about PCI bus. I went to control panel, etc., devices and there were two instances of PCI bus. I asked Windows to update the driver for both and got a message that it had the most up to date driver. Also indicated they were working properly. When I sent the link at the bottom of the EventViewer info to Windows, I got a screen saying it was an unknown error.
I bought PrE on Saturday ... to replace NERO. I thought it would be more consistent with the other programs I use, but maybe I should cut my losses and go back to NERO??? What do you think?
I really do appreciate the help.
Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          14/08/2012 5:59:52 PM
Event ID:      17
Task Category: None
Level:         Warning
Keywords:
User:          LOCAL SERVICE
Computer:      MaryRose-HP
Description:
A corrected hardware error has occurred.
Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)
Bus:Device:Function: 0x0:0x3:0x0
Vendor ID:Device ID: 0x8086:0xd138
Class Code: 0x30400
The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
    <EventID>17</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2012-08-14T23:59:52.830276300Z" />
    <EventRecordID>651021</EventRecordID>
    <Correlation ActivityID="{3D023B18-BA52-49EA-A02C-2DBEF2BA8D91}" />
    <Execution ProcessID="1796" ThreadID="7340" />
    <Channel>System</Channel>
    <Computer>MaryRose-HP</Computer>
    <Security UserID="S-1-5-19" />
</System>
<EventData>
    <Data Name="ErrorSource">4</Data>
    <Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="FRUText">
    </Data>
    <Data Name="ValidBits">0xdf</Data>
    <Data Name="PortType">4</Data>
    <Data Name="Version">0x101</Data>
    <Data Name="Command">0x10</Data>
    <Data Name="Status">0x407</Data>
    <Data Name="Bus">0x0</Data>
    <Data Name="Device">0x3</Data>
    <Data Name="Function">0x0</Data>
    <Data Name="Segment">0x0</Data>
    <Data Name="SecondaryBus">0x0</Data>
    <Data Name="Slot">0x0</Data>
    <Data Name="VendorID">0x8086</Data>
    <Data Name="DeviceID">0xd138</Data>
    <Data Name="ClassCode">0x30400</Data>
    <Data Name="DeviceSerialNumber">0x0</Data>
    <Data Name="BridgeControl">0x0</Data>
    <Data Name="BridgeStatus">0x0</Data>
    <Data Name="UncorrectableErrorStatus">0x0</Data>
    <Data Name="CorrectableErrorStatus">0x40</Data>
    <Data Name="HeaderLog">00000000000000000000000000000000</Data>
    <Data Name="Length">672</Data>
    <Data Name="RawData">435045521002FFFFFFFF02000200000002000000A0020000333B17000E080C140000000000 000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC0 93CF161AFC4DB8BC9C4DAF67C104EDA8C93F747ACD010000000000000000000000000000000000000000000000 0010010000D0000000010200000100000054E995D9C1BB0F43AD91B44DCB3C6F35000000000000000000000000 00000000020000000000000000000000000000000000000000000000E0010000C00000000102000000000000AD CC7698B447DB4BB65E16F193C4F3DB000000000000000000000000000000000300000000000000000000000000 00000000000000000000DF0000000000000004000000010100001000070400000000868038D100040300030000 000000000000000000000000000000000010E042012180000007010100023D39034300027100009800C0030000 080001000000000000000000000000000000000000000000000000000000000001000115000000000000000010 20060040000000000000000E000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000043010000000000 000002000000000000E50601000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000 0000000000</Data>
</EventData>
</Event>

Has Adobe solved the crashing issues for Premiere Elements 10?

Hi there,
I've been using Adobe Premiere Elements 8 for about 2 years now. I do like this program and appreciate it being quite a straight forward, uncomplicated, video editing program. One thing which really annoys me about it, however, is its constant tendency to just crash when I import and move around *.jpg images using motion tracking, or just dragging something around the screen. For example, I film myself walking into a room with my hand pretending to hold a balloon. I then import a *.jpg image of a balloon into the shot and move to position it in my hand as though it's really there.
My intention is to edit the balloon image to follow my hand while I'm in the room and, while I could use the motion tracking feature, I prefer to edit frame by frame, or else the *.jpg image doesn't always line up properly with what it's following (it's close enough, but I prefer doing it myself).
Whenever I move an imported *.jpg image on the screen, it obviously becomes blocky for a moment until you wait for the image to become clear (I think pixilated is the right term, but am not certain) or unblocky (ie curved edges, which moved and became square, become curved again).
What Premiere Elements 8 has been doing on my computer (which has an i5 processor, more than enough memory and so forth) is to crash out of the program when I drag an image across the screen.
It has helped to move a picture slightly, wait for it to become clear, then move it slightly again, but this still has a tendency to cause Premiere Elements to crash out.
CAN ANYONE tell me, please, if Adobe Premiere Elements 10 has this or similar issues because this problem alone is driving me crazy?
Advance thanks.

Welcome to the forum.
Many users felt that PrE 8 was a very weak release (kind of like Adobe's version of MS's Vista OS), but most users, with properly setup and tuned computers, find that PrE 10 is a very stable build.
For the issues with PrE 8 crashing, I would see this ARTICLE. It starts with a checklist on setting up PrE and the computer, for best results. Then, it goes into many tuneup tips, for both the computer, and the OS. Finally, it lists links to help with troubleshooting.
Good luck, and hope that something in the article helps,
Hunt

Adobe Elements 11 from OS X App Store Crashing

Hi,
Just recently purchased Adobe Elements 11 off the APP Store.
It wont even open without crashing.
It seem like it should be a simple error to fix but I cannot find any information with regards to solving the problem. Please see the information below.
Thanks
Process:         Adobe Photoshop Elements 11 Editor [2091]
Path:            /Applications/Adobe Photoshop Elements 11 Editor.app/Contents/MacOS/Adobe Photoshop Elements 11 Editor
Identifier:      com.adobe.pse11editor
Version:         ???
App Item ID:     571583293
App External ID: 11641628
Code Type:       X86 (Native)
Parent Process: launchd [164]
Responsible:     Adobe Photoshop Elements 11 Editor [2091]
User ID:         501
Date/Time:       2014-02-10 07:57:32.008 +0200
OS Version:      Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 6C8B6495-FA3B-FC9A-E45B-FB90648B5D70
Sleep/Wake UUID: 1ABF7E23-69BD-413C-A911-6E1733C13FA2
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/AdobeMPS.framework/Versions/A/AdobeMPS
Referenced from: /Applications/Adobe Photoshop Elements 11 Editor.app/Contents/MacOS/Adobe Photoshop Elements 11 Editor
Reason: image not found
Binary Images:
0x8fe06000 - 0x8fe38417 dyld (239.3) <4B280BB1-55F8-313F-86A6-8ADD644ED69E> /usr/lib/dyld
0x902de000 - 0x904e0ff7 com.apple.CoreFoundation (6.9 - 855.11) <50F70E07-043A-3A2F-87EF-A36BA6C5C9D9> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90bf6000 - 0x90c42ff7 libcups.2.dylib (372) <9A2BE8DC-37E4-3019-B665-1036FE7868EA> /usr/lib/libcups.2.dylib
0x91d7c000 - 0x92997ff3 com.apple.AppKit (6.9 - 1265) <AE258D94-0272-394F-BBB7-9B5C165A4A78> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x92a4a000 - 0x92a4afff com.apple.Carbon (154 - 157) <6E680560-FD53-3C00-BDF7-7AFA28747DC8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x965a1000 - 0x96616ffb com.apple.framework.IOKit (2.0.1 - 907.1.13) <86D72735-9DFB-35C8-83F7-CE0DCF17D354> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x9661e000 - 0x967caff1 com.apple.QuartzCore (1.8 - 332.0) <07F9B77F-35A2-3D21-99FA-CD3FCE5B9C7B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x968e4000 - 0x968f2ff3 com.apple.opengl (9.0.83 - 9.0.83) <16CFFD50-217E-3E18-88AF-7F2AD980628B> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x96a33000 - 0x96d5eff6 com.apple.Foundation (6.9 - 1056) <C8AE9C03-3460-354A-A8B6-EF4955BE600D> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x997d7000 - 0x99a44ff6 com.apple.security (7.0 - 55471) <5FCF76B2-92C6-3404-87D3-91B3F6E203AA> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x99ef1000 - 0x99ef8ffe com.apple.agl (3.2.3 - AGL-3.2.3) <E26A1D2C-596E-31F0-8E70-FC381874F8DA> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
Model: MacBookPro5,3, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2.66 GHz, 4 GB, SMC 1.48f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Corsair Force 3 SSD, 60.02 GB
Serial ATA Device: MATSHITADVD-R   UJ-868
USB Device: Built-in iSight
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: Composite Device
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus:

Hi,
Thanks for reply but I cannot even get Photoshop elements to start. I click on the app to open it and it crashes within a few seconds. No interface even appear to work with.
Does the error above you an idea of what the problem may be?
Especially around:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/AdobeMPS.framework/Versions/A/AdobeMPS
Referenced from: /Applications/Adobe Photoshop Elements 11 Editor.app/Contents/MacOS/Adobe Photoshop Elements 11 Editor
Reason: image not found

Adobe elements 10 is not responding--program keeps crashing

I have elements 10 and it is forever crashing with message "Adobe Elements 10 is not responding."

Ken, thank you for responding.
When I get the error, I’m given two options, cancel the program or wait until Elements 10 responds. Some time if I wait long enough it will respond but only to crash again. This seldom happens in Editor.
This is a new catalogue on the new computer. I never had this problem with earlier versions of Elements—only with 9 and 10.
Thank you,
Robert

Adobe Premier Elements 7- crash-when burning says" Please insert a blank disk" and already a disk in

I have a Adobe Premier Elements 7. I have had a lot of problems with it of crashing and not burning.. I just had my computer wiped out and installed everything back on like windows xp service pack 3..etc. First I have Windows XP service pack 3 with an Intel Core 2CPU ,6400 @213GHz, 2.13 GHz, 1.98 GB of RAM. When I went into disk menus premier elements 7 crashes... why is that??? also I tried to burn a DVD and does the progress of burniing and almost done burning WHILE there is a dvd in the drive and says"Please insert a blank disk and click ok to burning" why doe sit do that also? I just had adobe reinstalled and my computer wiped out? Please respond and help.. I am using this program as a business of video editing and nee this solved.

Along with Steve's questions, let's talk about the process of Burning a DVD-Video.
From PrE, which is doing the authoring of the DVD-Video, the first thing that happens is a quick check of the Project and the Menu Set chosen. This happens in an instant. Next, the program must Transcode the Timeline to MPEG-2 that is fully DVD-compliant. This takes some time and is a very intensive process, stressing the computer, and also heating things up greatly. This process will often cause a poorly ventilated, or poorly cooled computer to crash with either a reboot, or a BSOD (Blue Screen of Death). Every component, save for the video card, will be stressed like few other programs can do. PrE uses a 2-pass Transcode, where it goes through the entire Timeline, and maps out sections with high motion, or great detail. It builds a "script" on how to proceed, and then goes back at the Timeline with that script, but also still looking for ways to improve things. This is about 90% of the entire Burn Disc process. Nothing has yet to be burned. Instead, files are created in the Scratch Disk folders. Now, the program takes those newly created MPEG-2 files, the Menus, and all navigation such as Markers, and assembles them into another working folder, in the full DVD structure of VIDEO_TS folder with the IFO, BUP and VOB's. When this is done, the actual physical Burn starts. This is quite a ways into the total process. It is at this point, that the program looks at the burner and the blank media, and not before.
When the program cannot get the necessary info from the burner, or the blank media, it will throw an error message, similar to yours. Also, "SenseCode Errors" usually indicate a problem with the burner, or the media.
Now, let's address this last bit. Is the firmware for your burner up to date? If not, update/flash the firmware. This will be available from your burner mfgr's. Web site. Next, what brand of blank media are you using? Verbatim and Taiyo Yuden are the most recommended brands. Memorex, TDK, newer Ritek and all store brands should be avoided at all costs. Last, is your burner a fully-certified multi-drive? If so, it should be able to handle +R, or -R media. What type are you using, and are you sure that this is blank media, and not a disc that you have already burned, or even attempted to burn?
Hope that we can stop the crashes, and get you to burning.
Good luck,
Hunt

Why does Adobe Elements 4.0 suddenly crash about the time Apple has a security update?

Why does Adobe Elements 4.0 suddenly start crashing about the time Apple has a security update?

An ADOBE FORUM "Community Professional" commented:
"Well, I'm not sure any of this is going to work, but go to your username>library>preferences and delete:
com.adobe.Photoshop.Elements.plist
The PSE 4 Paths and Settings folders (can't remember whether they're called Adobe Photoshop Elements 4.0 Paths or something different, but you want folders with Paths and Elements 4 in their names--you should be able to figure out which they are)
Opera preferences (if you have it)
Repair permissions and try again.
If it still quits, go to the PSE 4 folder in applications and delete the Adobe TWAIN driver from the plug-ins folder (note that you may have trouble with Epson scanners in PSE after doing this).
However, PSE 4 is pretty darned old and it's less compatible with every new OS X update, so what I've suggested may work and may not. FWIW, you probably will not be able to reinstall the program if you ever need to do so--installed versions of PSE 4 keep working in 10.6, but the installer does not."
Hope this helps

Adobe Elements 9 Crashing

Similar Messages

Maybe you are looking for