cebec

Yes, on Windows XP Pro SP2a with an E-MU 1616m running ASIO or MME (WDM/KS) drivers, a lot of crashes result in Max staying resident and unable to be killed via the Task Manager. A hard reboot becomes necessary if I intend to continue working in Max.

max-stays-resident-after-crash

I have the same issue, which I suspect to be related to my m-audio 410 asio

drivers. I really wish I could isolate the crash and make a proper bug

report, but I have never managed to nail the problem down so I could

reproduce with a single max patch. Afaik there are more people experiencing

this on XP sp2. I know this isn't helping you much, but I just wanted to let

you know. Hopefully someone can locate this bug someday...

I have the same issue, which I suspect to be related to my m-audio 410 asio
drivers. I really wish I could isolate the crash and make a proper bug
report, but I have never managed to nail the problem down so I could
reproduce with a single max patch. Afaik there are more people experiencing
this on XP sp2. I know this isn't helping you much, but I just wanted to let
you know. Hopefully someone can locate this bug someday...

 do any good to you guys? this seems to be 

related to driver issues, maybe this could help somehow.

in xp pro, there is a taskkill command line utility, that might be able to 

forcefully end a task(start->run, taskkill /F /IM max.exe).

does http://www.asio4all.com/ do any good to you guys? this seems to be 
related to driver issues, maybe this could help somehow.
btw, are you using xp pro or home?
in xp pro, there is a taskkill command line utility, that might be able to 
forcefully end a task(start->run, taskkill /F /IM max.exe).

Max stays resident after crash