Help! Kontakt3 is making Cubase SX3 crash

Suddenly my computer is giving me the message "an exception occurred in the module: Kontakt3" and making Cubase SX3 crash just after a project is loaded up and ready to go. When I load an older version of the project that does NOT include K3 (it does have K2) it works fine. The problem started after I started accessing the web through somebody else's network, and had to add new addresses to the keychain (this had not been an issue before - and somebody else configured my computer for this new setup). I also downloaded the driver for a Skype phone, along with Skype. I'm at a residency in Italy, where I've come to compose, so any suggestions would be greatly appreciated so I can quickly get back to work!

 

Could it be RAM related? Some versions of Kontakt cause Cubase to crash when the RAM limit is exceeded and maybe K2 and K3 use different amounts of RAM.

 

No idea, but are you sure you're using the latest version (3.0.2)?

 

I'm using 3.0.2.004. It works fine as a standalone, but the plugin makes Cubase SX3 crash. I don't suppose there's any kind of workaround to open the Cubase project?

 

Off the top of my head, if you were to remove Kontakt 3 from the VST plug-ins folder, I think the Cubase project should open (and give you a "missing VST plug-in" error).

Alternatively, in this situation, on my DAW (Digital Performer) I can start it up with the audio system shut down (i.e. MIDI only) and this lets me bypass any buggy plug-ins causing trouble.

 

Thanks for the suggestions. Cubase doesn't have the same functions, but when I try to open a K3 plug in in a new project, it still makes Cubase crash. Sounds like I should try to reinstall K3. I'm very far from home: do I need my serial number in order to uninstall and reinstall K3 on a computer that already has Kontakt3? I see that there is not an uninstall function with K3. If I reinstall will it write over the previous version, or do I have to remove the old files first? And will all of my sounds remain intact if I remove the application?

 

I uninstalled and reinstalled K3, now it's working fine. It was labor intensive - an uninstall function would have helped here, but it's up and running again.