KVR Audio

D-Fusion · Post by **D-Fusion** » Wed Oct 03, 2012 8:41 am

When it happens it is usually a usb device that makes it stay.
If you have a keyboard or soundcard connected thru usb you should unplug it and the zombie will die

Clydewinder · Post by **Clydewinder** » Wed Oct 03, 2012 6:15 pm

D-Fusion wrote:When it happens it is usually a usb device that makes it stay.
If you have a keyboard or soundcard connected thru usb you should unplug it and the zombie will die

That is the correct answer.

LawrenceF · Post by **LawrenceF** » Wed Oct 03, 2012 6:19 pm

Cool. The only USB devices on my desktop (beside the keyboard and mouse anyway) are an iLok and a Midiman 4x4 so I'll try that when it happens again.

Thanks for the tip.

D-Fusion · Post by **D-Fusion** » Wed Oct 03, 2012 6:27 pm

The Midiman used to do this allot so next time try to unplug it when it crash.

It happens mostly with Usb soundcards, usb 2 midi or midi keyboard so no need to disconnect ilok or or typing keyboard/mouse.

CrushCrawfish · Post by **CrushCrawfish** » Wed Oct 03, 2012 9:03 pm

D-Fusion wrote:When it happens it is usually a usb device that makes it stay.
If you have a keyboard or soundcard connected thru usb you should unplug it and the zombie will die

Unfortunately my 1010LT is a PCI card.

However, that does give me an idea though! Maybe if I went into the device manager, disabled the card, and then re-enabled it... I'll have to try that the next time my DAW goes down in flames.

D-Fusion · Post by **D-Fusion** » Thu Oct 04, 2012 10:14 am

CrushCrawfish wrote:
D-Fusion wrote:When it happens it is usually a usb device that makes it stay.
If you have a keyboard or soundcard connected thru usb you should unplug it and the zombie will die
Unfortunately my 1010LT is a PCI card.

However, that does give me an idea though! Maybe if I went into the device manager, disabled the card, and then re-enabled it... I'll have to try that the next time my DAW goes down in flames.

Sounds like a good plan

CrushCrawfish · Post by **CrushCrawfish** » Fri May 10, 2013 9:35 pm

Sorry to be a necromancer, but I feel that what I have to add may be relevant. It seems that this problem stemmed from either M-Audio's driver or hardware design. I've since switched to a Focusrite Saffire Pro 14, and now any time an application using ASIO crashes, the driver is properly released and the application vacates the memory space it was using.

Earlier as a test I opened up Studio One, opened the task manager, and then intentionally crashed S1*; upon selecting "Close the program" in the error handler dialogue, Studio One.exe disappeared from tasks list, and I was able to start S1 again immediately afterwards without any errors or warnings.

The Saffire's interface is Firewire 400 and the controller in use is an LSI FW322/323 that's directly on the motherboard.

CrushCrawfish wrote: However, that does give me an idea though! Maybe if I went into the device manager, disabled the card, and then re-enabled it... I'll have to try that the next time my DAW goes down in flames.

Also, this did not work for me.

* Drag in a Battery 3 .musicloop utilizing missing samples - which causes Battery's "missing files" dialogue to open up - then push said dialogue into the background, right click on the newly inserted track, and select Remove Track and Instrument.

hibidy · Post by **hibidy** » Fri May 10, 2013 11:29 pm

This is an issue with maudio, it's confirmed. Whenever I have a crash, I simply restart. I crash so rarely, it's just not a big deal. That reminds me though, I have 14 laying around still and I want to try it again for s..t's and giggles.

paradiddle · Post by **paradiddle** » Fri May 10, 2013 11:48 pm

On win xp when the daw crashed the process would stay there also "zombie". Closing any connected usb devices (midi keys) would make the app go away but on win 7 it's doesn't do that for me. The process stays there for like 10 minutes no matter if I close the usb keyboard even if I try to terminate it.

metamorphosis · Post by **metamorphosis** » Sat May 11, 2013 12:24 am

CrushCrawfish wrote:Of all the DAWs I've used over years with my Delta 1010LT (Acid Pro 6, FL Studio 8 trial, Cubase 5/5.5, Studio One 2, Reaper 4 trial), whenever one has crashed it has stayed memory resident - opening up the task manager will show its process still there, eating up the same amount of memory as it was when it went down. Even worse is that they're "zombie" processes; I can't kill them no matter what method is tried, with the only solutions being to either wait around an hour for the process to go away on its on or to reboot the system.

Why does it have to go away? Aside from hogging up a lot of memory it also keeps the ASIO driver locked, meaning that whenever I try to start it (or any other application that uses ASIO) up again, it cries about ASIO being in use/unavailable.

DAW crashes happen about once a week for me now (about ten times daily with Acid), but it's still incredibly annoying when it happens. What exactly is going on? Is there any remedy?

For the record, I've always made sure that my 1010LT's drivers are up to date.

I'm guessing this is a Win7 thing, because I've never had this problem with XP.

hibidy · Post by **hibidy** » Sat May 11, 2013 1:59 am

I used to have issues like that all the time with xp. Me thinks you are very lucky

LawrenceF · Post by **LawrenceF** » Sat May 11, 2013 2:32 am

The name is perfect.

It is indeed "the living dead".

brok landers · Post by **brok landers** » Mon May 13, 2013 6:40 pm

paradiddle wrote:On win xp when the daw crashed the process would stay there also "zombie". Closing any connected usb devices (midi keys) would make the app go away but on win 7 it's doesn't do that for me. The process stays there for like 10 minutes no matter if I close the usb keyboard even if I try to terminate it.

you still have to kill it manually from the taskmanager. but if you unplug the usb device once you have killed the process from the taskmanager, the process will be deleted, as soon as you unplug the usb device... in my case it's actually enough to turn off the usb device, no need to unplug it physically.

Resplendence · Post by **Resplendence** » Tue May 21, 2013 10:08 am

hibidy wrote:This is an issue with maudio, it's confirmed. Whenever I have a crash, I simply restart. .

For M-Audio, drivers are apparently nothing more than a necessary evil. I have two M-Audio firewire devices and their drivers don't support either hibernate or suspend causing the system to lock up. On top they did not do their homework by not unmapping shared kernel memory from a process upon termination leaving me with nasty BSODs. A typical beginner mistake that I pointed out to them with bugcheck analysis and explanation that was throroughly ignored years ago but the problems still present today.

Now I have to admit, they are not the only audio interface company that completely ignores the impact of customer experience by shipping possibly good hardware products with completely bullshit drivers on Windows. It is a problem that exists among all markets but it seems even more so among audio companies. One suggestion is that they should not let their hardware engineers also do the drivers. Instead they should be using the expertise of people who are specialized at that task.

//Daniel

hibidy · Post by **hibidy** » Tue May 21, 2013 6:40 pm

Yeah, I don't know why that happens either. As long as I restart my computer after a crash, I don't have BSOD. I like my profire 610 though. It sounds good and isn't any cause of crashes.

Actually, other than the occasional crash I don't have many so it's not a big deal.

Any DAW that crashes becomes a "zombie"