![]() ![]() Got a new error - "Windows ran out of memory. This time read cache wasn't even close to full. :EDIT: I just updated to 3.4 (build 30660) and the problem still stays the same. I'm using currently uTorrent 3.3.2 (build 30544) and I haven't seen any fixes in any versions I've used for a some time. My current disk cache -settings from uTorrent are as an attachment. Previously I didn't have RAID at all, just normal different aged and types of disks and SSD. My system is now on 2 x SSD RAID 0 and I'm using 2 x 3TB WD Red disks as an RAID 1 array for my downloads at the moment. I did clean install of Windows 8.1 and I had Windows 7 previously. I upgraded motherboard, processor, memorys and disks and still uTorrent continues to crash the same way. This problem was also with my old hard drives and SSD and still with my brand new hard drives and also SSD. If the downloadable files are small, such as 1GB, there's no problems. Read cache also gets bigger automatically as it gets full. It seems to be working perfectly after continuing, no matter how fast it comes. Opening it again shows it is missing the previous file I just started to download and re-downloading shows the file is still there and it starts checking the already downloaded parts. During this time I cannot even use my web browser (Chrome), it just says something like "Waiting for cache." at the bottom bar.Īfter the crash computer continues working normally but uTorrent forced to quit itself. I've noticed how read cache goes full (doesn't get bigger as it should) just the moment it crashes. +8GB with speed +15MB/s uTorrent gets jammed and crashes quickly, within a minute. I've tried to find specific answer to my problem but cannot find one, so here I am, asking for your help oh mighty helpers
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |