Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I closed application, but the process remained in the list. I try to stop in from the task manager, but nothing happens. No error messages, process just stays in the list. I try to debug it, but the debugger says:

Unable to attach to the crashing process. The requested operation is not supported.

This happens with VS2008 and some other programs, sometimes.

How to kill it?

share|improve this question
    
That's one of the reasons I switched to Linux. Though I experienced this problem under Win XP, it seems that it hasn't changet since then. –  petersohn Apr 30 '10 at 7:07
2  
According to samba.2283325.n4.nabble.com/… there's exactly the same situation in Linux - processes waiting on the kernel are unkillable. This is one of the reasons I switched to Windows. –  ta.speot.is Jun 12 '11 at 2:25

3 Answers 3

up vote 9 down vote accepted

Unfortunately, the only real recourse is to reboot.

I've had this problem too, and I could find absoltely no way to successfully kill the crashed process. I tried just about every pskill/similar app I could find, and they all fail.

As I understand it, it's caused when the offending process loads a system driver, and then sends it an request that it fails to complete. Apparently the kernel can't properly deallocate the memory from the process when it closes because the crashed driver is in a IO wait state that requires access to the process address space.

(Mostly cribbed from) http://blogs.technet.com/markrussinovich/archive/2005/08/17/unkillable-processes.aspx

share|improve this answer
    
Yup, that is certainly the most common cause of this sort of thing. Most of the unkillable processes I have seen were either related to the CD-drive (eg EAC.EXE) or the TV tuner/video card (eg ATIMMC.EXE). In both cases, it comes down to a driver fault, and anyone who’s learned and done driver work will know how problematic things can get at that level, and what kinds of seemingly “strange” effects they can have in userland (BSODs at least are definitive and clear). –  Synetech Jun 12 '11 at 3:24
    
@ Synetech inc. - All the problems I had were disk related, or in software that really had no need for a driver at all (I have NO idea why the decided they needed to run in the kernel). I don't think you can make any blanket statements about what kind of software has most often has un-killable crashes. –  Fake Name Jun 13 '11 at 0:40

Sometimes the process could be blocked on a resource or thread or something, and quitting or freeing that up, frees the process and lets it end. It is somewhat similar to how when you delete (to the recycle bin) a file in Explorer that is in use, it doesn’t actually go away and seems stuck (without immediately returning an in-use/locked error), but if you quit the program that has it locked within five seconds, the file suddenly disappears.

I have seen this happen on occasion, especially with programs that have a pop-up dialog or something that somehow gets hidden; finding a way to dismiss the dialog allows the thread to terminate, thus allowing the process to end.

I suspect that with the increase in, yet still relatively new practice of multi-threaded programming, things like this will become more common, at least for a while.

share|improve this answer

It is likely that the programs you are using were developed before Windows Vista/7 and are incompatible with the changes made.

Your best bet is to locate the executable for the programs which have this problem, right click, go to properties, then select compatiblity, finally select Windows XP as the compatibility mode.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.