None generated by SONAR. There might be something in the Windows logs. Failing that the best information is in the minidump SONAR creates which is only useful to Cakewalk.

I took a look at the Windows Event Viewer and see a few things.  Probably not very helpful in solving the problem but will get some more data on the record.
 
1.) As expected, there is an application error event being captured:
 
Faulting application name: SONARART.exe, version: 22.6.0.26, time stamp: 0x57645bc4
Faulting module name: RaptureSession_64.vst3, version: 2.0.4.25, time stamp: 0x569d4005
Exception code: 0xc0000005
Fault offset: 0x00000000000e87a3
Faulting process id: 0x1380
Faulting application start time: 0x01d1d4d6b0c8dc1c
Faulting application path: C:\Program Files\Cakewalk\SONAR Artist\SONARART.exe
Faulting module path: c:\program files\common files\vst3\Rapture Session\RaptureSession_64.vst3
Report Id: 01cdeff7-45c3-48d0-900e-69bc51bef997
Faulting package full name:
Faulting package-relative application ID:
 
2.) As reported earlier, I am no longer able to send fault reports.  This was working fine but stopped working when I updated to the 2016.06 release.  The FaultReporter.exe is crashing and is logging 2 different events:
 
a.) An Application Error
 
Faulting application name: FaultReporter.exe, version: 2.5.0.1, time stamp: 0x57603978
Faulting module name: KERNELBASE.dll, version: 10.0.10586.306, time stamp: 0x571af331
Exception code: 0xe0434352
Fault offset: 0x0000000000071f28
Faulting process id: 0x1834
Faulting application start time: 0x01d1d490456fdf60
Faulting application path: C:\Program Files\Cakewalk\Shared Utilities\FaultReporter.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 56fb6cf5-3e83-4d24-b968-68a17211f409
Faulting package full name:
Faulting package-relative application ID:
 
b.) .Net Runtime Error
 
Application: FaultReporter.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at PhoneHome.Config..ctor()
at PhoneHome.Program.Main(System.String[])
 
3.) I tried opening Rapture Session independently from SONAR.  RaptureSession_64.exe is crashing also:
 
Faulting application name: RaptureSession_64.exe, version: 0.0.0.0, time stamp: 0x568579cf
Faulting module name: RaptureSession_64.dll, version: 2.0.4.25, time stamp: 0x569d4005
Exception code: 0xc0000005
Fault offset: 0x00000000000e87a3
Faulting process id: 0x1c20
Faulting application start time: 0x01d1d4d6a823fe29
Faulting application path: C:\Program Files\Cakewalk\VstPlugins\Rapture Session\RaptureSession_64.exe
Faulting module path: C:\Program Files\Cakewalk\VstPlugins\Rapture Session\RaptureSession_64.dll
Report Id: 50b52a55-343a-4976-a8da-9d9c6c7a4f62
Faulting package full name:
Faulting package-relative application ID:
 

Could this be caused by the fact that I'm not using ASIO?  Time to try ASIO4All?

I wonder if it would matter if you tried a test where you temporarily took your VST 3 path out, or perhaps there is a better way - but essentially whenever a VST 3 plugin and a VST 2 plugin for the same synth are present, Sonar will use the VST 3 plugin instead, so scook perhaps you could comment on the most logical way of getting the VST 3 version out of the equation - for testing purposes - so that the VST 2 version is what would get loaded into the project, or even a new empty project, other than inserting the VST 2 version.
 
This only comes to mind because lots of folks in Sonar had issues with the Arturia V Collection 3's initially delivered VST 3 versions of those synths.  SOME, like 3 or 4, just did NOT like running in Sonar as VST 3, and the workaround for THAT situation was to temporarily move or rename those (cannot recall the precise method of getting them out of being seen by Sonar), and the VST 2 versions of those particular failing 3-4 of them worked FINE.
 
Could it be that since you are running fine in other Windows versions, that your Windows maintenance is not completely up to date on that particular machine?  THAT has certainly caused access violations before for folks - like the giant swath of folks that were missing SP1 for Windows 7, and I believe Sonar wouldn't install, or IF it installed, it didn't run - that sort of thing.
 
Anyways - could something along those lines be happening here?
 
Lastly, for now (nearly 2:30 in the wee hours with a wake up coming at 5:30), I don't know if there are any free versions of something like this or not, but I picked up an application for somewhere around or less than $50 usd, called WhoCrashed, and I used that to analyze some crashes and I found it quite helpful.
 
I will check back on this thread and try to further assist Sunday late afternoon, after what will be a grueling time of things for my day prior to then. :)
 
At some point, I DO recommend you pick up at least a decent but inexspensive dedicated audio interface, with Windows support into Windows 10.  There are several in the $130-$200 range that would fit the bill well for that - certainly I think your computer would work WAY less hard on dealing with an application like Sonar going THAT route, particularly if you begin to want to get into any real complexity with your projects.
 
Hang in there - scook is a great person to have helping - and if I can help in any way, I certainly will try, and maybe some others will jump into it all as well.  I am just stuck with a block of time from 7:00 AM through around 2:00 PM of solid 'me and my brain and my fingers as a keyboard player are required'.
 
Now, however it is time for zzzzzzzzzzzzzzzzzzzzzzzzzzz.
 
Bob Bone
 

robert_e_bone
I wonder if it would matter if you tried a test where you temporarily took your VST 3 path out, or perhaps there is a better way - but essentially whenever a VST 3 plugin and a VST 2 plugin for the same synth are present, Sonar will use the VST 3 plugin instead, so scook perhaps you could comment on the most logical way of getting the VST 3 version out of the equation - for testing purposes - so that the VST 2 version is what would get loaded into the project, or even a new empty project, other than inserting the VST 2 version.
...
Hang in there - scook is a great person to have helping - and if I can help in any way, I certainly will try, and maybe some others will jump into it all as well.  I am just stuck with a block of time from 7:00 AM through around 2:00 PM of solid 'me and my brain and my fingers as a keyboard player are required'.
 

Thanks, I had not thought about plug-in format. No need to mess with scan paths, use the VST3 migration settings. They are on the same page Preferences > File > VST Settings. Disable both check boxes to insure the VST2 format shows up in the plug-in lists and will not get replaced when used in a project.
 
I really do not think this is a driver issue. ASIO would be useful in testing whether the stand alone synth works is all.

I unchecked the "Hide Related VST2 Plug-ins" and "Replace if Possible on Project Load" boxes.  Unfortunately, I got the same result (crash) when I added the VST2 plug-in and tried opening the properties page.
 
Both of the machines that I'm working on are using the same version of Windows; namely, Windows 10 Pro 64-bit.  They are both current from a Windows update perspective.  The Dell Precision laptop is working; the Dell Optiplex mini-tower (detail in my signature -- above) is not.
 
What are your thoughts on my installing a trial of Rapture Pro?  I'm concerned that would just muddy the waters, though.  At least in my current state, I have e-mail support for Session.  I have a feeling my Rapture Session ticket is not very high on their list, at the moment. Which I understand, believe me.

Yeah, that does not surprise me.
 
RPro is a different plug-in. It might work where Rapture Session does not but I doubt installing the demo will resolve the Rapture Session issue. Also whatever is causing Rapture Session to fail will probably bring down Rapture Pro too. We just have not found the difference between the two installations. Still if you want to mess with it, with the experience gained so far you know how to cleanly remove and reinstall Cakewalk products. On the other hand, let's say RPro works and RSes is still broken, are you prepared to buy the upgrade?

Was a dump included with CWBRN-51195?

There should have been a dump included with the fault reports that I submitted.  I have submitted a total of four: 51195, 51196, 51778, and 51779.  Since the FaultReporter stopped working with 2016.06, I might rollback and try submitting a new report.
 
I have some of the recent dump files on my PC if they would help.  I'm going to have a go at seeing if I can find anything meaningful in the files.  I'm used to Unix/Linux cores but I'll see what I can do with this Windows dump.
 
Thinking of other differences in the two different machines, the one that is not working had SONAR X1 LE installed before I made the upgrade to SONAR Artist.  I have no idea if this could be related but wanted to put it out there.

I opened the .dmp file in Visual Studio 2010 (installed on a different laptop I'm using) and here's what it reported:
 
Exception code: 0xc0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
 
Searches for this error code seem to point to malformed or incomplete registry entries.
 
Unfortunately, VS isn't giving me much more meaningful information.  I opened the file in WinDbg and it didn't yield much either.  Though, admittedly I am not an expert in this tool and without the source code I won't be able to see much detail.