Jump to content

Freeze only when download starts


Sammy

Recommended Posts

I have a problem and am looking for suggestions. I have looked but haven't found anything quite like this in the forum.

When I start uTorrent on my main computer it initially acts fine. The UI works, it adds torrents, if I start one it shows queuing and then as soon as the torrent goes to downloading the UI freezes and I think that all of uTorrent freezes too. The rest of the computer seems to be working fine.

This is clearly a software interaction problem because:

1) There are lots of services and things running on the computer but I can't find any references to any of them in the uTorrent forums.

2) Another computer running the same version of windows XP through the same switch connection to the internet runs uTorrent without problems.

3) If I start the problem computer in Safe Mode (with Networking) then uTorrent downloads and runs correctly so the problem must be something that is loaded in normal mode.

Any suggestions on how I go about identifying the conflicting code would be greatly appreciated.

Link to comment
Share on other sites

You may have broken your computer's Winsock LSP links by installing/uninstalling alot of stuff.

HijackThis.exe might help, by letting you know if your Winsock LSP is broken -- under Config, Misc Tools, check list empty sections, and click generate startup list. Check to make sure there's no errors in the Winsock LSP portion.

Link to comment
Share on other sites

Windsock LSP shows:

Enumerating Winsock LSP files:

NameSpace #1: C:\WINNT\System32\mswsock.dll

NameSpace #2: C:\WINNT\System32\winrnr.dll

NameSpace #3: C:\WINNT\System32\mswsock.dll

Protocol #1: C:\WINNT\system32\mswsock.dll

Protocol #2: C:\WINNT\system32\mswsock.dll

Protocol #3: C:\WINNT\system32\mswsock.dll

Protocol #4: C:\WINNT\system32\rsvpsp.dll

Protocol #5: C:\WINNT\system32\rsvpsp.dll

Protocol #6: C:\WINNT\system32\mswsock.dll

Protocol #7: C:\WINNT\system32\mswsock.dll

Protocol #8: C:\WINNT\system32\mswsock.dll

Protocol #9: C:\WINNT\system32\mswsock.dll

Protocol #10: C:\WINNT\system32\mswsock.dll

Protocol #11: C:\WINNT\system32\mswsock.dll

Protocol #12: C:\WINNT\system32\mswsock.dll

Protocol #13: C:\WINNT\system32\mswsock.dll

Protocol #14: C:\WINNT\system32\mswsock.dll

Protocol #15: C:\WINNT\system32\mswsock.dll

Protocol #16: C:\WINNT\system32\mswsock.dll

Protocol #17: C:\WINNT\system32\mswsock.dll

I haven't used HijackThis before so don't know if this is normal output. I don't see anything that screams out trouble to me in any of the HijackThis output.

Link to comment
Share on other sites

Winsock LSP isn't broken after all in your case...but those 17 protocols seems a bit much. I think I only have 5 on mine. I know of TCP, UDP, and broadcast/multicast protocols...so that only leaves 10+ more. :P

Your startup list is no doubt slowly adding up in length though with each install/uninstall of programs. Too many leave behind an extra DLL or 2 that you may not really need.

Have you tried any registry cleaning tools and/or DLL remover?

Link to comment
Share on other sites

I have used a couple of registry cleaning tools, Cleansweep and Registry Mechanic in particular. I'm not sure that they are being quite aggressive enough though. In order to avoid problems I've been assuming that if the registry was ok then extra dlls wouldn't hurt so I haven't been going after them very often.

Link to comment
Share on other sites

Use Win XP's own CTRL+ALT+DEL menu to see what services are running...and do lots of internet research on what each service is. It's a pain, but that's the best suggestion I have.

You could use Process Explorer for a little more info, but it mostly repeats what CTRL+ALT+DEL will show you.

Link to comment
Share on other sites

I have no trouble seeing what services are running and have a nice tool to help with that. Are you saying that all I can do is trial and error disabling (or even uninstalling) of services until I find the problem? There ought to be a better way to get some clues than that.

Link to comment
Share on other sites

Yup, probably had several of each, except for system security suites, over the years. The system is several years old, started out as Windows 2000 and then upgraded to XP but there is far too much that's good about the system for me to want to do a fresh install. I do have Norton Ghost running and it works well in making full image restores so I'm not adverse to rather drastic and otherwise dangerous experiments.

So what is it about uTorrent that tends to cause negative interactions with other software. I assume it is something about the way it interacts with the network since that's what it mainly does and my problem only starts the instant uTorrent actually starts downloading but why do all sorts of other programs work ok? Oh, by the way, Azureus does work on this machine but it tends to hog resources and I'd rather use uTorrent if I can. There MUST be some sort of debugging or monitoring or logging tool that will get to the bottom of this better than trial and error. Even if it takes as much time I might learn something useful in the process!!

Thanks for your continued help.

Link to comment
Share on other sites

I recently formatted and reinstalled this box for crashes and slowdowns I was getting.

Process Explorer was showing I had DLLs that weren't loading into their allocated memory addresses.

And that's about all I had to go on as to what was causing my crashes.

Link to comment
Share on other sites

  • 2 weeks later...

Well, I have uTorrent working finally after cleaning up a LOT of stuff. I'm still trying to figure out what the real problem was and will post the info if I ever figure it out. Some leftover Symantec junk seems the most likely so far.

Link to comment
Share on other sites

It might (have been) be a good idea to reinstall windows. An years old installation with a heap of software installs and removals including applications that nestle deep in your OS might have a lot of bugs that might pop up at any time. This was probably just one of them. And cleaning up is a lot of work and won't nearly prevent/remove as many of then as a new installation.

Link to comment
Share on other sites

It's a good learning experience to try to clean up a junked-up box.

But it's often an exercise in futility...so if you're in a hurry, just reinstall and make good backups!

A hard drive backup image of a fresh windows install can be almost a lifesaver.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...