I have done this many times without issue. Recording vocals, multiple looped takes around 4 minutes long. 12 times without stopping. After recording, the tracks are not set in time correctly and are randomly out of time.
1 in 4 is set right in time with the backing track.
I’m not using track lanes. I don’t have time for a learning curve. Has anyone else had this issues?
The problem has a definite tell. As recording, the backing track will go silent for a second then come back.
On playback there is a static click, Then the track changes its space in time.   

Good day,
Did you happen to notice if some of the loops have measures that are not complete. I had an issue when the loops have slight 'open' measures at the end. These items cause blank, sometimes clicks, and accumulates to cause timing issues.
Hope this helps,
MJ
 

Hum? I don't think that's the same thing I'm dealing with.

How many hard drives do you have in the setup using CW more info on system specs...perhaps making the system of one drive (if that is what is being used with os and your setup?) into many independent drives of fastest types possible put...supposedly fragmentation of drives and data ...in windows 10 is buggy?
 
Reading into win 10 and issues with...is now more issues to look deeper into...?
 
Not easy without more intel of system build...and RND....
 
 

Sounds system/project-specific. Need more info:
- Have you rebooted recently?
- What interface, driver mode and buffer size? Any changes recently?
- If ASIO driver mode, is 'Use ASIO Latecny enabled in Record Latency Adjustment, and/or do you have a non-zero Manual Offset entered?
- Does the looped region start at 1:01:000, and if not, are you starting recording at the loop start point?
- Are the loop points snapped to measures/beats?
- Is punch also enabled?
- Is metronome count-in enabled?
- What tempo? Any tempo changes?
- Direct or Input monitoring?
- Are there any PDC-inducing plugins in the project?
- How much error/variability are we talking about in samples?

If your interface has poorly written drivers or your using anything but ASIO you will have this issue. Perform a lop back test to see if this is the case. Freeze a drum track and lop it from audio interface output back to a new recorded track. Zoom way in and see if it records out of sync. This will happen when the driver lies to Sonar. If so you ( best idea) buy a better interface, adjusting the manual offset and hope for the best. Below you can clearly see that my Scarlett and Tascam are in sync with ASIO mode, But the Tascam starts to be late when in WDM mode and way out in MME mode. Note that the new WASAPI mode was closer to ASIO performance but still not perfect. 
 

Here, I found the screen shot with WASAPI. So note that all tracks in all modes are out of sync except  ASIO which is at the bottom. 
 

I have done a loopback recording and mine drifts like one of those race cars .
 
Snow edition RME Babyface < not blaming this but its what i use
1)totalmix fx loopback recording into sonar : bad drifting
2)FL Studio rewire : bad drifting
3)ableton : perfect sync at 2048 buffers BUT disconnection bug currently on large projects
4)Kontakt 5 : drift is small and ( importantly in time ) so we can use the midi offset
5)jack audio : loopback into platinum SHOCKING DRIFT + when you zoom in and look at a wave you just recorded it has changed forever .
 
glitch and drift : my arch enemies i find time for here and there to battle my demons
 

i am having the same issues since the update
i rolled back 
but no help
timing for sonar plat has always been glitchy for me