CPU Overload (error 6101) on intel macbook pro

[Wolfgang Eller]

Originally Posted by DigiTechSupt

You can't do that. M-Audio devices are not compatible with FW800 drives.

Sorry, but where can I read this?

I can´t find it on the website or in the manual.

[cueball73]

same problem here. i get this issue constantly. i honestly have just lived with it, but really it is unacceptable and truly pisses me off.

it completely f$%ks with the creative process which is why i poured all my money into this company in the first place.

sooooo..... answers?

;-)

[JrummerJ]

Originally Posted by Wolfgang Eller

OK, but why do I have the same problem with a FW400 drive?

And why do I have NO problems after the first half an hour, anyway if FW400 or 800 drive???

What kind of drives are these you are having problems with? If you've read through the thread, you will have seen that I had major problems before, too. They seem sorted out now, everything runs great for the most part. VIs still seem to trip the cpu errors every now and then.

Anyway, if your drives don't have the oxford chipset then that could be the problem. Try a siig expresscard with fw400 ports. I had my WD drive (not Oxford chipset) working just fine with that setup, so maybe the expresscard helps even with non Oxford drives.

J

[JrummerJ]

Originally Posted by cueball73

same problem here. i get this issue constantly. i honestly have just lived with it, but really it is unacceptable and truly pisses me off.

it completely f$%ks with the creative process which is why i poured all my money into this company in the first place.

sooooo..... answers?

;-)

Well, don't just post, complaining, without leaving us some basic info on your setup, drives, etc and whether you have tried all the things in the general troubleshooting section. There is usually a reason you are getting this message, from drive chipset to using too many plugs at too low of a buffer, firewire networking enabled, etc, etc.

J

[cueball73]

fair enough. i have actually done all the troubleshooting in the past.

this problem has been prevelant throughout my last 3 MacBook Pros. and with 3 different interfaces...

but, my current setup:

MacBook Pro 2.6Ghz Core2Duo
4Gb RAM
200GB HD 7200RPM for system software and ProTools
External 500GB 7200RPM drive for recording connected via eSata on card slot

M-Audio ProFire 2626 into MacBook Pro direct. Nothing else daisy chained.

- Airport off
- Disabled sudden motion sensor
- Ignore RTAS errors is even checked
- Tried all sorts of combinations of buffer settings

CPU usage is never all that high, but it gets those spikes that cause the error in the middle of the most creative and wonderful takes of course. It's evil that way.

Originally Posted by JrummerJ

Well, don't just post, complaining, without leaving us some basic info on your setup, drives, etc and whether you have tried all the things in the general troubleshooting section. There is usually a reason you are getting this message, from drive chipset to using too many plugs at too low of a buffer, firewire networking enabled, etc, etc.

J

[JrummerJ]

Cuball73,

You aren't the first person I've heard of that is having issues while using an esata expresscard. I would try disconnecting the card and drive and see if you get the same errors just using the internal drive temporarily. If that drive has fw400, try chaining it the the 2626 and see if you still get them. Also, what kind of drive is it? What FW chipset?

J

[Wolfgang Eller]

Originally Posted by JrummerJ

What kind of drives are these you are having problems with?

It´s all Seagate drives. It´s 3 different (400 and 800). 2 of them (400) are working regularly on my PT HD without any problem since years.

if your drives don't have the oxford chipset..

They all have the oxford chipset.

EVERYTHING is what Digi expects and I still have the Problem.

Digi?

[cueball73]

i have a firewire 800 and 400 drive to try later as well.

the truth is i only got the sata card and drive after repeatedly getting errors with the firewire route

but, for the sake of argument, i will test out the firewire drives again later this weekend.

-r

Originally Posted by JrummerJ

Cuball73,

You aren't the first person I've heard of that is having issues while using an esata expresscard. I would try disconnecting the card and drive and see if you get the same errors just using the internal drive temporarily. If that drive has fw400, try chaining it the the 2626 and see if you still get them. Also, what kind of drive is it? What FW chipset?

J

[Wolfgang Eller]

So what did I do the whole sunday?
I set up a fresh OS with no additional programs at all, just PT on it and - the same error within 30 minutes.

Three times in a row after a restart.

What now Digi?

[guitates]

I will throw in my $.02, as I have had Great success with M-Powered on Intel MBPro - 2G ram (I have the first one made = No FW 800 slot, and only 2gb ram available) and a FW800 drive.

I also use LE at home on my Quad, but I will carry my FW800 Glyph drive back and forth from home to work, where I mix and Bounce on my MBPro, with 9 to 12 reverbs, and Full blown Strike, with all drum tracks recorded to 12 individual tracks and around 20 to 30 SSL plugs with up to 40 tracks (Music Production TK).

I have a Nitro A/V FW 800 card for my Glyph and I use M-Audio TRANSIT, and I do have to crank it up to 2048 to bounce, but the M-audio is very excellent with my FW800 drive, and I only use 2g of Ram.

M-Audio transit works great with FW800...

Hey - Get a Nitro card and a FW800. I actually used a FW800 EZQuest drive for a year, as I just got the glyph. Any FW800 with Oxford chips should work.

I can't imagine using FW400? Digi thinks this is better than 800??? go figure ?