@Benjamin Goldman, Unfortunately I can't help, but there are a lot  of us in this same situation.  Please follow and post to this thread http://forums.adobe.com/message/4522741#4522741 , we currently have 6,800 views and 143 postings, hopefully the more attention we bring to this thread the quicker a fix will be made.

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

To be clear, I do have a CUDA card installed on my system but it's not utilized by Premiere/Mercury engine because the memory is too small (512MB I think) so I am stuck on software mode only. ATI Radeon HD 3770 and NVIDIA GeForce GT 120.

Regarding Mac Pro5,1: I  had a  very stable FCP, AE, PS CS5/6 station since mid-2010 (from 10.6 to 10.7.4). I updated software/repaired permissions regularly. I used Permission Manager, SuperDuper, and DiskWarrior to keep my ducks in a row. (see config below)

Unhappy with Apple's commitment to FCP/Pro users, I geared up for switching from FCP to PrP, specifically, I added a Nvidia Quadro 4000 Mac (which seemed like the most powerful card Adobe was recommending to take advantage of CS6 improvements). I also added a fast cache volume.

I decided to learn PrP by editing a DSLR project with it. (No recompress of h.264? Awesome!!, I thought). Though I had the latest Cuda drivers and Mac & Adobe updates, the day I started using PrP to  edit, I got kernel panics, serious errors, and what I would later learn is a harmless/annoying line 87 error. (Thanks @benwinter!)

Phone calls with Adobe tech support: escalated to a higher tier. An employee who shall be referred to as "V" told me to try creating a new Admin account, and to email him the results. The results were: "serious error" in the first few minutes of use. I sent the update to V along with my crash report. He has not yet responded but has (or has allowed the system to) mark my case #0183359996 as "withdrawn" for some reason. But I digress! I have great news, keep reading!

@Jim Simon asked if I had tried simply wiping/rebuilding my system. I didn't have time in the middle of the project (and why would I have to wipe/rebuild a highly functional box?? Was this a wild goose chase??? What's the deal?? I'm on a deadline, waa waa!) I hobbled through the project by turning rendering from GPU to CPU, quitting PrP after it sent anything to another program, and incessantly clicking the error 87 dialogue until it disappeared for a while.

But as soon as my project was finished, I wiped/rebuilt my system. ALL CLEAR SO FAR! Thanks Jim!

My next steps are to back up my functional system and begin adding all of the things I need to really use it: Wacom diver, Epson Expression 10000 XL driver, GoPro CinePro codec etc...

In the age of the App Store, Apple makes a fresh install tricky. I have listed the obsessive steps I took to create a fully-fresh&functional edit system that dynamically links to AE and AU the way I always hoped it would. I will definitely update this post if I encounter  kernel panics and serious errors as I incorporate the rest of my programs/peripherals.

Details:

1. Download Lion (again) from App Store and make a bootable install disc on an external FW drive using these fantastic instructions:

http://reviews.cnet.com/8301-13727_7-20080989-263/how-to-create-an-os- x-lion-installation-disc/

2. Boot from FW; Erase my system drive; Install 10.7; (note: no migration, no time machine, just a fresh install) restart

3. Upgrade to 10.7.4; restart

4. Download/instal latest Mac Cuda driver (4.2.10)

http://www.nvidia.com/object/cuda-mac-driver.html; restart

5. Give Admin Automatic login; un-require password for sleep and screensaver

6. Instal CS6: PrP, AE, AU, PS, AI, FL; I did NOT launch any of the applications.

7. Launched AAM Updates Notifier; downloaded/installed all updates; restart

8. Launched PrP; it asked me to (click to) install Java Runtime; I complied; PrP downloaded Java, installed it, then launched.

9. I made a new project:

10. General tab: I left everything as is -- Renderer is set to the default "Mercury playback...GPU" (come on Quadro 4000, I'm rooting for you!!);

11. Scratch Disc tab: I set all capture/cache directories to a folder within my dedicated CACHE volume; I set the proj file directory to a folder on my dedicated project and media drive.

12. Sequence Preset: DSLR 720p24 @23.976

13. It took five seconds to load the interface, so I quit and relaunched; much snappier results on the second launch.

14. Edited a project with various h.264s from Canon 5D & Canon 7D; no problem, works great!

15. Made a 1080p24 sequence. Warp stabilize a shaky shot in that? No problem! Load the result into my 720p24 sequence? Sure! I'll even "Scale to Frame Size" (NOTE: Though i love the one-stop scale feature -- I've notice a bug or bizarre interface choice at this point: I have 1080p footage in a 720p sequence, I can see the whole frame but  the footage shows a scale of 100% in its effects control; the correct value is about 66.7%)

16. Highlighted all clips in sequence and initiated "Replace with After Effects Sequence"; It launched AE

17. AE Prefs; I left everything the same except -- I set all of my caches to a folder on my designated Cache drive. (Note: I point all disposable Adobe data to a folder called "CACHEs" in every App that gives me the choice on where to save temp stuff. Along with preferences, this folder gets emptied/trashed when things run-amok.)

18. Rotated, scaled, masked, vignetted and otherwise jacked around with footage in AE; was astounded to see near-instant update in PrP. Some clips had poor playback on first drag-through, but very quickly cached themselves and suddenly I was living the dream: not rendering in AE :)))

19. Sent sequence audio to AU; changed temp directory to designated cache volume/folder; it told me changes would take place after I restarted App, so I restarted and re-opened the XML PrP had previously sent to AU.

20. EQed and sent back to PrP; no problem!

21. Went back into AE; turned on raytracing, added some lights, shadows, bending... back in PrP things were a bit more sluggish on that clip as expected. (About the same as dragging through the AE timeline ) Rendered in PrP... Heard the Quadro fan kick in... Green lines, good playback...

CS 6 Production Premium | 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) |

I too have been having incessant kernel panic crashes in PremierePro CS6.  AfterEffects and other production apps are pretty solid, just Premiere that is problematic. I've been thinking it was having issues with scaling or files with alpha channels ie. both 4444 and animation, but, it appears to be anything and sometimes nothing.   I've tried turning off the CPU acceleration and it appears more stable then, but still on edge with everything I do.  I'd like to focus on the edit instead of saving after every click awaiting the crash.

I've run into issues on CS5.5 where I've used the dynamic link for MediaEncoder, then the file takes a month of Sunday's to save, so now I just duplicate the file to bring into AME.

Back to PPO CS6 I've done all the stuff, repaired permissions, reinstalled, monitor, no monitor, completely out of anything I can do on this end except, now creating a snow leopard partition  and moving program to that see if I can just get through a small edit running from that with the hardware accelleration off.

Dear Adobe, I hope you will address this issue.  It is making many of us macbookpro users absolutely crazy.  It is quadrupling the time I need to spend working on student stuff and instruction.

-------------

MacbookPro 2011 I7 2.0 Ghz - Lion 10.7.4 | 16gb ram - AMD 6750m - Lacie 4tb Thunderbolt Raid- CS6 Production Premium connected to external HDMI monitor.

I've been getting help from Tier 2 tech support, but alas, even after systems checks, mem tests, etc. the problems persist. 

Here's a blog post I just did on my four kernel crashes from yesterday and one already today.  My issues tend to be with using images I've brought in from PSD as .pngs. 

I also have had crash problems on Export straight from PR. 

http://claxtoncreative.com/2012/adobes-premier-pro-cs6-kernel-crashes- continue/

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.

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.

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!

I have a suspicion its to do with Dropbox and timemachine, when I stop both from running I hardly ever get crashes. I have a feeling it has to do with Premiere writing files to disk. Like I said it is a suspicion as I have done everything possible short of buying a new MacBook including calling Adobe support and re-installing Premiere Pro