Still getting -9173 errors PLAY Kontakt info

[notedmusic]

Hi all. Anyone who has followed my harrowing journey knows that I am still trying to get the CPU errors resolved and I've had this issue for close to a year now with a windows machine, and two mac machines and with HD native and with core. I've had apple experts, the people from EWQL, and AVID look at my system and NO ONE can fix this problem.

At any rate... I found out that TEMPO changes trigger this problem every time. This is caused by a multitude of random factors, but I get it consistently with any kind of tempo alteration.

Something breaks with the combination of kontakt and play in switching tempos.

Still waiting to hear back from EW and AVID... my last conversation with them was several weeks ago.

Specs in my sig. Updated everything and optimized obviously.

Every release it seems to get a tiny bit more stable- I can get a few more instruments in, but still I have a ton of CPU left over, a ton of RAM left over and it throws the out of cpu message.

I'm on 11.3.1 now with 10.10.2

[notedmusic]

This dreaded error has haunted me from day one with PT.

[jryser]

Very odd. I had problems with this from 11.2 but not 11.3. Had a stable system all the way to 11.1.3. It is ok now.

[priyatsomo]

OMG!! this error code is the bane of my existence!
Just got my mac pro back from apple after they did extensive hardware tests and everything is fine on that end.
I just go through playback and then BAM -- the CPU shoots up to 100% and AAE-9173...or -9172... or -9171. ugggh.

Ive spent enough time on the phone with avid tech support in the past 3 weeks that I can recognize all three phone guys by voice. They say they have taken the problem to the avid developers or something, but it kinda seems like they might be starting to run out of ideas. The last thing they asked me to do was push a button on the mother board of the computer (which was unsuccessful) soo....

I get some weird stuff coming up in the console when the error code pops up like:

(2/12/15 2:03:50.000 PM kernel[0]: process Pro Tools[4294] caught causing excessive wakeups. Observed wakeups rate (per sec): 532; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45040)
and
(2/12/15 2:03:50.464 PM ReportCrash[4613]: Invoking spindump for pid=4294 wakeups_rate=532 duration=85 because of excessive wakeups)

Ohhhh I also have not noticed any relation to tempo changes however I will investigate further. I have noticed when I arm a track to record the CPU goes up. Have you noticed that?

Anyway, please let me know if you figure anything out for your system.
Best,
Priya

Mac Pro
Early 2009
Processor 2.93 GHz Quad-Core Intel Xeon
Memory 16GB 1066 MHz DDR3 ECC
Graphics NVIDIA Ge Force GT 120 512 MB
Software OS X 10.9.5 (13F34)
Pro Tools HD 11.3.1
PCI HD Native Card (in slot 2)
Avid HD IO 16/16 Analog

[lexaudio]

I've been on PT11.3 for about a week now.

With the lagging it has, and errors it really seems like a dog.

Is it just me or is Pro Tools REALLY going down hill?

They want us to pay annually for software that doesn't work?

MehAVID