I did lower it as far it was able, to 64.

It might have done it or atleast it looks way better now and no dropout when testing.


The reason i havnt tried to change the buffer size is that before when opening the Asio panel, the actual asio panel showed up. Thats the way it always been for me.

With my latest computor when trying to open it, it would open up the avid mbox panel instead.. i had no idea why but i found out yesterday that in the setup menu i could change the buffer size and i guess thats the "new" Asio panel for me now.

Need some more testing but i´ll  let you know how it works out!
 
Edit: Have to ask also, if i have Sonar installed at C drive, and store the audio files on D drive, can that make this worse or be the problem?

Jens-Åke
With my latest computor when trying to open it, it would open up the avid mbox panel instead.. 

This is what it should do. The "ASIO panel" button opens the native ASIO panel for you audio driver, which in your case is the AVID MBox panel.
 

Jens-Åke
Edit: Have to ask also, if i have Sonar installed at C drive, and store the audio files on D drive, can that make this worse or be the problem?

This depends on how fast your drives are, but assuming both drives are of equal speed, having your audio files on a separate drive is generally a good idea.

From what i remember from past the asio panel opened and always looked like this https://imgur.com/a/oX6pr4m
But i get now its the same but in the mbox panel.
Took my slow brain a while to figure this out.
I upgraded from Sonar 8 to Platinum, maybe it changed between these two.
 
I fotgot to mention that my C drive is SSD 250GB and my D drive Sata, not sure but think its 7200 RPM.
 

ASIO4ALL is a wrapper around standard Windows WDM drivers. If you were seeing this on your old PC, then you must have installed this separately.
 
You shouldn't need to use ASIO4ALL if you're audio device has a native ASIO driver, which your MBox obviously has.
 
Native ASIO drivers will almost always perform better than ASIO4ALL.
 

If he was using Asio4all that would show in the screen shot. 
I found M audio drivers are not very good. At least my experience with a M audio fast track pro. It was always out of sync. Might work fine with pro tools on a MAc but was crap on a PC. Bought a Tascam and problem went away.  Just sayin' 

sock monkey
If he was using Asio4all that would show in the screen shot. 
I found M audio drivers are not very good. At least my experience with a M audio fast track pro. It was always out of sync. Might work fine with pro tools on a MAc but was crap on a PC. Bought a Tascam and problem went away.  Just sayin' 

Maybe in that case, installing ASIO4ALL is the answer!

I used a fast track pro for five years or so without a problem. I used asio driver mode. I did not manually set the offset.

I know i did install asio4all on my old system many years ago, but cant remember for my new computor, but it seems like i didnt!
I cant see that driver setting in sonar and i cant find the program in windows so i guess its a native asio driver as you said?
I had same problems with my old computor ( same mbox ) and it had as i said asio4all so i dont think that is the problem.

I tried to record some more today and it seems like its way better now after i lowered the sample rate to 64.
Who could have known that it would help in my case when the lip was to early and not to late.

Thank you all very much for all help!