CoreAudio Crashes but Pro Tools 9.0.3 on 10.6.8. v1.1 working

[studiozennyc]

Here is my system
-Mac Pro 2x2.93 Ghz Quad-Core Intel Xeon
-OS 10.6.8
-15GB 1066 Mhz DDR RAM
-Digi 002R audio interface
-Pro Tools v9.0.3
-USB Hub (3ft cable) with 2x ilok, Digi 002 (6' FW400 cable with FW800 Adapter connected to the Right Port in back), 2x Glyph GT50Q Drives (Daisy chained 6' FW800 cable)
-4x interal SATA drives, GUID Partitioned (1) Main - for applications and OS (2) Audio - for session files and audio (3) Sample Library 1 (4) Sample Library 2.

After updating to OSX 10.6.8 due to driver compatibility for an nvidia video card and Davinci Resolve, i have been having problems with my Digi CoreAudio Manager. Pro Tools v9.0.3 works completely fine. NO software nor hardware issues. All I/O's work fine.

When Core Audio Manager is launched alone it does detect the hardware.
When opening an application that uses Digi CoreAudio Manager, CoreAudio Manager Crashes. The application does not. This happen whether i open CoreAudio prior or autolaunch with application.
When i relaunch CoreAudio, it no longer finds the interface.
If i restart the computer, it is recognized again.

For testing reasons, i tried an older DigiCoreAudio v8.0.4, It works fine. But it v8.0.4 installed will not allow for Pro Tools 9.0.3 to launch. It seems to be the current Core Audio v9.0.3 giving me problems.

i have tried
-installing 10.6.8 Combo v1.1
-clean reinstalling Pro Tools
-downloading and reinstalling latest Digi CoreAudio manager
-un pluging all prepherals (USB, Firewire)
-check and remove unsupported plugins
-downloaded latest pace drivers
-Deleted Pro Tools, Audio/Midi, and CoreAudio Preferences Manually and with software assistance.
-repaired permissions on all drives and volumes
-used DiskWarrior
-Delete Database and Volume files

so lastly i Created a New Admin Account, but i am stil l having the same problems. Unfortunately i do not have a time machine backup with the previous OSX 10.6.4 install.

[gaffney film]

Have you had any luck with a solution for this? My system is suddenly doing the same thing. It was perfectly stable last week.

[TiPo]

I am also having the same exact problem with CoreAudio since OS X 10.6.8. Were you able to resolve your problem?