File System Weakness

It is the second time that I am observing this.

Ktorrent included in PCLinux has this tendency to mark many files as corrupt. Compared to the eventless transfers experienced in utorrent under Windows, Ktorrent' behaviour is disappointing and irritating.
Large downloads suddenly become corrupt and after a recheck bulk of the downloaded data is trashed. Could this be because of Ktorrent or the ext2 file system? Doing a fsck on the partition gives a clean status. So how did the file get corrupt? And why did it get corrupt after most of it has been downloaded. THe error I confronted previously was when after the download was complete, the file would be checked, this would reveal a few corrupted pieces, then these would be downloaded, and on a recheck again a few pieces would be found corrupt and the process would continue. This way I had to download almost twice the actual file size before the downloaded file was found to be free of errors.
I consider this a major problem, since having to worry about the fidelity of the data is not appreciated. I wonder if converting the partition to ext3 would help.

Update: A few minutes later
After the data corruption problem, I stopped Ktorrent. Then launching any program would lead to a crash. So I restarted the system.
Shock after shock. Opensuse would not boot, even in safe mode, PCLinux would not boot even in safe mode. In all normal options I would get a blank screen, in the Fail safe mode I would get a CRC error.
The last part was a hint that the RAM would be to blame. But, then I tried the many live CDs that I had collected. Centos, Knoppix, Opensuse, PC Linux, all would stop with a blank screen. Then I removed the hard disk, thinking that the corrupt partition would be preventing the creation of a temporary swap file. That did not rectify the problem. Then I removed one of the RAM sticks, and things were back to normal. So now I am with 128 MB RAM (32 MB Shared with graphics). On getting back the PC Linux, I re ran the data integrity check routine, and guess what, all the downloaded content was detected. Relief.

So, a useful diagnostic message rather than a blank screen is needed. But I guess the CRC error is sufficient in many cases.