I managed to get the server reset finally. It's still a bit of a mystery what actually happened. I was able to connect and run task manager, but it only showed 6 processes all at 0% CPU, but said 60 processes were running and CPU was at 100%. TWGS was not among those processes showing, and I managed to run it with the SHUTDOWN command in case it was out there somewhere, but that just brought TWGS online again. That means TWGS was offline, and that usually kills whatever processes were started by TWGS (NONPSERV, TW2002, etc). So I'm baffled. I guess I'm going to keep the current version up there and watch it to see if I can catch anything going bad. At least now I know what to do to get back under control if it happens again. Shutdown /r /f is your friend
So I guess let's just do what you were doing yesterday when it blew up and see what happens. I'm thinking that the problem I created with orphaned TW2002 processes was just a coincidence and not the cause of the crash. I just don't see evidence that there were hundreds of processes running at all, and those would shut down with TWGS anyway, so I'm looking for more clues on this one.