If you have a mini-dump file, you can poke around in it with http://www.nirsoft.net/utils/blue_screen_view.html to see if you can spot a specific driver involved in the crash.
 
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

thanks abacab - what a great resource that is!!  Pretty sure my problem is a couple of old 32bit plugins causing 
ntoskrnl.exe ntoskrnl.exe+4881ae to crash
Will go through my plugins tomorrow and see if there are any 32 bit that I still want

So I'm cool on Windows 7. Good to know.

Works for me. My DAW is still on Win 7 and the update installed and ran perfectly yesterday

The only thing I'm getting is each time I start my Sonar session for the day, I get the stops working thing. Usually I close and run Sonar again and the project fires up. Yesterday, it took 2 close and restarts before the project loaded. Everything from that point is great. I had one other stops working on another project later that day, whilst other projects started okay. Hope this gets rectified soon. Yes Win updates are fickle although this issue started after I installed the 2016-11 update, so I don't know whether Win update features at all?

I'm having the problem as well. Initially I thought it was a Waves problem but I can now make Sonar crash by adding any softsynth as well. I have NEVER had a problem with Sonar and have been using it for years. This is shocking.

My Waves VSTs need to scan for licenses every session now.. And Kontakt is stuttering and buzzing like crazy on my end. And the VST scan just hangs every time I run it.. These used to work flawlessly until the Windows 10 update / Sonar November update interaction issue.. I hope we find a fix soon..! 

This actually was the final straw for me for Windows 10.  MS kept screwing things up with the updates.  Plus, I had really annoying display bugs on my laptop probably do to driver support.  Sometimes I'd turn my computer on and I'd just get a black screen.  Other times I'd log in and then it would go right back to the login screen.  I am really turned off by their forced updates and how they are secretive about the data gathering and what the updates do.
 
I've reverted back to Windows 8.1 this weekend.  Had a few hiccups getting the updates to install (There's like 2 gigs of updates and Sonar won't install unless all the updates are installed.  There's a bug in Windows 8 where at one point it searches for updates forever and you have to manually take corrective action.)  I have no plans to move back to Windows 10 ever really.
 
Sorry, a little off-topic.

For Roland users (usb audio interface) on W10:
 
Uninstall current driver in "add or remove programs" (device needs to be disconnected/off), restart W10, then reconnect/power on device. W10 will then (re)install (new?) drivers. This will get rid of the ASIO "no device for your current driver model" & "Sonar.exe stopped working"- crash. At least it did in my case.
 
Tested on a 64bit installation/48KHz projects

If one has Win 10 Pro you can turn off the automatic updates.  I did even though my computer is off-line most all of the time.  The only time it is on-line is for updates.