It's been perfectly stable for me so far on two systems - Windows 7 and 8. I have seen reports of MSVCR100.dll crashes with CS6, though. Try a forum search to see if any solutions were found.
Premiere CC worked fine for me yesterday. Started crashing tonight, during use, not start-up. Can only work a minute or so before it "stops working." Still trying to find a crash file. The path it gave me during the error/crash message had no file by the name given.
Can't do simple cut editing and now I can't even complete the H264 export media file.
Fresh install and all updates to Windows 8 on a system using a 3770K, 32GB ram, an HD6950 2GB card and the 13.06 drivers.
It's probably the drivers. Getting tough to find drivers that will work in Cinema 4d and Adobe CC and still play games on the same system I guess. May be time to build a workstation for work, or maybe Apple will release this Mac Pro in my lifetime. Something has got to give.
EDIT: setting Mercury Playback engine to Software Only got me through the media export. Seems Mercury Playback / video card / driver related in my case.
Asus p6td deluxe i920 (overlocked a wee bit). 12gb super duper ram (geil 7-7-7-something)
240gbSSD (sandisk Ultra).
Footage was on a single wd 2tb Black drive. (Many other drives in system though including raid 5, 5x2tb on areca controller). Scratch disks all as default though.
2GB GTX660 (yes I know, but it worked flawlessly on ppro cs6).
Yes using mercury.
I was doing different things, one of them I was using a nested clip that was behaving strangely - time remapping was on but when I nested the clip it was doubling the size of the nested clip. Source footage for that particular clip was a photoshop generated MP4, otherwise MOVs froma nikon d800.
Whirlpool forum in Aus has a public member section where you can list hardware might be handy for these forums? Just a suggestions.
I'm having a crazy amount of crashes today too. Started with just srubbing B-roll from JVC camera. Went nuts once I started importing sequences from other projects to integrate. Now if I so much as make an edit with imported sequence files I get the "Sorry, a serious error has occured" dialog box and a crash. I have a ton of recovery projects already and it's only lunch time.
still play games on the same system
Oh, dude. That's not a good idea. You should have two systems, one for gaming and one for editing. It's entirely possible you have something installed on your system that is causing this crash. You need to keep your edit system clean, ideally installing only what you need for editing.
Jim Simon wrote:
It's entirely possible you have something installed on your system that is causing this crash.
Actually, though, not in this particular case.
Since I consider replacing CS6 with CC to be a major install, this is a clean install of Windows 8, all updates and just Adobe CC. No games or anything else installed, yet.
I was more talking about using game cards like an HD6950 and then dealing with AMD driver/beta driver hell. I had problems with Cinema 4d last year that were driver related.
I'd build a separate system just to use the most approved video card I could find for Adobe and Cinema 4d, and it probably would not be a good gaming card.
I think the key part in my post was where I turned Mercury Playback to software only, that seems to let it work without crashing, although, somewhat slower.
EDIT: ok, so, I set Mercury playback to GPU Accelerated/OpenCL from Software and got some message thay my render hardware was not supported? This message is inconsistent in showing up though.
No games or anything else installed, yet.
Are you using the Lumetri effect? This seems to cause pretty consistent crashes with OpenCL acceleration.
Turns out, my card is on the supported list:
- ATI Radeon HD 6950 (OpenCL)
I was not doing anything complicated at all.
I had one sequence with audio and I synched the video on top of that. Then tossed that sequence into a new sequence to simply edit out all the in between shot stuff so the producers could review just the content.
I may try again, or roll the drivers back to a previous version, but, I think I'm reading on here that for some, 13.06 is the fix for them, lol.
I also have a MBP 17" with a supported 6750M, so, that's an option, although I was hoping to use my beefier desktop for this one.
EDIT: narrowing it down. Now when I switch between GPU and Software only, I lose all video image in GPU mode. Put it back into software only, and the video shows up again. Odd thing is, I used the GPU mode for a whole day with no issues? Now it barfs with anything GPU related. I can say though, the GPU accelleration is pretty massive. Software only mode is tangibly slower.
Hmm... feels video card/driver/Mercury related, though I don't know exactly how, so I don't know whether it's the drivers (I can roll those back for free) or if I should get a new video card? This computer has been overall quite stable.
If I did throw money at the problem, NVidia or AMD? CUDA seems on the way out, but is still probably better supported at this moment in time? AMD drivers seem sketch, but then I also read that Nvidia drivers are sketch too.
EDIT2: No changes. Worked fine all day with Mercury Enabled. 2 days it has been fine. 1 day, unstable as could be.
EDIT3 (July 12): Still fighting crashes. Computer is rock solid in everything but Premiere Pro CC. Applied the just released update. Uninstalled 13.6 beta drivers and installed 13.4 WHQL drivers. Better for a quick session or two, then driver crashed and recovered. It's stable when I use software only and turn off hardware acceleration, but, it's just too slow, even on my 3770K with 32GB of ram. I'm considering an HD7950 but if it's the AMD drivers, then that might not work. The only NVida card supported that interested my was the GTX680. Not sure why the 660ti or 670 are not on the list, but they are not. No GTX7xx cards are either.
Not sure what to do. I have a few videos to edit. I may give my MacBook Pro a try but while it's capable of doing the job, it's not as fun to use as my desktop is when it's not crashing out. Maybe Premiere Pro CC is just not ready and I'll switch to FCPX for a while. Argh.
has my long reply to this been removed for some reason?
I have a dell m6700 with an integrated Intel HD 4000 and a nVidia QUADRO K4000M graphics cards. I've update both drivers, rebooted Windows 7 and Premiere Pro CC seems working fine now.
If I did throw money at the problem, NVidia or AMD? CUDA seems on the way out
It does seem like CUDA is still more stable than OpenCL at this point, though the newest nVidia driver is causing an issue. But with an older driver, it works great.
Even if CUDA is on the way out (and I rather hope it is myself), the advantage of OpenCL is that both cards can use it for hardware acceleration. OpenCL is not proprietary technology like CUDA is.
has my long reply to this been removed for some reason?
Yes, I truncated your crash report. Sorry, I meant to sent you a PM. Please don't copy/paste crash reports to the forum. This is a user to user forum and most folks cannot make sense of a crash report. Feel free to copy it to a bug report, though. You can file one here: http://www.adobe.com/go/wish
PPCS6 was fairly stable. I'ved worked with it since the change from 5.5 on a pc and saw my shares of crashes but nothing out of the ordinary.
Recently I started a new job and the studio has all macs. I got a top of the line 12 core, 32 GB RAM, Nvidia Quadro K5000 for Mac with 4GB of memory, SSD drives... you name it. I've had nothing but headaches with it. When it works, the machine is fast, but PP crashes consistenly. When I think I have found a culprit, something else comes up.
Some actions that have usually caused crashes: working with audio and jpgs. Nesting audio has been problematic and has caused crashes. Changing to audio time units and sliding audio around has caused many crashes. Simple movements of a jpg image have caused crashes.
I have been on the phone with Apple support, Nvidia support, Adobe support for hours. Even allowing them to remote control my machine (adobe) and look at the logs and crash reports. Nothing, it is voodoo at this point.
My left hand defaults to Command S the entire day. I save after every single change...
My workflow includes AE comps for motion graphics, including the use of 3D. That has been problematic to say the least.
I need help with this as well. I am running Premiere Pro CC on a 27-inch, Late 2012 iMac with 3.4 GHz Intel Core i7 and 32 GB of memory. NVIDIA GeForce GTX 680MX 2048MB. OS X 10.8.4. Most current update of CC.
Within this project I have two sequences. One is about two minutes, the other about 90. They have the same intro and outro, same content inbetween, 2 minute version is heavily edited and the 90 is the full-length.
I can export the 2-minute version with no issues. The 90 minute version I have tried exporting using multiple codecs, as well as multiple resolutions within each codec.
Half way through export I get the "Sorry, a serious error has occured that requires Adobe Premiere Pro to shut down. We will attempt to save your project" error message. I tried switching from GPU accelerated to software, it just sat at 0% on the export for a very long time. What is going on? With the exception of audio edits to raise or lower level, and some EQ, these sequences are basically the same, just one is longer than the other. It is the same content, from the same folder.
To anyone interested-including Adobe engineers-,
After trying everything I could to make this file export, the solution came to me by turning off a "RGB Curves" effect, as well as "Sharpen". Don't know if this is a bug or a small hiccup, but after turning those effects off (not removing), the file exports with no issues.
I had the exact same issue as Cody. And am pretty sure I'm using an almost identical iMac. Certianly the same GFX card.
Premiere Pro CC has been fine exporting sequences - up until today, when I had to export a 55 minute one. It just crashed during export (from both AME and Premiere Pro CC.) I ended up exporting them on an Macbook we have here, with a slightly different GFX card.
However I just tried that fix of turing off the effects (I too had RGB Curves on), and it worked.
HOWEVER.. I just changed my Mercury Playback settings too. I had left them on default before, and they were set to OpenCL rather than CUDA. I changed them to CUDA, put the RGB Curves back on, and tried to export.. and it worked!
So I guess it could be something to do with that and the graphics card - GeForce GTX 680MX.
I'm running Premier Pro CC and it's been nothing but buggy. I'm running on a Toshiba Qosmio with a Nvidia GeForce GTX 670M - with a CUDA hack
Premier Pro CC is unusable - opens, but crashes before it's fully linked all media.
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 184.108.40.206
Application Timestamp: 51cbdef8
Fault Module Name: StackHash_b267
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c0000374
Exception Offset: 00000000000c4102
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: b267
Additional Information 2: b26762f9642e0590c5844c830ef208e8
Additional Information 3: 0f28
Additional Information 4: 0f28b32deccc496a1ecb39e9884c7019
You might try updating. 7.1 is the newest.
I am having the same issues - constant crashing of Premiere Pro CC.
Crashes during edits - crashes in exports.
Mostly is just hangs and is in the dreaded "not responding" mode.
I run a small independent production business and never experienced this amount of issues
I have a Samsung Desktop.Windows 8, Running Intel Core i5, RAM 8GB, 64 Bit Operating System
Please can anyone help?
Not running games or very much other intensive software - this is my work computer.
What can I do?
Its not as bad as it was for me now. I get occasional crashes but especially before the windows 8.1 update it was pretty good. Try updating windows and make sure you're using the most recent version. Try deleting your premiere media cache (Google it).
Any resolution to this? CC crashes every 3 minutes. Impossible to work.
Brand new mac tower
most recent software
all updates installed
what's going on?
Are you getting exactly the same exception codes and faulting modules, Sarasea, or more generically just a lot of crashes?
Also, exactly which version of CC? Please report the version number shown in the About box.
I'm having similar issues to those in the initial post.
I'm working with a project made entirely in CC 2014, involving After Effects, Premiere and Speedgrade. I've had only a few less issues than when I worked with a project that was created in a previous version and moved to 2014.
This new project is far less complex than previous projects I've finished in previous versions (4 layers as opposed to 10+) yet at every stage I seem to be encountering new crashes and issues (it simply won't export, Speedgrade causes strange psychedelic effects on my screen, I get 'Unknown error' and 'Error compiling movie' - everything.
I've spent over 20 hours with various Adobe staff logging in to my computer to try finding a resolution for each problem to no avail. Not to discredit them though, I think they are just having to answer for problems with fundamentally defective software.
Is there something about my specs that suggests I should just use an older version? They still had many bugs, but I've literally been sitting on an otherwise finished project for 2 weeks trying everything suggested in these forums to resolve these issues.
I've tried re-installing, opening project in a new sequence etc.
Processor 3.1 GHz Intel Core i5
Memory 24 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6970M 1024 MB
Software Mac OS X Lion 10.7.5 (11G63b)
I tried that, then re-installed the Adobe software. It is still doing exactly the same thing.
I can actually render the whole sequence and watch it, I just can't export it (even using render files).
What is the speed of your hard drive, is it 7200 rpm?
I Have had the same prob with Premiere pro cc i have the same mac system as Frank@NPN ,
Will cs6 work better ?
I do find it extremely buggy. Whether it crashes, or I have to force quit, it's usually not more than a few minutes before one or the other. Sometimes it stops showing video when I'm reviewing my project (these projects are like 4 minutes long, not exactly Hollywood films), sometimes it's just "application not responding". Brand new iMac 27. Everything is up to date with CC.
I managed to fix this problem by opening a new Premiere Pro CC2014 project, File->Import-> Import the project file which keeps crashing, Choose only import selected sequence, choose the sequence you want to work on and import.
This was the only way I could work around the constant crashing after opening the original project file
Thank you everyone for your comments on these forums.
I fixed constant crashing by turning off an effect (not removing, just simply turning it off). I was using an Adobe simple effect (included in PR) "Perspective> basic 3D." I turned it off and I had successful playback. On egg shells trying to get this short project exported and out.
Recently updated PPCC2014, doing multicam sequences for a variety show. First I was having problems with output GPU error. Now, it's been firstly getting glitchy on screen, flickering between cameras in parts and now freezing when I get to a particular point on a sequence - yet to find the reasons but no obvious reason why - no effects etc.
no obvious fix, it just started working better.
I have just started experiencing regular crashes. I have rebooted and re-installed PP CC 2014 but it still crashes.
There doesn't seem to be anything specific that provokes it. It just happens seemingly at random.
I submitted a bug report but it won't allow me to include the full crash report because it's too long.
Mac OS X 10.9.5
Macbook Pro 2Ghz Intel Core i7
Me too. This is the first time Adobe Premiere CC 2014 is crashing everytime I spend between 15 minutes to 3 hours of work. I was complexing about my PC, but now I see that I'm not the only person who get this problem. First time, I was like: "Maybe if I drop the resolution of the view it will resolve my problem!"... same thing.
Win 7 x64
Intel Xeon E5-1620 3.60 ghz
Hey ya'll, I've been having this issue as well. I contacted adobe support through chat and what they did was delete all my preview files through premiere. I've been working without crashes since then.
Looks like a promising fix...
I have been having the same problem and have been losing my client's projects. I have had over 6 hours in my project and the system crashed. Even though I've saved the project a hundred times, the project now acts as if the files are missing and the pinwheel spins forever. There needs to be an update fixing this or I can't use Premiere Pro CC anymore.
I know what you mean. I keep getting regular crashes and so have resorted to going back to CS6 which luckily I still have and can use with Mavericks (CS6 is no longer supported by Yosemite which is why I've resisted upgrading). It seems far more stable.
I spoke to an Adobe rep a few weeks ago over the phone and they took ages looking at my Mac. They 'flushed' Premiere clean and it seemed to work OK for a bit but now it's gone back to its old tricks. This is only a recent thing. A few months ago I was having no problems, but since these issues have surfaced it's seriously affected my work and I've wasted hours of productive time force-quitting and restarting from an auto-saved version, re-doing stuff I've already spent ages working on.
I've listed a couple of the supposed 'fixes' below, but they only seem to be a temporary solution and like I said I'm not going to use version 2014 for now. Hopefully an update is coming soon...
Not good enough Adobe. Not good enough.
Possible Premiere fixes:
Move your preferences to the trash. Preferences should be in Documents>Adobe>Premiere Pro>8.0. Just delete the folder entitled '8.0'.
Hold down 'Alt' while opening Premiere (this is another Preferences reset I think).
Open a new project in Premiere and Import into it the project that crashed and basically create a whole new project. Save it and hope for the best.
Reinstall Premiere (I tried this but it didn't help at all which was frustrating because it took ages and I lost a heap of time).