Opening Rapture Session Synth Property Page Causing SONAR Artist Crash

I saw the post over in Cakewalk instruments. This post is in the right place. Moving it to Cakewalk Instruments would not gain anything other than it will hang around on the first page longer.
 
Crash could mean a lot of things and rarely happens without a message or log entry somewhere. Maybe providing a better description of the crash would help.

Do you have a CWBRN from the initial report?
What driver mode are you using?

Maybe you can be of assistance? I have not seen this reported before. How would you proceed to help this user?

You are correct, MME is the default for your machine. And while others have mentioned it is unlikely to be the issue were it set to something else it might have contributed to your problem.

BTW, does the stand alone version work?

The stand alone synth RaptureSession_64.exe should be in the folder with RaptureSession_64.dll
The default path is "C:\Program Files\Cakewalk\Vstplugins\Rapture Session"
 
On second though that won't work because you do not have an ASIO interface, I suppose you could try adding ASIO4All but before that we might try a clean install of Rapture Session. Give me a minute to look up the registry keys.

Just followed through these instructions and have ended up with the same result.  The first key, HKEY_CURRENT_USER, did not exist.  The second key did exist and I removed it before reinstalling Rapture Session.
 
Should I try ASIO4All?

No.  It does not have the key under HKEY_CURRENT_USER either.

They're both using integrated Realtek audio devices.  The working machine is a Dell Precision laptop.  Both run Windows 10 Pro 64-bit.
 
One difference on the machine that isn't work is that it has a dedicated NVIDIA GeForce video card with available audio on HDMI.
 
 

I disabled the NVIDIA sound devices in Device Manager as it would be very unlikely that I would use them.  The plugin crash continues to occur.
 
Are there any log files present at which I could take a look?

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:
 

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
 

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.

Was a dump included with CWBRN-51195?

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.