Premiere Pro 4.1.0 crash

Hi.
I have 2 versions og Premiere Pro installed on a WinXP SP3 system.
Premiere Pro 2.0
Premiere Pro 4.1.0
When I play 1x a straight DV movie from a sequence, which shows in the monitor window, I get CPU loads of 60-80% with 4.1.0 and 20-25% with 2.0. On top of it, 4.1.0 crashes from time to time, I believe due to too high load. The error is C++ related (can't recall exactly what it says). Again, all on the same system with the same Premiere video settings.
What's wrong with 4.1.0 that this straight play produces crashes?
Thanks,

Indeed ...!
The high CPU was gone, the crashes (so far) and also a memory leak (which I didn't mention in my initial post).
Many thanks,

Similar Messages

  • Premiere Pro & SpeedGrade CC keep crashing in Windows 8.1

    I just bought a brand new MSI laptop with Windows 8.1 and installed the CC suite. Premiere Pro and SpeedGrade continually crash when I try to use them. Premiere Pro crashes almost every other time I open it. Once it is open it works fine, but almost every other time I start it, I have to close and reopen it. SpeedGrade does the same thing, except sometimes it crashes in the middle of using it, which is VERY frustrating. These are the only programs on my computer that give me problems. The programs are installed to the OS partition on an SSD drive. Below are the error messages I receive for both programs and a copy of my computers specs. Please help me!
    Adobe Premiere Pro CC has stopped working.
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 7.2.2.33
      Application Timestamp: 532c3999
      Fault Module Name: GPUFoundation.dll
      Fault Module Version: 7.2.2.33
      Fault Module Timestamp: 532c367b
      Exception Code: c0000005
      Exception Offset: 000000000009a8f5
      OS Version: 6.3.9600.2.0.0.768.101
      Locale ID: 1033
      Additional Information 1: 84d7
      Additional Information 2: 84d72b4dc5a3d80213c9686cefe70939
      Additional Information 3: b9ea
      Additional Information 4: b9eab8acd04a6acc51b37ec54653b7b4
    Adobe SpeedGrade CC has stopped working.
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: SpeedGrade.exe
      Application Version: 7.2.1.0
      Application Timestamp: 53310645
      Fault Module Name: StackHash_0ae4
      Fault Module Version: 6.3.9600.17031
      Fault Module Timestamp: 530895af
      Exception Code: c0000374
      Exception Offset: PCH_D4_FROM_ntdll+0x000000000009B13A
      OS Version: 6.3.9600.2.0.0.768.101
      Locale ID: 1033
      Additional Information 1: 0ae4
      Additional Information 2: 0ae437b0d272d1d0fbcf3609ee0adbe4
      Additional Information 3: c92f
      Additional Information 4: c92f74bb31cdbacd81a9ea722a9da079
    MSI GT60 Laptop:
    Intel Core i7 4800MQ (2.70GHz)
    16GB Memory 1TB HDD 128GB SSD
    NVIDIA GeForce GTX 880M 8GB
    2880 x 1620 16:9 3K Display
    Windows 8.1 64-Bit

    Hi iduno8912,
    Very glad your issue is fixed.
    iduno8912 wrote:
    I fixed my problem! No thanks to the non-existent adobe support team.. Hope this helps someone because you can be sure adobe isn't going to help your ***.
    What happened? Did you contact support via Contact Customer Care ? Did you chat or talk with an agent over the phone? If so, please PM me the case number, I'll follow up with the agent to see why they weren't able to solve your case.
    iduno8912 wrote:
    They can't even make working programs for even the most up to date OS. What a nightmare!
    From your description, it sounded like it was a problem with your computer system, specifically your GPUs. What wasn't working from the application side?
    Let me know so I can prevent problems in the future.
    Thanks,
    Kevin

  • Premiere Pro CC 2014.2 crashes when "locating media"

    The problem;
    Premiere Pro CC 2014.2 crashes when "locating media".  I am working on a project that has not given me any problems for the last 200 hours.   About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs.  I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail. 
    Project workflow
    - 700gb of 5d footage
    - 20 sequences under 5 minutes
    - Dynamically linked files with AE
    - Warp Stabilized about a dozen clips of under 5 sec
    - On every sequence color correction adjustment layer with  RGB Curves, Three way color corrector and sharpen filter
    - I kept old versions of the sequences (I was in version 5 before the crash)
    What I have tried;
    - Unsuccessfully tried to open auto-save files for this project.
    - Successfully opened other older non relevant project
    - Removed Mercury playback engine in the project settings
    - Cleaned out media cache database through pp in media Preferences
    - Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
    - Tried importing sequences into new .proj file; it would crash as a result.
    What "worked".
    I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client.  I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
    Questions.
    - What the hell happened? Why could I open it on one computer and not on the other?
    - Is there a way to fix a corrupted .proj files on a PC?
    - What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
    Windows 8.1  64bit
    Premiere 2014.2
    Intel Quadcore i7-4770    3.40GHz
    16gb Ram

    Hi,
    I would suggest the following steps:
    http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
    Run a disk permission repair on your boot drive, and
    Reset Home Folder permissions and ACLs Error | Apple Support Communities
    Thanks,
    Rameez

  • I just installed Adobe CC Premiere Pro and it continuously crashes!

    I just installed Adobe CC Premiere Pro and it keeps crashing.  I've tried creating a new project, opening an existing project -- nothing works.  I can start a new project and get as far as to import clips into the project window but the moment I try to play a clip or create a sequence from it, it crashes.  I'm running off a brand new laptop (Lenovo X1 carbon 3rd gen)  8Gb Ram, i5 processor, best of anything I could get on this specific machine.  Any thoughts??
    The files I'm opening with a new project are MP4 files from a gopro camera.  The existing project was a CS5.5 file that it attempted to update to CC -- it actually located all of the files fine and as soon as it gets to the workspace with everything laid out, it crashes.  Let me know if I can supply any more information. 

    I just posted Im having the same issue.
    Premiere Pro 2014.2 is crashing
    I love PPRO 2014 very much but, wrote an nasty gram to Adobe because each update seems to have issues.
    I have set my autosave to 5 min saves and each time I see it say AUTO SAVING I use it as a reminder to do a real save.
    I have a super system and it didn't use to crash like this every hour.
    Why not try it out for a year and do a major update vs little updates that have issues the last 3 times.
    I can't render either with the hardware setting, which did work for a year then, the latest update screwed that up.
    The Adobe Tech blamed it on Apple but, hey - it worked for a year until Adobes update.

  • Premiere Pro CS 4.1 Crashes at Startup While Loading NI's VST's.

    Premiere Pro CS 4.1 crashes at startup while loading Native Instrument's VST's. My work around is to move the VST folder off the Plug-Ins directory, but that is a pain because I have to do it everytime I wanna use Premiere. In all honesty, I use my audio apps a lot more than Premiere. Any help would be great.
    System Specs...
    MacPro
    Mac OsX 10.5.7
    Premiere Pro CS 4.1
    4GB RAM

    With your VST folder in its proper place, try launching and re-launching Pr.  Theoretically, every time it fails to start the plug-in that caused the problem should be automatically blacklisted.  Sooner or later, all of the VST plug-ins that cause problems will be blacklisted and Pr will start normally.
    That's the theory, anyway.
    -Jeff

  • Premiere Pro CS5 - Media Encoder Crash when Exporting to MPEG-2

    System:
    Core i7 920 @ 3.8 Ghz
    Gigabyte X58A-UD3R
    12GB DDR3 1600
    External Sound Card - M-Audio ProFire 610
    OS Drive - 2x300GB WD Raptors - Raid 0
    Project Drives - 3x300 WD Raptor - Raid 0
    Video Card - Geforce GTX 285 1GB
    Adobe Premiere Pro CS5 and Media Encoder CS5 continually crashes or hangs every time I try to export to MPEG-2.  I can successfully render to every other codec without any issue, but need the MPEG-2 for an Adobe Encore Project.
    The project is approximately 38 minutes long and contains AVI and MP4 files, all of which were ripped from DVDs as I'm producing a reel for a producer who provided his DVDs for me to rip and use as content.
    Possible issues:
    1.   Currently have Magic DVD Ripper and DVD Fab installed (codec conflicts?)
    2.   Originally ripped the DVDs at 630x360 (my mistake - hadn't really worked with a DVD ripper before and was the largest avi pre-set) and I'm exporting to MPEG-2 standard 720x480 Widescreen)  (I know I should've just ripped them as the original lossless MPEG-2 files - I'm a tool)
    2.   Blank space in the timline (there are a number of these)
    I would like to get some input before I try to export to MPEG-2 again as I blew a capacitor on my old mother board (Gigabyte x58-ud3r) after I had gotten my computer to start rendering a MPEG-2 after about 50 tries to export/launch media encoder set on MPEG-2.  I just installed my new motherboard to replace it.  Clearly MPEG-2 taxes the system more so than any other codec (from what I can tell).  However, I thought the issue with the blank space/no media in the timeline was fixed with CS5.  I saw in a previous post that someone thought that ffdshow was conflicting with AME.  I don't have ffdshow, but I believe that's a ripper program like Magic and DVDFab.

    I experienced this at one point.  Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime.  (I have no idea why the quicktime player would have an impact.)  However, reverting to an earlier version of Quicktime fixed the problem.  Search this board using quicktime as a search phase.  The quicktime web site allows you to download the earlier versions.  I'm not at my editing machine, but I believe that I am at version 7.5.2.

  • Premiere Pro and Media Encoder crash while rendering H.264

    Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
    It's only while rendering H.264 - other formats seem to work fine.
    And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
    It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
    I've tried disabling CUDA and my overclock to no avail. Please help!

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • Premiere Pro painfully slow or crashes while encoding on reasonable system?

    Hi Folks, I'm new to the forum and new to premiere pro. I am having a real issue with encoding videos. If I have any fx on like Magic Bullet Looks then the media encoder says it will take around 3 hours for an 8 minute video (h.264 HD for youtube) but my system seems to crash before it finishes encoding (some times blue screen, some times encoder error message).  If I have no fx it still takes a couple of hours for an 8 minute video. This seems like an excessive amount of time, even for encoding my AVCHD files, which I know are notoriuosly slow to encode. I have the latest updates for Looks & PP.
    My system:
    Windows 7 Ultimate
    Intel Q9550
    Asus P5Q-EM
    GTX 480 unlocked for CUDA
    16GB 800mhz DDR2 RAM
    500GB Western Digital HD
    Which I would have thought was pretty decent for video encoding!
    Anyway any help or suggestions on how to speed things up and maybe stop crashes welcomed.
    Thanks

    Hi
    I had some BSOD's too in the beginning after building a new PC for PP CS5, but in my case it was the RAM, like Harm points out to be one reason, that was the problem.
    You could run a memorytest or burn in test for a day or two just to stress the PC and see if it find anything.
    http://www.memtest.org/
    http://www.passmark.com/products/bit.htm
    /Ulf

  • Premiere Pro CC 2014 TickTime Crash FIX (in some cases)

    In my experience so far, Premiere Pro can return a TickTime.ccp error in several different situations. In some instances (too much Warp Stabilizer) just clicking okay a gazillion times is a usable workaround. In a case I had recently, Premiere Pro CC2014 crashed completely every time I tried opening the project file and all its autosaved versions. Here's a description of what I figured out to be the problem and how I solved it.
    My project file was created in CS6, then edited in CC2014 on a Mac, then Windows. After this the crashing started on both Mac and Windows version of Premiere Pro CC 2014.
    Symptoms:
    An error message pops up on opening project [..\..\src\TickTime.ccp-290]. Clicking okay brings up another more serious one about a Serious Error and PP needing to close. Then it dies.
    The problem:
    Somewhere between CS6 and CC2014, Adobe seems to have changed their XML file structure from using a comma as decimal separator to instead using a period. Somewhere within my project file, Premiere left one as a comma.
    My fix:
    1. Make a copy of your project file and change the extension from ".prproj" to ".gz"
    2. Use something like 7zip and extract the file, this should give you a new file with no extention.
    3. Edit this file in a text editor (I'd reccomend Notepad++ or TextWrangler, but Notepad and TextEdit will also do).
    4. Search for the term <PlaybackSpeed>. Most of your clips would have a numerical value of 1 directly after this, referring to a playback speed of 100%. Click Find Next a few times and look at the numbers following the selected bits. Anything that is not a multiple of 100 will be a decimal number, that should look like "0.5" or "1.2759984", (referring to speed values of 50% and 127.59984% respectively). If you see a comma, replace it with a full stop. My project had a value of "0,8845" I had to change it to "0.8845"
    5. Save the file, and using 7-Zip, compress it into a new gz file.
    6. Change the ".gz" extension to ".prproj" and you should be set to continue your edit.
    If you didn't change the speed of any of you clips, chances are this is not your problem.

    Hi Karel,
    Thanks very much for writing this up. I hope this helps others having this issue.
    Thanks,
    Kevin

  • Premiere Pro CC 2014.2 - Crash when dragging videofile into timeline

    Hey guys,
    when I try to drag a image or videofile (doesn't really matter which fileformat, codec or length) into a sequence Premiere Pro CC 2014.2 will crash immediately, without a warning. Just the usual "Adobe Premiere has stopped working" in Windows 7.
    I'm using Windows 7 64-bit with 4GB RAM, Intel Core i3-4130 COU @ 3,40 GHz and a Intel HD Graphics 4400. Premiere Pro worked seamlessly just days before, without any change to the system. The error occured in Premiere Pro CC 2014.1 too. Maybe it's a problem with the video preview? Music files are no problem.
    Thanks in advance! Need help asap. customers are waiting

    Solution:
    My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
    But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
    Thanks Michaela from the Adobe Support Chat!

  • Adobe premiere pro cc 2014 - constantly crashing

    Naturally, my project is under deadline..
    My system is running OS X 10.9.4 (13E28)
    late-2012 MacBook Pro Retina
    2.6 GHz Intel Core i7
    16GB 1600 MHz DDR3
    Intel HD Graphics 4000
    NVIDIA GeForce GT 650M
    768Gb Flash Hard Drive
    My project consists of DSLR footage (h.264 compressed files) and Zoom H4N Audio (.WAV files)
    Even after spending most of Thursday and Friday on the phone with Adobe support; deleted all files from media cache, re-imported project, waited for premiere to re-conformed footage, etc..
    ...I still find my project loading sluggishly.. like it takes 15 minutes until video clips in the sequence will fully loads & appear in the project window... it becomes momentarily operable before quickly becoming inoperable as the video and audio no longer playback or respond to the cursor.
    At that point  (when playback no longer works) I can still save the project.
    It seems as though the software loses the dynamic link between the footage as it completely goes black.
    Then when I try to exit Premiere CC 2014.. the program locks up and crashes with no report.
    The crash reports I have are from a few days ago when they first began and before they stooped generating reports.
    Majority of the errors were:
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    It also crashed a few times with the following errors:
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fbfdef0
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
    Any help would be greatly appreciated!

    First I must say.. ADOBE PREMIERE PRO CC 2014 is glitchy as hell (and in my three weeks editing a documentary or rather two weeks bc I lost an entire week due to this issue) I have come to learn and identify some workaround solutions..
    Here is what I originally wrote after speaking to five different Adobe engineers...
    It is only an issue with PrCC2014 and the temporary solution before the upcoming update is to...
    1) Go into Preferences... Audio... and UNCHECK the box next to "Maintain pitch while shuttling."
    [this is a new feature in PrCC2014 that is processor intensive, causes audio dropouts, and is a major player in why the playback suffers]
    2) Go into your sequences settings for each sequence you have for DSLR footage and change the Editing Mode preset to "CUSTOM"
    3) Next scroll down to Video Previews and change the preview file format to "QuickTime" and the codec to "Animation."
    4) Uncheck the box  next to "Composite  in Linear Color (requires GPU acceleration or max render quality).
    [this is another new feature that is also processor intensive & is also a key suspect to the problem]
    THE KEY TO FIXING (temporarily) THE BEHAVIOR
    When your computer begins to show signs of the glitchy - sluggish playback behavior..
    Stop.. go back into your SEQUENCE SETTINGS and change it to a different EDITING MODE (only temporarily) and click OK.
    You could change yours from ProRes to CUSTOM (as indicated in step #3)
    Next a prompt will pop up asking you...
    Click okay then immediately go back to SEQUENCE SETTINGS and change it back to your original setting, in your case, ProRes.
    Somehow, by DELETING those PREVIEW FILES it essentially resets the issue... until the dreaded glitchy behavior returns.
    I have had luck with this trick and hopefully you will too..
    Cheers!

  • Premiere Pro CC (2014 version) crashes (beach ball) when trying open certain large Projects

    Hi,
    I'm currently editing for a TV channel using the latest version of Premiere Pro CC and certain projects (it seems to be with ones with a lot of footage) crash when I open it. Basically, it doesn't even load all the footage up, one that crashed just now said it had around 140 files left to load, but the beach ball arrives and I sat there waiting for half an hour and nothing happen, apart from the beach ball spinning.
    Now, we're on an high spec iMac 3.5Ghz i, 32GB ram, 512gb Flash Storage, 4GB Geforce Graphics card, so I don't think the issue can be the mac, unless the macs faulty, but seems to work fine, when I create new projects etc.
    Also, their workflow uses USB 3.0 drives, could this be the bottle-neck making them crash? That being said I've edited lots off my USB 3.0 drive at home and my desktop is a lot weaker then this iMac.
    Any ideas what the issue may be?
    Thank you,
    Matt

    Hi Matt,
    Please mention the exact version of Premiere Pro. Assuming you are using 2014 version, please try some steps mentioned below.
    1. Clean the media cache files by navigating to /Users/User Name/Library/Application Support/Adobe/Common
    2. Check the version of the drivers of your NVidia card. So, go to Apple Menu>System Preferences and check if you have a CUDA Preference pane if it is not there then go to the below link and update the Card to latest drivers.
    CUDA Drivers for MAC Archive | NVIDIA
    3. Also, please mention if you have any third party plugins used in the project. If yes, then try to update those Plugins or copy and paste those plugins to some other location and Trash them from MediaCore of Premiere Pro. The location of third party plugins is mentioned below.
    Startup Drive or MAC HD /Library/Application Support/Adobe/Common/Plug-ins/7.0
    Hope it helps.
    Regards,
    Vinay

  • Premiere Pro CS6 Trial Mac crashes on launch

    I installed Master Collection CS6 on my Mac Pro tower 3,1 quad core, 16 GBs RAM.  I set up a new video project in Premiere and all was going fine, loaded all assets, etc ... Next I was attempting to set up audio hardware for recording a narriation on a track.  I was using a USB VoIP device.  I could not arm a track for recording, so I figured audio hardware needed set up.  My VoIP was already selected in Preferences>Audio Hardware once inspected, but I still could not arm a track.  So, I tried Utilities>Midi Set Up>Aggregate Audio Devices to add my headset to Premiere Pro.  Headset was in list but I could not add anything to premiere.  Everything I checked automatically unchecked once selected. 
    Back to square one.  So I unhooked my headset, went to Preferences>Audio Hardware and attempted to select a Built-in I/O device. Then, Premiere just crashed. 
    Everytime I try to open premiere it crashes.  I rebooted, tried a different project, etc .... nothing! 
    So ... h e l p !

    You are right , to use the trial you do not need the serial number however it is a prompt screen that comes up at the time of launch so that you can serialize the software and turn it to full version also it let you know the number of days left for the trial.
    In your case it seems to be different , BTW what is your OS  ? Premiere Pro CS6 will only work in 64 bit OS actually, it will get install on only 64 bit OS so that might be the reason you have only Encore present not Premiere Pro.

  • Premiere Pro CS6 on Mac crashes when attempting to capture HDV

    I've seen this topic previously but without an answer and was hoping for an update. I'm using Premiere Pro CS6.0.5 on a MacPro running 10.9.2
    The camera is a Sony HDR-FX7. When in the capture window, the camera is recognized. I can rewind and fast forward but when i push play it immediately crashes and gives the "serious error" notice.  The camera settings are set to HDV in the VCR setting and PremierePro is set to HDV capture format as well.

    http://helpx.adobe.com/premiere-pro/kb/cant-capture-dv-hdv-video.html
    Also, Go to http://forums.adobe.com/community/premiere and, in the area just under Ask a Question, type in
    maverick
    or
    mavericks
    or
    10.9
    You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question

  • Premiere Pro CC 2014.2 Crashing while loading project...

    When trying to open Premiere project the program opens and looks like it will load and then crashes.
    If I create a new project Premiere opens and I can import footage but as soon as I try to play footage in the preview window or drop it in the timeline the program crashes as well.
    I am working on a Windows 7, 64-bit, i7, 8GB ram, 1TB multiple partitioned hard drive. My Graphics card is, Intel(R) HD Graphics 4600 - Driver Version: 9.18.10.3204
    My Error Log is:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: MXF_SDK_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d772c
    Exception code: 0xc0000005
    Fault offset: 0x00000000000bdc55
    Faulting process id: 0x378c
    Faulting application start time: 0x01d02c3625e455c1
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_4.4.33_vs10.dll
    Report Id: b1b66e81-9829-11e4-95ce-c4346b64bc4f
    I can't figure out what the faulting module is.
    I just installed CC 2014.2 3 days ago. It all worked fine until yesterday when Premiere started crashing. I restarted the system - same issue. I uninstalled and reinstalled Premiere2014.2 - same issue. Premiere seems to be the only faulting application. Everything else (Ps, Ae, Lr, Id, Au, Ai) appears to still be working.
    My version of CS6 (Purchased before getting a creative cloud membership not downloaded through CC) is also still working properly.
    Thanks for the help.

    Update: I updated my Graphics Card Driver to a more recent version. Restarted computer and reopened Premiere and similar crash happened. I went through to get some more crashes and had different crash reports. The faulty module is not always the same.
    Problem Event Name:                        APPCRASH
      Application Name:                             Adobe Premiere Pro.exe
      Application Version:                           8.2.0.65
      Application Timestamp:                     5486db4a
      Fault Module Name:                          devenum.dll
      Fault Module Version:                        6.6.7600.16385
      Fault Module Timestamp:                  4a5bded7
      Exception Code:                                  c0000005
      Exception Offset:                                00000000000016a0
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  ec5a
      Additional Information 2:                  ec5adb2545b190cc19da7bdfa78d5bf1
      Additional Information 3:                  6e59
      Additional Information 4:  6e59168cf9de1a4a9616903b4a4ba1e1
    Problem Event Name:                          BEX64
      Application Name:                             Adobe Premiere Pro.exe
      Application Version:                           8.2.0.65
      Application Timestamp:                     5486db4a
      Fault Module Name:                          OpenCL.dll_unloaded
      Fault Module Version:                        0.0.0.0
      Fault Module Timestamp:                  50eb1a5b
      Exception Offset:                                000007fee84516a0
      Exception Code:                                  c0000005
      Exception Data:                                   0000000000000008
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  a527
      Additional Information 2:                  a527a6af76c2b04cfd1fc255c66e5364
      Additional Information 3:                  21c7
      Additional Information 4:                  21c71ffc516aa3806e495b8080bd51fe
    Both of those are different from the original posted report.
    I did have some success following these instructions.
    Premiere Pro CC 2014.1 has stopped working - Win 7 64 bit
    It appears I do not have a graphics card that is compatible with the mercury engine. I have had three successful tests and one crash since I selected Renderer: "Software only"
    I plan to upgrade to a Nvidia card or the supported Intel Iris Card.
    This seams to be the issue but I am hesitant to use CC 2014.2 for the time being because I don't know if it will crash randomly and CS6 is working fine. The second error code with "Fault Module Name: OpenCL.dll_unloaded" seems to be directly related to the graphics card and rendering processes. I will update as I learn more.
    Please comment with any suggestions or resolutions you have had.

Maybe you are looking for

  • How To Stop An MMS Download

    I tried sending myself a picture message a while ago to see if I could recieve them, and I can't. The thing is, I can't get my Centro to stop trying to download it. Whenever I go to the message center, the little envelope with 0% always shows up and

  • Execute button for BEx Analyzer in the Query Designer

    Hello, My current BEx Query Designer 7.1 and we are using Excel 2003. Currently, I can execute query through BEx Web but I am also looking for green check button of BEx Analyzer also. Could you please tell me how can I incorporate/add this BEx Analyz

  • Thunderbird 24.6 just stops working . . . all the time.

    I've hinted at some of this before, and I've searched the forums for help . . . alas! We have an iMac running 10.8.5 and Thunderbird 24.6. We've been running Thunderbird since it was Netscape and before . . . it's our primary email program and we hav

  • Error installing Oracle 10.2.0.4 with CRM 7 / NW7.01

    I am in the process of installing CRM 7 with Netweaver on 7.01 on a Windows 2008 64-bit system.  I would have preferred a windows 2003 system, but according to an OSS note (1326698 and 1320013) CRM 7.0 isn't supported on Windows 2003. SAPInst runs ju

  • Lxpanel battery monitor plugin issues

    I have a pretty standard install of arch with lxde+openbox as my DE. For a while I had a problem with lxpanel that occured after I issued startx (after login). lxpanel would rapidly flash for about 3 minutes resulting in NetworkManager being unable t