New system drive now -9093 errors

[Tim R.]

My system drive failed, so I opted to replace it and do a fully clean install. After getting everything back to the way it was previously, I'm getting -9093 errors with only a couple tracks playing a single audio file with some stock plugins instantiated. I've trashed prefs, done recommended optimizations running ONLY PTs install plugins, pulled my extra I/O out, so I'm ONLY running the HD Native TB and OMNI.

[64GTOBOY]

Since you have been inside it I would first double check internals especially to make sure you didn't knock any RAM loose or something similar.

[Tim R.]

Originally Posted by 64GTOBOY

Since you have been inside it I would first double check internals especially to make sure you didn't knock any RAM loose or something similar.

Ah. Good point. Although, I'm troubleshooting further and indications at this point are that it is an issue with my OWC Thunderbolt 2 dock. Currently running happily (with stock plugs only) on the Mini alone. I'm missing my ultra-wide display that requires the Dock video card to work though. Gonna be a bummer if that is the culprit.

[64GTOBOY]

The readme's and several threads here show a lot of issues with graphic cards, or unsupported displays also , so keep that in mind

[its2loud]

Tim? Chicago Tim? “O” Tim?

What kind of drive did you replace it with? How did you format? I’ve had my dock cause errors but it’s odd that you’d only get this after replacing the drive. If you have a time machine backup of the old system try restoring and see what happens.

[Tim R.]

Originally Posted by its2loud

Tim? Chicago Tim? “O” Tim?

What kind of drive did you replace it with? How did you format? I’ve had my dock cause errors but it’s odd that you’d only get this after replacing the drive. If you have a time machine backup of the old system try restoring and see what happens.

The only difference is the OS was bumped from 10.12.2 to 10.12.6. The drive is same format/specs.

I'm currently testing the system with no dock and adding back 3rd party plugins individually and running a minimal test session for an hour continuously.

Strangely enough (and FRUSTRATING). This morning, when I booted up the computer and launched Pro Tools and opened my test session (same setup/plugins that were working last night playing for hours without issue), the CPU usage was sitting at 2% but spiking to 100% and I got the 9093 error on first playback. I quit and relaunched and it seems to be working now. WTF!?

[Tim R.]

Originally Posted by its2loud

Tim? Chicago Tim? “O” Tim?

Yes, I think. Do I know you? "O"....Ah.. "O" I get it. Yes, I'm "O"'s Tim. ; )

[Tim R.]

Update: This morning, playing test session fine (after a quit relaunch as noted earlier). I moved all the "Air FX" bundled plugins into the plugins folder. Launch Pro Tools and open my test session, and I'm back to spiking CPU. Quit and relaunch, and now it's seems to be fine.

[its2loud]

Originally Posted by Tim R.

Yes, I think. Do I know you? "O"....Ah.. "O" I get it. Yes, I'm "O"'s Tim. ; )

Ha Ha, Tim, its MG. How are you man?

[its2loud]

Originally Posted by Tim R.

Update: This morning, playing test session fine (after a quit relaunch as noted earlier). I moved all the "Air FX" bundled plugins into the plugins folder. Launch Pro Tools and open my test session, and I'm back to spiking CPU. Quit and relaunch, and now it's seems to be fine.

Wow strange. Frustrating indeed. Maybe delete and reinstall air plugins. Perhaps it was a bad install. You know how even the order you install things in Pro Tools could ruin your whole day.