HAstraeus

Established Members
  • Content Count

    11
  • Joined

  • Last visited

Everything posted by HAstraeus

  1. OK, time to (re?)report a long-standing problem I've been having with uTorrent 'hanging' every now an then, as it as been getting worse lately. Basically, if I start up uTorrent and leave it running, every once in a while all traffic will suddenly drop to 0 and stay there indefinitely. The program window is responsive, I can check on all sorts of statistics, but there are three key factors that tell me something is wrong. First, nothing gets done; as I said, download and upload both drop to 0 and stay there. Second, my internet connection is taken down with it. Third, and most annoying, the only way to end uTorrent is to restart my computer. I can tell it to exit, but nothing happens. If I open up process explorer and tell it to end process (or process tree or whatever), nothing happens. Even logging off does no good. There seems to be one condition or factor that triggers these episodes: uTorrent has to be competing with something for bandwidth. My maximum connection speed (up and download added together) is around 1 MB/s as established by regular torrent use, so if either uTorrent's usage doesn't go that high (not often) or I don't use the internet while it is using that bandwith (annoying but far more frequent) then I'm generally OK. If, however, I forget uTorrent is running and open up Firefox for instance, somewhere along the line I'll usually be rudely interrupted by a 'connection timed out' screen, and sure enough uTorrent has crashed my connection again. My stopgap solution to this mess has been to run uTorrent when I'm sleeping, and until now that's worked relatively well (though not perfectly). This time, however, I see my uTorrent capping at 200-400KB/s, suggesting to me that other members of my family appear to be using significant amounts of bandwidth as well (who knows, maybe even uTorrent). The problem is that this usage seems to fulfill the 'bandwidth competition' clause that I noted seems to be the trigger for the crashes, and now uTorrent has taken to fouling up within the hour on average. As it is not practical for me to sit here and prod my computer every time it conks out, and I cannot reasonably ask my family not to use the internet, I'm hoping we can get this thing fixed once and for all. Additional data: -Windows 7 64-bit administrator account, no antivirus/firewall/etc. software that might block connections -Bluetooth-WiFi interference was once implicated as a culprit, and I have since switched to a wired connection (powerline adapter) to no apparent effect. -I am unable to reach my router (192.168.1.1) when my connection breaks. -uTorrent has died again as of my typing these words.
  2. I've been having a problem with utorrent getting stuck if I leave it alone too long. I discover that about an hour or two after I start it download and upload both drop down to 0 and stay there until I reset my internet connection (web browser works fine so it's not my connection's fault). Also sometimes when this happens utorrent freezes entirely and I can't even kill it with task manager. The only solution I've found so far is to keep resetting my internet connection but I can't be doing that every hour or so.
  3. or if that doesn't work, 5. The problem seems to be uTP; setting it to 5 turns that off.
  4. There's gotta be something weird going on with the uTP. 7 chokes my download to a fraction of its usual speed and 13 or 15 pretty much kill everything but I get my normal speed back as soon as I set it to 5.
  5. Uhhh did anything happen with the element not found bug I brought up?
  6. Err, here's the log as it stands now (■■■=censored): [2009-02-12 14:04:41] NOTE: Settings file found in directory of executable; using that. [2009-02-12 14:04:41] IPv6 is installed [2009-02-12 23:41:55] Help file not found in settings directory, attempting to download [2009-02-12 23:41:57] Could not download help file. Error: HTTP Error 404 [2009-02-12 23:42:05] Help file not found in settings directory, attempting to download [2009-02-12 23:42:06] Could not download help file. Error: HTTP Error 404 [2009-02-13 00:10:52] ReadFile error: _____padding_file_9_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■ [2009-02-13 03:00:05] ■■■: No longer have piece: 0 [2009-02-13 03:00:05] ■■■: No longer have piece: 2 [2009-02-13 03:00:05] ■■■: No longer have piece: 3 [2009-02-13 03:00:05] ■■■: No longer have piece: 8 [2009-02-13 03:00:05] ■■■: No longer have piece: 10 [2009-02-13 03:00:05] ■■■: No longer have piece: 15 [2009-02-13 03:00:05] ■■■: No longer have piece: 16 [2009-02-13 03:00:05] ■■■: No longer have piece: 17 [2009-02-13 03:00:12] ■■■: No longer have piece: 635 [2009-02-13 03:00:13] ■■■: No longer have piece: 661 [2009-02-13 03:01:04] ■■■: No longer have piece: 4948 [2009-02-13 03:01:04] ■■■: No longer have piece: 4949 [2009-02-13 06:09:19] ReadFile error: _____padding_file_10_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■ [2009-02-13 12:11:58] ■■■: No longer have piece: 0 [2009-02-13 12:11:58] ■■■: No longer have piece: 2 [2009-02-13 12:11:58] ■■■: No longer have piece: 3 [2009-02-13 12:11:58] ■■■: No longer have piece: 8 [2009-02-13 12:11:58] ■■■: No longer have piece: 10 [2009-02-13 12:11:59] ■■■: No longer have piece: 15 [2009-02-13 12:11:59] ■■■: No longer have piece: 16 [2009-02-13 12:11:59] ■■■: No longer have piece: 17 [2009-02-13 12:12:05] ■■■: No longer have piece: 635 [2009-02-13 12:12:05] ■■■: No longer have piece: 661 [2009-02-13 12:12:55] ■■■: No longer have piece: 4948 [2009-02-13 12:12:55] ■■■: No longer have piece: 4949 [2009-02-13 19:04:34] ReadFile error: _____padding_file_10_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■ [2009-02-13 19:51:25] ■■■: No longer have piece: 0 [2009-02-13 19:51:25] ■■■: No longer have piece: 2 [2009-02-13 19:51:25] ■■■: No longer have piece: 3 [2009-02-13 19:51:25] ■■■: No longer have piece: 8 [2009-02-13 19:51:25] ■■■: No longer have piece: 10 [2009-02-13 19:51:25] ■■■: No longer have piece: 15 [2009-02-13 19:51:25] ■■■: No longer have piece: 16 [2009-02-13 19:51:25] ■■■: No longer have piece: 17 [2009-02-13 19:51:35] ■■■: No longer have piece: 635 [2009-02-13 19:51:35] ■■■: No longer have piece: 661 [2009-02-13 19:52:22] ■■■: No longer have piece: 4948 [2009-02-13 19:52:22] ■■■: No longer have piece: 4949 In other words that's 3 times it's given me the "Element not found" error and 3 times I've had to force a recheck and restart the torrent (losing several pieces in the process, as you can see). I'd also like to point out that this problem isn't limited to these so called "padding files", it's just that in this torrent those were the ones I decided to skip (for obvious reasons); the same problem will occur regardless of the size or type of file as long as it's set to be skipped in a partially downloaded torrent. P.S. On an unrelated note I'd also like to ask if there is some explanation for the help file 404.
  7. I've switched to 1.8.2 but I'm still getting this problem: From time to time torrents that are finished downloading but not complete (i.e. not all of the files are selected) will give me an "element not found" error. Seeing as how it (still) isn't on the fix list I assume this problem, among many others it seems, plagues the new alpha as well (correct me if I'm wrong).
  8. Nope, everything on drive C: with my OS. I wonder if it's a Vista bug...
  9. Then what's causing the file missing errors? I'm rechecking after it gives me the error, not before. Edit: Apparently I don't have to close utorrent for it to happen, it just did it again... Edit: Wait a minute it says "element not found" not file missing...
  10. I seem to be having a minor problem with 1.8.1 and it doesn't look like it's on the fix list: If I close utorrent while uploading torrents that are finished but not completely downloaded (i.e. only some of the files are selected), then when I start it back up sometimes the first or last chunks of the selected files have gone missing, causing a file missing error.