utorrent makes computer restart or cuts connection

[zigzagman]

i think ever since utorrent was last updated, the program has been doing these things whenever i leave it to dload something.

it often makes my computer suddenly restart. other times it will stay up dloading for about 10-20 mins then the connection to my router is lost (it doesnt say that the connection is lost, but speeds go to 0.0 and browsers no longer work - i have to "repair" to get the wireless working again).

all this only happens when utorrent is runnings, as far as im aware. its annoying because i usually leave utorrent on when im away during the day, but now when i come back to it, its either waiting at the welcome screen in windows (comp has restarted), or its sitting at 0.0 and info shows that it only dloaded about 2% on each torrent before it shut down.

is any of this common? any way of fixing?

[µtorrent-Guest]

make shure your PC is absolutely malwarefree!

If this is the case then its that your network equippment can't handle BT traffic properly. Try disabeling DHT in µtorrent. this is one measure to reduce the traffic. another is to limit the conections in the torrents tab of preferences

[NaraJin]

Yeap, same problem here.

Tried firmware fix on router, and limiting utorrent connections. Nothing seems to work so far.

[Ultima]

And you tried disabling DHT already? And patching TCPIP.SYS if that doesn't help?

[Firon]

Turn off automatic rebooting and see what's BSODing. Usermode processes can't do that, so it's either a) bad hardware broken drivers c) broken kernel-mode software (firewall/av/etc)

[JellyBelly]

Same problem for me here.

I seed about hundred torrents on the bootlegsite Zomb torrents and my system gives an error and reboots a couple of times a day. Also sometimes my connection with the wireless router got broken.

I don't have this problem with utorrent 1.3. Utorrent 1.4, 1.5 and Azureus are giving this problem. Can't use utorrent 1.3 anymore because only the newer versions are allowed on Zomb Torrents.

At the moment I am using BitComet 0.64. My system is now running for 4 days in a row and my PC didn't reboot a single time and also my wirelss connection didn't went down.

Last week I formatted my PC and did install everything fresh but I still have this problem with utorrent.

Any ideas?

[Firon]

JellyBelly: did you turn off the automatic rebooting so you can see what's causing the crash? Control Panel -> System -> Advanced -> Startup and Recovery

[JellyBelly]

I didn't turn off the automatic rebooting because my system goes on with the seeding after the rebooting. I will turn it off this evening to see what message I get.

Thanks in advance for the help!!

[NaraJin]

Would disabling DHT work better than limiting connections? I'm not exactly sure what patching the TCPIP.SYS would do. Care to explain what it does or how to do it? A link to it would suffice. Thanks.

[Firon]

If your PC is rebooting, then DHT and so on don't really have anything to do with it. Turn off automatic restarting and write down the error message.

if it's your internet that's not working, http://www.utorrent.com/faq.php#Modems_routers_that_are_known_to_have_problems_with_P2P

Try those instructions.

TCPIP.sys patch -> http://www.lvllord.de/?lang=en&url=downloads

[zigzagman]

my router is a BT (British Telecom, lol) router that came with the connection (for sum strange it wouldnt work with my old Linksys from america).

as far as i could see its not listed as problematic (and it never has been in the past).

i tried the TCPIP patch, and disable the auto restart. will post updates tomorrow, as i will leave utorrent running all day and see what has happened when i return.

[NaraJin]

I have a d-link 524 which isnt really on the list. However, I haven't had this problem before with my old router so I think it might be the router which causes the disconnect. Tried limiting connections to 100 and disabling DHT but apparently it still disconnected. Already got the d-link company firmware upgrade. Btw, is 10 concurrent TCP connection attempts the default windows limit? How does that translate to the 750 default global connections of utorrent? It looks like there's a big difference there, if they're the same. It seems to me this patch just increases the limit of concurrent TCP connections but how could other machines survive without the patch and maintain a big number of connections?

[µtorrent-Guest]

because it is not the number of connections that is limited but the number of connections that are not fully established! (aka. half open) concurrent TCP connection ATTEMPS not connections are limited! you can have connections to hundrets or thousands if your network equipment can handle that. but you can in xp sp2 only shout hello to 10 at the same time. if this ten are responding then you can shout out to ten again and see if they respond and establish the connection

So to patch this limit away will not nessesaryly mean faster Downloads but only faster Shouting.

[zigzagman]

success.

i disabled DHT as well as patching the TCPIP and left utorrent on all day. it was still on when i came back with all dloads finished (except one, which has no more seeders )

thanks for your support!

[NaraJin]

Thats good man!

Unfortunately, for me even after patching TCPIP and disabling dht, limiting connections it still cut the connection this morning when I checked(ie. couldn't web surf). I'll try an even lower connection limit(lowest I tried is 100). I have a feeling that it might not be the connections that mess up my connection. But what other things can I do?

[Ultima]

Try connecting directly to the modem.

[NaraJin]

Lol, I think the point here it to make it work with the router since I'm on a network. Its been working so far for 4 hours or so now with new trial settings. Hopefully it works till the morning.

[Firon]

It'd just be to test if the router is the cause.

[zigzagman]

alas, i spoke too soon. just recently my utorrent stopped the connection again. i reverted back to 1.4 but its still no help...

i also got another shutdown, but bcuz the automatic shutdown was turned off i got a bluescreen instead. this is what i gather was the problem:

RQL_NOT_LESS_OR_EQUAL

then the bottom code thingy was:

***STOP 0x0000000A (0xC0000000, 0x00000002, 0x00000000, 0x804F164A)

can anyone make sense of this?

[Firon]

Didn't it have any more info in the error? Usually it says what driver or something was related to it.

That being said, that error is generally caused by faulty hardware or broken drivers.

[JellyBelly]

I got the following error message:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

STOP: 0x000000D1 (0x00000030, 0x00000007, 0x00000000, 0xB9EA59A0)

viamraid.sys addres B9E9B000, datestamp 4063e304

After several hours of Googling I found out that it's possibly a problem between the VIA Serial-ATA Raid Controller (VT8237) and my Maxtor S-ATA drives.

I updated the driver for the S-ATA Raid Controller to the most recent (v5.20) so I hope the problem of the rebooting is over now.

About the wireless connection: I patched the TCPIP.sys to a value of 50 and also set the net.max_halfopen to 50. I also updated the driver for my NetGear WG111v2 USB 2.0 adapter. I couldn't update the firmware of my NetGear WGR614v6 router because it has special firware from my ISP.

After this I still have problems with my wireless connection while BitComet runs fine.

Has it something to do with some settings in utorrent?

I have the following settings:

- global maximum number of connections: 1000

- maximum number of connected peers per torrent: 500

- number of upload slots per torrent: 100

- maximum number of active torrents (upload or download): 150

I have these high numbers because I have about 100 torrents active on the Zomb Torrents Bootleg site (I almost seed 24/7 on maximum upload speed). Not all the torrents have leechers at the same time. Most of the time around 15-20 torrents have leechers.

What are the best settings to get rid of the problems with the wirless connection and to still seed about 100 torrents.

[Firon]

Yeah, according to that your VIA RAID drivers are the ones causing the BSOD. Also, net.max_halfopen MUST be lower than the value tcpip.sys! Set it to 40.

Um, your wireless adapter or router probably can't handle that many connections. Unless you have 100mbit, you shouldn't be using that many upload slots, connections, or torrents (and even then, you STILL shouldn't)

[JellyBelly]

Thanks, I will set the net.max_halfopen to 40.

About the number of connections, connected peers per torrent, upload slots per torrent and number of active torrents: I think thats it's possible to seed 100 torrents because I do the same with BitComet without problems. It's not that my wirless connection is cut (or that the USB adapter gives a connection of 1 MB/s instead of 54 MB/s) every hour or so. It happens about once a day.

Is said earlier I have about 100 torrent in Utorrent of which 22 torrent have leechers at the moment. I uploaded all these torrents in the past and want to keep them active in case someone wants to download a bootleg.

Maybe I can lower the values because not all the torrent are active at the same time. Maybe something like this:

- global maximum number of connections: 500 instead of 1000

- maximum number of connected peers per torrent: 200 instead of 500

- number of upload slots per torrent: 50 instead of 100

Are there any other setting that I have to change?

[Switeck]

If you're really running 100 torrents at once, I hope you can upload at least 1 KB/sec per upload slot on each active torrent.

So reduce the upload slots PER torrent to only 1 or 2.

Reduce the max number of connections PER torrent to only 40.

You can leave global max connections at 500, though even that is excessive for a weak router or DSL/cable modem.

What upload bandwidth are you using in µTorrent?

[µtorrent-Guest]

Switeck, what would you bet with me that he might be just a normal "Random J. Household"-Internetuser with a ~1 MBit Uploadline ?! :-(