A single 1010 should be fine (although certain versions of them had issues with transistors or capacitors or something going bad, I'm no technician, but whatever they were they were flaky to a certain batch/version, and had to be replaced in many cases) , the latest driver version was 6.0.8 which works fine with Windows 7 and Windows 10, the previous driver not so much. I always ran the 1010 at 128.
 
You could also try transferring all your tracks etc (a PITA I know, but) to a new project. I had various strange issues in SONAR that were cured by doing this. That's part of the reason I jumped ship 3 years ago because of all the flaky stuff that could happen in SONAR, none of which I have seen again since I switched.
 
I still have 1 machine running with a 1010 (I have 3 more stored away) and it is fine with Windows 10. The flaky issues I observed with SONAR weren't related to the 1010, as they also occurred when I swapped out the 1010 for the RME on my main PC, and as I said once I jumped ship from SONAR I never encountered these strange issues again.
 
Also, from memory (and I could be mistaken, it was a long time ago) that either the 1010 with Windows 7 forward, or the 6.0.8 driver forward (the last driver available) daisy chaining multiple 1010's together either wasn't advised, or supposed not to work properly. In the XP days I use to chain 4 of them together effortlessly, but stopped when I moved to Windows 7 because of the changes that occurred, I think they also took away something in the latest driver that aided multiple card use. It may or may not work for you, some say yes most say no, I dropped it because I no longer needed to chain them and because of the possible issues reported. A quick search pulled up this
 
http://community.m-audio.com/m-audio/topics/have_the_win_7_drivers_been_fixed_to_support_synching_two_delta_cards
 
But as I said, restarting in a new project did fix up some strange issues I came across in SONAR, I just chose not having to go through the bother and moved on. No more issues, problem solved.

Perhaps this coukd shed some light on subject as im still dealing with the issue...im running delta driver 6.0.8..win 10 32bit..so if im playing back my recording it plays fine..my stereo master out is 1010A channel 1 and 2....if while playing back i open a plugin with alot of visual for instance the eq in the pro channel..that's when it starts clicking and the track actually slows down...so i changed my output in master to my 1010B..when i plug in my trs wires to the output of 1010B i get really bad buzz..loud buzz...but when i play track back i can just hear it enough to tell if it changes when i open eq...from what i can tell through the buzzing the project is not slowing down and clicking...does this tell anyone anything ?.i also tried to get that latency monitor but site is down

Scratch last post..pretty sure its still slowing down...perhaps the outputs of one of the 1010 buzzing tells something ? Someone mentions dsp ?

Not sure why your sync setting says internal. Sonar should sync to audio. Also, are there settings in the audio driver for clock source? The clicking and slowing sound like the interface is freewheeling and not running at a stable rate.

bvideo
Not sure why your sync setting says internal. Sonar should sync to audio. Also, are there settings in the audio driver for clock source? The clicking and slowing sound like the interface is freewheeling and not running at a stable rate.

+1  SONAR should automatically switch the Clock Source to 'Audio'; 'Internal' works only for pure MIDI projects driving hardware synths. Also, check Playback and Record Timing Master selections under Preferences > Audio > Driver Settings; both should be channels of the same device.
 
But if video activity is affecting it, you might have some kind of hardware/driver conflict and need to roll back some update. Have you recently moved cards to different slots or made other hardware changes?

I've had this issue years ago running duel 1010's running on win 7.
 PCI audio interfaces seldom to never have latency issues as do external USB and Firewire interfaces do.
 Which pretty much narrows it down a physical failure and or corrupted drivers.
 
 I had solved my issues by covering as many of those bases by simply pulling out the 1010's cleaning dust from the cards themselves and blowing out the PCI slots as well, and swapping them out between PCI slots, which will force the drivers to install to the new locations.
 However uninstalling the drivers, rebooting the computer, and reinstalling the drivers fresh gives a better guarantee against driver package corruption.
 Certainly worth a try, but make sure you have and know where a saved your I/O patching and configuration settings to a user defined file to save yourself a considerable amount of extra work and frustration.
 
If problem persists I'd pull one and try running 1010 at a time to isolate the problem for component failure on one of the cards. Keep in mind these 1010's are at least 15+ years old.
 I was still running win 98SE when I installed my first Delta 1010 LoL. I'm actually shocked and amazed that M-Audio supported them all the way up to win 7x64!
 They do NOT offer support to win 10 where they may or may not be usable, 'tis a crap shoot.
 I've read reports of some using them without issues in win10, some reports that they don't work at all.  The last of my 1010's got extremely flaky and unstable in my living room computer which was just used for playing music and surround sound DVD playback, (nothing hooked to it supported ASIO drivers) went PITA after upgrading to win10 and would always default the clock setting to 44.1k/Hz upon boot up and have to be manually set to 48 k/Hz to get any sound at all.
 I'm thinking it didn't like the new and improved Windows sound drivers? Why does the clock need to be set to 48 k/Hz to even play CD's or .mp3's in Windows Media Player???
 And what even more confusing is how in the name of Zeus's butt hole did my grand daughter figure THAT one out?

Thanks for all replys I changed the mme or whatever they are drivers to asio and it works better...occasionally it acts up, i found when it starts sounding odd i stop playback and turn off or on "global record arm"..then the noises are gone when i continue playback...very odd

Yup.. latencymon.

Do you have any other DAWs installed?
Completely uninstall any virtual drivers like ASIO4ALL as well (if installed). Reboot..

You were using MME...??? No wonder, funny nobody even asked that all important question which is usually the first one...   "Are you using the latest ASIO drivers?"  standard reply. 
And at no point did you say you ran latency monitor,, which no matter is worth while on any system. 
 
Alex... you said you were leaving? Your addicted, admit it :) 

I'm leaving.. :)