I recently updated Applied Audio Systems String Studio VS-2 to version 2.1.0 and tried instantiating it in a SPlat project (version 23.10.0 build 14).
 
It crashed my system...not just the SONAR application.  The blue screen described it as a "Page Fault in Unpaged Area".
 
This is 100% repeatable.  It blows up with the VST2 and VST3 versions.  This also occurs with all the other AAS softsynths I tried with the exception of Tassman 4.1, which is no longer being updated.  Other non-AAS softsynths I tried also worked fine.
 
My system information...
Windows 10 Pro, version 1709, build 16299.309
Intel i7-3930K @ 3.20 GHz
16 GB RAM
AMD Radeon HD 5450
 
This smells very much like an AAS problem, but attempting to contact them reveals that their support resources don't seem to be very robust.
 
Has anyone else had problems with AAS stuff?
 
Note that AAS plugs supplied with SONAR (like Strum and Lounge Lizard) seem to still work, but they seem to be built on the same older framework as Tassman.

I am using AAS String Studio VS-2 version 2.10 on Sonar Platinum with the following configuration:

Windows 10 Pro, version 1709, build 16299.309 Fully patched
Intel i5-4670 @ 3.20 GHz
16 GB RAM
NVidia GTX560TI video with latest Nvidia drivers
Focusrite 2i2 2nd Generation with January 2018 drivers
Sample rate 44.1 khz
24 bit set to 256 samples

I am not having any issues what-so-ever.

Do you get the BSOD using the stand alone version or just within Sonar?

I have contacted AAS support and compared to some companies they are pretty good but will not be instant. 
 
I don't have String Studio but have their other synths and have not had an issue with them. Normally a BSOD would be cause at the driver level and not software. What audio interface are you using and are your drivers up to date? 

I do not have the String Studio, however the test I just did with the ASS stuff I do have, Strum, Lounge, Ultra Analogue and Player all worked fine on both my PC's.

What are your system specifications?

In modern Windows (and other OSes), applications are unable to cause BSOD. Even intentionally (and I am sure AAS has no such intention).
 
But they can trigger BSOD in buggy driver or system itself.
 
There are 2 places where VST "speak" with the system, drawing own interface and in the anti-piracy checking.
 
Try to run VS-2 standalone.

+1 for what Azslow3 said above. Blue screen relates to hardware. It can be an indicator of a hardware problem such as a memory chip dying or a loose component. However, I don't think it suggests a hardware failure in your case as you only seem to be getting it with AAS plugs and nothing else? It could be driver related. It could possibly be related to your graphics card so update your graphics driver and make sure all your drivers are up to date. Also as others have suggested try running the standalone version to see if you still have the problem - if you still have the problem you then know it's specific to AAS. If not the problem relates to AAS running in Sonar and the interaction it has with the hardware through Sonar. Have you got another DAW you can try it with too?

I have String Studio and use it and the other AAS synths all the time. I hadn't used SONAR in quite a while so I just loaded platinum up (last/final build) and loaded up string studio (v 2.1, 64 bit VSTi2) and confirmed it is working properly here. I am using Windows 10 pro 64 bit and it is current and up to date as well. So not Windows 10 (per se) either as far as I can tell. As others have said it would more likely be something system specific.

I've seen some useful suggestions here.
 
I guess there are a couple of possible hardware exposures.  One is the audio driver.  I'm running a relatively ancient M-Audio Firewire 1814 interface running the ASIO driver version 5.10.0.5058, which I downloaded on 09/27/2010.  I don't think this is being updated anymore, so they don't have an explicit Win10 version.
 
The other exposure is the video driver...which I can do something about.  It's quite possible that video is where the problem lies, since there's a marked difference between the presentation of the older/working AAS plugs (like Tassman, Strum and Lounge Lizard) and the presentation framework of the newer/crashing plugs (Ultra Analog and String Studio).
 
Lemme update my video drivers and see what that does.
 
Oh...running in another host (Savihost) works fine.  I haven't tried running their own standalone.

I'm using an ancient M-audio ProjectMix which I expect may use the same firewire driver. I got it off ebay last summer, so I went to M-audio website and downloaded the latest driver. I think the release date of that driver was 2015 and may have been for win 8 - works fine with win 10 and no issues with my AAS plugs. If you are running a driver from 2010 I would recommend you update it for the latest one even if it isn't the cause of your problem.

35mm
I'm using an ancient M-audio ProjectMix which I expect may use the same firewire driver. I got it off ebay last summer, so I went to M-audio website and downloaded the latest driver. I think the release date of that driver was 2015 and may have been for win 8 - works fine with win 10 and no issues with my AAS plugs. If you are running a driver from 2010 I would recommend you update it for the latest one even if it isn't the cause of your problem.

It would appear that the latest driver for my Firewire 1814 is the 5.10.0.5058 that was released 11/14/2009 for Windows 7 (64).  There wasn't anything released after that for Win8 or Win10.
 
I also tried updating the video driver for my AMD Radeon HD 5450.  It turns out that it has also lapsed into "legacy" state and only had a beta driver released on 02/29/16 that was newer than what I already had.  I installed that, but the BSOD behavior still persists.