Kontakt crashing Sonar.

I am presently working on a project and every time I want to add a Kontakt 5 track I get the following message 
" Background loading warning.  Your memory is getting low. Please use the purge function to free some resources.
   Kontakt will progressively cache only the required samples and offline bounce."
After the message, Sonar X3 Producer stops working.
 
This ONLY happens when I want to add a Kontakt track.  
It is also the first time it has happened to me. I have had other projects and this never happened.
 
Thank you in advance for any help.
Regards
 
Gerry
NOTE: I have also sent this message to Native Instruments. I posted here just in case  someone might have had this 
           same issue in the past.

Gerry 1943
I am presently working on a project and every time I want to add a Kontakt 5 track I get the following message 
" Background loading warning.  Your memory is getting low. Please use the purge function to free some resources.
 Kontakt will progressively cache only the required samples and offline bounce."
After the message, Sonar X3 Producer stops working.

This ONLY happens when I want to add a Kontakt track.  
It is also the first time it has happened to me. I have had other projects and this never happened.

Thank you in advance for any help.
Regards

Gerry
NOTE: I have also sent this message to Native Instruments. I posted here just in case  someone might have had this 
         same issue in the past.

 
Hi Gerry.
 
I don't have much experience with Kontakt in SONAR. I have a couple of the freebie instruments from them and the Kontakt 5 player. I just haven't used them with SONAR.
 
That said - for the folks with the experience to really answer, they will need to know more about your setup. Mostly - which Operating System and what bit depth are you using. You've given us that you are using X3 Producer and Kontakt 5 (which instrument?).
 

• Is it Windows 10?
• Are you using 64 Bit Windows and 64 bit X3? Big VSTi need the full 64 bit memory space.
• And speaking of Memory, how much do you have? I'm guessing at least 8 GB, but I don't want to guess.

 
I went for 16 GB on my workstation, but I'm using Windows 7 Professional 64-Bit. If you do really big projects, even 16 GB might not be enough.  I chose to go with Windows 7 so that I don't have any surprise updates that will kill all my drivers (the only real worry with Windows Updates is you lose access to "unusual" hardware - all MIDI and Music Creation tools should be considered unusual in the Microsoft world). I still get Security updates and other than touch screen control (I do not have a touch screen capable monitor) I don't miss much about Windows 10. I think Windows 7 is safely out of "Beta" at this point - Windows 10, not so much.

Now, on to what you might try, based on your error message, is to clear the picture cache. Probably, if left as default, it is C:\Cakewalk Projects\Picture Cache
 
You can delete the *.WOV files there.
 
I don't really know enough about Kontakt to go further. I will say the error message sounds like it is coming from Kontakt. Maybe there are Kontakt memory settings to manage. 

Are you running in a 32-bit Sonar? If so, you are limited to a 4 GB memory space, minus the size of Windows and any loaded programs, like Sonar and any plugins, and loaded  samples and such.
 
Running in a 64-bit Windows with a 64-bit Sonar and 64-bit plugins lets you access up to way more memory, like more than 150 GB, of course limited to the amount of installed, minus overhead like Windows itself and running programs, etc....
 
There is also a Purge function in Kontakt to reduce number of loaded samples and lessening memory load, but if you have enough memory installed and running 64-bit, you shouldn't need this.
 
Bob Bone

You'll simply need to install the 64 bit version of x3.
If you don't have the 64 bit version already installed, you may find you also need to install the 64 bit version of all your plugins and instruments.
 
You don't need to uninstall anything.

scook
On 64bit Windows the SONAR installer has an option to install either 32 or 64bit. By default 64bit SONAR is selected.
May want to check if both are installed.
 
The default path for 64bit X3 Producer is C:\Program Files\Cakewalk\SONAR X3 Producer
The default path for 32bit X3 Producer on a 64bit OS is C:\Program Files (x86)\Cakewalk\SONAR X3 Producer

Very good point, it's a very good possibility that the 64 bit version is already installed.
I've often lost startup icons from the desktop before, and had to go a hunting :-)
 

If you are running 64bit there is a screen early in the install process to select 32 or 64bit (just like the update). It defaults to 64bit so in order to install 32bit the first time you had to make that selection. Don't forget to run the X3e update again after installing 64bit X3.

If you failed to save the X3 installers, you will need to download them all again. There are no separate 32 and 64bit installers. Both versions are included and all the installers have a 32/.64bit screen just like the update you just ran.

This should end up resolving your original issue in this thread, as with a 64-bit Sonar running, it can take full advantage of whatever available memory is there when you launch it, so loading up several instances of Kontakt should work just fine.
 
A thought - sine you had been running a 32-bit Sonar, that means that any of those plugins available to that Sonar will also be 32-bit, and when you run 32-bit plugins in a 64-bit Sonar it requires bridging software (Sonar comes with and automatically will use BitBridge to attempt to let the 32-bit plugins run).  PLEASE NOTE that MANY folks have had all kinds of nightmares with Sonar project stability, when using 3rd party 32-bit plugins in a 64-bit Sonar.
 
Because of that, most folks have gone back to see if 64-bit versions of their 32-bit plugins are available (usually for free as updates or free additional downloads), and have tried to completely shift over to using only 64-bit plugins in a 64-bit Sonar.  I HIGHLY recommend that you too go through that process. as otherwise you will likely be posting again about stability issues with Sonar 64-bit.  For whatever the worth, I do NOT have my 32-bit plugin folder path added to the Sonar Plugin Manager search path for plugins.  What I DO do, is to have a sub-folder within my 32-bit plugin path, and I move any 32-bit plugins that I want to still try to use to THAT folder, and I test them out before deciding to use them in any serious production capacity - it is the path to that sub-folder that is added to the search path, so that ONLY tested and trusted 32-bit plugins are ever allowed to be loaded in 64-bit Sonar projects.
 
Bob Bone
 

Well, YOU did the hard part - you lived through the problems :)
 
Hope all is well now for you with it.
 
Bob Bone