Two Common Problems: Possibly Related?

So, the first time I got a message saying "Are you sure you want to delete 'WINDOWS'?" when I tried to empty the recycle bin, and then access was denied, I was worried about a virus. After looking around on the web for a bit, I figured out it was a corrupted recycle bin. It's strange though, since usually, when you have a corrupted recycle bin, Windows will tell you, and ask to remove it. Not this time though. In fact, you can't even remove it by force. The corrupt file I have in there right now, Dg26, cannot be deleted, and its attributes cannot be changed. All access is denied.

Until I reboot. Then whatever corrupted file I have in there dissappears...

Around the same time, I started having another problem that seems common on the internet. When moving (not copying) multiple files (especially big ones like videos) at the same time (using seperate move functions), the move will work properly. The file, however, will be left behind, exactly where it was, and all access to it is denied. It cannot be deleted, and its attributes cannot be changed.

Until I reboot. Then the bogus file dissappears...

Both these problems are not officially explained anywhere. Both are incurable (none of the solutions for a corrupt recycle bin or an uneditable file work) yet both solve themselves on a reboot. And, for me at least, both of them started at the same time.

I haven't tested it extensively, but I believe the first problem, in fact, caused by the second. I was just moving some large avi files, and the second problem occurred. I then tried to delete something, and the first problem occurred. I then browsed my now corrupt recycle bin, and found that the culprit, Dg26, is actually a 700MB Dg26.avi, a file very similar to those I was moving about except in name. So it looks like when moving multiple large files, the delete processes get broken somehow, leaving non-existant copies behind and non-existant corrupt files in your recycle bin.

This issue wouldn't matter much since it clears up on reboot, but sometimes I'm trying to clear up some space on a drive and the files stick around, or the recycle bin becomes corrupt so I can't delete anything without bypassing it, I'd rather not have to reboot. Not to mention the annoying BING sound every time access is denies to something.

Some other information:
The problems' beginnings also seem to coincide with my installation of a couple of SATA drives. After the first one, a WD 200GB, I didn't notice it, but I didn't move files from that drive much. The second one, a Maxtor 200GB, is where the problem normally occurs (ACDSee also seems to have trouble automatically refreshing its file list on that one to account for files that have been moved). So it could be connected to the fact that they're SATA, or specifically to the brand of the second one (though I have no idea at all how), or to nothing.

Does anybody have any information on cause/solution to the second problem? It seems common, like I said, but nobody knows why it happens or how to fix it that I've found.

 

moveonboot.

 

When your at this point .. "since it clears up on reboot ", can you clean out recycle bin? If yes, clean out all Temp/Tmp files on your system, reboot into Safe Mode and try defragging BOTH drives.
ALSO ... not having a clue what I'm talking about, but that's never stopped me ...
Kosma seems to create this issue when moving multiple large GB's (?) size media files. What happens when they exceed RAM and Page file memory allocation commitments.

 

Well, there are some small things that need to be cleared up in those threads. For one, while the recycle bin shows no files no matter what you do, actually browsing the directories in cmd allows you to find the culprit files. And all the other files that you have sent to the recycle bin, that you thought you got rid of, but you haven't until you reboot.

Circumventing the recycle bin works perfectly, but adding anything to the recycle bin after it has hiccuped does not. Even if you remove them, singly, in the recycle bin, the space is not cleared up and you can still find them in cmd. On reboot, the recycle bin is once again empty and pristine and the memory is free, just like the leftover files from moving also dissappear.

Formatting (which I just did yesterday) does not fix the issue. The fix in the second link seems, by my understanding, to be trying to clear the file from the recycle bin, which happens on reboot in my case.

The drives I am sure are quite fragmented, I will defrag soon. And then try to move masses of files all over the place all at once...