Premiere elements 8 causes my system to crash, suggestions?

premiere elements 8 causes my system to crash, suggestions?

Version 8 was a bit unstable upon release anyway. Have you downloaded the patch for it?
Meantime, can you please give us more information? Can you be more specific about the crash? Does it literally cause your computer to shut down and reboot?
At what point does it crash? As soon as you start it, or after you've added media to it? If the latter, what model of camdorder is this video coming from and what format and resolution is it?
What operating system are you using? Have you manually gone to Windows Update and installed the non-critical or optional updates that do not install automatically?
How fast is your processor, how much RAM do you have and how much free, clean, freshly defragmented space is on your hard drive(s)? Remember that even brand new computers are a mess of junk files and defragmentation.

Similar Messages

  • Premiere Elements 8 keeps closing or crashing

    Hello,
    I was really looking forward to the new Premiere Elements 8, downloaded the trial and....it keeps closing with no error when I am editing very simple videos.  The other thing it does is it will crash sometimes and come up with the Adobe Send Error dialog box.  I have checked other posts and looked at some things like making sure I have the latest Quicktime and I did download the latest Nvidia driver as well.  Thought that it fixed it but nope, had another unexplained crash/closing last night.  I am running Windows 7 RC but dont know if that is the problem.
    Any help would be very much appreciated.
    Oh, and my system is a quadcore and 8 gb of ram, so it should have enough power.
    Doug

    These are their forums and should have moderators monitoring these threads. They are the ones that should bring it up to their development team or someone that can look into it, or get someone from Adobe to come read this thread and give their input on it.
    Here we agree, though not on the exact details. The MOD's on these fora are volunteers. They are mostly power users, who have businesses and lives far beyond the Adobe fora. They give freely of their time, both answering questions and helping to keep the fora running perfectly. None is an employee and none gets any compensation, other than added responsibility and a Moderator's Console to correct things on the fora.
    Other than that point, we are in sync. Especially with a new release of PrE, I feel that there should be an Adobe presence here. Someone from development should be assigned to furnish info on working with the new program, sort out problems and offer suggestions on how to run it to the max. The PrPro forum is very fortunate in that an Adobe employee has showed up and is now a major contributor. I do not know if the forum is part of his "assignment," or if he has just decided to spend time on the forum, contributing. To date, he has furnished tons of great info on upcoming updates and even on CS5, which is still under development. I hope he gets some extra compensation for his efforts and also full support from Adobe.
    The Photoshop has Chris Cox, one of the original developers of the program. I do not know if Chris is there out of love for the program, or as part of his work at Adobe. It's really moot, as his contributions are wonderful, whether he does it out of altruism, or because it's part of his job - the result is the same - a benefit for all forum subscribers.
    One of the big pluses to having someone from the development team would be that we do not spend countless hours of trying to troubleshoot problems, when some simple tweak, fix or change would take care of it. As we are but lowly users, we have to rely on what we have experienced, read, or encountered elsewhere. None of us really knows what is "under the hood." Even Steve G., our MOD, is on the development team. Now, he probably does get his hands on the beta of every version, as soon as possible, but other than maybe some tips from Adobe, he doesn't have access to the code. His knowledge is built on his experience and a sharp mind to figure out how the thing works. Same for AT Romero. While he gets his copies, as do the rest, he has torn into PrE 8 with a critical and analytical eye and published his observations, built on years of experience with PrE and with NLE work in general. Both are invaluable assets, but with a simple Adobe presence, both could be greatly aided. Going back up to Chris Cox and the PS forum: I've been a power-user of PS from the instant that it hit the PC about 20 years ago. I've done most of what PS can do at one time or another. Still, there are times that I speculate on something in that program, only to have Chris come forward and correct me, explaining exactly what the code does and how it does it. I never fail to learn something new about a program that I have used extensively for about two decades - a little Adobe inside info goes a very long way.
    I would also strongly urge Adobe to assign a rep. to this forum, especially now. I would hope that this person is on the development team and not from marketing or elsewhere. I would also hope that this person has actually used the new version in real-world situations, as there are often major differences between the lab and the Projects that people actually produce.
    I realize that there is a major price-point difference between PrE and PS, PrPro, AfterEffects, etc., but the install-base, or potential install-base is much greater for PrE. For Adobe, the unit profit is potentially smaller, but the volume is much, much greater.
    I support your contention that Adobe needs to be here. If they show up, I would strongly urge the forum to be respectful of their time, as they are probably doing this out of the goodness of their heart - though Adobe COULD add a little something to their paycheck. If someone does show up, I'd hope that the subscribers would ask only technical questions and keep any personal feelings about Adobe products to themselves. There should also be respect for the material that this representative could not share for various reasons.
    Going back some years, we were blessed by the presence of an Adobe employee, Wil Renczes, in the PrPro forum. Some people spent a great deal of time yelling at Wil for things that Adobe had done, or not done. Hours of typing went into telling him how much better Avid, or FCP were, compared to Adobe. They demanded to know what the next version would hold. One day, Wil didn't come around anymore. The forum had lost a most valuable asset. My guess was that it just ceased to be fun for Wil anymore and he chucked the whole idea. I hope that the same does not happen with our Adobe representative, Dennis, this time around.
    Just some observations,
    Hunt

  • Premiere elements 12 organizer keep on crashing

    Why does the elements 12 organizer keep on crashing during the import of mts files? Does anybody have the same problem?
    Adobe does not really seem to be interested in helping, since they outsource everything to forums!!

    From the Premiere Elements Information FAQ http://forums.adobe.com/thread/1042180
    •What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
    •Have you installed any recent program or OS updates? (If not, you should. They fix a lot of problems.)
    •What kind(s) of image file(s)? When talking about camera raw files, include the model of camera.
    •If you are getting error message(s), what is the full text of the error message(s)?
    •What were you doing when the problem occurred?
    •What other software are you running?
    •Tell us about your computer hardware. How much RAM is installed?  How much free space is on your system (C:) drive?
    •Has this ever worked before?  If so, do you recall any changes you made to Premiere Elements, such as adding Plug-ins, brushes, etc.?  Did you make any changes to your system, such as updating hardware, printers or drivers; or installing/uninstalling any programs?
    And some other questions...
    •What are you editing, and does your video have a red line over it BEFORE you do any work?
    •Have you viewed the tutorial links at http://forums.adobe.com/thread/1275830 page?
    •Which version of Quicktime do you have installed?
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    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
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Premiere Elements cause problems with Windows Media Center while streaming to TV.

    I was having the following problem:
    The audio from the streaming process of a recorded TV show on my HP computer to the remote receivers, a Sony Blu-ray player and/or a Sony Streaming Player, results in the loss of audio signal at exactly 30 seconds from the beginning on either devices. The video continues on as normal.
    A user on the Windows 7 forum had the following possible cause and solution.  His response was as follows:
    I "solved" my issue, at least partially. Turns out for me a codec installed by Adobe Premiere Elements for audio (Main Concept) was causing mfpmp.exe to fail (you should see it getting an appcrash in the event log two or three times as soon as you start playing the media remotely.) This program is used by microsoft for DRM. I went through and one by one remained the various attached (non-microsoft) modules until i found the one that caused the appcrash. I haven't fully figured out if Elements is now negatively effected, but that's for a different forum.
    I tried the quick fix by un-installing Adobe Premiere Elements.  The uninstall solved my problem with Windows Media Center, but I want to re-install the software but I do not want to recreate the problem with Windows Media Center.
    Is there another solution for this problem?

    I reinstalled Adobe Premiere Elements 10 and the above mention problem reoccured.  With a little detective work I was able to determine that the file causing my problem was "mc_dec_dd_ds.ax".  I am not sure what this does to Adobe Premiere Elements 10 since I removed (renamed) the offending file.  A strange side affect, renaming the file did cause an increase volume. Strange.  

  • Problems exporting HD video from Premiere Elements 9 for Vimeo (program crashes or video is blurry)

    I have a 10 minute wedding video I am trying to export from Adobe Premiere Elements 9 to upload to vimeo. I followed the directions from this video: Exporting for upload to Vimeo with Adobe Premiere Elements on Vimeo to figure how to accomplish this. The first time I followed the directions, the resulting video file was fuzzy and blurry, not at all like the HD video I could view in the program before export. Since then, I've tried exporting it multiple times with different settings, and each time the program crashes when the video is around 95% complete. How can I rectify this situation? This is a wedding video I made for a paying customer who would like their video on vimeo as soon as possible.
    Thanks for your help!
    Let me know if you need more details or clarifications.
    Laura

    Laura
    What are the properties of what you are putting on the Premiere Elements 9.0/9.0.1 Timeline? Are you working with a SD or HD file?
    What have you set as the project preset when you started the projec?
    1. So, video compression, audio compression, frame size, frame rate, interlaced or progressive, file extension, pixel aspect ratio...as
    much information as you can supply....sometimes the brand, model, settings of the camera recording the video will give us all the
    information that you need to set up the project correctly or to verify that it has been set up correctly.
    Case Study....
    Let us assume that your video is 1920 x 1080 @ 29.97 progressive frames per second.
    Project Preset in New Project Dialog
    NTSC
    DSLR
    1080p
    DSLR 1080p30@ 29.97
    When you go to take your Timeline content to Vimeo from within the Premiere Elements 9.0/9.0.1 feature
    Share/Online, you will discover that there is no Vimeo choice in that version.
    So, what you are going to do is to export your Timeline to a file (AVCHD.mp4) saved to your computer hard drive and then upload that file
    to Vimeo at the Vimeo website.
    Share
    Computer
    AVCHD
    with Presets = MP4 H.264 1920 x 1080p30
    Have you been there and done that?
    Summary...
    The answers are in the details....needed
    a. properties of source media
    b. project preset
    c. details of your project's Timeline content
    c. export settings used
    We will be watching for your follow up.
    Thank you.
    ATR

  • Dose Premiere Element process AVCHD system

    I am trying to by Premiere Element 13 but I have Canon video camera that supports AVCHD system, long time a go Adobe did not support that system that is why I went to Coral, Pinnacle they did. I wonder if Adobe finely does have that.
    Any one know?
    Thank you
    Ameen Kay

    From the help file for Premiere Elements:
    Supported file formats
    You might get better answers from the dedicated Premiere Elements forum:
    http://helpx.adobe.com/photoshop-elements/kb/supported-file-formats-premiere-elements.html

  • Premiere Elements 7: WMSDKACodec.vca and Crash

    Premiere Elements 7
    I've just finished to edit a 25 mins video and want to make a DVD (Standard Definition PAL Widescreen).
    The program crashes immediately when (in the SHARE section) I click on the DVD/BlueRay button.
    The crash refers to the program exe file and the WMSDKACodec.vca.
    The same crash occurs when trying to make a MPEG file for computer use same settings: Standard Definition PAL Widescreen
    Does anyone encountered the same problem?

    OK. I solved the problem:
    I just removed the WMSDKACodec.vca file from the Premiere Elements 7/MediaIO/Codecs folder (compressed in a zip file) and the crashes disappeared.
    Now it works fine.
    I made a test DVD and one MPG file from my project. They both look good and the sound is clear.

  • Premiere Elements 9 Low System Memory

    There seems to be a lot of threads on this subject, but no conclusive answers.
    I'm getting a "running low on system memory, proceed with caution" error, then it usually hangs (sometimes I can save (or save as which works better)).
    System Info: Dell Studio XPS w/ i7-920 64bit, 6GB memory, 450GB HD w/ 236GB free, ATI Radeon HD3650 w/ 256MB, Windows 7 (64bit), latest drivers.
    Virtual memory- custom @ 5000MB min and 15000MB max.
    I just installed version 9 after using version 7 w/o problems for several years. Right now, I'm only trying to make a slideshow using jpegs that were massaged using photoshop elements 7 (4.5 x 6 300dpi). File size is generallyaround 2MB but some go as high as 4.
    I have shut down everything I can in startup and running files (used enditall2). No additional programs that I can see are open. PE9 just seems to suck up memory until I run out, then I get the error. I have rendered the pictures after every 4 additions (PITA!).
    When I first got the message, I un-installed PE7 and PS7, then uninstalled PE9 and PS9. I then re-installed PE/PS9. No help there. I initially had the files on a portable usb HD, but moved everything to the main (C:\) drive in my video folder.  I'm using the PE9 project settings: NTSC-DV-Standard 48KHz.
    Appreciate any help I can get on this. I've already wasted way to much time on this.

    First, do both a Save_As (increment your Project's name), then do a Save_As_a_Copy. I would Copy that copy to the external, for safe keeping.
    Win7 has a better Windows Indexing system, than prior versions, so I do not know how much difference that will make. The 8GB RAM can likely be easily, and inexpensively bumped up to 16GB (make sure to match any RAM 100%). I would also take a look at this article: http://forums.adobe.com/message/2910195#2910195 and look into removing any unnecessary running programs, while you edit.
    Take a look at your Windows Virtual Memory Page File, and see how it's managed, plus the size (if dynamically managed, then Min and Max). Allocating more HDD space to the Page File, if you have the HDD space. For a video-editing rig, I like to statically manage my Page File, and set it up, when I first install the OS, before the HDD's get filled to any level. Again, Win7 is better with the Page File, and with a 64-bit OS, if one has the installed RAM, then the Page File will see less use, than with 32-bit OS's.
    Good luck,
    Hunt

  • Flash Causes Entire System to Crash

    I installed Arch for the third time about a month ago, the longest I've stuck with this distro. I think Arch is here to stay. The first two times I tried Arch, I went running back to Ubuntu or Fedora. However, thats not to say that I don't have some bugs to still work out.
    I'm running kernel26-lts if it matters, and I believe I'm running 32 bit flash rather than the 64 bit driver. I'm almost certain, but I'm unsure of how to double check the version of flash I'm running. After upgrading flash a week or so ago, flash video has been causing intermittent crashes. Is there a known issue with the new version of flash? Should I roll back to the previous version of flash, or perhaps try the 64 bit version?

    So I installed catalyst and removed xf86-video-ati. Flash seems to work MUCH  better, haven't had a crash yet today and I've been testing it with long videos and fullscreen. I'm fairly certain that I'm running flgrx and not the fallback video drivers (mesa or something?). How should I confirm this?
    Also, the following warnings appear now in my Xorg log. Is this anything to be concerned about?
    grep -E '\((WW|EE)' /var/log/Xorg.0.log
    [ 15.976] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 16.071] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 16.463] (WW) Falling back to old probe method for fglrx
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    [ 16.527] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    [ 16.634] (WW) fglrx(0): board is an unknown third party board, chipset is supported
    [ 17.134] (WW) fglrx(0): Option "VendorName" is not used
    [ 17.134] (WW) fglrx(0): Option "ModelName" is not used
    Thanks for your help

  • What is causing my system to crash all the time.

    This is the report that is being sent to Apple. What happens to these reports anyway?
    Interval Since Last Panic Report:  -2 sec 
    Panics Since Last Report:          2
    Anonymous UUID:                    8F4198A3-5E01-A05F-25F1-2B21B4C12007
    Sat Sep 14 19:17:39 2013
    panic(cpu 1 caller 0xffffff7f9d51ff1a): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff810c1ef000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
    Backtrace (CPU 1), Frame : Return Address
    0xffffff810c15ac50 : 0xffffff801b21d626
    0xffffff810c15acc0 : 0xffffff7f9d51ff1a
    0xffffff810c15ad90 : 0xffffff7f9ba19f1e
    0xffffff810c15ae50 : 0xffffff7f9baee12d
    0xffffff810c15ae90 : 0xffffff7f9baee18e
    0xffffff810c15af00 : 0xffffff7f9bdb4ed0
    0xffffff810c15b030 : 0xffffff7f9bb16a75
    0xffffff810c15b050 : 0xffffff7f9ba20d50
    0xffffff810c15b100 : 0xffffff7f9ba1e7d0
    0xffffff810c15b300 : 0xffffff7f9ba2010a
    0xffffff810c15b3d0 : 0xffffff7f9ca683a5
    0xffffff810c15b550 : 0xffffff7f9ca652d0
    0xffffff810c15b5d0 : 0xffffff7f9ca661d4
    0xffffff810c15b660 : 0xffffff7f9ca667b3
    0xffffff810c15b7a0 : 0xffffff7f9ca67332
    0xffffff810c15b8e0 : 0xffffff7f9ca9a18e
    0xffffff810c15b920 : 0xffffff7f9ca9af2b
    0xffffff810c15b940 : 0xffffff7f9ca94c69
    0xffffff810c15bab0 : 0xffffff7f9ca9553d
    0xffffff810c15baf0 : 0xffffff7f9ca90df6
    0xffffff810c15bb20 : 0xffffff7f9ca8ae95
    0xffffff810c15bb50 : 0xffffff7f9ca73014
    0xffffff810c15bba0 : 0xffffff801b667853
    0xffffff810c15bbc0 : 0xffffff801b66842d
    0xffffff810c15bc20 : 0xffffff801b665e2f
    0xffffff810c15bd70 : 0xffffff801b298c01
    0xffffff810c15be80 : 0xffffff801b220b3d
    0xffffff810c15beb0 : 0xffffff801b210448
    0xffffff810c15bf00 : 0xffffff801b21961b
    0xffffff810c15bf70 : 0xffffff801b2a6536
    0xffffff810c15bfb0 : 0xffffff801b2ce9e3
          Kernel Extensions in backtrace:
             com.apple.driver.AppleMuxControl(3.4.5)[49FEF732-D7A3-327B-A7AA-6AC5A6E3DCFF]@0 xffffff7f9d512000->0xffffff7f9d524fff
                dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[1D0BB11E-7D71-34CF-ACC3-57DF01CADA 08]@0xffffff7f9d50d000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9b81f000
                dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7f9d4f9000
                dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f9b7e8000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9b9a4000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9b961000
             com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9b9 b8000->0xffffff7f9bc5dfff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9b81f000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9b9a4000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9b961000
             com.apple.nvidia.nv50hal(8.1.2)[988EAF3A-3318-3787-8A5A-844830FA1522]@0xffffff7 f9bc69000->0xffffff7f9bf3dfff
                dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9b9 b8000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9b81f000
             com.apple.GeForce(8.1.2)[7EC545A4-4B57-32F1-8DC3-C31023AFBDCB]@0xffffff7f9ca360 00->0xffffff7f9cb03fff
                dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9b9 b8000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9b9a4000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9b81f000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9b961000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    12E55
    Kernel version:
    Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
    Kernel slide:     0x000000001b000000
    Kernel text base: 0xffffff801b200000
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 112411795281
    last loaded kext at 9268717434: com.apple.driver.AppleHWSensor     1.9.5d0 (addr 0xffffff7f9d2db000, size 36864)
    loaded kexts:
    com.rim.driver.BlackBerryUSBDriverInt     0.0.74
    com.apple.driver.AppleHWSensor     1.9.5d0
    com.apple.driver.AudioAUUC     1.60
    com.apple.iokit.IOBluetoothSerialManager     4.1.4f2
    com.apple.filesystems.autofs     3.0
    com.apple.driver.AppleTyMCEDriver     1.0.2d2
    com.apple.driver.AGPM     100.12.87
    com.apple.driver.AppleHDAHardwareConfigDriver     2.3.7fc4
    com.apple.driver.AppleHDA     2.3.7fc4
    com.apple.driver.AppleMikeyHIDDriver     122
    com.apple.driver.AppleMikeyDriver     2.3.7fc4
    com.apple.GeForce     8.1.2
    com.apple.iokit.IOBluetoothUSBDFU     4.1.4f2
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport     4.1.4f2
    com.apple.driver.ACPI_SMC_PlatformPlugin     1.0.0
    com.apple.driver.AppleIntelHDGraphics     8.1.2
    com.apple.driver.AppleIntelHDGraphicsFB     8.1.2
    com.apple.driver.AppleSMCPDRC     1.0.0
    com.apple.driver.AppleSMCLMU     2.0.3d0
    com.apple.iokit.IOUserEthernet     1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X     7.0.0
    com.apple.driver.AppleUpstreamUserClient     3.5.10
    com.apple.nvidia.NVDAStartup     8.1.2
    com.apple.driver.AppleMuxControl     3.4.5
    com.apple.driver.AppleBacklight     170.2.5
    com.apple.driver.AppleMCCSControl     1.1.11
    com.apple.driver.ApplePolicyControl     3.4.5
    com.apple.driver.AppleLPC     1.6.0
    com.apple.driver.SMCMotionSensor     3.0.3d1
    com.apple.driver.AppleUSBTCButtons     237.1
    com.apple.driver.AppleUSBCardReader     3.1.7
    com.apple.driver.AppleUSBTCKeyEventDriver     237.1
    com.apple.driver.AppleUSBTCKeyboard     237.1
    com.apple.driver.AppleIRController     320.15
    com.apple.driver.AppleFileSystemDriver     3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
    com.apple.BootCache     34
    com.apple.iokit.SCSITaskUserClient     3.5.5
    com.apple.driver.XsanFilter     404
    com.apple.iokit.IOAHCIBlockStorage     2.3.1
    com.apple.driver.AirPort.Brcm4331     615.20.17
    com.apple.driver.AppleAHCIPort     2.5.2
    com.apple.driver.AppleFWOHCI     4.9.6
    com.apple.driver.AppleUSBHub     5.5.5
    com.apple.iokit.AppleBCM5701Ethernet     3.6.1b4
    com.apple.driver.AppleUSBUHCI     5.2.5
    com.apple.driver.AppleUSBEHCI     5.5.0
    com.apple.driver.AppleSmartBatteryManager     161.0.0
    com.apple.driver.AppleEFINVRAM     1.7
    com.apple.driver.AppleACPIButtons     1.7
    com.apple.driver.AppleRTC     1.5
    com.apple.driver.AppleHPET     1.8
    com.apple.driver.AppleSMBIOS     1.9
    com.apple.driver.AppleACPIEC     1.7
    com.apple.driver.AppleAPIC     1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient     196.0.0
    com.apple.nke.applicationfirewall     4.0.39
    com.apple.security.quarantine     2.1
    com.apple.driver.AppleIntelCPUPowerManagement     196.0.0
    com.apple.iokit.IOSerialFamily     10.0.6
    com.apple.kext.triggers     1.0
    com.apple.driver.DspFuncLib     2.3.7fc4
    com.apple.iokit.IOAudioFamily     1.8.9fc11
    com.apple.kext.OSvKernDSPLib     1.6
    com.apple.nvidia.nv50hal     8.1.2
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport     4.1.4f2
    com.apple.driver.AppleHDAController     2.3.7fc4
    com.apple.iokit.IOHDAFamily     2.3.7fc4
    com.apple.driver.IOPlatformPluginLegacy     1.0.0
    com.apple.driver.AppleSMBusPCI     1.0.11d0
    com.apple.iokit.IOFireWireIP     2.2.5
    com.apple.iokit.IOSurface     86.0.4
    com.apple.iokit.IOBluetoothFamily     4.1.4f2
    com.apple.NVDAResman     8.1.2
    com.apple.driver.AppleBacklightExpert     1.0.4
    com.apple.driver.AppleSMBusController     1.0.11d0
    com.apple.driver.AppleGraphicsControl     3.4.5
    com.apple.iokit.IONDRVSupport     2.3.7
    com.apple.iokit.IOGraphicsFamily     2.3.7
    com.apple.driver.IOPlatformPluginFamily     5.3.0d51
    com.apple.driver.AppleSMC     3.1.4d2
    com.apple.driver.AppleUSBMultitouch     237.3
    com.apple.iokit.IOUSBHIDDriver     5.2.5
    com.apple.driver.AppleUSBMergeNub     5.5.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice     3.5.5
    com.apple.iokit.IOBDStorageFamily     1.7
    com.apple.iokit.IODVDStorageFamily     1.7.1
    com.apple.iokit.IOCDStorageFamily     1.7.1
    com.apple.iokit.IOAHCISerialATAPI     2.5.1
    com.apple.iokit.IO80211Family     530.4
    com.apple.iokit.IOAHCIFamily     2.3.1
    com.apple.iokit.IOFireWireFamily     4.5.5
    com.apple.iokit.IOUSBUserClient     5.5.5
    com.apple.iokit.IOEthernetAVBController     1.0.2b1
    com.apple.iokit.IONetworkingFamily     3.0
    com.apple.driver.AppleEFIRuntime     1.7
    com.apple.iokit.IOHIDFamily     1.8.1
    com.apple.iokit.IOSMBusFamily     1.1
    com.apple.security.sandbox     220.3
    com.apple.kext.AppleMatch     1.0.0d1
    com.apple.security.TMSafetyNet     7
    com.apple.driver.DiskImages     345
    com.apple.driver.AppleKeyStore     28.21
    com.apple.iokit.IOUSBMassStorageClass     3.5.1
    com.apple.driver.AppleUSBComposite     5.2.5
    com.apple.iokit.IOSCSIBlockCommandsDevice     3.5.5
    com.apple.iokit.IOStorageFamily     1.8
    com.apple.iokit.IOSCSIArchitectureModelFamily     3.5.5
    com.apple.iokit.IOUSBFamily     5.6.0
    com.apple.driver.AppleACPIPlatform     1.7
    com.apple.iokit.IOPCIFamily     2.7.3
    com.apple.iokit.IOACPIFamily     1.4
    com.apple.kec.corecrypto     1.0
    Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.8 GHz, 8 GB, SMC 1.58f17
    Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
    Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334348302D4346382020
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334348302D4346382020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.17)
    Bluetooth: Version 4.1.4f2 12041, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: APPLE SSD TS512B, 500.28 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 5
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 7
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 4
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0xfa120000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2
    USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 4
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

    One more thing....  it makes weird sounds as well... very high pitch sounds that you hear in movies where UFO flying by while it is doing the rebooting...

  • Adobe Premiere Elements 0.9 project crash, HELP!

    This is the first time I am using these forums, so I hope I posted this in the right sektions.
    I need help and solutions for a Project which constantly crashes on my Adobe Premiere Elements 0.9. This program has been awesome and helped me create some projects and videos successfully, up until.... well for about 3 days ago when my latest project crashed when I had just antered and checking the storyboard etc, triggering a "Serious Error" message and then it shuts down. I try again and again, but everytime I try to put something (any sound or video etc) on the storyboard and start working etc the same damn "Serious Error" message and then allways shuts down. It's allways this same and only project (which has worked fine before) that crashes like this...
    In an attempt to first solve the problem myself I went through the Premiere Elements 9 files and deleted finnished projects and automatic saved process on projects etc, but still won't work even better... The funny thing is that when I open another project (a finnished project I left saved just in case) and go through the storyboard there and messes around a little and such, it won't crash nor trigger the same message as my latest project. And that program even has some effects on every footageclip on it too, but still it works fine. Haven't touched the program or the program until and since yesterday night to give it some rest but it still won't work, the project just keeps crashing like when and since it first started a few days ago.
    I have also read through and tried some things from this Help/Troubleshoot page:
    http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
    I have so far been doing 1 and 2 of the "Beginning Troubleshooting", otherwise I have been reading it all and such. I am also kinda afraid to do the 3 of the first quests because I worked so hard on this project and even tough it just keeps crushing, I'm afraid to lose it. Other, I have deleted audios and such from my filegallery on my Adobe Premiere Eements, stuff I don't need anymore because its projects are already done. After I did that I also tried to create a new project just for testing. The amazing this about this is that this the new created project I created works just fine, I could do all kinds of the stuff, effects and advanced editing which I did on the same project before it started crushing. Tough I didn't save that test-project since I didn't find a reason to since it worked so good. And so the thing is that I can start and create a new project and start working and do usual stuff on it with no problem, same when I open up another project and do stuff, it all works just fine! It is just this one and only project that keeps crushing with this "Serious Error" message, all the time... Does anybody else have, or has had the same problem? What could the problem and error be and how to fix it?
    This crushing project do has some effects on every footageclip/videoclip on it, to set the right mood for the musicvideo I'm making. I am making a musicvideo, and I haven't even done the half of the project/video. The song I am making this musicvideo with is about 00:07:32 in length, and (tough this detail may have no influence or meaning) the music is Symphonic Metal. The actual file of the song is 6,96 MB in size. This is also not the first time I've done such projects with such long songs on this same program either, one of my last videos I managed to successfully make and create a musicvideo with a song which was about 13 minutes and 30 seconds in length, and I also used effects on pretty much every videoclip on that project too.
    The current filesize so far on the actual project.prel-file of my project that keeps crushing is 9.73 MB.
    I am also using Adobe Premiere Elements and doing this troubleing, crashing project on a PC, a Fujitsu Windows (I believe Windows 7, or even updated to a newer version?). It has a regular ATI-card. The computer also has 2 modems and there's still some pretty GB amount free on them. The PC's main system also has a RAM in 6.00 GB and the operative system is the 64-bites.
    In short, the PC should just fine be able to handle Adobe Premiere Elements 0.9 and all its projects, just as it has handled it all before plus all my PC games at that. So it must be something with my Adobe Premiere Elements and that specific project which is the problem, but what is the problem and the serious error and how to fix it?
    Could it help to save and create the actual video in this crashing project, delete that project then start a new project, upload and put in the videofile of the crashing project in that new project and then continue from there?
    In either cases, I need help with this. Please, help!

    Thanks so much for your reply, Steve!
    Even tough I trust you guys enough here on the official Adobe site/forums to answer those questions as best I can, I am at the same time not very fond of giving away too much information because of safety. I understand I have to If I'm to recieve the accurate answers and solution, but as this is the internet you can never know. But again, I trust you guys enough on here and thus I'll try to answer those questions as best I can, even tough I am not very good with such stuff about computers. The PC I am using is also not only mine, it is the family computer also which me and my whole family uses.
    The operating system on my computer (according to the computer propotions etc) is a 64-bites operating system and the computer/PC is also a Windows 7 Home Premium.
    The processor the computer/PC have is a Intel(R) Core(TM) i5 CPU and the RAM is 6.00 GB. However, (and I hope I make this understandable because the computer/PC is in swedish)the subscore of RAM in the computer's Performance-Classification/Ranking is 7,5. The processor subscore is 7,3 per second. And the free space? Well, we have two modems, let's say a modem A and a modem B. Adobe Premiere Elements 0.9 is set to save all its stuff etc on modem B, while modem A is the main modem and spaces all main stuff and other things of the computer/PC. Modem A has about 314 GB of free space, while modem B has 207 GB of free space. Modem A's capacity is a total of 489 GB in which 175 GB has been used, the modems filesystem is a NTFS. Modem B is also a NTFS filesystem and its capacity is a total of 439 GB in which 232 GB has been used. And the Disk Cleanup? I believe my that latest ran it for about a few weeks ago. We also have a CCleaner also. But about the Disk Defragmenter, I have no idea. What exactly does a Disk Defragmenter do?
    You mean, entering my project that keeps crushing and simply rename it by using "Save As"? If that is what you mean, I dunnow If that actually worked. When I still tried to do stuff and edit the crashing project (tough as said, it hardly took any changes and process before it triggered that message) and then crashed and shut down, and I opened up the program again (trying to open the same project that way), it asked me If I wanted to re-create the missing process from the last crash of the same project. I tried it and it automaticly was renamed to a for example Project.copy. But when I tried to work with that it was to no futher success, the project kept crashing. I haven't renamed the project by "Save As" tough, but I doubt it'll work, I even tried to rename the actual project file in the Adobe Premiere Elements files but nope... the project keeps crashing. But also about the same question, "Save As" under a new name but in its own folder? You mean the actual project folder or Adobe Premiere Elements preview folder of the projects?
    My camcorder is pretty old by now, have had it since I turned 15, it has worked pretty good since then. Its model is a Sony Handycam, Carl Zeiss Vario-Tessar OPTICAL 20x. Even tough the last thing maybe doesn't say anything, this is all I know about my camcorder, except that it is a model no. DCR-HC17E PAL. But in that Project  which keeps crashing, there are only a few actual camcorder clips used as I am making a Game-MusicVideo and most of the footage of the Video-game (actually a PC game) I'm making a musicvideo of is downloaded from Youtube mostly from a guy I asked permission for to download his recorded footage of the game. I used a Youtube downloader called ClipConverter. As I don't have a SD card I cannot make this footage myself. But some footage I recorded on my camcorder, but If I can find high quality clips and get them, I will. The other footages is actual official trailers of the PC games which also was downloaded from the net. But I can give you the stuffs filetypes and hoping that may help. The downloaded footage which was downloaded by this ClipConverter, are MP4 files. The other stuff (which were official trailers) and most of them are also MP4 files, the others are QuickTime-film files. Many of these downloaded footages and trailers are also in HD quality, at least some of them I think.
    The actual filetype ofthe footage I myself recorded with my camcorder are, well.... it says Videoclip in the file. Maybe it is AVI?
    The project settings? You mean the settings you set at first when starting as a new project? The general settings are, in editingsettings it is AVCHD 270p square pixel. This is kinda hard for me to tell since everything is in swedish in my program. But these settings has worked perfectly before, same with all files, footages and videoclips I have been using, also all the soundfiles etc. Even the actual crashing project worked perfectly before it started crashing... So why does it so suddenly start crashing now?
    The audio is a song I copied directly from its album and CD into the computer/PC and it seems to be in WMA format in filetype.
    And lastly, no I haven't rendered the timeline of the project ever, not even on my other projects. What does the rendering do and is useful for? I have very little knowledge of it. Other, I keep the Timeline mode open all the time because I can edit my videos much better with it, but perhaps that editing method make little influence of the actual problem.
    Other, yesterday when writing the post and topic, I forgot to mention that I restarded my computer right after I created a new project, that testing project. When finnished with the testing I restarted the computer. Since then I haven't touched the crashing project since now tonight, when checking its settings for this post. I am also right now trying to create and save the actual videofile of it, saving it on my computer. I'll soon see If it's successful without any crashing interruptions, plus that the video itself works and is smooth when I'll play it on Windows Media Player like all the rest of my other videos. I do this just in case I must create a new project to be able to continue with my musicvideo, as the first part of it I worked very hard on.
    Other and again, I am still puzzled about why this is even happening, that this project which worked perfectly fine before, just suddenly starts triggering that "Serious Error" message and crashes. And in this program which worked so perfect before. Has this happened to anyone else before? Has anyone else experienced the same issue I have? Is this a knowledgable issue which has solutions and ways to fix it?... :/

  • Adobe Premiere Elements 8 Hangs Crashes Errors - Vista 32

    Hi,
    First I'll admit i'm no pro (obviously why im using elements), so if im doing something amatuerish it's because i'm not a professional.
    I remember using adobe premiere elements 3 a while ago, and it ran fine.
    I just bought Premiere Elements 8 and it's crashed more than any program i've ever used. Ive been to many forums to address the issues however there seems to be no solution in site (especially given that their support seems to be down at the moment).
    The first "weird" issue is that I get a little red X that appears at the lower left portion of the screen and when I click on it it says that my preformance will be poor because my graphics card isn't working properly.  This is not true as my Dual Nvidia 9800GT cards are working fine.  (I have sli turned off for the record because of a conflict with Cubase).  So I don't know what this means.  But I did notice something odd in my windows video display options I have 1 montor enabled but I see 3 grayed out disabled monitors even thought I only have 1 plugged in.  (I was using an additional one but it's unplugged currently)
    My most common issue is with hanging that won't end.  This usually happens when I apply a change to a file and trim it, or move it almost always in the timeline. The progrom just closes all together when I edit still images from time to time especially when I overlap it with a video.
    When the hangs happen my Cpu is at 12%ish, and I have ram available.  Although Premiere uses a truckload!
    Here are my project specs:
    The preset project mode that I chose was HD (hard drive) video, widescreen 48k because the files are from my hard drive so I didn't know what to choose
    Working with .mov files which were improperly formated from the source with regards to aspect and given to me so i had to stretch them out (could this be an issue?)
    Using the standard Premiere sound driver, although I do have a focurite interface but i only use that for Cubase.
    Backround rendering is on (seems to speed things up with regards to workflow)
    Autoanalyzer is off
    Computer specs:
    Dell XPS 630i
    Intel Core2duo 3.16 Ghz
    4 Gigs of ram (although only 2.8 showing because of partition issues anyone have a solution?)
    Windows Vista 32 home premium
    Dual SLI Nvidia 9800GT graphics cards - Both rated at 512 memory (latest drivers, physex, and 3D have been uninstalled threaded optimization turned off)
    Mcaffe security system
    If anyone can figure anything out from what I wrote please let me know!  thanks

    Here's some basics (some of which you've already covered). Definitely disable McAfee realtime scanning while using PRE.:
    Install all Windows Updates.
    Install latest version of Apple QuickTime (v7.6.8 at time of writing). Even if you don't use QuickTime, PRE relies heavily on it.
    Install most recent graphics and sound drivers from the manufacturers web sites.
    Run Disk Cleanup.
    Run Defragmenter.
    Temporarily disable any anti-virus realtime scanning.
    Use the GSpot Codec Information Utility to analyse the file and post screen image.
    Post back here with the necessary information described here: Got a Problem? How to Get Started
    As you've JUST bought PRE8 contact Adobe and get the complimentary upgrade to PRE9. Upgrade eligibility after new product announcement
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

  • Help uninstalling Adobe Premiere Elements 1.0 Error 1402.???

    have my movie done ready to burn dvd
    have had premiere elements 1.0 for 4 years
    on my dell E1705 windows xp media edition 2005
    computer has recently had some problem... freezes up
    that was triggered in the DVD burning process
    so i uninstalled and then reinstalled premiere 1.0 from the original discs
    and when i went to open the program would get
    a message that the registration is invalid and to uninstall the program
    so when i went to uninstall the program it runs through the process
    and when it gets to the part where it starts to remove registry values
    i get a message window pop up that says:
    Error 1402. Could not open key:
    HKEY_LOCAL_MACHINE\...\DefaultPreset.
    Verify you have sufficient access to that key or contact your support personnel...
    Adobe doesnt support this software anymore
    as i was told by their tech people
    so i downloaded a free trial version of adobe premiere elements 8.0
    and it crashes when i try to open it
    ive been told by adobe tech that this is because
    i need to uninstall APE 1.0
    duh!!!
    can you say catch 22
    any body got a clue ?
    thank you for taking the time to read this
    310 869-2454
    blessings and light
    dae

    One thing that can be done to clean Registry values is to run a Registry cleaner, like CCleaner. I would strongly suggest that you first manually create a System Restore Point, and then take advantage of CCleaner's offer to create a Registry backup, just in case. Run it several times to clean out all vestiges of PrE 1.0.
    Also, getting back to the problems with PrE 1.0 and burning, please list the full specs. on your system. It is likely that what caused the burns to fail in the earlier version will still be there, and cause problems with PrE 8 too. Pay special attention to your I/O sub-system, i.e. your HDD's, their size, speed, amount of defragmented free space, controller type and how they are allocated.
    Good luck,
    Hunt
    PS - are you running as Administrator? You should be.
    Also, when you go to install, make sure that all AV, pop-up blocking and spysweeping software is turned OFF, along with all Windows firewalls, etc.

  • Can't open Adobe Premiere Elements 9

    I've had some problems with Adobe Premiere Elements 9 recently, and right now I'm not able to use it. I'm not sure what the problem is really or how to fix it so I'll just write down what has happened here and hopefully someone knows what to do.
    A week or so ago my laptop started to crash repeatedly, but fortunately that was solved. But then I noticed that when I opened Adobe Premiere Elements, that's when it crashed and only then. It stopped crashing altogether except for when I opened this program (if it is of any importance I also tried opening Windows Movie Maker to edit there in the meantime but the same thing happened there, which seems strange and kinda random to me). I decided to get an antivirus software and install that and see if that took care of it, which I have now done. That didn't exactly take care of it though. The laptop did stop crashing when opening the Adobe software, but nothing happens once it's opened. The tabs on the top right are there but the whole program is just grey (where you would normally have the timeline on the bottom, video to the left, and the files etc. to the right) and nothing else comes up. I then tried to uninstall Adobe Premiere Elements 9 from my laptop altogether and then re-install it with the CD I still had from purchasing the laptop a couple of years ago. But after re-installing there is no change. Just a grey screen once again, except for the tabs and all that on the top. Now I'm not sure what else to try. It's frustrating as I need this program to work right about now. Does anyone know what to do? Thanks.

    From the Premiere Elements Information FAQ http://forums.adobe.com/thread/1042180
    •What version of Premiere Elements? Include the minor version number (e.g., Premiere Elements 12 with the 12.0.1 update).
    •What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac"
    •Has this ever worked before?  If so, do you recall any changes you made to Premiere Elements, such as adding Plug-ins, brushes, etc.?  Did you make any changes to your system, such as updating hardware, printers or drivers; or installing/uninstalling any programs?
    •Are you using an account with Administrator Privileges?
    Run as Administrator http://forums.adobe.com/thread/969395 (Encore + "All" Premiere)
    •Have you installed any recent program or OS updates? (If not, you should. They fix a lot of problems.)
    •What kind(s) of image file(s)? When talking about camera raw files, include the model of camera.
    •If you are getting error message(s), what is the full text of the error message(s)?
    •What were you doing when the problem occurred?
    •What other software are you running?
    •Tell us about your computer hardware. How much RAM is installed?  How much free space is on your system (C:) drive?
    And some other questions...
    •What are you editing, and does your video have a red line over it BEFORE you do any work?
    •Which version of Quicktime do you have installed?
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    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
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    Some of the below is for Premiere Pro, but the idea is the same for Premiere Elements
    Dual video problems - Do you have dual graphics adapters?
    Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
    IF YES, read below
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
    -HP Fingerprint/Password conflict http://forums.adobe.com/thread/911575

  • Is Adobe Premiere Elements 10 compatible with OS X Yosemite?

    I have Adobe Premiere Elements 10 that I use on my IMAC.  I recently updated my operating system to OS X Yosemite and when I go to use the add menus portion of the the program it consistently crashes.  I have uninstalled and reinstalled Adobe Premiere Elements 10 and it still crashes when trying to add disc menu's to my movie?  Is Adobe Premiere Elements 10 not compatible with OS X Yosemite?  Do I need to upgrade my version of Adobe Premiere Elements for the program to work? Larry

    Lawrence3973
    I am strictly an Elements Windows person and do not have a Mac computer to road test this one. I do remember that question being asked before. My recollection is that Premiere Elements 10 is, but it a recollection which I would need to research. Most of the threads with that question can be found unanswered.
    Does Premiere Elements 10 run on Yosemite?
    Most of the "Elements" discussions with information revolve around Photoshop Elements Mac and Yosemite.
    Are you running the program as Administrator and do you have the latest version of QuickTime installed on your computer? Is it only disc menus that bring the project down? Is it all disc menus or just one or two that are involved in the issue?
    But, first I would ask "What video card/graphics card are your computer use?" Therein may be the problem if the card is a NVIDIA GeForce one.
    You could try delete the Adobe Premiere Elements Prefs file which I believe can be found in Mac
    Users/Owner/Libraries/Application Support/Adobe/Premiere Elements/10.0
    Please review and consider.
    ATR

Maybe you are looking for