Task Killing in Windows, Why 3 times ?
~ CycleBurner ~
snap, crackle, pop
I wondered the same thing for a while, but I think it's largely coincidence. After you end a task, look for a task called dumpprep to pop up. If you don't want to send any crashy goodness to Microsoft, just kill the dumpprep process - the one you wanted to kill should die along with it.
Microsoft usually gets it right the third time.
I think windows simply calls the programs own function for quitting at first. Before it tries to forcfully remove a program from memory you usually get a pop up saying X is not responding.
This is normal, reasonable and safe behavior.
"If you don't like that, switch to the "processes" tab and kill the task on the spot. "
Fog Creek Home