Check the I/O buffer in Preferences:Audio.
If you are mixing, a small buffer is not needed, and you can give Logic some "room to breathe" by using a larger buffer.
Next you need to establish if it is a CPU issue or a Disk issue: open the 'Performance' meters in Logic and have a close look.
Is the Project running from the System disc, or another internal (in a Mac Pro)?
I too was plagued by this problem on a couple of projects, part of a an album being finished at the moment.
Whilst some of the projects had over a hundred tracks and many many plug-ins and would run seamlessly.
Others, some of them only with less than 20 tracks and few plug-ins, would refuse to play for more than a few
seconds before the dreaded (-10010) would occur.
I am running all projects from internal dedicated Sata drives for, Audio and separate internal Sata drive for samples. 64 bit, 16Gb Ram
I tried just about every suggestion I could find on all of the usual websites to no avail.
So I muted all tracks in the project and opened them one by one.
It became apparent that the tracks which caused the problem had been transferred from a ProTools 6 session.
I had noticed when I started working on them that they did not have any of the usual identifiers (.aif.wav. etc)
but Logic seemed content to import and play them, except that they semed to eat up HD transfer rates causing
the (-10010) error.
I copy/converted the tracks in question and the problem was resolve.
I am sure that this is not the only cause of this error, I pass on the experience in case it helps.