Participating Frequently

Question

Premiere Pro CS6 Constantly Crashing

Forum|Forum|13 years ago
May 29, 2012
10 replies
54849 views

I am having the worst time using Premiere Pro CS6. The program is constantly crashing, saying it has encountered a serious error and has to close. This is happening during the most basic operations like scrubbing the timeline or pressing play. I am using footage strait from my Canon 7D (h.264) with no effects or filters. I have all the latest updates to the software and my computer. No other programs are open during these errors. I'm using a 2011 MacBook Pro i7 8GB RAM with AMD Radeon HD 6750M 1024 MB and OSX 10.7.4.

I wanted this to be an alternative to FCP 7, but so far it is not working out.

Any ideas?

This topic has been closed for replies.

J

jordanc13347886

Participant

I have the same problem. It always seems to crash at the most inopportune times and then you lose everything you'd worked on. For me it crashes when I copy and paste multiple clips on the timeline.

H

HarleyTDavis

Inspiring

This problem seems only to occur on mac systems running 10.8 and above. Some 10.8 systems don't crash, they simply freeze until you close all instances of media encoder from the process monitor. Some actually work, and the only real difference is that they are running the programs in 32bit mode, with a hack-rosetta install. CS6 must look for the instance of the encoder by a 32bit call, perhaps in the old style, that isn't compatible with the new software. Where's Steve? Rolling in his grave while his ghost is upstairs jumping up and down and screaming down "Somebody shoot these morons they put in charge of my company! I'll get you a nice place up here if you just stop the madness!" He wouldn't have stood for grabbing at a strict 64 bit kernel without some backward compatibility. 10.8 and above, you're stuck with one clip at a time, and you're probably going to get a few crashes besides. Check your systems process monitor (Activity monitor). Some premiere resources and AME resources show up twice as different processes that stop responding. With a single instance, everything runs smooth. But they cannot find each other in memory, so multiple clip types will call different instances, and multiple clips of similar type will probably do the same.

H

HarleyTDavis

Inspiring

I've noticed that processes with the same name or process id tend to crash on both win and mac systems lately when multiple instances are called from "protected" memory. It's a virus protection mechanism that prevents filling memory with random data to overflow it. I've seen duplicates of dynamic link engine show up on mac in activity monitor. When they have similar id-tags or similar memory counts, crash. I've seen some other programs do the same. There has to be a problem with the way the memory is being handled, or the way the program asks for memory from the system.

I am starting to think that SAAS is not the way to go for operating systems... ...Back when you had to sell the product in a solid form, you had to provide quality, now all you have to do is reply with a, "keep your subscription current, as we're working on a repair for this in an update," while you leave them hanging until you rewrite the whole GUI before you even get to the main problem. With a hard product, you've bought something with embedded information in a hard copy form that can be tested and retested in legal form, and then you have recourse. With SAAS, you "Digitally" sign a document handing over everything but your first born child, then you get hassled, and when you imply legal action for failure to service, they throw it all back at you and say they never agreed to any kind of service. Ultimately you're at the mercy of what they call a "Reasonable update schedule", which basically means you pay for the service, then they choose when you get any.

With CS6 I'm starting to wonder also if recent updates didn't build in a few bugs in order to force the upgrade to CC, another SAAS model. I don't like SAAS, I like the software I was already doing well with. I don't mind end of life for updates, as long as you provide the list of file format compatibility, so I can make proper arrangements with my encoders. That's no issue. Ingesting is always a first step. Love the software, but hate CC SAAS. IT's buggy, and reworking it over and over to remove a bug on one system while not creating one on another system is tough enough without having to make sure that the Web function is built.

D

Design-Kink

Participating Frequently

My Premier crashes a lot, sometimes just opening it, on a new MacBook Pro (Retina, 15-inch, Mid 2014) with OSX 10.10.3

I don't know why Adobe asks you to submit a crash report, I gave up after the first 100 crashes or so because I never heard from them, they don't seem interested in helping the customers they charge good money for software that constantly crashes.

I have seen people have more luck running stable pirate software.

Today is a pretty standard day for me, edit a video on Premier, crash repeatedly, get too scared to even play a sequence to avoid a crash, watch a previously rendered video in VLC just so I know where to go to make some edits and render it out & hope for the best. sigh.

ColbyFulton

Known Participant

Yeah i'm scared to use Premiere for serious projects, it totally failed me on a simple test project. Adobe Dreamweaver is a mess and Indesign crashes like a mo'fo. I know programming isn't easy but these programs have been around for several years, you'd think they'd eventually iron out the bugs.

MarkWeiss

Inspiring

I've not imported HDV in years, but this evening I tried to open several HDV clips, one at a time, and after the file imports and indexes, Windows 7 64 freezes. I mean the mouse pointer, keyboard--everything. Just like Windows 3.0 would freeze. I've never hung Windows 7 before, and I've been using it for years. This is a first. I guess CS6 no longer supports HDV.

D

dphawkins34

Participant

I am also suddenly encountering these serious errors. For me it only happens when I add jpegs to my timeline. When I delete the images I can edit fine again. I think I'll try editing my text/images in AE then importing as a video into PP.

MarkWeiss

Inspiring

The first time it crashed for me was when I hit the 'cancel' button while it was indexing media files. It just 'went away' without so much as a crash report dialog. Other than that, been pretty stable on older hardware. (2008),

M

MigrationMedia

Participant

Did you ever find a solution?? I am having the exact trouble with a serious error. I can not even open the program to work on my projects.... and the technitions can not find a solution. I need help!

P

Paul_van_Dinther

Participant

No solutions to offer. Another "me too" post.

Radeon 9750 card, Windows 7 64 bit with 8 Gig of ddr3. Probably due to the work I am trying to achieve. In my case the crashes are severe. Full blown Blue screen of death and every once in a while also a simple application crash.

It seems to happen when I import a bunch of wmv video files into the project. Some thumbnails change to black and while and are suddenly displayed upside down similar to this thread ( http://forums.adobe.com/message/4611938#4611938 ). Once I get the black and white, I know we are about to explode and sure enough seconds later the mouse stops moving and the blue screen of death appears accompanied by a series of expletives from the operator.

This morning I went out and bought another 8 gig of ram increasing the total to 16 gig, hoping this would solve my issue. It is eary days but this seems at least to reduce the number of crashes to only a few crashes per hour I feel I can actually do a little work using PP CS6. I really need to hear Adbobe respond to these cries for help. The subscription to the software is a good deal but the hours I lose trying to do work cost a lot more.

I hear CS5 is much more stable. I would be happy to be given access to CS5 as productivity is more important to me then running the latest buggy code.

josephs51576386

Participating Frequently

Have you tried removing the original RAM you had? Then using just the new RAM you just purchased by itself for awhile. The fact it crashes less with the new RAM makes me question if some sort of memory error was occuring and now that there is more RAM there it has started occuring with less frequency.

It's worth a shot anyways

P

Paul_van_Dinther

Participant

Thanks for the suggestion. After some more time trying to work with PP I find the number of crashes is the same. It is just I get more done because it is a bit quicker. I did try what you suggested but it made no difference.

In my case, the crashes only occur when I work in the project panel. Crashes occur mainly when I move the mouse over the thumbnails "Hover scrub" although not exclusivly. However, all crashes seem related to activity in the project library window (Is that the right word?)

For the last few hours I disabled my other two monitors in windows and work exclusively on a single screen. So far no blue screen although hover scrub still causes the graphics driver to crash but this time Windows caught it and even balloon notified me. I looked up the event: "Display driver amdkmdap stopped responding and has successfully recovered."

After it recovered PP would respond again. Needles to say that working on a single screen using PP is painful.

J

johnmangino

Participating Frequently

I am also having this problem. Premiere would crash in the middle of the most mundane things. A ripple edit. Moving a clip down the timeline. Adjusting volume on the waveform. It crashed so many times that now the entire MBP is locking up when I try to open Premiere. Completely locking up. Hard power-button reboot needed.

This is CS6, on a MacBook Pro mid-2012.

I've uninstalled PrP and will try reinstalling and see if that helps.

I think all the sessions have been corrupted though.

C

ClaxtonCreative

Participant

Wil, I've had five or six kernel panics now since Friday and I'm in the middle of a huge series of outputs. I have captured two crash reports I'm happy to send whereever. I'm in bad need of help and don't want to jump back over into FCE to get all this done as I've finally got myself up to speed on all the tools in Creative Cloud and I'm quite thrilled with the product. The crashes, however, are dampening my enthusiasm. I've been to the Apple Store here in Dallas and they ran tests producing nothing. I called Adobe Customer Service on Friday and all that guy did was tell me how to back up the project and tell me that Premiere Pro is a high-end product and it sometimes causes crashes. I hope that's not standard training as it's not a satisfactory answer. My ticket number was 183274410 if someone wants to thank the guy on the phone for his time and send him to work for AT&T; he'd fit right in over there with that kind of support.

Please help me. I'm @daddyclaxton on twitter and if I have an email addy, I'm happy to forward these two crash reports to help give a better idea of what's going on with my system. Both reports seem to cite an issue with CPU 2 or CPU 6, but I don't know what I'm looking at in all the techno speak.

Donny

N

needles27

Participating Frequently

Can you post your hardware and software config? Are you running 10.7.4? Are you running with a CUDA-enabled card? Does it make a difference if you are using GPU acceleration or Software Only on the Mercury Engine? Does it matter if you are running other apps that are using the GPU, such as watching video in Safari?

Are you getting full-blown kernel panics, or just error messages too?

B

benwinter

Inspiring

Hi. I am getting full-blown kernal panics (requiring hard power cycle to unfreeze), "serious error", and "Premiere Pro has encountered an error". The last of which allows me to save, but keeps re-posting the error dialogue. The resulting "save" in this state is a corrupted PrP proj.

PrP projects seem to get corrupted just after I have dynamically linked with After Effects and begin to tweak the resulting timeline in AE (masks, levels... regular stuff/no special plugins).

Haven't seen the kernal panic*** and "serious error"** since running Disk Warrior, but I have seen "Premiere Pro has encountered an error" repeating dialog after DW.

EDIT: I have seen all three crashes. It doesn't seem to be related to invoking dynamic link. I've also gotten it just by scrubbing in my timeline, or by switching render settings from "performance" to "memory"

Specifics:

"Premiere Pro has encountered an error.

[/Volumes/BuildDisk/builds/tightykilt/shared/adobe/MediaCore/AudioRenderer/Make/Mac/../../Src/AudioRender/AudioPrefetch.cpp-87]"

SYSTEM:

Premiere Pro 6.0.1

Mac OS 10.7.4

MacPro5,1

32 GB Ram

PROJECT & MEDIA drive: Mercury Accelsior. Blackmagic Disk Speed Test: > 500 MB/s read/write

CACHE drive: Internal SATA Raid 0. Blackmagic Disk Speed Test: > 400 MB/s read/write

Nvidia Quadro 4000 Mac

CUDA Driver Version: 4.2.10

GPU Driver Version: 1.3.4.0 (270.00.00f06)

Cineform 1.2.0.127 codec installed for access to GoPro footage

FOOTAGE:

• h.264 from GoPro Hero 2: 720p60, 1080p30

• h.264 from Canon D5: 1080p30, 1080p24

• h.264 from Canon D7: 720p60, 1080p30, 1080p24

• ProRes 422 720p24 recompressed Hero 2 footage which is longer than 10 minutes to avoid sluggish response.

SEQUENCE:

• 720p24. I have tried both "no" compression, and DSLR PrP settings.

PROCESS AFTER CRASH:

• delete Premiere prefs. with Prefrence Manager Version 3.2.1 (3210)

• trash cache files

• repair permissions

• restart

• duplicate latest auto-save and try to avoid using dynamic link.

I want to start grading and vignetting in AE asap. Any suggestions?

Thanks!

Benjamin

** Update. Serious error is back even after running Disk Warrior, trashing prefs, caches, and previews, etc:

Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.

*** Update. Turning render settings from "performance" to "memory" was the last thing I did before a kernal panic initiated.

Message was edited by: Benjamin Goldman

Benjamin,

The AudioPrefetch.cpp line 87 error has to do with Premiere rendering the waveform previews of audio tracks, in my situation it was clips whose speed or duration had been changed or reinterpreted. I believe it's unrelated to this thread's particular "serious error" issue (might be related though? Only Adobe knows), as I had this issue repeatedly in CS5, where it would cause it to crash. In CS5.5 the error was still there but you could dismiss the dialog and keep Ppro open, no crash. CS6 I have yet to see the error at all. Sorry to see it hasn't been completely addressed.

It costs you the waveform visualization, but you can stop the error from happening by keeping all audio tracks collapsed (triangle to the side) or by selecting Show Name Only instead of Show Waveform using the Set Display Style selector.

In CS5 and 5.5 the error dialog still allowed me to use Ppro if I hid it off in a corner and kept working. So to save a 'corrupted' project file, I would open it up, switch all the audio tracks to Name Only, save, then quit and close the warning box. If it doesn't allow you to do that, import the old project into a new project file and close up those audio tracks.

Here's a live thread on the problem.

http://forums.adobe.com/thread/388281

N

needles27

Participating Frequently

I am getting this a lot too. "Serious Error." It wasn't happening on 6.0, but a few things changed since then so I don't know what to blame it on.

I am on a MacPro 4,1 32GB RAM GTX285. Running 6.0.1 and 10.7.4, latest Nvidia drivers.

I thought it was a Dynamic Link problem, but it is happening on all sequences now. (Although when it happens on a DL, it will bring down AE as well) Tried trashing all preview and cache files. Happens on H.264 footage and ProRes footage.

It happens a lot on scrubbing, but also playback. I notice sometimes that the program and source monitor will stop functioning right before the Serious Error happens.

I am now testing with a lot of startup items and other drivers disabled to see if there is a cultprit. So far so good, but i have thought that before. I will report any progress.

What apps/drivers are you running in the background on your system? I am testing right now with the following disabled:

Hazel

Text Expander

iTunes controller

Wacom tablet driver

Dropbox

Growl

Scansnap

Pathfinder

Launchbar

Chronosync

Drobo

N

needles27

Participating Frequently

Forget it - still crashing with all the background processes gone.

J

JohnnyGuitar1

Participant

Just a general response here. I have two Mac Computers with loads of RAM and power, both crashing every time I use Premiere Pro CS6 with the latest updates. I am only using DV footage so it should be easy to use. Has problems even trying to capture from my editing deck(JVC-BR600UA and it is fully cleaned and set up): one has to go back and forth with the play and record buttons before it actually caputres anything. And while editing or viewing footage that is finally captured, it will crash...no effects, no power-hogging reasons...just crashing. Reminds me of when I used Premiere back in the 90's with a Media 100 card and a very expensive RAID system...very buggy. When Final Cut Pro came out, I switched over and couldn't believe how wonderful it was. When it met it's death after Final Cut Studio 3 and all the raves about how much better Adobe Creative Suite has gotten, I bought into the Cloud and got the whole shabang. What a sucker I was. I have people asking me which editing software they should get for their Macs and I will tell them this: stay away from Adobe. They can't even handle DV...how are they going to handle HD? It is junk and they must hire the cheapest of labor to wrtie the programs. Reading what others have written about using their programs leads me to believe there will probably be a class-action suit against Adobe.

Hey, iMovie blows the doors off their stuff and it's free.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded