Hello,
When I try to copy file from the USB to the computer. I get the message "The request could not be performed because of an I/O device error."
I have tried diff usb slot on the computer. I also have tried diff usb device. I get the same error.
I use the Hard Disk Sentinel and CrystalDiskInfo to check the HDD. It shows "good".
The computer: Windows XP home. It's a IDE hard drive.
Can you tell me why I can't copy the file from usb to computer?
Hey Joel - I am far from expert in these matters but I can offer a basic explanation and ask you to try a couple of things which may prove helpful for others who reply to this topic:
The error message you are receiving is indicative of a hardware problem. Seeing you were attempting to transfer data from USB to internal HDD and have tried more than one USB device, [i:30dz6cir]and [/i:30dz6cir]the error repeats for all, that would seem to indicate a hardware problem on the host machine, your computer....most likely HDD.
If you were trying to write from HDD to USB drive and received that error message, it would indicate a likely problem with the USB device.
1) Can you please try transferring data [i:30dz6cir]from[/i:30dz6cir] the internal HDD [i:30dz6cir]to[/i:30dz6cir] the USB device and let us know how that goes?
2) Can you please try transferring data to and from the USB device/s on another (different) computer and let us know what happens?
3) Have the USB devices in question worked OK previously?
Cheers...Jim
Joel,
After you're done looking at the event log give this a shot...
Copy all the data from the USB to a hard drive on one of the computers where it functions correctly. Format (uncheck quick) the USB drive (NTFS if you have a choice) and copy the data back to the USB drive. Then try it again in the problem computer.
Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 10/11/2010
Time: 12:42:48 AM
User: N/A
Computer: my name.
Description:
An error was detected on device DeviceHarddisk1D during a paging operation.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink.....events.asp.
Data:
0000: 00680303 00b60001 00000000 80040033
0010: 0000012d 00000000 00000000 00000000
0020: 00000000 00000000 00008c5a 00000000
0030: ffffffff 00000003 4e000040 00000000
0040: 120a20ff 4020024c 0000e000 0000000a
0050: 00000000 84f22ae0 00000000 84c9d8b0
0060: 00000000 000d7750 0d000028 00005077
0070: 00000070 00000000 00000000 00000000
0080: 00000000 00000000 00000000 00000000
Hey Joel - As I said mate...I am no expert in these things, but I do have a basic understanding.
Error 51 is very much a generic error; which means there is no 'one size fits all' cause nor solution and leaves us, pretty much, with educated guesswork.
My first thoughts were impending hard drive failure but that ain't necessarily so. I've been searching around the forums and there are lots of reports of the identical problem but no absolute solution.
Seems for some it has been caused by a faulty cable and replacing the wiring loop that connects the HDD to the motherboard has fixed the problem. For others, with the same problem but in reverse, replacing the USB cable has worked (for external hard drive). There is also talk of Nvidia motherboard and graphic card drivers regularly causing the same issue. It could also be caused by a dry solder joint on the mobo creating an iffy connection.
What brand is your motherboard and do you have an Nvidia graphic card installed?? Have you updated drivers for those components recently?
You could try replacing the cabling as suggested by others, rolling back any recently updated chipset or graphics card driver installs. That's the trouble with these generic errors Joel, they are very difficult to track down and often involve a long winded process of trial and error.
One thing I would suggest mate is that you back up all your important (personal) data from the main drive to external media....just in case!
Cheers....Jim
Jim, I think you're on the right track, but (IMHO) pointing your efforts at the wrong device. I still think this is related to the flash drive. Could it be a drive cable, chipset driver, or something similar? Absolutely, but the easiest thing to troubleshoot is the USB drive. It's the most likely culprit in my opinion. I've seen this happen a couple times and a chkdsk /r and/or format "fix" it. Put the data back and all is well. Why is it different on two different machines? Well, I can't answer that.
Flash memory is a fickle sort and the memory used in USB flash drives isn't of the highest quality. There is also a huge black market of counterfeit devices that use memory of even a lesser quality. The memory also has a finite limit of read/write cycles. As that limit is approached reliability decreases quickly. Don't rely on a USB flash drive to be 100% safe.
Just my .02 cents!
Dave - Absolutely agree you may well be correct. Mate, you know a lot more about this stuff than I do.
This from Joel's initial post:
[quote:kbp7tc4g]I also have tried diff usb device. I get the same error.[/quote:kbp7tc4g]
Would it not be a rather unlikely coincidence that two or more USB devices would exhibit the exact same issue at the exact same time? The common factor is the host machine.
Your point about USB devices being unreliable and easier to troubleshoot is well taken.
Cheers.....Jim
[quote:ghcidh4z]I also have tried diff usb device. I get the same error.[/quote:ghcidh4z]
I overlooked that Jim. Sorry! It could still be related to USB drives in general depending on age of the computer (formating, file size, etc), but you're probably right about it being the actual computer. I'll bow out now.
Hi Joel,
Jim has it pretty much covered. But I'd like to propose something that is easy to try out and might help.
Could you please check if write caching is enabled for both your HDD and your USB device (flash memory)?
If you need help on checking, open the Device Manager, go to Disk Drives, right-click on your HDD, choose Properties and go to the Policies tab.
You can check your flash memory the same way - it'll appear in Device Manager under Disk Drives when pluged-in.
If this feature is enabled, disable it (on your HDD first) and try a copy test.
In any case, follow Jim's advice and do a full back up of the HDD stuff you care about, as this error is often a warning of a HDD dying.
Cheers
I am human
1 Guest(s)