I was working on a 14 song album all week and logged a lot of Sonar time over this weekend :) 
 
First the first time in years I was experiencing Crashes :(
 
Edit Monday to change title & add the event log here too: 
 Looking in event log   all of them say SONARPLT.EXE  and this is also the module fault only 2 said otherwise. 
Aug 11 1:31PM 
Aug 22 8:39PM 
Aug 25 8:50 -- this might be it!!   module fault  VCRUNTIME140.dll   main app was still Sonar
      11:59 PM 
Aug 26 1:47 PM
            3:28PM   Module fault Adictivedrums.dll 
            6:01 PM 
Aug 27  2:59PM
            4:27 PM  
            
 
I never lost anything as I always save as I roll along and Sonar successfully created recovery copies which I had to use twice.  
 
The very first time I had just inserted Dim Pro and when I clicked on the GUI to select a patch I got the warning. 
Then twice as I was just closing a project. 
Once when I came back after lunch and touched the mouse note_ all sleep settings are off other than monitor 1 hour  
I also opened Melodyne to fix a little flat note on the guitar and Sonar immediately crashed twice in a row. 
 
The reason for the title is I have used Melodyne to convert all my audio bass tracks to MIDI so every project has Melodyne running,  unless its gone once the conversion takes place. 
 
I saved most of the crash dumps and I guess I need to submit them somehow. My DAW is off line so they don't go automatically. 
Tonight I will enable the network adapter and figure out how to submit them. I will also just leave it on line until this is solved.
 
So I spent an hour trying to see what had changed to make my DAW do this all of a sudden. 
Windows just updated to Creator a week or so ago and I also  updated Splat. 
At first Latency Monitor showed marginally bad @ 1,000 u. It shows Windows USB hub as most active so I unplugged everything other than my wireless mouse/ keyboard and it still showed same results. 
I opened the bios and disabled all the power saving stuff ( again! why does this come back? ) 
Then I stumbled around all the windows settings and found nothing interesting but disabled various background apps.. I even uninstalled a few apps I don't need like Bonjour. 
Latency Monitor now stays at 300 u for hours on end even with Sonar running so it's not DPLAT, . But Sonar continues to crash about once every 3-4 hours. 

Johnny I'm curious what sample rate your projects are? The reason I ask is because I've started a new album after a 3 months break to get other stuff done, and have been suffering crashes like yours. I've added a few new tricks to my arsenal. Izotope Ozone and Neutron, and a few new wave plugs like the TG12345 channel strip, (just awesome), but I'm suffering major crashes every time I either try to change presets, or parameters, crashes when I close projects etc. The only real change I have made for this current project is deciding on 48k/24bit, away from my usual 41k/16 I had used the last few years. This week I've started all over creating new projects back on 41k/24, dragging over what I can, exporting out and in, and re-tracking everything else. It's been a huge effort and a lot of time, but I'm back to no crashes, so far....  I'm thinking it's my focusrite, or something I either don't understand, or I'm doing wrong.....
 
I've been using Melodyne a lot, but I'm still in the old habit of one clip, bounce, at a time, not forgetting the 2 years or so of mayhem, and this is still working well for me. It's not crashing from Melodyne. For me anyway.
 
Hope you get it sorted. It's hard to maintain focus when you have to keep stopping chasing problems.

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.    
 
 

Thanks Johhny. I would expect most people are successfully using 48k, but it did seem to be my problem, for now, and I'm really not sure why. If your getting 3 hours out of multiple tracks loaded with Melodyne, it's probably not the issue causing the crashes, though, having said that, what would ? Hopefully someone might have an idea. My crashes were instant, having to restart every time I touched something. I know when I did my last full album, sitting up sometimes for 24hours at a time, I would get crashes after long periods. I always figured it was because I had saved things too many times, or created too many files or something, and found cleaning up temp files, recycle bin etc, and a restart, would get me going again for another session. I guess a 3 hour crash could be considered a forced fatigue and coffee break

FWIW Melodyne has NEVER crashed Platinum for me at 48K. 

I went through a lot of bumps and bruises with Sonar over the past few months. Did a complete cleaning and a full reinstall, and it's night vs. day now. Runs smoothly without a hiccup on exactly the same computer and configuration. Melodyne was an absolute mess. Now it runs great. 
 
I posted about it here :
 
http://forum.cakewalk.com...02-Error-m3645148.aspx

No, not like that initial 4.0 debacle.
It's safe now (and for now)

Thanks Dale, I see that a possible fix might be what you have done and instead of a rollback  a complete clean install is in order. What I might do is order a new SSD drive. as this system is now over 4 years old and might be going weird on me ,, I know it shouldn't matter, but I'm thinking this only has happened after the last Windows update. 
I had to re install my iLok software to use my Air products. Have no clue why but at least the software told me this and even gave me the link so it was an easy process,, but these things cut into my time and have no logical reason to happen other than W10 updates seem to re set things to zero.  

Ok, I just read the "your DAW is not a Game"  thread posted above. 
I might be correct in thinking the Creative update has screwed things up.. I see a few things happened to people I haven't check,, Like I'm not sure if this gaming mode is on or off as I was unaware it is a default. It's probably on! 
I just check this laptop I'm using at works and yep... it was on.. 
I also forgot to check device manager to see if it has re enabled my HDMI audio. 
Seems the update re sets to defaults. 
I will check tonight when I get home. 
I hope it's that simple, I've ruled out Melodyne thanks to those who vouched for it's stability. 

So this is totally not Windows Update I see I'm still on 1607? It definitely said it was updating a few weeks ago after I left it running all day on line.  I guess it only did certain updates. 
First thing I noticed was I went to disable the Gaming mode and there was no Gaming icon on the Windows Settings page. 
So I went looking in event log   all of them say SONARPLT.EXE  and this is also the module fault.  only 2 noted below said otherwise. 
Aug 11 1:31PM 
Aug 22 8:39PM 
Aug 25 8:50 -- this one is weird- module fault  VCRUNTIME140.dll  but main fault was still Sonar
      11:59 PM 
Aug 26 1:47 PM
            3:28PM   Module fault Adictivedrums.dll 
            6:01 PM 
Aug 27  2:59PM
            4:27 PM