Basically thats what I'm seeing too. Too much CPU for not very big projects.  

When you don't have Sonar running, are you seeing any extraneous CPU activity in task manager?  Just trying to rule out the high-CPU issue I have seen on a number of Win 10 PCs (IT is my day job).
 
Bill.

I wouldn't know I rarely use the task manager. I am referring to the performance module in Sonar. 

I m still in ipswitch and i ain t moving ....if you guyz wants me to check but the thing is that to do it well we have to have the pretty same specs
Win 8 here i7 4790s

Personnaly i m noticing more dropout for no reason ( dpc latency exellent, 20 % cpu usage ) than previous versions , than x1 for sure with dropouts once a year !

It does seem like Lexington spreads the usage out over my 12 cores (visible with Sonar's performance meter and inside Microsoft's SysInternals Process Explorer (acting as a replacement for Task Manager).  The total overall CPU usage doesn't seem higher though to be honest, but I'm not rolling back to find out.  It does seem like more cores are active than I remember seeing before.  Could be my own fault though since I know I've fiddled endlessly the cryptic INI options.
 

Uhhh... so now I'm getting crackles while recording which I have not experienced since X1 and I replaced my old interface.
 
This is indeed disappointing and I do not have the time to sort it out with support just yet.
 
So is Sonar still being tested with Win7? Has that ship sailed?
 
I really hope I don't lose good takes due to crackles on this project. I have NEVER had to worry about this problem for YEARS. The worst that would happen is I would get an engine stop and even that never happened while tracking (only editing/mixing with playback running).
 
Ugh... guess I'm gonna have to adjust my workflow/buffers/etc to get through this project. Bad timing. I should not have updated yet.

Beepster
Ugh... guess I'm gonna have to adjust my workflow/buffers/etc to get through this project. Bad timing. I should not have updated yet.

Why not just roll back to Kingston ?
 

@PaulP...
 
Because previously I was on Foxboro (I had not installed or downloaded any updates in the meantime) and I am an offline installer so the rollback process isn't quite as elegant (and I've never done it).
 
Also I'm balls deep in a session so I can't be futzing with this right now. I should not have updated in the middle of a session but wanted to get access to the Aux Track stuff and (and performance enhancements). Lex seemed to be working well for everyone so thought it would be safe.
 
For now I'm going to have to keep working as is until the next batch of tracks is done then maybe I'll have to use the restore point I created before installing Lex.
 
I just can't be troubleshooting right now.
 
Cheers.

So freezing a couple tracks and nudging my interface buffers up a notch (which is juuuuust barely starting to introduce noticeable latency) has solved the crackles for now but I've never had to do that before.
 
Essentially it's not unmanageable but something ain't exactly right.
 
I just don't want to leave the impression Lex is totally fuxxored... but it is exhibiting some undesirable behavior for playback/recording audio.
 
Oh and those actions has knocked down the Perf Module CPU meters down a bit too. They are jumping a little more out of sync like I am used to (as opposed to staying in a relatively static and uniform line across all cores). Not sure what that means but that's what's goin' on.
 
Just reporting what I'm seeing so I can come back to this later when I can proeprly troubleshoot/report.

Try running Latencymon in the background, while you are working in Sonar.  It should give you an idea of what driver is using up the resources.  Usually on my system, it is the network driver.  
 
http://www.resplendence.com/latencymon
 
I don't get crackles on my system, until my performance meter (CPU) hits the red.  This only happens when I'm using some rogue 32 bit plugin or instrument on my 64bit system.   What I can't figure out is why only my first CPU core hits the red.  The other 7 cores are under 30%.