PS elements 6 crashes while editing

While using the clone tool PS keeps crashing every few minutes. I do save my work, but am consuming an inordinate amount of time editing a photo. Can anyone provide some assistance. I am using a Dell Inspiron 6000 with Windows XP w/service pack 2, 2GB RAM, 1.6 Ghz Pentium processor.
Thank you

Peter,
You might try deleting the Editors preferences and, if that doesnt work, reinstalling with anti-virus and other services temporarily disabled. See steps 4 and 9 in Adobes troubleshooting document:
http://www.adobe.com/go/kb402520

Similar Messages

  • Workshop CRASHED while editing a page flow

    Workshop Gurus -
    Any clues on this bug. I get this error while editing pageflow. It just started
    happening this morning.
    I must say, WLW crashes gracefully. It allows me to report this message directly
    to BEA, and then allows me to save my files. However, I do need a resolution to
    this problem, hopefully soon.
    java.lang.NullPointerException
         at workshop.pageflow.model.ExternalPageFlow.refChanged(ExternalPageFlow.java:120)
         at workshop.pageflow.model.DocumentEventAdapter.processModelObjects(DocumentEventAdapter.java:492)
         at workshop.pageflow.model.DocumentEventAdapter.process(DocumentEventAdapter.java:177)
         at workshop.pageflow.model.DocumentEventAdapter.elementChange(DocumentEventAdapter.java:123)
         at com.bea.ide.element.ElementChangeSupport.fireListeners(ElementChangeSupport.java:253)
         at com.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupport.java:243)
         at com.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupport.java:219)
         at com.bea.ide.document.DefaultDocument.fireElementChildRemoved(DefaultDocument.java:482)
         at com.bea.ide.sourceeditor.DefaultSourceDocument.mergeComplete(DefaultSourceDocument.java:523)
         at com.bea.ide.sourceeditor.DefaultSourceDocument.mergeMetadata(DefaultSourceDocument.java:610)
         at workshop.sourceeditor.compiler.CompilerProject$MergeRunner.run(CompilerProject.java:1448)
         at workshop.sourceeditor.compiler.CompilerSvcImpl$TreeMergeLock.runMerger(CompilerSvcImpl.java:161)
         at workshop.sourceeditor.compiler.CompilerProject$4.run(CompilerProject.java:1498)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
    Thanks
    Kunal Mittal

    Raj -
    Yes I am using SP2. I have had Workshop crash SEVERAL times when working with
    page flows. Some sort of null pointer exception. The only good thing is that workshop
    crashes gracefully, so I didn't lose any work that I was doing.
    Thanks.
    Kunal
    "Raj Alagumalai" <[email protected]> wrote:
    Kunal,
    Can you try using SP2 ?
    Thanks,
    Raj Alagumalai
    Backline Workshop Support
    "Kunal Mittal" <[email protected]> wrote in message
    news:[email protected]...
    Workshop Gurus -
    Any clues on this bug. I get this error while editing pageflow. Itjust
    started
    happening this morning.
    I must say, WLW crashes gracefully. It allows me to report this messagedirectly
    to BEA, and then allows me to save my files. However, I do need aresolution to
    this problem, hopefully soon.
    java.lang.NullPointerException
    atworkshop.pageflow.model.ExternalPageFlow.refChanged(ExternalPageFlow.java:12
    0)
    atworkshop.pageflow.model.DocumentEventAdapter.processModelObjects(DocumentEve
    ntAdapter.java:492)
    atworkshop.pageflow.model.DocumentEventAdapter.process(DocumentEventAdapter.ja
    va:177)
    atworkshop.pageflow.model.DocumentEventAdapter.elementChange(DocumentEventAdap
    ter.java:123)
    atcom.bea.ide.element.ElementChangeSupport.fireListeners(ElementChangeSupport.
    java:253)
    atcom.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupp
    ort.java:243)
    atcom.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupp
    ort.java:219)
    atcom.bea.ide.document.DefaultDocument.fireElementChildRemoved(DefaultDocument
    .java:482)
    atcom.bea.ide.sourceeditor.DefaultSourceDocument.mergeComplete(DefaultSourceDo
    cument.java:523)
    atcom.bea.ide.sourceeditor.DefaultSourceDocument.mergeMetadata(DefaultSourceDo
    cument.java:610)
    atworkshop.sourceeditor.compiler.CompilerProject$MergeRunner.run(CompilerProje
    ct.java:1448)
    atworkshop.sourceeditor.compiler.CompilerSvcImpl$TreeMergeLock.runMerger(Compi
    lerSvcImpl.java:161)
    atworkshop.sourceeditor.compiler.CompilerProject$4.run(CompilerProject.java:14
    98)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
    atjava.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.ja
    va:197)
    atjava.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
    :150)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
    Thanks
    Kunal Mittal

  • Elements 8 crashing while viewing pictures windows 7

    Help, I have been having problems with elements 8 organizer crashing while reviewing photos one at a time. It will go for a while, then get a grash message, and the program closes. I'm using windows 7. I tried looking up one of john ellis's (sp) links, but it was a broken link.
    Any help you can provide? thank you in advance
    blind Squirrel
    [email protected]

      Are you running any background tasks such as Auto-Analysis or face recognition.
    If so; it’s worthwhile turning them off temporarily by going to Edit >>Preference from the Organizer menu.
     

  • Photoshop CS5 x64 crashing while editing layer styles

    Hey there,
    I searched and seeked through the whole interweb, but hardly anyone seems to have ever had such a problem, so I am guessing this is the right place to ask and hopefully be helped . Short version is: Photoshop CS5 (x64) is constantly crashing when editing a layer style.
    I recently installed my CS5 Design Premium on a new laptop (Fujitsu Lifebook AH351) and am having severe problems with Photoshop CS5. On first run everything was fine, and it kept that way for a while. Now everytime I try to edit a layer style Photoshop crashes immediately. I do not need to alter anything, just open the layer style, press OK and Photoshop is gone. I can workaround by resetting preferences which works until next reboot, no matter if I change ANYTHING on the settings or not. Had tried this on the initial PS release and on the latest update (12.0.4). Once I reset settings again, I can work on layer styles again. Did anyone of you have a similar problem or a hint at what I might look?
    The Lifebook has a decent feature which I suspect to somehow be the culprit of this case: it has an onboard graphics unit and a separate GPU (nVidia GForce GT 525M) which can be added in on a program-to-program basis. Photoshop indeed recognizes it and lets me activate OpenGL features as well, so from that point it seems fine. The internal GPU cannot be disabled since you connect your monitors to it.
    Some data about my system:
    Fujitsu Lifebook AH531
    Intel® Core™ i5-2410M
    RAM: 8 GB DDR3 1333 MHz
    750 GB SATA HDD 5400 U/Min
    Windows 7 Home Premium x64 (up to date)
    NVIDIA® GeForce® GT 525M with 1GB VRAM
    Photoshop CS5 x64
    no plugins in use/installed
    no settings changed, not even shortcuts
    Thanks in advance
    enoversum

    Funny replying to myself repeatedly. It seems I have found the problem with no solution in sight. My findings are as follows:
    I am running two external monitors on my laptop (HDMI and VGA), the laptop screen is off. If I unplug one screen, Photoshop is fine with me. No crashes.
    In nVidia settings you can choose what GPU is being used for specific programs. Changing it to the internal one, Photoshop is fine with me. No crashes. Crappy performance.
    I came to the idea of it having to do with dual monitors in my long way through help forums, and one thread here (on problems with 4 monitors) suggested to disable the ScriptingSupport.8li via re-naming which didn't work for me nonetheless. Now it seems up to me whether I'd love to farewell either my powerful GPU or my second monitor for working with Photoshop.
    Still, does anybody have a notion of what else I could possibly do? I won't assume Fujitsu to offer a fix for this, since it is hard to track down precisely where the problem comes from.
    All the best
    enoversum
    Edit: BTW, Windows settings confirm both screens are handled by/connected to the internal GPU, no matter what Photoshop is using ultimately. That seems like normal behaviour, and I cannot switch since the two ports are on the internal card.

  • Aperture crashes while editing. Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Hi! First, Aperture began to fail while editing, all the time. I repaired the library a lot of times, also repair permissions and move the library to a external HD for working with a new library. Nothing worked. I also did a test on my computer and the memory seems fine.
    I'm using Aperture 3.4.3 and I have a 13-inch, mid 2012 MacBook Pro Version 10.7.5, 2.5 Ghz Intel Core i5, 4 GB 1600 MHz DDR3.
    I copy the error message below, thanks!
    Process:         Aperture [558]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.3 (3.4.3)
    Build Info:      Aperture-310022000000000~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [129]
    Date/Time:       2013-03-04 23:13:04.401 +0100
    OS Version:      Mac OS X 10.7.5 (11G63)
    Report Version:  9
    Interval Since Last Report:          240513 sec
    Crashes Since Last Report:           25
    Per-App Interval Since Last Report:  80640 sec
    Per-App Crashes Since Last Report:   21
    Anonymous UUID:                      21FCBB11-229D-443A-9527-F6BFD46EE7D9
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x00000001303df200
    VM Regions Near 0x1303df200:
        MALLOC_LARGE           0000000130135000-00000001303df000 [ 2728K] rw-/rwx SM=PRV
    -->
        IOKit                  000000013046b000-0000000130470000 [   20K] rw-/rw- SM=ALI
    Application Specific Information:
    objc[558]: garbage collection is OFF
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.geode                    0x000000010b512041 -[DGGetPixelsProcessor processConstArea:bufferPtr:rowBytes:format:] + 1119
    1   com.apple.geode                    0x000000010b4c90a9 __52-[DGImageBuffer processConstPixelsInArea:processor:]_block_invoke_0 + 72
    2   com.apple.geode                    0x000000010b4c9592 -[DGImageBuffer forEachImmutableTileInROI:processor:] + 1183
    3   com.apple.geode                    0x000000010b4c905b -[DGImageBuffer processConstPixelsInArea:processor:] + 111
    4   com.apple.geode                    0x000000010b4fd755 DGGetPixelsForArea + 492
    5   com.apple.geode                    0x000000010b4c9635 -[DGImageBuffer getPixelsForArea:destPtr:destPtrRowBytes:] + 54
    6   com.apple.RedRock                  0x000000010a27ee34 -[LazyLabImage getPixelsForArea:destPtr:destPtrRowBytes:] + 2667
    7   com.apple.RedRock                  0x000000010a27d3c6 -[RKSelectiveMaskProcessor processStamp:radius:softness:brushBounds:brushPtr:brushPtrRowBytes:destData:des tDataRowBytes:] + 520
    8   com.apple.geode                    0x000000010b4f8611 -[DGBrushStroke rasterizeToMaskWithProcessor:scaledMaskBounds:maskPtr:maskPtrRowBytes:scale:clo se:startIndex:lastStampedIndex:] + 1403
    9   com.apple.Aperture                 0x00000001098eb5a7 0x109591000 + 3515815
    10  com.apple.geode                    0x000000010b4c9860 __54-[DGMutableImageBuffer processPixelsInArea:processor:]_block_invoke_0 + 72
    11  com.apple.geode                    0x000000010b4c9d1b -[DGMutableImageBuffer forEachMutableTileInROI:processor:] + 1144
    12  com.apple.geode                    0x000000010b4c980d -[DGMutableImageBuffer processPixelsInArea:processor:] + 139
    13  com.apple.Aperture                 0x00000001098eebe3 0x109591000 + 3529699
    14  com.apple.Aperture                 0x00000001098ef4ff 0x109591000 + 3532031
    15  com.apple.Aperture                 0x00000001098ed012 0x109591000 + 3522578
    16  com.apple.Aperture                 0x0000000109a062c7 0x109591000 + 4674247
    17  com.apple.Aperture                 0x0000000109a06e85 0x109591000 + 4677253
    18  com.apple.Aperture                 0x0000000109a07e83 0x109591000 + 4681347
    19  com.apple.AppKit                   0x00007fff96967a0e -[NSApplication run] + 555
    20  com.apple.prokit                   0x000000010aaa8be1 NSProApplicationMain + 387
    21  com.apple.Aperture                 0x00000001095a14a2 0x109591000 + 66722
    22  com.apple.Aperture                 0x00000001095a0df4 0x109591000 + 65012
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib             0x00007fff964dd7e6 kevent + 10
    1   libdispatch.dylib                  0x00007fff92934786 _dispatch_mgr_invoke + 923
    2   libdispatch.dylib                  0x00007fff92933316 _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13
    Thread 5:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13
    Thread 6:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13
    Thread 7:
    0   libsystem_kernel.dylib             0x00007fff964dcbca __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x00007fff952a72a6 _pthread_cond_wait + 890
    2   com.apple.Foundation               0x00007fff94fb3a5c -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation               0x00007fff94f7d22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proxtcore                0x000000010b77403a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                0x000000010b773282 -[XTThread run:] + 329
    6   com.apple.Foundation               0x00007fff94f8472a -[NSThread main] + 68
    7   com.apple.Foundation               0x00007fff94f846a2 __NSThread__main__ + 1575
    8   libsystem_c.dylib                  0x00007fff952a38bf _pthread_start + 335
    9   libsystem_c.dylib                  0x00007fff952a6b75 thread_start + 13

    Dear Léonie, I'm editing some pictures for work, so I tried them in my original library and then in another one, and It crashed anyway. So, I think that may be is a corrupt file issue in my work photos. Today I worked relatively well, with those photos in a new library, and only failed 3 times (before the faults were thousands!). Every time, before and now, It's crashes when I'm editing, mainly while using brushes. I work with RAW files, so they're very large images, and I have no plug-in installed.
    Dear Frank, as I said to Leonie, I imported my files back into a new library and keeps crashing. I'll try to create a new user and run Aperture. What is the use of that?
    Thank you both!
    PS: I think there might be a corrupt file, because one of the times it crashed the photo I was workig on appeared like this (attached here) when I restarted the program.

  • Premiere Elements 11 crashes while saving a video?

    My Adobe Premiere Elements 11 crashes when I try to save a simple video made up of still images to MPEG format (1080p, 29.97fps, Dolby audio)
    PC:
    Windows 7 Professional x64
    Intel Core i3 2350m
    6GB ram
    500GB HDD
    Intel GMA HD3000

    >video made up of still images
    Photo Scaling for Video http://forums.adobe.com/thread/450798
    -Too Large May = Crash http://forums.adobe.com/thread/879967
    -And another crash report http://forums.adobe.com/thread/973935

  • Runtime error microsoft visual c++ crash while editing

    I get this while editing in audition cs6 in the waveform window.  it happens rarely (twice so far).  see photo attached!    Thank you for your time!

    Unfortunately we are not the application's support team - we are the U2U group. You need to contact Adobe help directly.

  • PS Elements 11 crashing while saving

    Hi everyone,
    I have a problem with PSE 11 : each time I try to save a picture I made, PS crashes or just show me a "broken" window (without background or "save" button).
    When it crashes, it shows me a detailled report (I pasted the very first part of it next to that) but as i'm not very codes friendly, I don't get a line of it.
    Could someone help me please ? (I already restarted my macbook, checked for any update, deleted and re-installed PSE).
    Process:    
    Adobe Photoshop Elements 11 Editor [498]
    Path:       
    /Applications/Adobe Photoshop Elements 11 Editor.app/Contents/MacOS/Adobe Photoshop Elements 11 Editor
    Identifier: 
    com.adobe.pse11editor
    Version:    
    11.0 (11)
    App Item ID:
    571583293
    App External ID: 11641628
    Code Type:  
    X86 (Native)
    Parent Process:  launchd [153]
    Responsible:
    Adobe Photoshop Elements 11 Editor [498]
    User ID:    
    501
    Date/Time:  
    2014-04-24 23:32:31.273 +0200
    OS Version: 
    Mac OS X 10.9.2 (13C1021)
    Report Version:  11
    Anonymous UUID:  D468120D-10B6-A07C-7E6D-D204C85A5F94
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    *** CFRelease() called with NULL ***
    Performing @selector(performAction:) from sender S4WCocoaPushButton 0x11cb4510

    Go to your username>library>preferences and delete:
    com.adobe.PhotoshopElements.plist
    Adobe Photoshop Elements 11 settings
    Adobe Photohop Elements 11 paths
    To see the library,  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 go to the Saved Application States folder and delete any for PSE.
    Repair permissions and try again.

  • Photoshop Elements 8 crashes when "EDIT" opens from Welcome screen

    When Photoshop Elements 8 is launched from the shortcut on the desktop, welcome screen opens and at the bottom it shows "gathering user info....". It keeps doing it as long as I don't click on edit button. When I click on edit button, the edit windows opens with my name and soon it crashes and closes the program. After the program closes, it opens a crash report window which I submitted to Adobe three days ago. I am still awaiting for the response. Sometimes, instead of closing the program, it crashes my computer and a blue screen shows up. In this case, I have to shut down the computer and restart again.
    I thought I can reinstall the proram but this software would not allow me uninstall either. When I click on "remove" button on the program in the control panel, a window pops up with a message " this action is only valid for  products that are currently installed".
    Any help from Adobe technician is highly appreciated. Thanks in advance

    Following could be the possible workarounds :
    1)      On the drive on which you have installed PSE,on my machine it is on C:
             Go to c:\Program Files\Adobe\Photoshop Elements 9\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.
    2)  Try resetting the PSE preferences by
       1. Close Elements.
       2. Launch the Photoshop Elements Welcome Screen and hold down ctrl + alt + shift as you click Edit.
       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.
    3) In case any network printer is attached try to launch without network or printer uninstall.

  • Premiere Elements 9 crashes while trying to import a movie.

    I have recently purchased Premiere Elements 9 and every time I try to import a movie from one of my homemade DVDs it crashes. I looked on Google and other Forums to try to find the answer but no luck. Does anyone have and suggestions?
    Intel Core 2 Quad
    1.5 TB hard drive
    Windows7 64 bit
    4 GB of RAM

    Also, see this ARTICLE from the Tips & Tricks sub-forum, for things to look at with crashes and hangs. It covers the hardware, the OS and the software, and offers links for tuning up the system, and getting it ready for video editing. I know that there is a lot of material in there, but Neale has done a great job of putting things into a checklist, and offering links to other material.
    That rec. is for use along with John T's links, which are a bit more specific to your burned DVD's.
    Good luck,
    Hunt

  • LR CC frequent crashes while editing (OSX 10.10)

    CC is crashing frequently (as often as every 5 minutes or so) while I'm editing in Develop module. Sometimes I simply select the next filmstrip image and BANG down it goes faster than a 2c hooker. Sorry bad analogy but I'm getting pretty frustrated. It happens instantly, just disappears in a flash so no time to note down what I'm doing.
    MacPro 2008 Quad Xeon 2.8GHz 20Gb RAM

    My CC membership is almost 1 yr old. I am the owner of LR 5, so this is an upgrade. Still don't understand the issue. Thanks all for trying to resolve this issue.

  • Premiere Elements 11 crashes while loading ImporterQuickTime.pm

    Hi all!
    I'm facing a problem with Adobe Premiere elements 11.0 whenever I launch it (even launched directly without passing the organizer's launch screen) it stops while loading ImporterQuickTime.pm.
    Here's my PC specifications:
    Windows 7 32bit
    Ram 2GB
    Intel Dueo CPU 2.20GHZ
    SIS Mirage 3 Graphics adapter
    QuickTime version: 7.7.4 (latest)
    Is there a troubleshooting steps or logs where I can find the culprit?
    Thanks for any help.

    Numerdiaweb
    This type of issue does not seem unique to Premiere Elements 11, and I am not certain that this is one answer to a fix.
    The person with this type of issue is usually put through the drill
    http://forums.adobe.com/thread/951360
    which includes
    a. Is latest version of QuickTime installed? If you have the latest version, have you tried uninstalling reinstalling it?
    b. Is your video card driver up to date according to the web site of the manufacturer of the card?
    c. Do you have the latest Windows Updates and was all working before the Windows Updates?
    I ran into this issue with Premiere Elements 11 on Window 7 64 bit. The only thing that worked everytime to get beyond this block for me was to go to the Task Manager/Processes and End Process for a Process named ElementsOrganizerSyncAgent.exe. The irony of it was that this .exe was located in the Premiere Elements 8.0/8.0.1 files on the hard drive. I have since deactivated, uninstalled, reinstalled Premiere Elements 8.0/8.0.1 and the problem has not reappeared.
    With the possibility of undefinited corrupted files, you might want to look at"
    a. Deleting the Adobe Premiere Elements Prefs file or the whole Folder that it exists in Windows 7 64 bit...(you may need to translate these details into 32 bit system...please ask for help if you need that...
    Local Disc C
    Users
    Owner
    AppData
    Adobe
    Premiere Elements
    11.0
    and in the 11.0 Folder is the Adobe Premiere Elements Prefs file that you delete. As I mentioned, if just the Prefs files has no impact, then try deleting that 11.0 Folder that it exists in.
    Remember to have Folder Options Show Hidden Files, Folders, and Drives on so that you can see the path involved.
    That 2 GB installed RAM caught my attention, but I would think that you would be able to get beyond that QuickTime message even at that. But do look into increasing that 2 GB RAM to at least 4 GB (which is the maximum supported for 32 bit system).
    Let us start here and see if any of the above leads to the solution.
    Thanks.
    ATR
    Add On...I was unaware of SG's post in your thread until after I had posted mine.

  • Adobe Pro X crashes while editing the forms

    Hi, I've been using Acrobat X Pro to edit forms for weeks now with no problems.
    Yesterday it has started crashing as soon as I entering Form Edit mode. I reinstalled it and it did not help.
    I am running it on Windows 7 home edition (64 bit).
    Please help.

    Still having the problem.
    I open any PDF in Adobe X, and go to Form -> Edit. It sais that Document cannot be edited and suggests to Save a Copy.
    Ok, I save a copy.
    Now, I open up a COPY that I have just saved and go to Forms-> Edit.
    Fields are being highlighted, but when I click on any field Adobe just crashes.
    Also I have another problem - some of the fields on the document become uneditable. I do not understand why I was able to change  them before and cannot change them now. This is very frustrated.
    I am on Win 7, 64 bit. I have Adobe X and Reader X installed on this PC.
    Please Help.

  • Premiere Pro CS5 crashes while editing 4.5K-RED-Material

    Hi there,
    I'm editing 4.5K-material with Premiere Pro CS5. After a couple of minutes (mostly after watching sequences longer then 10 seconds) the program crashes. Windows 7 tells me that "ImporterREDServer.exe" doesn't work anymore and then Premiere freezes. I doubt that it is a performance problem, because with CS4 and regular 4K-RED-material I haven't had any problems on the same PC. I deinstalled CS5 several times (with Cleanupscript and everything) and re-installed it, but the problem remained the same.
    I would really appreciate some help or any idea what the problem could be. Thanks in advance!
    Daniel
    My system:
    i7 860 @ 2.8 GHz
    8 GB RAM
    Windows 7

    Well, well. After many tests with other platforms we came to the conclusion that it was not Premiere Pro that caused problems but the material itself. This is some kind of a worst case scenerio. In the process of copying the data onto hdds some frames within the data got damaged and causes Premiere to crash. Since the data on both discs is corrupt differently we now try to rebuild as many files as possible. Yet there will be clips that can't be saved. Anyhow. There will be a film and that's the most important thing.
    Thanks again for your help everybody
    Daniel

  • Premiere Elements 10 Freezing while editing

    I apologize in advance if this has been brought up before, but I have searched for a solution with no results. Since installing Premiere Elements 10 this week, i have expirenced many freezes with the program that has forced me to exit out of the program. most common occurance is when adding a new clip to time line. after adding, the program stops responding, even if left alone for over an hour. freezing occationally happens when loading projects as well. Does anyone know of a solution to this problem? I have a project due and I really need Premiere to work so any help would be a major help. I have uninstalled and reinstalled today, and I have the latest version of quicktime.

    Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
    What is a CODEC... a Primer http://forums.adobe.com/thread/546811
    What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
    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
    For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
    For Mac http://mediainspector.massanti.com/
    http://blogs.adobe.com/premiereprotraining/2011/02/red-yellow-and-green-render-bars.html
    If you have a red line over the timeline after importing a video and before adding any effects... your project is wrong for your video... read above about codecs
    Once you know exactly what it is you are editing, report back with that information... and your project setting, and if there is a red line above the video in the timeline, which indicates a mismatch between video and project
    H.264 will NOT work inside an AVI wrapper http://forums.adobe.com/thread/854115
    More information needed for someone to help... click these links and provided the requested information
    -http://forums.adobe.com/message/4200840
    -http://forums.adobe.com/thread/416679

Maybe you are looking for