New
#21
Yes. Just take a look see, and see if you find anything with a Yellow triangled exclamation mark beside any item. If not, don't worry about it. But I would say you should update your drivers for hardware every once in a while from their websites.
Edit: Checked out your screenshots. Looks likes it's the thumb drive. Doh!
Last edited by Richardc269; 18 Feb 2012 at 12:04. Reason: Edited.
How did you format the pendrive and the SD Card from FAT32 to NTFS?
Okay I'm confused. My understanding you can go from Fat 32 to NTSF but you can't from NTSF back to FAT 32. Does that apply to thumb drives also?
Just encountered same issue and found this thread. On my machine, it's a driver issue and not a performance one. The lockup at 5 seconds locks the whole computer up. I'm going to try uninstalling all if not most of my USB drivers.
I do have Quicktime, itunes, Cyberlink Power DVD and Nero installed. Some of them have copy DRM issues that always mess all my drivers up. Hope this helps.
i know this post is old but i just thought for anyone else that reads this that i would say i built a gaming computer my self (i know what im doing) and it works flawlessly, except i get this too, from what i have gathered it happens everytime i copy large files more then around 3gb over, before i would just wait but ive been waiting a while
I noticed a possible explanation for the "Stuck at 5 seconds remaining" issue. It's not the filesystem of the USB stick, it's Windows 7's way of copying files. One can watch what happens on the Task manager, Performance tab, Physical memory Usage graph.
A file being copied gets buffered into memory as it gets written to the destination drive. The whole file buffers through the memory. With a large file, one can see the memory usage go up substantially as the file gets buffered into memory during the copy process, then tail off back to normal as the file finishes copying.
The "Time Remaining" progress bar in the File Copy window seems to be tied to the reading of the file at the source, not the writing of the file to the destination. So the progress bar will move across as the file is read into memory and the memory usage goes up. When the whole file has been read, the progress bar will read "5 seconds remaining". But the large amount of memory still being used by the buffered file contents is still waiting to write to the destination, and the progress bar gets "stuck". One can watch the memory usage drop down back to normal in Task Manager, then the progress bar and the copy window will finish.
If the progress bar were tied to the destination write process, it would show accurate times.