Sonar X3 crashing when using EW PLAY 4.2.25

I have had consistent crashing of Sonar X3 when using the latest version of EW PLAY 4.2.25.  At first, I could open and play a little bit with various EW programs, but then "out of the blue" Sonar would crash.  It could have been 15 to 20 minutes of using the programs before the crashing occurred.  I decided to roll back PLAY to the 4.2.22 version to see if this would make a difference in the instances of crashing, but it did not help, so I reinstalled the 4.2.25 version.  I have subscribed to the EW Composer's Cloud program, so I have access to a huge number of new programs and it is these that I have been examining to see what kinds of sound they contain.  The last crash occurred when I was trying to load the EW Hollywood Strings which is a very large program, but I have loaded it before without a crash happening.
 
I am having a hard time trying to figure out why Sonar will work for a considerable length of time and then suddenly crash when I am doing the same thing all along.  I have re-scanned the vsti locations for 32 and 64 bit, so I don't know what else I can do to solve the problem.  Is anyone else having this kind of issue.  I have used Sonar for years, so I know about its stability on my machine.  This is a new issue for me so I need some help to get it resolved.
 
Does anyone have suggestions that I can try.  I am open to try almost anything.
 
Thanks,
 
Tom
 
Computer: i7 980, Samsung 1 TB EVO 850 SSD system drive, 48 GB RAM, samples on 7200 HDD.

What kind of crash? BSOD or Sonar poofing?

Resonant Serpent,
 
It is not the BSOD, but Sonar just says that there has been a "fatal error and will close".  The only thing to do is to let it close and open it again to see if it will continue to work or will crash again.
 
Thanks for your reply,
 
Tom 

I've been using EWQL's Play for quite some time now. It runs well for me.

You say that you have Sonar scanning both 32 and 64 bit plugins.

Why not try removing the 32 bit path and just load 64 bit plugins and give that a try so you can start eliminating possible causes. You will need to do a rescan of existing plugins to do this properly.