The image has to be stored on a web page first. Then you copy the link and paste it using the image icon found in the little toolbar.
 
Well your windows 7 so that rules out the obvious W10 anniversary update bug that a lot of people have.

Here's what I've discovered...  First, as I said above, I updated my Platinum Instrument Collection from 1.0.0.10 to 1.0.0.15 at the same I time went to 2016.10.  Maybe that was a big mistake.  Because now, every project that has an instrument loaded from that collection (usually "TruePianos" or "Lounge Lizard" ) I get a crash the instant I hit play, every time.  If I load the project in safe mode and skip all synths that are from the Platinum Instrument Collection, then I get no crash.  The only rollback version offered for those Instruments is to 1.0.0.10.  I have tried to roll back to that version with the Command Center. It says it successfully completes but still reports version 1.0.0.15 is installed. So, in that regard I have no idea what's going on.  So maybe it wasn't 2106.10 after all.  At this point I don't know what to blame, but in future I'll be updating only one component at a time.

That is an odd bug for sure, keeping my fingers crossed for everyone. I will say it was worth it to upgrade my W7 to 10, that cured what few instabilities I had with platinum. Though I can still crash it if I don't pay attention when I record soft synths. try adding each instrument until you find the culprit then reload that particular one is all I can think to do atm, good luck with it sir, I know I hate when crap goes sideways, fighting with my event ez-bus atm meself.

I feel for you. Fortunately I haven't had to deal with this kind of thing in a long time, but I do remember the time that updating a graphics driver threw my system into total chaos for anything audio-related.
 
I do believe Dell changed something recently that causes problems with SONAR, and Cakewalk is working on a fix to deal with it...that may not relate to your situation in particular, but maybe there's a connection between the two. 
 
Also, try re-installing the drivers for your audio interface. I'm not sure whether that will help, but based on several posts in this forum, it seems when there is a mysterious OS issue that re-installing drivers can solve the problem for reasons no one can quite explain...
 
Things like this are enough to drive some people to the Mac, but then again, OS X hasn't exactly been a paragon of trouble-free operation lately and we get caught in the crossfire. 

Many thanks Craig for your consideration and sympathies. I can further report that I was re-working an older project for several hours yesterday using 2016.10 with no problems whatsoever.  Needless to say, it contained none of the synths that seem to now be causing me problems from the Platinum Collection. I have no idea if its only one or two specific synths in that collection or all of them.  The fact is the only thing I really use from there is TruePianos.  And while TruePianos is (or in my case, 'was') a fine product, since I purchased Addictive Keys with all four piano offerings over a year ago, I haven't looked back.   Addictive Keys is now my go to piano just like Addictive Drums 2 is my go to kit.  Both of those are fantastic, rock solid products. My solution going forward is to avoid the Platinum Collection and replace TruePianos with Addictive Keys, if necessary, when revisiting older projects.  Cheers...