USB Mass Storage Drive - Code 10 - BIOS - MOTHERBOARD -

[TripleRLtd]

hi, i have the exact problem with an external hdd; not recognized by xp sp I; and code 10 in the device manager , saying the device (when recognized) cannot start...
pleassssse tell me how dod you solve the problem!
thank you ))

Welcome to WD irridiumh.
Here is what code 10 mean and what the suggestions are. Try them and let us know if it works. If not we will need more info about the external drive:

Code 10

If the device has a "FailReasonString" value in its hardware key, that string is displayed as the error message. The driver or enumerator places this registry string value there. If there is no "FailReasonString" in the hardware key, the following generic error message is displayed:

This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)

Try upgrading the device drivers for this device.

Solution button: Update Driver

To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.

[mib]

I am currently experiencing the same problem as noddy44, but with a different type of device. I have a generic (non-branded) USB caddy with a 60GB Toshiba HD (notebook form factor). Here are my observations:

1. The USB HD works with newer PC's, e.g. Dell Optiplex GX-240 (P4, 2.4G) desktop, Dell Latitude D505 (Centrino, 1.4G) notebook, Fujitsu-Siemens Amilo-D (P4, 2.4G) notebook, but not with older PC's, e.g. Compaq Evo (P4, 1.7G) desktop (my computer), Compaq Deskpro (P3, 677M).

I am fortunate enough to have access to a variety of computers in the company I work for. Unfortunately, this HD does not work on my computer.

2. Most of the PC's tested had Win 2000, SP2 or SP4, except Amilo-D, which had Win XP Pro. For the newer PC's, installation is straight-forward, without any need for drivers or anything. But for the older PC's, the error appears.

Although I am still doing my research, I do not think this is OS-dependent. I did find a Win 2000 patch in Microsoft (through Windows Update) that relates to an SP4 bug that might have an effect on this issue, but I installed the patch, and still the same problem.

I also don't think tinkering with the motherboard or BIOS settings or anything as radical as formatting the PC is required.

Sorry, I don't have any answers. Just sharing my thoughts.

[NooNoo]

Welcome to Windrivers MIB

Code 10 points to an acpi issue. This is born out by your observation that newer machines don't have this problem.

If there is a bios upgrade that mentions acpi or "general issues" I would try that followed by an overlay install to ensure that the windows kernal does update correctly.

[mib]

Welcome to Windrivers MIB

Code 10 points to an acpi issue. This is born out by your observation that newer machines don't have this problem.

If there is a bios upgrade that mentions acpi or "general issues" I would try that followed by an overlay install to ensure that the windows kernal does update correctly.

Thank you very much for your suggestions, NooNoo, and sorry for the long delay in my reply.

All this time, I have been browsing through the Internet for solutions to this Code 10 error, to no avail.

I tried your suggestion and upgraded my BIOS from the Compaq website, but it did not solve the problem either.

Finally, I have learned to live with this nuisance by simply connecting the device to another computer and transfering files through the network. Does the job anyway.

Once again, thanks!

[pagiii]

Thank you very much for your suggestions, NooNoo, and sorry for the long delay in my reply.

All this time, I have been browsing through the Internet for solutions to this Code 10 error, to no avail.

I tried your suggestion and upgraded my BIOS from the Compaq website, but it did not solve the problem either.

Finally, I have learned to live with this nuisance by simply connecting the device to another computer and transfering files through the network. Does the job anyway.

Once again, thanks!

I'm not sure if you already have a solution to this but try the following.
I had the same Code 10 error when I installed my USB enclosure with a 200 gig
hard drive with windows 2000. The solution that fixed my problem was setting my hard to MASTER instead of the Cable Select pin settings. Their was nothing in the instructions telling you to do this. I happened to find the solution on the web somewhere.

Patrick

[mib]

I'm not sure if you already have a solution to this but try the following.
I had the same Code 10 error when I installed my USB enclosure with a 200 gig
hard drive with windows 2000. The solution that fixed my problem was setting my hard to MASTER instead of the Cable Select pin settings. Their was nothing in the instructions telling you to do this. I happened to find the solution on the web somewhere.

Patrick

Welcome to WD.

Thank you very much for using your first post to help out. Most people, like me, came here to get answers for problems they could not solve, but you used your first post to suggest a solution.

I will try your suggestion shortly. Thanks.

[dean99]

Just confirming, setting HDD to Master also solved the problem for me (I had it set to Slave as it had just come out of the PC).

[mib]

After a few weeks of on-and-off tinkering, and trying the suggestions in this forum, and with a little bit of luck, I finally got my USB hard disk to get detected properly. No more yellow (!) in Device Manager.

Now, I'm down to one problem. I could not find the drive in Windows Explorer. It seems like the drive is not assigned any drive letter.

I tried going to Disk Management, to assign a drive letter manually, but it's not there.

I am using a Compaq EVO, P4, 1.7G, 512M, Win2000 SP4 with complete downloads from Windows Update. Also, I have 3 hard drives (30G, 20G & 20G, all Western Digital & all set to Master-Slave instead of Cable Select, as suggested in this forum), one CD Drive, and a host of network mapped drives.

My USB caddy is a generic one, with a Toshiba MK6021GAS 60GB disk. This device is working in other newer computers, which is how I got around, by copying files across the network.

Appreciate any suggestions you can give.

[NooNoo]

does it have its own power supply mib?