Is the crashlog always the same as in your first post?
This shows Kontakt is causing a stack overflow in a processing thread that appears to be parsing some script:
Thread 35 Crashed:
0 libsystem_kernel.dylib 0x00007fff92cc0002 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff88a945c5 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8f5e2787 __abort + 145
3 libsystem_c.dylib 0x00007fff8f5e3066 __stack_chk_fail + 200
4 Kontakt 5.MusicDevice.component0x0000000119be1c73 BEngine::SetEngineParAsync(bool, BEngine*, BParTag, int, int, int, int, char const*, char const*, BParVal, int, bool, BParProperties::rep_mode, bool*) + 1171
5 Kontakt 5.MusicDevice.component0x0000000119a76441 BScriptParser::DoSetEnginePar(int, int, int, int, int, bool) + 737
6 Kontakt 5.MusicDevice.component0x0000000119a64461 BScriptParser::RunStatementList(MPrsStatement*, int*) + 20705
7 Kontakt 5.MusicDevice.component0x0000000119a75468 BScriptParser::RunCallback(int, BCallbackEvent*) + 328
8 Kontakt 5.MusicDevice.component0x0000000119c3a222 BEngine::RunEvents(int) + 5170
If you can reproduce this crash, with the same crashlog for the crashing thread, this most likely is a bug in either the library developers script, or in Kontakt itself.