I wasn't being arrogant, I was merely stating a fact.
Actually, if you keep taskkilling in a loop for a while, svchost will give up starting it. Unfortunately I believe it also disables the service, causing problems with SQL server.
Also- what if SQL server is in the middle of a transaction when you taskkill it? databases could get corrupted, file handles remain open, meaning starting it again later (assuming the fact that svchost hasn't already disabled the service because it kept "crashing"), would cause SQL server to have problems gaining exclusive access to it's own databases again.
Killing processes is never a really clean solution, even if it would appear so- even when it works- terminating processes leaves a lot of cruft, from open file handles to open registry keys and even open devices (try killing a burning program when it's in the middle of a burn...)