Well, it seems that having VS .Net OFF my system has extended my up time a bit. I made it to almost 3 full days and just now crashed with that same old error that this thread is all about. So, as Rink observed, having the .Net Framework present is not necessary to have this bug happen, but it may make it more frequent. Also, some scripts may have this bug more happen more than others since I saw it or some OS configurations more than others, but I saw it more with Sysreset on Win XP than I have with UPP on Win XP. Others may have a different experience with different hardware and software.
Please post your experiences so Khaled can see what is going on, folks.
