NOD32 vs. torrent - FIGHT!

A copule of days ago I left my recently acquired notebook trough the night downloading with μtorrent. When I woke up the download had barely begun, and the HD was at full load. Tried again and the problem repeated- μtorrent would start to download and like 30 seconds later the HD would get fully loaded and the download rate went down. And the HD would still be at full load even after I closed μtorrent. So I start to track what's wrong, focus on ZoneAlarm first, found nothing, moved on to NOD32 and found out that if I kill the process nod32krn.exe everything goes back to normal.

So next step I added μtorrent to NOD32's exclusions in AMON and IMON, to no avail. Everything remained the same, so I decided I should share and see if someone else knows how to handle this. Any ideas? System is a Dell Inspiron 6400, on XP MCE. I use μtorrent 1.5 build 437, and NOD32 version 2.51.8. Help is appreciated!

 

I usually use bitcomet. But the other day I had a torrent that kept crashing bitcomet (very weird) so I used utorrent and it ran fine throughout the DL. Oh ya I have both NOD32 and zone alarm.

I don't quite understand what you mean by HD and full load. You mean being accessed or is it being filled with files/space disappearing?

 

It's being constantly accessed, and it continues even after i close μtorrent and doesn't stop until I terminate the process nod32krn.exe.

 

Do you have the option (in utorrent) set to reserve the disk space before hand. I mean create the files (fake files) before the download begins. I hope you understand what I am refering to, if not I can dig out the exact option.

What I am thinking of, is that NOD32 is trying to scan these disk reserving "fake files" and for one reason or another is going into this state of full blast HDD access.

 

As a matter of fact I do, I'll check it right away. BTW, thanks for your quick reply!

 

Ok... this is kinda weird. I thought it was turned on because I saw the file it created and it has the full size (it was pre-allocated). But under preferences the "pre-allocate all files" checkbox is unchecked. And it never asked me to allocate the file, nor I have any idea on where to set that for a specific file. I do belive you might be right in that this could be what's causing the strange behaviour.

 

Sorry I cannot help with utorrent because I rarely use it. I can barely understand the awkward behavior I sometimes get from bitcomet

 

Hey, no problem. You might've pointed me in the right direction, I just learned μtorrent always pre allocates the files that are actually downloading, to prevent disk fragmentation. But there's a way to disable it, just learned here. So I'm gonna try it now.

 

Wahoo! Problem solved. Big thanks!

 

Your welcome

glad it was a simple problem/solution