your next crash take note of the plug ins you are using and then you'll have to determine which you believe are solid and which might not be solid.
then load those ones you believe to be not solid and wait for it.
These are tough. its a process of elimination.

Are any of your plugins 32 bit?  Those seem problematic, although I haven't seen many problems reported lately with them.  That could be because many people have migrated to 64 bit only now, though.

Zip up a collection of your crash dumps and put them on the net somewhere and post a link here.  I can look at them and at least give you a better idea of what is crashing.  Right now you don't really have enough info to go on without analyzing your crashes.  No guarantees what I'll be able to tell, but it at least might help you narrow your focus.
 
As a rule with Win10 it almost always comes down to not applying all the updates for Windows, not applying all the updates for the now half-dozen runtime libraries (which plugin developer's installers should install but don't or install older versions that don't work with Win10).  Sometimes it's a 3rd party utility (anti-virus, malware scanner, firewall scanner, window screen utility) that just doesn't work well.  There are so many poorly written real-time anti-virus scanners it isn't funny.  You don't need and should never run any "real-time" scanners on a DAW.  I've also seen a handful of other odd utilities that wedge themselves into every running process in order do some "cool" effect that more often than not just aren't up to working in a DAW/plugin environment.  Most of these things will show up in a crash dump though.
 
With nVidia cards you usually will need to disable the HDMI sound device, since having it enabled can cause all sorts of strange performance problems.  But I don't think that causes crashes very often, usually just breakups and glitches. 
 
And of course you need to update the drivers for all your hardware, not just your sound card but your motherboard BIOS and drivers for all your hardware too.
 
With Sampletank 3 I recommend not using the VST3 version, it's buggy and will crash SONAR.  The VST2 version is much more stable and reliable.  Some people have no problems with it, but that doesn't mean it's good for everyone.
 
SONAR stores its crash dumps in %APPDATA%\Cakewalk\SONAR Platinum\MiniDumps in .dmp files

I had more problems with nVidia graphics cards and graphics cards in general, I removed them and use my onboard dual DVI. Because we are not playing world of Warcraft here, we really don't need great video cards. As a matter of fact, personally I believe the only time you should be using a graphics card for your DAW (DAW only) is if the onboard Graphics doesn't have enough ports for dual or triple screens or what ever you are needing.
 
Its one less thing to worry about when it comes to graphics cards. And again, this is only myself personally, I choose to go the route of the less hardware (only what I need) the better.

Not if you need a lot of sample memory every mb counts.

interpolated
Not if you need a lot of sample memory every mb counts.

im not following you ? Do you mean onboard graphics sucking up RAM ?
If so, its tiny. Sonar doesn't require massive amounts of graphics.
 
I will say this though, My Waveform draw is slow. But the trade off is well worth it.

Just wanted to say thanks to all who have replied and offered advice. I will take the time to review all this info on detail and offer responses later this evening when I am back in my studio.

This is such a great community.

Cheers

Chris - SquareSpiral

chuckebaby
I had more problems with nVidia graphics cards and graphics cards in general, I removed them and use my onboard dual DVI. Because we are not playing world of Warcraft here, we really don't need great video cards. As a matter of fact, personally I believe the only time you should be using a graphics card for your DAW (DAW only) is if the onboard Graphics doesn't have enough ports for dual or triple screens or what ever you are needing.
 
Its one less thing to worry about when it comes to graphics cards. And again, this is only myself personally, I choose to go the route of the less hardware (only what I need) the better.

Or, as is the case with my motherboard, there isn't an onboard graphics port

Ok,
 
Quick catch up through the suggestions:
 
All pulg-ins are 64bit - I went this route ages ago and stick to it like glue!
 
I still think that ST3 is a major player here as more crashes have seemingly been caused by it than any other thing as far as I can tell. I may well be using the VST3 version so I can happily switch that out for the VST2 version instead if that is more stable.
 
As to the graphics card question - I agonised over this one myself but came down on the side of including a moderately powerful card in the build for three reasons:
1, I often work to picture and felt this would be better handled by dedicated hardware allowing the processor and system memory to me reserved for Sonar.
2, When funds allow I will be getting a second screen as this is my preferred working arrangement for the reason above.
3, I occasionally need to do minor video editing tasks on this machine so I wanted a little power under the hood to accomplish this.
 
Matt Sorrels - You mentioned in your post above about posting my crash dumps - If you have the time to look I would appreciate it:
https://www.dropbox.com/s/w3es1itxrvnedht/SquareSpiral%20MiniDumps.zip?dl=0
 
Again thanks to all taking the time to help!
 
Chris - SquareSpiral

Have you checked your bios settings?
Make sure power throttling / sleep states are disabled.

Very important: check the settings for the ram in your bios i.e. timing, voltage and multiplier.
You might want to try a (different) xmp profile. (Check with Corsair and the Forum there.)