OK I just Googled VCRUNTIME140.DLL I asked "What is it?"  Didn't find an answer but it seems Software installs it and it is somehow associated with C++ 
So this is  C++ issue I'm guessing.  
I will re install Sonar. I might just wait for the next release as possibly this one is the problem child. 
I will try a Roll back first? Hmm.. ideas anyone.. 
I'm first going to get some work done and deal with it later. 

It's just a C runtime library.

Cactus Music
Hi Dave.. I have to stay at 44.1 because my Yamaha 01v only talks that language. So sorry that is not my issue. 
Funny 48 didn't work for you. I originally used 48 back in  my M Audio 8.5 days. But when I moved my studio back home I needed the 01v so have been using 44.1 for years now. Just fine for my work as it's not going to end up on some audiophiles system :) 
Yes when I use Melodyne its mostly for the audio to midi conversions. I only used it for pitch correction on one project and that was about a 2 second clip. 
 
I may be forced to roll back to May which was my last update. Trouble is you really need to be putting in hours for this to happen. In the past I would only have a few hours at night to work.  
 
Just a note for others who may have insight into problem VST's
All the projects use more or less the same stuff 
Dim Pro  Full Acoustic bass all songs 
Session Drummer with my own sampled brush snare on a few songs.   
AD 2 on the rest
Air Mini Grand Piano on a lot of songs 
Mr Tramp ( 32 bit) on a few.
TTS-1 a few songs for percussion and misc.
 
Audio=  2  guitar tracks ( mike and DI )  using Effects send to reverb. Automated Volume. pan and effects.
one vocal track with Sonitus compressor some volume automation. 
 
LP 64 Multi band on MAster, Lexicon reverb, some songs Sontinus Delay. 
 
Pretty basic songs as I want them to represent what I sound like live so basically a backing track I use live and my guitar and vocals.    I

Notice you are using a 32bit plugin. I'd look there before anything else.

I would normally agree but I've been using Mr Tramp in 64 bit since 8.5. It's the only 32 bit VST I use and never seems to cause a problem before. Its only on 3 of the 14 projects and the crashes have happened randomly, I know for sure it's not the same project and the 2 that have the recovery files didn't use Mr Tramp. 
 
We I worked for 3 hours last night without a crash. I left the computer on line so if it did the report would be submitted. 
One weird thing was my computer completely shut down on me,  Sonar wasn't open I was reading the Event logs,   and then when it re booted it told me I had to re set my BIOS to the defaults. I had disabled the CPU throttling that Latency Monitor always recommends. So much for that. The default is AUTO so oh well. 
 
 
 
 

I started getting crashes and unexplained problems right before my C Drive failed.  It could be a sign that your hard drive is going.

The VC runtime is the runtime library for C++ objects. An unhandled exception (unexpected data) can cause the VC to be reported as the faulting module, but the underlying culprit is whatever was using that library. That could be Sonar, or a plugin, or even your audio interface console. To really determine the true source of any error, you must be able walk the stack trace in the debug data. Unfortunately, most of us do not have the object definitions installed on our local PC's so, while we can narrow down the problem, only Cakewalk can read the full stack trace and identify what actually happened.
 
It would be awesome if Cakewalk had a debug reader application that we could use locally.
 
Regards,
Dan

Run a virus check, Malwarebytes for example.

You may have picked up summat nasty.

Cheers,
Jerry

Lynn- You no that was something I mentioned earlier, my Hard drive is a first generation SSD Samsung and I remember they had a utility you had to run because there were issues with the storage becoming corrupted after so many cycles of read/write. It was defiantly on my suspect list. SSD have come a long way. I don't use the C drive for storage because it's only a 128 another reason to upgrade. It just a major hassle to swap drives and re install. In this case I would not wish to do an image as it's 4 years of crap on there. 
 
Thanks Dan I was hoping someone might understand the C++ issues. Sonar saved the crash dumps I just need to find the time to submit them. 
 
Jerry- my DAW is offline and never, ever used for any internet other than updating Sonar. I have plenty of other computers for that. I am a huge fan of my DAW is a studio hardware device,, and the internet is the very last thing needed to make that run properly. I didn't even use CCC for the first 2 years, I did offline activation. If I have a virus it came from Cakewalk, Celemony or XLN. 
 
 

FWIW, For the last few years, I've recorded all my projects at 96k, and I rarely have crashes in Sonar, when working on a project.  
 
When Sonar does crash, I usually find that it it related to a rogue VST, VSTi plugin, or a 32bit plugin has sneaked into my project (I've removed nearly all 32 bit plugins).  
 
Other culprits include my Roland interface driver.  I also keep an eye out for background tasks, running.  Things like updates, virus scanners, notifications, ect.

Thanks Dave, but as I said 2 of the projects that crashed did not have 32 bit plug ins. 
I'm seriously now thinking the SSD drive which I checks and it's at 80% as well> I forgot to clean out my CCC data folder after the last update but even then I think I'll just upgrade as a matter of this is my normal pattern. I always update my Hard drives every few years and put the old ones on the shelf,,, I even have my original 10 GB drive from my first PC! I'll turn the 128 GD drive into a back up's drive.