New
#21
Yes!
So I decide to completely remove NOD32 from system, as it was most suspicious piece of software to me. It looks like that problem is solved. I copy files from C to D disc for almost an hour but can't repeat problem with memory now when NOD32 is removed from the system so I suspect it was NOD32 causing the problem. If problem came back I will inform you here.
Thanks to all who tried to help me solve this problem.
If someone wants to see how it looks before I take NOD out, here is screen snapshot: