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