BSOD opening Kontakt 4 with ASIO driver - RESOLVED - NOT!

I'm a new Komplete user here and have posted in the NI forum also.

Komplete 6 loaded and activated/updated great (although I missed being able to assign a specific location for samples). However, when I open Kontakt 4 I get the opening setup screen - made sure all settings are correct but when I click on OK - zap BSOD.  I have NOT tried opening in Sonar having read of the issues there prior to opening in stand alone.

I rebooted and tried opening each of the other elements i.e. Bat 3, Traktor, etc.   All of these open fine in stand alone. Kontakt 4 is the only one that crashes the system?

This is on a clean install of Win7/64.  Any ideas? I looked for the dump file but can't find it and haven't figured out what Win7 did with the search option on right click.

I haven't checked the Win7 tweaks mentioned at NI but will do those late tonight to see if that makes a difference.

Can I uninstall and reload JUST Kontakt 4?

Intel DP35DP, Q9550, 8GB, nVidia 7300GT, Win7/64, Lynx L22

EDIT: I was able to uninstall Kontakt 4 alone and reinstall.  Worked like a charm.
Okay: Well I thought the reload fixed it. However, I've found that I still get the blue screen when I try to use the ASIO driver.

All other components in Komplete work with ASIO (standalone) but NOT Kontakt 4? The latency with WASAPI is 10ms which is really noticeable and unusable.

I've tried turning off Mulit-core usage and cannot raise the buffers at all.

Posted at the NI forum but no takers?  Can you guys give me a clue?

Wren,
first - sorry I couldn't do lunch again today. 

on your problem - this sounds like a driver problem to me, not specifically a Kontakt problem (although whatever driver problem there seems to be is affecting Kontakt specifically).  I assume you have win7/64 drivers for the lynx? 

here's a suggestion - I know you have at least one other soundcard - a MOTU, IIRC.  load the win7/64 drivers for it then open Kontakt in ASIO mode.  if you still get the same problem then it might point to a problem with Kontakt, but if you don't get the same problem then I'd look at the Lynx drivers as the suspect.

gustabo


Have you tried running all the NI stuff in standalone before trying to load it as a vsti?

This is a very important point. All NI stuff must be run in standalone mode prior to vsti mode. Otherwise the vsti will not work properly.

Oops, apparently speed reading is not my forte!

Wild guess, shot in the dark...

What is the sample buffer of your ASIO set at?

Put it at 256 or something moderate if it is either very small or very large.

best regards,
mike

1) You should have definitely been able to set a library path  :~
2) What's the stop error given by the BSOD?
3) You are running as administrator and not just with UAC turned off, right?

Your NI forum moderator,
ew

The three most common causes for that error in W7 are:

1) graphics drivers- especially with nVidia cards
2) network adapters
3) RAM

Check for updated drivers for your graphics card and mainboard. Considering you're a nVidia user, I'd start there.

ew