LightScribe Drives Blew A Fuse

I just finished burning a DVD on my LG burner, and then started to burn the label with Lightscribe, but it couldn't find any LightScribe drives. I then noticed that the activity light on the LG kept blinking and then found that I couldn't open the drive, so I rebooted, thinking that would release it, but it didn't. I had to remove the DVD with a paperclip.

I then continued to reboot, but the drive detection seemed to freeze much longer than usual, and then Windows froze at the startup screen. I shutdown and disconnected the drive, which seemed to fix the problem, though boot time was still a bit longer than usual.

I then started to attempt to burn the label again, with my Samsung burner, but again the LightScribe labler said that it didn't see any LightScribe drives.

Even though the LG is the newest drive, the SamSung is not all that old itself, and I can't imagine why they both would decide to act up simutaneously. The Samsung is operational as far as reading disks (I didn't test it for burning), so would anyone have any idea of what the problem might be...besides gremlins?

Have you tried disconnecting the Samsung and then rebooting to see if the boot is still slower than normal? Also try the LG drive again with the Samsung disconnected. I've seen cases where the drive that is suspected of being the problem isn't the one with the problem but another device is the problem.

After a few hours of sleep, I finally got around to trying your recommendation. I unplugged the Samsung and replugged the LG and voila, it worked! I then proceeded to try to burn that same label as before, but the LightScribe labeler still didn't see it. I then went to the Device Manager, and it was listed without any ! or ? marks, but when I selected Properties, the Device Manager froze.

I then replugged the Samsung and both drives appear to be working, and now the Device Manager can display Properties on both drives... but the LightScribe labeler still can't see any LightScribe drives.

I guess that the next step is to reinstall the Labeler, but I'm still wondering if the Lightscribe could have failed on both drives at the same time, yet remain functional?

I just finished reinstalling both the LightScribe engine and the labeling software, and now both drives appear as they should have before. It now appears that the problem was always the LightScribe software/driver. I guess when it fails it throws a BIG monkey wrench into the works.