Error 10010 CoreAudio

Hi!
I've got a session of 32 tracks (I've had much more before), 8 audiotracks and 24 audioinstruments.
When I try to play the song the moment everything comes together Logic stops and I get "CoreAudio error 10010 disk too slow or System Overload".
My audio prefrences are : i/o buffersize 1024
proces buffer range LARGE
I've also changed the settings but it still stopped at the climax...
Can anyone give me advice?
Thanks in advance

Blay-
Ive seen you answer on other threads. Do you have any other advice re: CORE AUDIO SYSTEM OVERLOAD (-10011) ? You seem to say to get another hd on the other threads as well.
I have two (2) G-DRIVE Q's hooked up to a SONNET TEMPO SATA EXPRESS CARD. I have 2 gig of ram, running 10.4.10 and Logic 7.2.3. I shouldnt be having this issue of "core audio system overload". My 500 gig G-Drives have all my media- my internal hd's are just running Logic. My plug-ins are on the ext G-Drives as well. My M-Audio Firewire 410 is on a seperate buss than the ext G-Drive hard
drives so that shouldnt be the issue. I keep reading peoples responses but they arent so true. Do you have any other words of wisdom or insight on this matter hearing my setup? Im just trying everything I can to figure this out.
Thanks

Similar Messages

GarageBand Error -10010

I hardly use my MacBook Pro, though it does have all my main apps on it. I used it to record vocals singing over music played by another computer before with no problem, but today when I tried recording and playing back, the error kept popping up to say my MBP is too slow and asked me to check out Apple's Help to optimizing GarageBand. All the suggested methods + googled methods didn't work, so I deleted and reinstalled GarageBand. It STILL had the same problem, except now it added the Error code 10010 or something like that. If I exported it to listen to it via iTunes, I could play it back fully (unlike in GB), but there was a "compressing" **** noise throughout the whole track.
I am recording onto my INTERNAL DISK not using any extra disks. Tried all methods since 2009 articles (same problems for them...) but to no avail.
My MBP is OSX 10.9, 2.9 GHz Intel Core i7, 16GB MHz DDR3.
What is the problem and how could I solve it? I've deleted A LOT of stuff on my computer and emptied the trash, and the same problems still occur.
Thanks in advance!

i having the same problem too.. this had impacted my whole working environment after upgraded into OSX. Typing also choppy, video playback also choppy.. i don't see anything good on this OSX so far on my MBP mid 2012. sad sad sad

DCOM error - 10010 - Server 2008 R2 Standard

My server is generating a DCOM error with GUID : 995C996E-D918-4A8C-A302-45719A6F4EA7
I did some research and found that this should be due to Auto play being enabled, I disabled it and restarted the server but the DCOM event is still happening.
Another DCOM event is also generated by GUID B286F068-5B17-4AE8-989B-8F9A199C47BA which refer to an HP printer DLL, no one is having any issue with the printer so wondering why it is logging that event.
Any idea ?
Thanks

Hi,
Regarding to Event ID: 10010 Source: DCOM, please refer to the following thread. It provided the possible causes
of DCOM Event ID 10010.
DistributedCOM Error ID 10010
http://social.technet.microsoft.com/Forums/windowsserver/en-US/77b1db1d-f186-4515-8f7d-2241942eb9b7/distributedcom-error-id-10010?forum=winservergen
Based on current situation of this problem, please use
sfc /scanfile command to scans integrity of this specified DLL file. And then check the printer and make sure that install exactly the right drivers. Meanwhile, please find if can update
the printer driver.
By the way, you can use
regsvr32 <filename> command to re-register the DLL file. Then please monitor if the Event ID 10010 still persists.
Hope this helps.
Best regards,
Justin Gu

Error -36 coreaudio

Hello
I searched around this forum and the rest of the web but could not find any similar problems to the one I have.
When using garageband, I get this Error code -36 from coreaudio and the program stops reading the track. This happens when trying to read or even record a single track, within the first 5 seconds.
I have used the Disk Utilities, yet nothing comes up, everything seems ok.
I never had this error with other applications (itunes, dvd, ...).
What would be the problem and the solution?

a -36 is an I/O error, it generally means the file is corrupt. I would suggest deleting the project and starting fresh B-(>

Disk is too slow or System Overload Errors(-10010)

Hi, It may have been a mistake, but for the 1st time in a long time, I updated my system and software two days ago, after which i tried to runm Logic 9. During playback, I am not getting a random error message that "Disk is too slow or System orverload. This is a system that has operated error free for the past eighteen months, no problems, until now! What really puzzles me about this is the part about "motion Sensor" ! My system is a Mac Pro Desktop unit and not a laptop, and definitely not equipped with and motion sensor(s) at least not that I am aware of.
Can nyone shed some light on this for me?
Thanks in advance

Hi
rockfort wrote:
Did you repair permissions after the OS update?
** I don't know how**
To repair Permissions, in the Finder, use the Go:Utilities function, and run Disk Utility.
In Disk Utility, select the boot drive partition on the left and click on "Repair Disk Permissions".
rockfort wrote:
Free space on the OS and/or Project drive(s)?
** 1.78TB space free on the drive**
So, are you recording /playing back your projects from your System drive?
This is not generally recommended. Instead one should really use an second (Project) drive either Internal (no good for an iMac) or external Firewire/Thunderbolt drive (depends which iMac you have).
Further, the error message you have been getting is a general "Disk too slow" and/or "CPU overloaded" message.
It would be worth keeping an eye on the System Performance meter in Logic whilst playing the project (Double click on the CPU meter in the Transport or use :Options:Audio:System Performance) to see if it is CPU or Disk related
CCT

Error -10010?

"Disk is too slow or System Overload."
This is the error that pops up when I try to listen to one of the logic express demo songs. What does this mean and how can I fix it?
I'm on a brand spankin' new macbook pro that I haven't quite figured out yet.
A lay-response would be much appreciated.

Hmm...I cant even find that error number in apple's own list
(see my post on another 'users' cryptic message)
http://discussions.apple.com/message.jspa?messageID=6568577#6568577
However I have noticed in my own experience that I often get this 'overload' message when simply plugging in my headphones while the track is playing, I get error -10011.
'System overload' The audio engine was not able to process the data in time'.
I then click the continue button and then the play button.
I suppose that doesn't help much, but in my case it seems to point to a problem with the audio-out device being used.
If i then follow my own advice and look in the console app I see a message from the console messages saying 'audio engine overload' which as you say isnt helpful at all.
I don't think it really is a 'system' overload as I can play a single track loop and get the same error. I think it is a 'bug' plain and simple. However at least see
http://docs.info.apple.com/article.html?artnum=305927
do simple stuff like make sure that Logic is the only thing running (shutdown all other apps) make sure you only have on session open etc etc. Also see if you can change any settings in system preferences for 'sound' regarding the audio out...this is all a bit 'in the air' troubleshooting to be honest, but as far as I can see this is an error from the logic software than the apple OS.
but they don't give you much to go on at all.
P

Error message CoreAudio: Invalid input setting (-10021)

I was recording a guitar part (thru an M-Audio MobilePre) in the 24 track template (all audio tracks) on track 2, and there was a keyboard part already recorded in track 1. I tried to arm track 3 to do a second guitar part, and I got this error message. Suddenly, none of the other tracks will work -- only 1 and 2. If I open a new file using that template, it now gives me only tracks 1 and 2 to use, while all the other tracks have the same error message. If I open a Basic Setup, however, with audio, inst, and MIDI tracks preset, all the tracks will arm just fine. How do I fix this so I can use the 24 track template again -- it was working just fine! In fact, I reloaded the whole program hoping that might help, but no. Also, if I stay in the Basic Setup and create another track, why does the one above it arm at the same time (both rec lights go on)? How can I separate those? Thanks!

It sounds like you probably are trying to specify your recording input through an input on your interface which doesn't exist, or one of your previously recorded tracks are still in use. So 1st make sure that your other tracks are not record enabled, then make sure the input of the track you are recording to is set to either input 1 or input 2 (depending on which input you are using). I believe the UA-25 has only 2 inputs, so you will only be selecting those 2 when recording audio.

CoreAudio: Disk is too slow (Prepare) error message?

Hi,
In a Logic project I'm currenly working on, each time I open the file and press play for the first time, Logic hangs for 15 seconds or so and gives me this error message:
CoreAudio: Disk is too slow. (Prepare)
(-10001)
If I then stop, rewind and play again everything works fine. It only happens after this specific project is first opened and played.
Any ideas what this could be about? Disk is definitely not too slow. I get the same error if I start at a one track passage or bypass all effects and then play.
The file in question contains imported AIFF files, imported MP3 files as well 100 or so MIDI tracks.
Logic version is 7.2.1.
Thanks,
Maarten

It's in the energy saver preferences, uncheck spin down drive when idle thing.
HOWEVER, I posted this in another post, there is a bug where external firewire drives are still getting spun down with this checked off. I reported the bug to apple, they asked for more info, they said thanks, and last I checked the bug was still open, which tells me it wasn't reported before, and they're actually working on it.
So don't be surprised if unchecking the box doesn't fix it for your external drives.
The trick I use to get around it is simply double click the file on the external drive to open the song. That spins the drive up pretty good because you have to open a finder window which has to list all the folders etc...
hope this helps.

Insight / resolution on "disk too slow" -10010 errors

Got this error after upgrading to my 2009 13" MBP with Logic 8.0.2 and 10.6.2. 8 measly tracks with a few minor plugins. Worked fine on my 2.2 GHz '07 MBP with 10.5.8 but no go with the 13", repeatable error -10010 without fail. Reminds me of the same issue I had with Digital Performer which pushed me to switch to Logic.
Currently running 10.6.2/4 GB RAM/500 GB 5400 RPM HD on the 13". Error happens randomly but usually within a minute or two.
Resolved by...
1. Installed minimum OS on the 13" (10.5.7).
2. Updated to 10.5.8 using combo updater, but ran no other updates.
3. Installed Logic 8.0.0 with no updates.
4. Tested same project that previously had errors; ran OK, with no errors or overloads.
Repeated same process on August '06 8 core 3GHz Mac Pro. Ran OK.
5. Installed all available updates, errors returned. Installed same updates on the Mac Pro but it still ran OK. Updates installed that resulted in the error returning are listed below. I haven't narrowed down which update/s cause the issue yet, but since I have Logic on a separate partition and OS I don't care to install updates that are supposed to "fix" what isn't broken. Everything works fine without the updates. Been through this scenario before with Final Cut Studio. My other OS partition runs FCP and CS4 along with my day to day apps just fine with 10.6.2.
Updates installed resulting in errors in Logic:
Logic Pro 8.0.2
Pro Applications Update 2007-01 1.0
MainStage Update 1.0.2
ProKit Update 5.0
PluginManager 1.7.3
Remote Desktop Client Update 3.3.1
Pro Applications Update 2008-05 1.0
AirPort Utility Software Update 5.4.2
QuickTime 7.6.4
Java for Mac OS X 10.5 Update 5 1.0
iTunes 9.0.2
Performance Update 1.0
Safari 4.0.4
Security Update 2009-006

Clancy,
No problem!
I also added it to the Useful links and resources for Logic Pro X page in the tips sections....
Cheers..
Nigel

I'm getting the 10010 disk too slow error in Garageband--Macbook running 10.9.1

Hi--I know this error has been posted about a zillion times already, but I haven't seen it in relation to Mavericks yet, and I was wondering if anyone had any current info or fixes.
I'm trying to record audio in Garageband 10.0.1 on my 2009 Macbook (4GB 800 MHz DDR2 SDRAM, 2.13 GHz Intel Core 2 Duo) running Mavericks 10.9.1. I'm getting the "Disk too slow" error -10010 after recording for maybe a minute. I honestly don't think it's my machine. I've seen so many older posts about possible fixes that it looks like it's something to do with the OS.
Apple provided a possible fix in 2009 for Leopard and Snow Leopard but I haven't seen any similar fixes more recently. Thanks for any insights!

i having the same problem too.. this had impacted my whole working environment after upgraded into OSX. Typing also choppy, video playback also choppy.. i don't see anything good on this OSX so far on my MBP mid 2012. sad sad sad

Error message: "Disk is too slow or System Overload."

When I try to record from the line-in on my MacBook Pro (2.16GHz, 2GB RAM, 100GB 7200rpm HD), I get after some time (that can range from a few seconds to a few minutes) the error message: "CoreAudio: Disk is too slow or System Overeload. (-10010)".
This is weird because I get that error even when recording into an empty project. I have no such error on my old PowerBook G4 (867MHz, 512MB RAM) with the same version of Logic Express (most recent). Both computers are fully up-to-date.
I also get that error on my MacBook Pro very often when I'm working on a project and it's getting pretty annoying, it sorts of halts the process each time...
I also have Mail, iCal and Adium running at the same time as Logic Express, none of which use much CPU so the problem can't realistically be from them...
Any help to resolve this issue or at least shed some light on the potential cause would be greatly appreciated!

Simply having idle applications in the background is probably fine, but I certainly believe that something like Mail checking for new messages in the middle of recording in Logic could cause problems.
I would also check Activity Monitor to see if you have any background processes running that you aren't aware of. My wife's iBook slowed to a crawl once, and I discovered that a printer driver she installed to use a printer at work was using about 80 percent of the CPU.
-Eric

Disk too slow and system overload error

I like many other users am having problems with the "disk too slow or system overload error (-10010)." It only seems to occur during playback attempts, seeing as I recorded with no problems yesterday, and only began happening today (granted, I have not tried recording anything since this started happening). I have tried changing the buffer size (still occurs at all levels), and, as per noted in a similar post, ensuring that my computer does not at any time put drives to sleep. All my sessions are stored on an external Toshiba Canvio Connect 2.0 TB drive connected directly to my computer via USB.
My setup (I know that this is going to draw a lot of criticism) is a macbook air with 2 gb 1067 MHz DDR3 ram and a 1.4 GHz intel core 2 duo processor, running OS X 10.9.3. While I am fully aware (I promise) that these are well below the recommended numbers, I have been using this configuration since June without any problems whatsoever.

Clancy,
No problem!
I also added it to the Useful links and resources for Logic Pro X page in the tips sections....
Cheers..
Nigel

Logic 9.1: Disk is too slow or system overload (-10010)

After updating I kept getting this error: Disk is too slow or system overload (-10010)
Can't go five minutes without encountering this. I'm in 32 bit mode using record via rewire. It's maddening and I am now kicking myself for updating. The song that's doing this is a song I was using working on the day before I updated. I had no problems then.
Anyone else encountering this?

I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

Error message!!!!!Disk is too slow or System Overload this keeps coming up?

Logic Pro:
Disk is too slow or System Overload
(-10010)
Mac book pro
10.5.8 OX
4gigs RAM
recording to ext 800 firewire drive
any ideas???

I am just reposting my response to a similar question because I never found a solution to this problem just a work-around. I would love to know the actual solution.
I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

Continued DCOM Errors on Server 2012

We started noticing this error reoccurring after I set up a Powershell routine that sends daily emails to us with the errors from the systems Event Viewer log. At first it was once or two a day and today it was 5 yesterday it was 7. We are constantly
getting the follow error on our 2012 server:
The description for Event ID '10010' in Source 'DCOM' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information
is part of the event:
'{73E709EA-5D93-4B2E-BBB0-99B7938DA9E4}'
When I use a Powershell routine that returns information about all the DCOM's I get this:
Application ID: {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4}
Caption: Microsoft WMI Provider Subsystem Host
Description: Microsoft WMI Provider Subsystem Host
Installation Date:
Name: Microsoft WMI Provider Subsystem Host
Status:
So Powershell script says it says it is there. Then how can we get the error message that the DCOM cannot be found? We have ran a malware program on the server and come up with nothing. Checked the registry key and everything there seems to be
set correctly. Checked for server updates and there are none. Checked for Firmware updates (Dell PowerEdge Server) and nothing there either.
Of the 10 or so servers we have, this one with Server 2012 on it is the only one that giving us these errors, or any errors (not including Terminal Service errors), and we would like to find out what the problem is and correct it.
Thank you for any suggestions.
Mark

I am still getting these errors more than 10 times a day during the week but hardly any on the weekends.
Server
Event Time
Type
EventID
Source
Message
VOLCANO
08/27/2014 07:54:11
Error
10010
DCOM
The description for Event ID '10010' in Source 'DCOM' cannot be found. The local computer may not have the necessary registry information or message DLL files to display
the message, or you may not have permission to access them. The following information is part of the event:'{73E709EA-5D93-4B2E-BBB0-99B7938DA9E4}'
I had changed the power settings to every 5 hours which should have only given me 5 or 6 a day but I was getting as many as 15. Hard Drives were set to not power down. So I am not sure that the 'Sleep' suggestion in the one article is correct. But
this morning I went and put the power setting to never for the display.
Any other suggestions?

Error 10010 CoreAudio

Similar Messages

Maybe you are looking for