Yes seems so, right now have it in: 64 KB for playback and recording I/O cache, 11,6 msec 512 latency, with 14,0 msec and 618 samples for input or output ASIO reported latency, and seems to work ok, if turn off the wifi, antivirus, and any background process, will try 256 latency but not so positive about it anyway!

Stone House Studios

Jonbuho


What audio settings are you using? sampling rate 44100, 512 latency, playback and record I/O 256 KB
What is your reported latency? input 14,0 msec, 618 samples - output 14,0 msec, 618 samples
How many tracks are you trying to record? last crashed had 5 on playback and recording 1
Have you the latest drivers? from M-Audio guess so
Do you have any other programs running in the background? nope unless are system programs that i don't know
Have you optomized your laptop for audio? like how for example?

What audio settings are you using? What is your reported latency? How many tracks are you trying to record? Have you the latest drivers? Do you have any other programs running in the background? Have you optomized your laptop for audio?

Stone House Studios


What audio settings are you using?
What is your reported latency?
How many tracks are you trying to record?
Have you the latest drivers?
Do you have any other programs running in the background?
Have you optomized your laptop for audio?

There's more I'm sure - but having all of these items correctly set up will give you a good starting point!

Brian

Your latency seems high - make sure you don't have any other drivers besides the M-audio's selected.
 
What's on those 5 tracks?  As stated above, many do more with less. If you are running soft synths and FX, you should freeze to free up CPU for recording.  If it is all audio with FX, then again, bounce to tracks (saving and muting or archiving originals) while recording.
 
Again, that high of a latency tells me to look at audio set up - especially looking for un needed active drivers.
 
Brian

So anyway my happiness didn't last for much longer than few hours of recording (minutes), so took a deep breath and started what to do next. The only thing didn't try then was try it in WXP, so went through the not so easy way to boot my laptop in dual W7 and WXP 32bit. Installed and started to record and guess what, back to pops and clicks. So went through the old new setting up (again), and got back to the same setting that had on my W7: 64 on I/O cache, 512 on MAUDIO latency, it went good but it is still there, then disable a few drivers (have no antivirus) and turned the wifi off, and it went almost perfect, but it is just not there quite yet, maybe now the noise have turned in to imaginary pops and clicks, but i think i still can hear them in a very low level...

So there you go, now really have reached the bottom of my options. It is not W7 the cause neither W7 drivers of MAUDIO, neither antivirus, or background process, so what it is then? the hard drive??? but if it is so, i wonder why never had to deal with these issues back in 1999 - 2001, when used to work with whatever version was around then of Protools LE and the old Digi 001, and with what ever Mac (power mac G3 i believe) happen to be not so new back then?, my laptop it's million times better than that old Mac, and yes i know DAW's are much more complex nowadays, but why so much hassle? and btw, do not miss Protools neither Apple and not planing to go back there eeeeeeeeeeeeevvvvvvvvvveeeeeeeeeeeerrrrrrrrrrr!

Your hard drive could be a problem but as you said it could be a ton of different things.
 
If you haven't done it yet, there is a good step by step here.
 
http://www.native-instruments.com/knowledge/questions/847/Windows+7+Tuning+Tips+for+audio+processing
 
Good luck.
 
EJ

I would also check the DPC latency. An i3 should be more then enough but when one has the symptoms you describe its not Sonar or the card its the system. 

are there any other versions of the m-audio drivers you could try? i reckon it's the x64 drivers

i habe an i3 and run producer just fine..with synths effects..up to 30 tracks without a glitch..sounds to me your drivers are out of date or the interface may just have had its day
remeber if that interface is more than 3 or years old in most cases with windows 7/64bit..its going to give you problems and not be compat.

Hi Jonbuho,
on my HP laptop before running a SONAR session I need to disable my WiFi card in the Windows Device Manager. Otherwise I get clicks and pops as well. Try this.

Well first that anything, thank you all for the help...

Yes as @Jhon and @bentedgz recommended went and used the DPC latency checker and it went high as expected, according to that had to disable and try some drivers, did a bunch and the one that seem to work the best was the WIFI driver, so yes @Bzyk seemed it worked... Before i was just disabling the connection but not the driver, haven't record anything yet, but on playback seems to be doing fine, to soon to say loud VICTORY, but hope i will soon.

@chuckebaby well my interface is a M-Audio Fast Track, certainly not new but neither a dinosaur, and @pwal  remember i'm using now XP 32bit, the driver is brand new from M-Audio site (well the newest there i think is 2010 anyway), but that is latest...

Well if the recording goes fine, will post this thread as solved, i'm crossing my fingers anyway!

Back when I used a laptop and a M-audio fast track pro for Sonar I was getting pops and overall bad sound until I stopped using the laptop's usb to power the interface.
 
I got a powered hub and that did the trick! Worth a try.

Well did some recording and used 3 GuitarRig amps one on each channel with subs for each channel, and used session drummer to record a 2:30 min song, then played with those as backingtracks and did have almost no problem, yes ALMOST, actually felt so good that i would say it is solved but still not 100% sure, need to record more channels and a longer song to check if it really can cope with it...

Fantastic and cheap idea @boblette will get a active usb hub, maybe that will be the clue, thank you!