F5F Stay Refreshed Hardware Desktop The LG GH24NSD1 DVD writer isn't recognized by Windows 10 or the BIOS.

The LG GH24NSD1 DVD writer isn't recognized by Windows 10 or the BIOS.

The LG GH24NSD1 DVD writer isn't recognized by Windows 10 or the BIOS.

F
flaggum
Junior Member
17
06-29-2022, 03:46 PM
#1
Hello, I faced a situation where neither the BIOS nor Windows 10 recognized the optical disc drive from LG GH24NSD1. My system uses an MSI Z370-A PRO motherboard with BIOS version 7B48v2C. I attempted to free ports by rewiring the drive’s connector cables for SATA 3, 4, 5, and 6, but the BIOS still didn’t detect it anywhere. After updating the BIOS to the latest stable release, the issue persisted.

I also explored adding the EnumDevice1 registry entry at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Controller0, but this didn’t resolve the problem. Checked the chipset driver—Intel Chipset Driver 10.1.18508.8239 and SATA AHCI controller driver 10.0.19041.1288 are up to date. Tried swapping the connectors of my secondary hard drive with those of the optical drive, which worked perfectly. However, when I switched the HDD to SATA4 and the optical drive to SATA2, the BIOS still saw the drive in SATA4 but marked SATA2 as empty.

Inspected the cables for bent pins; everything seemed intact. Verified the power supply cable was securely connected. The only remaining thought was that the optical drive might be faulty, though this seems unlikely given its single or infrequent use. Overall, the setup includes: OS Windows 10 64-bit version 21H1 19043.1826, CPU Intel Core-i7 8700K, and the LG GH24NSD1 drive. I have attached screenshots of the BIOS for reference.
F
flaggum
06-29-2022, 03:46 PM #1

Hello, I faced a situation where neither the BIOS nor Windows 10 recognized the optical disc drive from LG GH24NSD1. My system uses an MSI Z370-A PRO motherboard with BIOS version 7B48v2C. I attempted to free ports by rewiring the drive’s connector cables for SATA 3, 4, 5, and 6, but the BIOS still didn’t detect it anywhere. After updating the BIOS to the latest stable release, the issue persisted.

I also explored adding the EnumDevice1 registry entry at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Controller0, but this didn’t resolve the problem. Checked the chipset driver—Intel Chipset Driver 10.1.18508.8239 and SATA AHCI controller driver 10.0.19041.1288 are up to date. Tried swapping the connectors of my secondary hard drive with those of the optical drive, which worked perfectly. However, when I switched the HDD to SATA4 and the optical drive to SATA2, the BIOS still saw the drive in SATA4 but marked SATA2 as empty.

Inspected the cables for bent pins; everything seemed intact. Verified the power supply cable was securely connected. The only remaining thought was that the optical drive might be faulty, though this seems unlikely given its single or infrequent use. Overall, the setup includes: OS Windows 10 64-bit version 21H1 19043.1826, CPU Intel Core-i7 8700K, and the LG GH24NSD1 drive. I have attached screenshots of the BIOS for reference.

P
Princess599599
Junior Member
37
06-29-2022, 03:46 PM
#2
With M.2 drives installed, some SATA ports can become inactive when the slots are full. For example, my Asus Tuf B550-PLUS turns off SATA 1/2 when the main slot is used, and SATA 5/6 when the secondary is occupied. I also noticed a curious situation when moving my 5900X to another case for an ODD drive—during the first boot or two, the system seemed uncertain about whether the HDD and ODD were part of a RAID setup, even though they aren't. This likely prompted me to adjust the configuration, which I did without making any changes afterward. It might be related to this adjustment.
P
Princess599599
06-29-2022, 03:46 PM #2

With M.2 drives installed, some SATA ports can become inactive when the slots are full. For example, my Asus Tuf B550-PLUS turns off SATA 1/2 when the main slot is used, and SATA 5/6 when the secondary is occupied. I also noticed a curious situation when moving my 5900X to another case for an ODD drive—during the first boot or two, the system seemed uncertain about whether the HDD and ODD were part of a RAID setup, even though they aren't. This likely prompted me to adjust the configuration, which I did without making any changes afterward. It might be related to this adjustment.

J
Jason2005_HD
Member
155
06-29-2022, 03:46 PM
#3
Thank you for your prompt reply! It seems the issue isn't related to M.2, since I don't have one installed. My main drive is a SATA SSD and the secondary is an SATA HDD, both using SATA ports 1 and 2. For the alternative approach, the only RAID-related setting available is in the SATA Mode option shown in the first screenshot, which uses AHCI.
J
Jason2005_HD
06-29-2022, 03:46 PM #3

Thank you for your prompt reply! It seems the issue isn't related to M.2, since I don't have one installed. My main drive is a SATA SSD and the secondary is an SATA HDD, both using SATA ports 1 and 2. For the alternative approach, the only RAID-related setting available is in the SATA Mode option shown in the first screenshot, which uses AHCI.

A
AndyPig007
Junior Member
4
06-29-2022, 03:46 PM
#4
I'm curious about whether the drive gets a letter that overlaps with another assignment. That could account for the Windows problem, though I imagine it might happen if you boot with just one drive, change its letter, and then switch back. It's doable but would need deliberate steps most people recall performing. Added note: You could also test booting from a single drive to check. But that doesn't explain why the BIOS ignores it. Have you tried swapping the cables? The connection might be faulty, as cords often get pinched or bent in confined spaces.
A
AndyPig007
06-29-2022, 03:46 PM #4

I'm curious about whether the drive gets a letter that overlaps with another assignment. That could account for the Windows problem, though I imagine it might happen if you boot with just one drive, change its letter, and then switch back. It's doable but would need deliberate steps most people recall performing. Added note: You could also test booting from a single drive to check. But that doesn't explain why the BIOS ignores it. Have you tried swapping the cables? The connection might be faulty, as cords often get pinched or bent in confined spaces.

I
iTz_NightWolf
Member
70
06-29-2022, 03:46 PM
#5
Another idea came to mind, though I'm not certain it's important. It could relate to a SATA 3.0 versus SATA 6.0 difference—like using a 6.0 cable with a 3.0 port, or the opposite. Another thought is that the motherboard might be damaged at the SATA connection area and can't detect drives anymore. Would it still work with other drives? Updated August 21, 2022 by An0maly_76 Added more info
I
iTz_NightWolf
06-29-2022, 03:46 PM #5

Another idea came to mind, though I'm not certain it's important. It could relate to a SATA 3.0 versus SATA 6.0 difference—like using a 6.0 cable with a 3.0 port, or the opposite. Another thought is that the motherboard might be damaged at the SATA connection area and can't detect drives anymore. Would it still work with other drives? Updated August 21, 2022 by An0maly_76 Added more info

D
DerpyBat
Member
124
06-29-2022, 03:46 PM
#6
Success!!! I realized that even though Windows and BIOS don’t recognize ODD, it should still function—meaning the LED should light up and the tray should slide out when the button is pressed. But neither happened. So I switched the SATA power cable, as the PSU has plenty of free ones, and voilà! - it works perfectly. Thanks for your help and have a great day!
D
DerpyBat
06-29-2022, 03:46 PM #6

Success!!! I realized that even though Windows and BIOS don’t recognize ODD, it should still function—meaning the LED should light up and the tray should slide out when the button is pressed. But neither happened. So I switched the SATA power cable, as the PSU has plenty of free ones, and voilà! - it works perfectly. Thanks for your help and have a great day!