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

Will,

I went through the checklist above, and was up to date on everything.  Still issues.  Then, I downgraded to 6.0, and am still having lots of problems which may/may not be related.  Getting some crashes (Serious Error), and now a new issue where the program and source will only show black during playback, but show current frame on pause.  Once this happens, I have to restart.  It will bring down both AE and Pr. There are dynamic links in the timeline with Warp Stabilizer.  One possible culprit - a few times I have been running stable, and then after starting Safari, I will go back to Pr and get the Black Frame issue.  Can you think of any conflicts with Safari?

Thanks!

Wil,

Thanks for reminding me of trying it with GPU off.  So, it looks like it won't crash when it is doing the black playback, so no log there. (but I will look for the crash logs from earlier with the serious error crashes)  But, if I switch over to Software Only mode, everything returns to normal.  Switch back to GPU, and it is black again.  Seems like it is getting narrowed down.

As said before, I am on 10.7.4, latest CUDA driver, latest nVidia driver for the GTX285.

I don't have access to another card easily, but would follow that road if everything is ruled out. 

Thanks for your help.  Is there anything else to try right away?

Happening to me too. Constant "serious error" crashes, usually when I'm doing hardly anything at all. One project was working with just a couple images and it was particuarly awful. Like you, H264 footage are a common thread.

I'm a Mac Pro 3,1 2x2.8GHz Quad-Core, 10.7.3 (will try updating), 8GB RAM, GTX285, 6.0.1 and CUDA 4.2.7. GPU Driver Version says 7.18.11 270.05.20f02.

As it stands I can't get anything done. My experience w/ CS6 so far has been to finish one project (2 tracks of DV, one of H264) that was originally started in CS5, and I don't really remember having any problems. Software worked much better than CS5 actually. Tried another one from scratch, same setup, but I encountered the H264 media pending bug that's been reported elsewhere and had to give up, go back to CS5. Project I mentioned above, I could barely do anything w/o the program crashing. This fourth project, another 2 DV/1 H264, I haven't encountered any problems playing back the footage yet, but this is when the software because very unstable.

My console is FULL of "invalid drawable" errors

5/30/12 2:40:09.845 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:09.846 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:09.988 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:09.993 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:10.017 PM Adobe Premiere Pro CS6: NSAlert is being used from a background thread, which is not safe.  This is probably going to crash sometimes. Break on _NSAlertWarnUnsafeBackgroundThreadUsage to debug.  This will be logged only once.  This may break in the future.

5/30/12 2:40:21.354 PM com.apple.launchd.peruser.502: ([0x0-0x5a05a].com.adobe.AdobePremierePro[603]) Exited: Terminated: 15

5/30/12 2:40:23.049 PM com.apple.spindump: Premiere Pro [603] didn't gather enough samples to report (only 3 samples)

5/30/12 2:40:26.594 PM [0x0-0x71071].com.adobe.AdobePremierePro: --- OpenGL Info ---

5/30/12 2:40:26.600 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Vendor: NVIDIA Corporation

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Renderer: NVIDIA GeForce GTX 285 OpenGL Engine

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: OpenGL Version: 2.1 NVIDIA-7.18.11

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: GLSL Version: 1.20

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitors: 2

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitor 0 properties -

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Size: (0, 0, 2560, 1600)

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Max texture size: 8192

5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Supports non-power of two: 1

5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 444: 1

5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 422: 1

5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 420: 1

5/30/12 2:40:26.646 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitor 1 properties -

5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Size: (2560, 0, 1360, 768)

5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Max texture size: 8192

5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Supports non-power of two: 1

5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 444: 1

5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 422: 1

5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 420: 1

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: --- GPU Computation Info ---

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: Found 2 devices supporting GPU computation.

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: CUDA Device 0 -

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Name: GeForce GTX 285

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Capability: 1.3

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Driver: 4.02

5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Total Video Memory: 1023MB

5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro: OpenCL Device 1 -

5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Name: GeForce GTX 285

5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Capability: 1.1

5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Driver: 1

5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Total Video Memory: 1024MB

5/30/12 2:40:26.662 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Not chosen because it did not match the named list of cards

5/30/12 2:40:47.412 PM Adobe Premiere Pro CS6: GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framewor k/Versions/Current/AppKit,_NSCreateAppKitServicesMenu) failed.

5/30/12 2:40:48.188 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:48.198 PM Adobe Premiere Pro CS6: invalid drawable

5/30/12 2:40:48.205 PM Adobe Premiere Pro CS6: invalid drawable

Disregard what I said about 6.0 not having the problem.  Multiple Serious Errors.  I will PM a crash log to Wil. 

Has anyone emailed a crash log and gotten a response?

Okay, because Adobe asked me for a crash log a week ago. I sent it, and all I hear are crickets.

Direct message, as was requested.  All my interactions are searchable by clicking my name.

Sure, or I'll send my next crash.  I tried before to forward a direct message on this site and came up empty.

It might. But if they're working to debug CS6 on a larger scale they might not engage individual complaints until they have a patch.

As Wil explained to me, it's actually a good thing to send these reports - they are getting in the hands of the engineers that build the software, and this is much better than tying to navigate the tech support department.

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 

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/AudioRend erer/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