One suggestion a very helpful Adobe guru gave us initially was to try starting the App with the SHIFT+OPTION+COMMAND keys pressed (where SHIFT resets the plugin cache, and OPTION resets preferences - no idea what the COMMAND button does to be honest), to basically give Premiere a "clean slate". However, we've found that on multiple systems holding down the SHIFT key crashes not only Premiere, but the entire system. Premiere will store when loading a random bundle (never the same bundle it seems), the CPU will run at 100%, and the whole system needs a hard reset. At first I thought that maybe it was one of our Red Giant plugins causing the crash - however upon uninstalling all of our Red Giant plugins that didn't fix the problem. It leads me to think that there must be a memory leak budget - given that Premiere seems to crash at different bundles each time. This is repeatable on multiple machines - again, I assume it's a bug. I would be interested to see if others can reproduce too.

Now that we've removed the Avid & Blackmagic codecs from the systems - it'll be interesting to see if Premiere is more stable and responsive - as we've been having crashes every few hours since updating to the latest Premiere 8.0.1 release. It's been EXTREMELY unstable and reliable. We thought it might be related to the fact we use Red Giant Colorista a lot, and a lot of our media in projects is R3D files - but I think legacy QuickTime seems to be the main issue. If others are noticing 'Adobe QT32 Server' crashes/stalls - try removing the Blackmagic and/or Avid components and see if that helps. If it doesn't - try removing ALL of the components temporarily and see if that makes a difference, then narrow things down to find the culprit. Hope this helps others!

Any questions let me know!

Best Regards, Chris!