this is a really wide-spread problem. As far as I know there is no "one for all"-solution out there.
Some succeed in reinstalling the ADT.
Some in starting an emulator-instance before Eclipse does and then "reuse" that instance.
Some succeed in clearing the emulator (Link
). <-- Could help if you upgraded SDK to the current version(m3-rc37a).
Some in killing the adb.exe pretty often o_O .
We can hope on the next update.