Pro Tools 10 "quit unexpectedly" constantly after install!

[mr punch]

hi there

please help me. i can't get pro tools to open. i have done a fresh install of pro tools 10 and every time i try to launch it quits when it gets to "setting up midi". we are running a mac pro (2 x 2.4ghz quad core, 8gb ram) mac os 10.6.8, mbox 2 pro. we also run a logic setup on the same computer with 2 x rme pcie madi cards and 2 x iz ada converters.

this is a brand new install with no additional plug-ins etc. the mbox 2 is connected using a firewire 800 - 400 cable. there are no other firewire devices attached. the mbox appears in the system profiler.

i'd be grateful for any help.

[mr punch]

still got the same problem! anyone have any ideas? here is the beginning section of the "crash report":

Process: Pro Tools [229]
Path: /Applications/Avid/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 10.0 (10.0f821)
Build Info: Unknown-1000821~821
Code Type: X86 (Native)
Parent Process: launchd [116]

Date/Time: 2012-01-11 17:35:06.224 +0000
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 9532951 sec
Crashes Since Last Report: 21
Per-App Interval Since Last Report: 308 sec
Per-App Crashes Since Last Report: 18
Anonymous UUID: 5C9FD488-DC42-4204-A2C8-DBB2A00CE227

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000028
Crashed Thread: 39

[crizdee]

Originally Posted by mr punch

Crashed Thread: 39

Hi,

Can you show us thread 39 of the crash log.

Are you absolutely certain there are no old/previous plugins still installed on the computer!


Chris

[TheMuffinMan01]

This happened to me, it was a plugin causing the issue. I watched the loading screen, and determined which plugin was causing the crash (the one that was displayed as loading just before crashing) I removed that plugin, and presto, it worked.

[robs59]

How do I remove the plugin? Seems to be digirewire

[mr punch]

Originally Posted by crizdee

Hi,

Can you show us thread 39 of the crash log.

Are you absolutely certain there are no old/previous plugins still installed on the computer!


Chris

hi chris

thanks for the reply. here is the info...

Thread 39 Crashed:
0 ??? 0x2a25a80b 0 + 707110923

there are some waves and uad plug-ins that we use for logic, could they be an issue? pro tools crashes at the point of "setting up midi", no plug-ins are listed during the boot and it doesn't get passed the "setting up midi" stage. we haven't had pro tools installed on this computer before.

[mr punch]

sorry, i just checked and a bunch of digidesign plug-ins are listed during the boot up. it seems to scan though them all ok, then dae, then the "setting up midi" at which point it quits.

[thoma1c]

I'm having the exact same issue on a macbook pro, running 10.6.8. I have a fresh install of pro tools 10, and I can't get past even the first half-second of the launch - it just quits.

I've tried repairing disk permissions, re-installing, rebooting, removing all the plugins and the result is the same. PT just won't boot at all.

This is very frustrating, as I spent all this money to upgrade to a version of PT that is compatible with 10.6.8.

Any help would be appreciated.

[thoma1c]

I am having a different crash error though:


Process: Pro Tools [372]
Path: /Applications/Avid/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 10.0 (10.0f821)
Build Info: Unknown-1000821~821
Code Type: X86 (Native)
Parent Process: launchd [166]

Date/Time: 2012-01-12 17:29:51.590 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 2708190 sec
Crashes Since Last Report: 35
Per-App Interval Since Last Report: 35 sec
Per-App Crashes Since Last Report: 12
Anonymous UUID: CE96D273-2535-4F0B-B6F0-7F8939966832

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000910b12e7
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0x0537c000 0 + 87539712

[mr punch]

i'm surprised how many people seem to be having issues with this, reading elsewhere on the forum. surely it should just work after installation without any problems?

i wonder if someone at avid could offer some advice on this matter...