I unplugged my thunderbolt display and no more Pro Tools errors!

[Brettster]

I have been having a hell of a time with -6101, -9173 (I think?) and similar errors. To the point where I could have a session with ZERO plugins and it would still lock up. My whole computer would slow to a crawl.

Well I just discovered a magical, but insanely frustrating solution. Apparently my Thunderbolt/HDMI connection to my external monitor was hogging up untold resources. When I unplugged that, my system ran like new again and no more Pro Tools errors. I was getting ready to sell my Profire 2626 I was so frustrated.

Unfortunately now I can't use my external monitor, which is totally unprofessional. This seems like it should NOT be an issue. Does anybody have any advice on why this is happening, and how to get both working?

[Carl Kolchak]

Look at disabling other hardware (some USB ports etc) and trying to re-assign interrupt requests.

Just by disabling something, a shared interrupt requests can be reassigned to a unique IRQ.

If you can manually change the IRQ's (some times that requires reseating cards in different slots, where possible - slot 1 having a higher IRQ priority over slot 2 etc) so much the better, but sometimes temporarily disabling something, can re-order a devices IRQ.

You want your Firewire card to have the highest priority IRQ possible (i.e lowest numbered interrupt) so that your interface, and any external hard drives, get their allocation of the computers resources ahead of less critical devices.

[Bruce Paine]

Since you are on a Mac, you may want to take a look at your Network prefs. No need for TB or FW to be enabled usually. See if they are, and disable to see if it makes any difference.

[Brettster]

Originally Posted by Carl Kolchak

Look at disabling other hardware (some USB ports etc) and trying to re-assign interrupt requests.

Just by disabling something, a shared interrupt requests can be reassigned to a unique IRQ.

If you can manually change the IRQ's (some times that requires reseating cards in different slots, where possible - slot 1 having a higher IRQ priority over slot 2 etc) so much the better, but sometimes temporarily disabling something, can re-order a devices IRQ.

You want your Firewire card to have the highest priority IRQ possible (i.e lowest numbered interrupt) so that your interface, and any external hard drives, get their allocation of the computers resources ahead of less critical devices.

I have no idea how to do any of that. I really need my USB ports though. I have my keyboard and MIDI devices plugged in.

[musicman691]

Originally Posted by Bruce Paine

Since you are on a Mac, you may want to take a look at your Network prefs. No need for TB or FW to be enabled usually. See if they are, and disable to see if it makes any difference.

You're talking about disabling TB and FW in Networking prefs right?

[zoff]

Originally Posted by Brettster

I have no idea how to do any of that...

It doesn't apply to Mac OS. He's assuming your on a PC.

[SpinningDisk]

I would just do a total clean install. Don't start playing with network crap. You shouldn't have too. Clean your disk and do a complete reinstall.
You didn't unplug the monitor while PT was running did you?

📀

[zoff]

Originally Posted by SpinningDisk

I would just do a total clean install. Don't start playing with network crap. You shouldn't have too. Clean your disk and do a complete reinstall.
You didn't unplug the monitor while PT was running did you?

📀

Much easier to disable TB and FW in Network preferences than doing a clean install.

[SpinningDisk]

Originally Posted by zoff

Much easier to disable TB and FW in Network preferences than doing a clean install.

Is that because of the HDMI? I have never had to disable anything. Not sure why you would😳

[zoff]

Originally Posted by SpinningDisk

Is that because of the HDMI? I have never had to disable anything. Not sure why you would😳

Why not?
Apparently the OP is having an issue that may be TB related. Most likely he isn't using TB or FW for networking, so why not disable it for networking, as a troubleshooting step.