windows xp process monitor kill restart memory threshold

Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute. Second 4: 10+1000*10 computers (11110 new ones)Īll the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). If you also consider that each of those infected computers will infect 10 others at the same rate: Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?. This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and 'reduce the threat' of worms spreading fast without control. Remove the limit on TCP connection attempts

Note the information below only applies to Windows XP Service Pack 2.

Please make sure you understand what you are doing before making any changes to your Operating System. In addition to the tweaks already covered in Win 2k/XP Registry Tweaks and More Win 2k/XP Tweaks, the Windows XP Service Pack 2 introduces a few new issues covered in the article below.

Windows xp process monitor kill restart memory threshold