Two new DVD drives will not work. Code 42

February 7, 2011 at 11:48:12
Specs: Windows XP, Intel Celeron 3.40 GHz 2048 MBytes Ram
I have installed 2 new identical dvd drives and keep getting code 42 in device manager. I have tried instaling them one at a time as well as both at the same time to no avail. All I come up with is the computer recognizes on as a cd rom drive and will not recognize the other. I cannot use the second drive as the computer does not know it is there. They both show up in the BIOS. In computer neither one show up. In Windows Explorer as I said one of them shows up as a cd rom drive. Any help would be appreciated.

See More: Two new DVD drives will not work. Code 42

Report •

February 7, 2011 at 11:59:02
Are the optical drives SATA or PATA type? What type of boot hard drive is in use? SATA or PATA?

Report •

February 7, 2011 at 12:23:16
Why do you need 2 optical drives? If they are PATA, don't put them on the same cable/channel.

Report •

February 7, 2011 at 13:05:30
The new DVD Drives are SATA and my HD is IDE which is PATA. Not sure what PATA is but my BIOS says they are PATA. I have 2 hard drives
The new DVD's are data connected SATA and power is 4 prong molex plug with SATA adaptor to the DVD.
I have 2 opticals so I can copy disk to disk instead of disk to hd and then back to disk.
Dick R.

Report •

Related Solutions

February 7, 2011 at 13:31:33
PATA = Parallel ATA. SATA = Serial ATA.

WinXP does not natively support SATA Controllers. You need to either set the BIOS to run the drives in IDE/ATA mode or provide the drivers for the SATA controllers. You had no problem installing WinXP because you installed to an IDE/ATA hard drive. You can try Installing the SATA controllers using the Hardware wizard. Get them from the motherboard manufacturer's site.

If your BIOS has an option to use AHCI for the SATA drives that may work. See the second link below for more on AHCI.

Report •

February 7, 2011 at 16:12:46
"The new DVD Drives are SATA and my HD is IDE which is PATA"

To be able to use SATA drives in XP, you 1st need to install the SATA/RAID drivers.

Report •

February 9, 2011 at 12:11:11
I installed these 2 DVD Drives as replacements for old drives. One was an old CD Rom Drive and the other was a completely SATA DVD Burner that was going south. So my MB and Windows XP SP3 must support the SATA as the DVD Burner worked just fine until it started going bad mechanically. Now I have installed 2 new SATA DVD Drives and cannot get both to work. Only shows one. Here is a blurb from the MB manual which clearly shows I should be able to run 2 SATA devices.

Connecting the Serial ATA (SATA) Cable
The SATA cable (4-conductor) supports the Serial ATA protocol and connects a single drive to the
desktop board. For correct cable function:
1. Observe the precautions in "Before You Begin" on page 23.
2. Attach the locking cable end to the connector on the board (Figure 19, A).
3. Attach the cable end without the lock to the drive (Figure 19, B).
Figure 19. Connecting the Serial ATA Cable

Something is wrong in Windows that makes this thing keep coming up Code 42. I realize that the devices are identical so the drivers are identical. But why won't it install both of the optical devices. One shows up as a hidden device and the other shows up with a yellow exclamation point and Code 42. I just cannot figure this out.

Help is appreciated
Dick R.

Report •

February 9, 2011 at 12:27:38
SATA controllers normally support TWO SATA ports. You may have multiple controllers. Be sure you have them all enabled in the BIOS.

Also, you may have one of the new optical drives connected to a SATA RAID controller. In that case you may need to install additional drivers. Consult your manual.

I have come across boards with SATA ports that DO NOT support bootable drives and it is possible that some ports may not support optical devices. Again, consult your manual.

It may help to separate the drives so they are not using the same SATA controller. The BIOS may be seeing them as only one drive for that reason.

Look at the link below for some information on code 42.

Report •

February 9, 2011 at 13:53:50
Both drive are set for "Auto" in the BIOS. I do not have a RAID Controller. MB does not accept RAID. It must support optical devices because it ran one of the two drives I removed that was SATA and obviously an optical drive. The BIOS has both listed and as using ATAPI drivers. But when I boot it all goes to H#*^%. AS I said one shows up in hidden devices and the other shows up as Code 42. I assume because it loads the driver for the first drive it won't load the same driver again. But that is rediculous since you could never run two alike devices. I just do not understand and I am not a total dummy.
Dick R.

Report •

February 9, 2011 at 14:33:59
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)

The same thing applies for the SATA power connection.

"The new DVD's are data connected SATA and power is 4 prong molex plug with SATA adaptor to the DVD."

Make sure the wires in the male and female molex connectors are locked into their holes - that they do not move when you tug on them.

You could try another wiring adapter. I have one that had one faulty SATA power connector when it was brand new.

"One was an old CD Rom Drive and the other was a completely SATA DVD Burner that was going south. "

Sometimes Windows makes lines in the registry when a drive is producing too many data errors. Those lines may still be there and Windows is assuming one of the DVD drives are still faulty.

Try this.

Start - Run - type: regedit , click OK, choose Edit - Find - type masteriddatachecksum - delete all the enties on the right that have that - press F3 to search again (there is usually more than one); do the same for slaveiddatachecksum; exit regedit - reboot

NOTE that Regedit in 2000 and above saves the location of where you last were in the Registry the last time you used Regedit - the next time you run Regedit, that's where a search will start by default.
Before you start a search, scroll to the top of the list on the left and make sure My Computer is selected (highlighted) at the top, or you will not be searching through the whole registry.

Try connecting the drives one at a time to another computer. Don't use the same power wiring adapter if possible.

Report •

February 9, 2011 at 15:04:42
No one inferred that you were a dummy. I was just pointing out all the possible reasons.

Did you look at the link above? Just click on it and then browse it. Seems as though there can be an issue when two identical drives are installed.

I suggested one possible solution. Move one of the SATA cables so both are not using the same controller.

Report •

February 9, 2011 at 21:37:36
Also see these:

Your CD or DVD drive can't read or write media

Your CD drive or DVD drive is missing or is not recognized by Windows or other programs

Report •

February 10, 2011 at 13:28:45
Sorry, I didn't mean any one implied I was a dummy. I just meant to say I wasn't a total dummy but I cannot figure this out. And I still can't.
Anyway this will get you totally confused. I tried reassigning drive letters and that worked until I installed the second drive again. Soooo in total desparation I went downstairs to my other computer to see what DVD Drives I had on it. There was a Sony and an NEC, both DVD drives. So I took the Sony out and brought it upstairs and took out one of the Lite On drives from this computer and installed the Sony. POOF, magically it works. (And it is a SATA drive too). I took the Lite ON from upstairs and installed it in the downstairs computer and, POOF again, it works just fine in that computer along with the NEC.
Now you tell me why 2 Lite On DVD devices will not work together but they will work with other mfgr's stuff. I have been tearing my hair out for a week trying to figure this out and still haven't but at least I beat it and have everything working now.
But if any one knows the answer I would really like to hear it just so I know in the future.
I even emailed Lite On about the problem but they never emailed back. So much for their support dept. They even have the nerve to put a link on their web site telling you to email them for support. Then they don't answer.
Any way I want you all to know I really appreciate your efforts to help me and if nothing else you now know that possibly 2 devices from the same manufacturer may not work together.

Thanx again,
Dick R.

Report •

February 10, 2011 at 14:02:25
"The new DVD's are data connected SATA and power is 4 prong molex plug with SATA adaptor to the DVD."

Did you try
- a different power wiring adapter ?

- both of the new DVD drives connected to the other computer ?

- searching the registry for masteriddatachecksum and slaveiddatachecksum ?

- the stuff at the links in response 11 ?

Report •

February 10, 2011 at 19:32:46
I guess you didn't look at the link I provided above. The message isn't too long so I am copying it here.

Code 42: Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system

Updated: August 31, 2007

Applies To: Windows Server 2008

Device Manager displays the following message in the Device Properties dialog box, on the General tab, in the Device Status text box:

Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)

A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named devices, or when a device with a serial number is discovered in a new location before it is removed from the old location.

Restart the computer.

The resolution may not work but at least it provides some incite into the issue.

Same thing happens when using identical flash drives.

I suggested trying to separate the connections hoping that may stop the issue.

Report •

February 10, 2011 at 20:06:39

Aha ! That may the problem.

Flash drives too?

That hasn't happened for me for identical hard drive models - maybe the unique serial numbers are detected ?

As I recall there is a similar issue with identical wired network adapter models, at least in 98SE back to 95.

Report •

February 10, 2011 at 20:37:02
OK, Hi People,

I tried some of the registry stuff that was suggested in the emails, and, some of it I had already tried.

Moving on from there, I finally solved the problem. This is something to dwell on. What is amazing is how I did it and I still do not understand why it works.

I took,the DVD drive (Lite On, SATA drive) from this computer, to the downstairs computer and installed it.

I then brought up the DVD drive that I took out of the downstairs computer (a Sony DVD,SATA Drive) and installed it in the upstairs computer. THIS ONE that we are communicating on. And it works.

So how do we figure this one out. The computer will work as long as you do not install more than one DVD optical device (from the same mfgr.) in the same computer. Is that the deal?

I am at a loss for this problem. I have sort of beat my problem, but I have not not solved it. I will welcome any help on this.

In the meantime I want to really express my total appreciation for the help that I have received so far in my efforts to solve this problem. Those of you who have taken the time to help is more than appreciated.

Dick R.

Report •

February 10, 2011 at 21:27:43
Apparently you have the problem only if the model numbers are identical.

Report •

February 26, 2011 at 06:24:14
I have had the exact same problem with twin LiteOn units of the same model. Check the serial numbers on the two units. Are they the same? If they are could you post them to me so that I can compare them with mine. The serial numbers are identical on my twins. I am working with LiteOn to find the source of the problem (chip vs firmware) and fix the problem. Hopefully the firmware will be able to update the serial numbers inside the units. We shall see.

Report •

February 26, 2011 at 06:38:00

See response 14.

The problem is not unique to any particular brand of optical drive.

You cannot use two identical optical drive models and have both of them work .

Report •

February 26, 2011 at 07:32:25

In addition to the above I suggest you check the serial numbers again. I find it hard to believe both are the same. You may be looking at the full model numbers.

If the serial numbers are the same please post back the results of your contact with Lite-on. I am curious as to why that would occur.

Report •

February 26, 2011 at 09:43:24

I don't know how to get the serial numbers from the drives without taking the computers apart and I don't feel like doing that. However they both show up in Device Manager as ATAPiHAS224 A. If that means anything. That probably is the driver or something. But they are the same on both drives.

Report •

February 26, 2011 at 10:59:57
Dick R.

The subject of this Topic has bee investigated and OtheHill previously found that you CANNOT use two identical optical drive models and have both of them work !!

Report •

February 28, 2011 at 10:43:24
No error on the serial numbers. They are stickers on the bottom of the drives and I even took a photo to send to LiteOn just in case they wanted confirmation. And yes to other who think this issue is "handled," you can mix different models and manufacturers, that does not fix the issue. For those of us who do a lot of disk burns, these devices are a little finicky, they each have their own disks that they like best, their own speeds that they make the least number of coasters at. I for one would like to be able to use what drives I would like, and how. So this is important and I will settle for a work around when I have no other option. I am hoping that the firmware people can come up with something that will help XP tell the drives apart.

Report •

February 28, 2011 at 11:58:41

You're not getting it.

If Windows cannot identify identical optical drive models uniquely, then you CANNOT use two or more of them on the same system, in 2000 and up.

Report •

February 28, 2011 at 12:07:40
I realize that. See my posts #12 and #14

Report •

February 28, 2011 at 12:14:03
Dick R.

You "get it" but drcrunch doesn't seem to .

I've added his name to response 24.

Report •

February 28, 2011 at 13:31:24
To: DRCrunch

I found a way to get the info you asked for without taking my computers apart. The program I have in my computers is called SIW (System Information Windows) so I got the serial numbers you wanted and more. Here is all the info for the two LiteOn DVD Drives I tried to install in a single computer and could not do it. I finally put them in 2 different computers and they work fine that way. Wish I could just attach the 2 Word files but apparently I cannot, so they are copy pasted below my sign off. You will see every bit of the info for both DVD Drives is exactly the same, other than it is the drive 0 in one computer and drive 1 in the other, including Serial numbers. That makes little sense but that is he way it is. So good luck in your crusade,
Dick R.


DVD Writer 1
Manufacturer [unknown]
Model ATAPI iHAS224 A (ATAPI iHAS224 A)
Firmware Version ZL0P
Serial Number 3743524019 338039503
Interface Serial ATA
Standard ATA8-ACS | ----
Transfer Mode (Current / Max) SATA-150 / SATA-150
Drive Letter(s) F:
Controller Buffer Size on Drive 2048 KB
Removable Yes
CD Writer CD-R, CD-RW
SMART Support No


DVD Writer Upstairs Computer
Manufacturer [unknown]
Model ATAPI iHAS224 A (ATAPI iHAS224 A)
Firmware Version ZL0P
Serial Number 3743524019 338039503
Interface Serial ATA
Standard ATA8-ACS | ----
Transfer Mode (Current / Max) SATA-150 / SATA-150
Drive Letter(s) E:
Controller Buffer Size on Drive 2048 KB
Removable Yes
CD Writer CD-R, CD-RW
SMART Support No

Report •

February 28, 2011 at 13:57:09
I get what you are saying that XP only appears to go as far as the model number for setting the ID. If that is truly the rate limiting step, then the situ may be fubar. I just generally don't find the answer "you can't do that" satisfying by itself.

I am wondering where the glitch is, and admittedly this may be an exercise in mental self gratification. Aside from the interesting fact that I truly have identical ID tags (and I am not sure in this case that the fact is germain or not) I do not know for sure if the identification of the drive in XP contains any part of the unique ID and I haven't found a tech article that states that fact plainly. I do not see any signs of the SN in the references to the drives in the hive such as you see with the HD units.

We as a group have noted that XP seems to only read the make and model and that causes the problem, no port ID, no SN. I don't have enough drives to test many permutations of the issue but that appears to be the fact.

The bios sees the drives based on their ports as well as their model IDs, not any unique internal identifier that I can see. I am not sure if the firmware hands any unique ID to the driver or bios, then to the OS and what identifiers it uses.

This would be nice to have fixed. The firmware can get fixed, even if it could just change a model number with a hyphen-2 for the second unit. If it is the OS which is limited, then oh, well XP is EOL now, maybe 7 could get fixed. I just prefer to know more. I will have to see what the LiteOn people come up with.

Report •

February 28, 2011 at 14:11:18

I don't see what the reason to have a serial number is, if it is going to be the same. I mean to me that should be the identifier between one unit and another. And the 2 units I purchased are identical in every way including the serial number. I mean if it is model so & so then they should be the same. But the serial numbers should be different. At least in the world I grew up in that is how it was. But I spent over a week day in and day out trying to figure this out and did not succeed so I gave up and put one of the new ones in each of my 2 computers. Thankfully it worked. But to me it should not be that way. If I want 2 dvd drives in my computer and I want LiteOn I should be able to install them. Just like if I wnated 2 HP printers model xyz and 2 flash drives and so on. But apparently it is a problem that no one has taken up yet.

Dick R.

Report •

March 1, 2011 at 10:37:20
Dick R.

That has been my point. The way I see it, and I hope LIteONs engineers will see it as well is that if there is a need in the industry for a fix such as wee need, then hopefully a firmware upgrade will do it. I have an email into an XP guru at MS to see if I can find out how the units are identified in XP, then maybe I will understand more. The serial numbers may be a red herring if XP only uses the model number but it is very odd that we are seeing clusters of identical SNs on disparate models from this manufacturer, and since many of the controller chips are from the same companies, then how many other manufacturers are producing SN clones? I dunno.

When I build systems I like choices of devices to be dictated by best performance to cost ratios, not by foibles like this. The LiteOn units are very good, I have never had a DOA or an early failure. I put a new Asus in to pair up due to this error 42 issue and already had to send it back RMA due to "unknown drive error, drive time out, cannot find this that or the other." I made a few golden coasters with that unit trying to figure out if it was media related or other.

The next question that comes up would this happening in " Windows 7?"

Report •

March 1, 2011 at 11:13:37

I don't know. I haven't seen or used 7 yet. Have no idea what it is all about. I still say it is ridiculous to have the same serial number on every unit. If it is going to be the same why bother to have a serial number at all?

Report •

March 1, 2011 at 12:40:37
To attempt to put this discussion to rest set me put my spin on it.

When I started fiddling with PCs there were 15 available IRQs. You had to manually assign them to the hardware and match memory allocations to them.

Then as industry recognized the need the process began to be automated. There were/and are growing pains with any process in flux. As it now stands with contemporary BIOSes and OSes, either or both are able to configure the hardware. This is part of plug and play. So the industry reacts to a need.

Now, if the need to configure two identical hardware devices were common enough, then the industry would find a way to fix this problem. I would guess that at this time it isn't considered a problem of any priority.

These types of conflicts have been going on for years. The issue of using two identical network cards is one example. While it may be possible for a modern OS to configure two NICs of the same model, this is usually addressed by providing NICs from two different vendors. This proves to be a superior solution anyway. One is usually much faster than the other, thereby addressing another issue.

PCs are becoming more compact all the time. Laptops and their brethren (netbooks/notbooks/etc) have surpassed desktops in popularity. Laptops by their very nature will most likely not have redundant hardware.

So, I doubt the industry will bother with the problem of installing two identical hardware devices.

The issue he is awareness. Once you know there is this problem then you work around it.

drcrunch, in #18 you stated the serials were the same. In #20 I asked you to verify that. Did you verify it. If SIW was the source I wouldn't be 100% on the information.

Report •

March 3, 2011 at 08:29:13
I see where you are coming from, the question is whether or not there is a perceived need. I am trying to push for that need but am likely to be a lone voice in the wilderness. I have confirmed the IDs of the units by both software and the stickers on the units, identical. I am not sure where this will end up, I am waiting for a replacement Asus BluRay for the DOA one that I got in order to work around the issue but I think this should be a relatively easy fix in theory, unless it is in fact at the core of how MS software looks at the drive IDs. I may put a Knoppix disk in and see how it sees the twins. Who knows, maybe the bios only hands off the unit name and model, in the setup it lists them by port and at that level the XP install disk had no problems using the drives. Once the install was complete is when the trouble started. You have given my food for thought though, if I use the bios to set up the IDs and not the plug and pray...might work but probably will cause something else to foul up. We will see, the LiteOn folks have started into RMA mode so I may be over their pay grade already. To most people this wouldn't seem that big a deal, and it isn't, it just cheeses me and I can't easily get it out of my teeth.

Report •

March 3, 2011 at 08:38:41
Serial numbers and model numbers are not the same thing.

The BIOS is also a problem. I have had problems when using two identical hard drives in the past.

I have 3 optical drives installed in this Windows 7 Ultimate rig. No problems. They are all different models.

Report •

March 3, 2011 at 17:54:12
I've seen DVD duplicating machines that use identical optical drives (up to ten of them) without problems. Of course, these machines don't use the Windows operating system. I believe they are Unix-based.

That would suggest to me that there is probably a rarely encountered bug in the way Windows identifies/enumerates devices. I wouldn't be surprised to learn that identical optical drives caused no problems in a Linux/Unix machine. My guess is that few (if any) Windows users have reported (or ,for that matter, experienced) the problem, so the bug has never been rectified. Here, I've referred to the problem as a bug, when it's probably more correct to say that the programmers have used a flawed method of handling hardware identification and enumeration.

Please let us know if you found someone's advice to be helpful.

Report •

March 7, 2011 at 13:56:52

I never implied that the model and serial numbers are the same thing. In this case the numbers between both units that are the by intent same model, also have the exact same serial number. I BS you not. Do you want to see the jpeg?

Everybody is on the same page though, it all goes back to how the devices are set up in XP. All of the references in the registry seem to use the model number string from the unit, not the serial numbers.

The bios at the most basic level doesn't seem to have an issue as an install of XP worked with both units installed. Knoppix works with them both installed. I think the bios is handling them fine. I have six identical hard drives installed and they are fine also. I believe ( I am not in front of the box now), that the registry entries for the hard drives all have the serial numbers as part of the ID string, the optical drives do not. I will have to check on the accuracy of that statement using some other apps.

I am playing with the plug and pray but haven't noticed anything different once the system is up. Emails from LiteOn have stopped so I think that they are going to go silent. Apparently this serial number snafu will put them in dutch with federal purchasing rules because you cannot have a valid warranty with this situation so they might start to stone wall. Looks like we have more than one problem here. One in XP and a likely unrelated problem within LiteOn. Dunno.

Report •

March 7, 2011 at 14:06:51
I agree the serial number duplication is cause for alarm.

Going back to the original issue, Microsoft evidently is only concerned with tracking hardware where the limited OS (SLP) license is keyed to those components.

Report •

Ask Question