I know people here have said  that Amplitube 4 VST3 is flakey, but i have ticket in to IK and i am trying to get  to the root of the problem. If i do the following it will crash 85 % of the time:
1. Create a blank project
2. Add 8 audio  tracks
3. Insert one instance of Amplitube 4 VST 3 on each track
4. Save the project 
5. Exit Platinum using the"x" button  in the  upper right corner 
 
After the project is created it can just be opened , saved and if Platinum is exited as i stated it will crash within 3-5 times through the saving and exiting procedure .
I have tried to replicate the crash using Reaper 5 and  Studio One 3 and cannot get it to fail.
I have run Prime 95, and Microsoft's memory checker but both pass. 
Can someone try this on their machine to see if it fails?
Thanks.

hi, followed your steps and all good here.
 
[edit] just for your info, whenever i use amplitube 4 i always use the vst3 version, never had any issues or flakeyness with it, and have never been aware that there was any.

I'm using the VST2 version of AmpliTube4 with several instances in many projects. I rarely have crashes caused by AmpliTube when closing projects. I tried as you said with VST3 AmpliTube4, and I had one crash in about 15 tries.
 
So, I can confirm that AmpliTube4 (both VST2 and VST3) may cause crashes in Sonar when closing a project. But on my system, this happens far less often. (I'm on Windows 8.1 64bit.)

Thanks Grim, i was hoping someone could reproduce the crash. I am using Windows 10(1511) and Platinum version 2016.10. Does this differ from your setup?

I just tried your process, and there was no crash on my side. Windows 8, Splat 2016.10

Thanks  Slugbaby. I assume  that you tried the save, close process several times?
This is beginning to look like a problem  with  my system only.

Thanks ralf for confirming the possibility that maybe it is not my system. Really strange though.

I don't use the VST3, primarily because the ST3 VST3 was/is? known to be flaky in SONAR;
So I'm not going there.
I can't recall a "crash" linked to AMP4 on my sys. (Win 7 mind you)
I haven't install the latest AMP4 update and new Fender2 yet, planned for today/tomorrow.
Should I wait?
T
 

I wouldn't wait. I have had this problem, off and on, since Amplitube 3. While a problem, it does not seem to affect the project itself. Only seems to happen in Sonar.

Thanks!