Instrument works for a day, then crashes

I'm given to understand that the normal technical support channels are closed for the time being, so I figured I'd put this here to see if anyone else might have some ideas. My problem might just be so unique though that all anyone can offer me is more confirmation that I'm the only one who has this issue, but here goes. I'm able to have an instrument (usually studio drummer) running for roughly 24 hours, give or take. Then it stops working and has to be reloaded. This entails killing the daw and any associated plugin processes and then starting it again. Others I know who use KK and other NI products have neither this issue, nor a clue as to why I'm dealing with it. I thought it might be something with my daw, so I ran KK in standalone just to check and it did the same thing after the same amount of time. Does anyone have any ideas of where I might look to see more specific details of what's crashing?

 

So, is this in a single session (you ahve your DAW/Komplete Kontrol) open for 24 hours at a time or you are saying just it works today then you open it again and it doesn't work?

System specs?
Is this with studio drummer running in Komplete or just Kontakt alone?
Is it every instrument?
When it "stops working" what exactly stops? Does your keyboard (I assume you have a keyboard) keep working, control works, is it audio that stops, the program freezes and you cannot load another instrument.

Probably enough questions to ask in one chunk

 

This is just a continuous session left open. I'm using windows 10 pro on a Dell Latitude E6430, 16 gigs of ram. My interface is a first gen Focusrite Scarlett 2i4. I haven't really tested other instruments. When it dies, the keyboard stops working. If I'm using komplete in a daw, it locks up the daw. If I use it in standalone, then komplete locks up. I haven't tried this in kontakt, just komplete.

 

Is your computer going to sleep at all? Sounds to me like a power management thing rather than software, Sleep modes can do weird things to the Software state upon sleep.

 

I turned off everything that I could find that looked like it was related to sleep or energy saving and the like.

 

Yeah I agree it does sound like something is going to sleep on your system. So in this 24 hour period is it playing something constantly or it is just you leave your computer powered on overnight and then in the morning everything is stuck?

It shouldn't be KK as when I develop NKS for some plugins it can take weeks for a script to run through say Omnispheres 10,000 presets and I have a system up and running this whole time, tho normally I have it running on a second system without my MIDI keyboard attached and in 5 years I have never had KK freeze on me, it has crashed a couple of times but far less than something like Ableton or even Vegas Pro has crashed.

However I have had issues with apps freezing in the past when I let my system "sleep" and it was related to the audio interface. Days gone by under Windows 2000 and Win 7 I would always have my system sleep then it was ready to go and I never had issues using a firewire interface (Presonus Firebox) at all. But when Win10 came along and was forced to upgrade my (perfectly working and suitable ) interface because driver support was dropped for Win 10 I updated to a USB interface (Roland Octacapture) and if I put the system to sleep and then let it wake whatever app was using it will tend to lock up and I cannot even force quit it, I need to reboot the whole system so I had to disable that.

Just check it is not set to sleep as laptops have a whole mirriad of power save features enabled normally and none of these play well with production software/hardware. You could also do some simple tests such as power up KK and set it to your system audio output instead and leave overnight again with your audio interface switched off and see if you get the same issue.

 

It's just that I leave things powered on for a day and it locks up. It doesn't take the whole computer down, just the daw and the plugin process. Or if I run komplete in standalone, komplete locks up and has to be restarted. I've read some articles detailing all of the different sleep and power saving features that need to be turned off and worked through those. A couple things that probably still go to sleep would be my logitech wireless headphones and keyboard, but I wouldn't think those would have anything to do with what happens in komplete. As far as switching to system audio, would I need to use ASIO4ALL for that? I'm given to understand I can't do that as long as I have focusrite drivers installed.

 

In KK it should allow you to select which driver for your audio interface to use. ASIO will be the prefered driver as it's low latency but sometimes if the driver gets disconnected while in use, such as your USB port going to sleep and disconnecting it of the audio interface dropping off, then it can cause the application to hang as it cannot reconnect the audio driver. It sounds like that could be the case. So a test would be to open the KK preferences and select the additional driver your interface offers.



Depends on the interface but again, as a test you could simply select the default audio output for your laptop (the speakers) just to leave overnight and see if it occurs and if not, then the issue is likely your audio interface is dropping out.

 

Sounds like your USB connection/setup cos as you will probably know even when in sleep mode your usb ports should still be alive and working. The only way to stop/kill usb is to switch off your system. I assume there is nothing in the system bios relating to sleep mode on the motherboard?

 

Not quite. In sleep mode they will not be maintaining a communication to the device and when using things like Audio Interfaces that have timing with the ASIO driver, when it gets disrupted the audio application can often lose connection completely and cause the driver to lock up. Seems it is much more of an issue with later versions of Windows than earlier ones but basically you never want your audio interface to disappear when you are using ASIO drivers with an application. WASAPI/Direct is normally fine as the software communicates with the windows mixer/driver not with the hardware direct.