Link please to source. Thankyou.

I opened a case at NATIVE Instruments, I had a response today that they have reproduced the problem and they would do a fix soon.
which is odd is that this problem I did not with X2.

Pls keep us posted on what NI replies, especially what the say regarding a fix (best post the link to their reply).  K5 is causing occasional problems on my system as well. Hence, I'm interested in anything that could improve the situation...
 
Just yesterday I had crashes in a project with 5 instances of Kontakt when trying to freeze synths. I could sort that out by changing the K5 settings to use multi-processing (I don't know if that really makes much of a difference) and I increased ASIO buffers. Afterwards I could freeze all instances of K5 without problems and could continue working ...
 
When thinking of the (occasional) stability problems I had in recent weeks with X3c, there was always Kontakt in these projects and ASIO buffers were (most of the time) set to lowest latency. However, I want to keep working at these low latencies so anything to improve K5 @ small ASIO buffers would be great!

+1, keep the case number! :)

@FreeFlyBerti, 
 
Quick question - when you have these multiple instances of Kontakt inserted in your projects, are you loading multiple instruments into each instance?  Or, is there one instrument loaded into each Kontakt instance?  (just curious, wondering if you are using the multi-rack functionality in Kontakt).
 
Can you also list which instruments you happen to have loaded into these Kontakt instances?  I am wondering if there is something there I could try to replicate and look for a workaround (or confirm your workaround), as I too use Kontakt all the time.
 
Lastly, even though it worked in X2, it is quite possible that the X3 code is properly following the VST specs, but that some tiny discrepancy between how Sonar interpreted something in the VST specs in their X3 changes and how Kontakt code interpreted the specs is causing this error to be seen only when Kontakt is inserted into projects in X3.
 
Fortunately, the NI folks seem to have decided that they could and would do something at their end to resolve the situation, and that is a good thing.
 
Hopefully a fix will be along shortly.
 
Bob Bone
 

I'm following this thread as well, so please keep us up to date. I love Kontakt, but it has lead to almost all of my crashes in SONAR  X2 & X3 in the past 9 months. That's not to say I've had a lot of crashes, but the Abbey Road drums act finicky at super low latency, I also get the one core shooting through the roof at times while the others barely pop, plus I've gotten weird memory crashes with Alicia's Keys at times.
 

They will probably charge for the fix...

They're pretty good about stuff at NI.
 
Sharke, I tried playing with the mixer settings thinking that it was the convolution reverbs eating up so much CPU. Turns out in a lot the mixer settings it's the Transient Master that causes high readings, especially on core 1. They have it on the master bus as well as a lot of the pieces in the kits.
 
 

OK here's a strange one. I loaded up Kontakt with just 1 stereo output in its configuration. I normally use the 8 in 8 out version. Anyway, my CPU usage for Modern Drummer was lower and more balanced across the cores than with the other version of Kontakt that uses multiple outputs.......discuss????
 

Well, I would imagine the version with less outputs requires less resources.
 
Bob Bone