Both Gads suggestions are really the key to getting the script to run stable. There's really nothing that can be done if you are moving around while the looter is "active". To make sure it won't crash on you most of the time, wait for the looter to become idle.
In addition to running other scripts that might be moving/opening items, it's also good that if you are using this script to not have things like Razor or UOS running actively. They tend to "butt" heads with EasyUO in a ghost-producing way.
I've mentioned this before, but if you get into a "rhythm" of play were you 1) stop, 2) kill, 3) remain still until killing is done, 4) wait for looting to complete, 5) move again. You can draw monsters to you by engaging them, but let them come to you while you're still. But if you run around like a spaz and loot willy-nilly, your personal corpse count will increase.
Before you ask, no I can't fix this. It's just how EasyUO handles items while it interfaces with the client. I've taken measures to mitigate this, but that's all I can do. Just about every looter suffers this same "feature". So if you can't change it, at least you can adapt.
Turbo mode probably won't affect your crashing. That's more when you should have looted a piece of jewelry, but didn't because of the way the Turbo mode was implemented. There are still a couple corner-cases where a "lootable" piece of jewelry will remain on the corpse. You will probably still miss things from time to time, and that also is affected by your rhythm of play. If you have a potion healer script running at the same time as looting is going on, it might cancel a drag/drop. Things like that.