|
User Reviews/Comments:
rate:
avg:
![]() ![]() ![]() ![]() ![]() ![]() ![]()
This is not entirely accurate. When I set the "Optimal Settings" in TCP Optimizer and then rebooted my computer, I got a BSOD immediately when my wireless adapter tried to connect to my network. When I rebooted again, no BSOD, but winlogon.exe crashed with a fatal error. I restored my registry settings from right before I changed them with TCP Optimizer and rebooted and everything was stable again. So the registry settings TCP Optimizer changes can lead to crashes.
I stumbled upon this site when I was trying to troubleshoot my own BSODs that I never had on a particular computer before I ran "TCP Optimizer for XP" from comcast's site. I got 3 BSODs within two days after running it, but, after I reverted to old TCP settings two weeks ago, I had no BSODs since then. My interpretation is that it's the driver for the network card - changing TCP parameters in Windows registry could have such indirect effect. Of course, it's the driver to blame, however, normally, a user, naturally, should not care too much whose fault it is exactly.
|