All burns fail no matter the media, DVD/CD/BluRay, drive.. Please help, I am stumped!

[jz1276]

I've had a LG BluRay burner for years. Never any issues burning CD's, DVD's or Blu-Ray's. Burning suddenly started failing 100% of the time so I switched media. I've tried Windows built in disc burning software, ImgBurn and Alcohol 120. I've also purchased a new (same model) BR burner. I had 2 DVD burners in storage and tried those also. Have tried other SATA cables & ports.
When using ImgBurn, the process buffers up to 100% then fails before the actual burning even starts.
Please guys, I am completely stumped and really need your help... and any is appreciated. Thanks.

Here's the log from the last attempt at burning a BluRay.
https://pastebin.com/cFz0JJmY

... the log from the last attempt at burning a CD.
https://pastebin.com/pK5yX7vv

[Ghitulescu]

I did not truly understand - is the second drive also giving the same error?
If YES, then it is something wrong with the drivers, or try some other software
If NO, then try a lower speed, if it works even 5% then you have a laser failure

[Sunspark]

To rule out software, try booting from a Linux live USB and trying out a burning program on it and see how it goes.

[jz1276]

Originally Posted by Ghitulescu

I did not truly understand - is the second drive also giving the same error?
If YES, then it is something wrong with the drivers, or try some other software
If NO, then try a lower speed, if it works even 5% then you have a laser failure

Yes, I tried multiple drives and multiple brands of discs on 2 computers. All failed using Imgburn, MediaMonkey & Windows built in software.

Originally Posted by Sunspark

To rule out software, try booting from a Linux live USB and trying out a burning program on it and see how it goes.

I took the drive out for a week or so with intentions of buying a SATA to USB cable to try that. Never got around to ordering it, reinstalled the drive, now it works. Had to have been a bad software update.

[Emulgator]

Could have been a filter driver interfering, and with the new drive letter a new registry key for that chain is made, and the old one not parsed anymore.
If it happens again, ImgBurn has an inspection tool: Filter driver load order.

[jz1276]

Originally Posted by Emulgator

Could have been a filter driver interfering, and with the new drive letter a new registry key for that chain is made, and the old one not parsed anymore.
If it happens again, ImgBurn has an inspection tool: Filter driver load order.

Thanks for the advice. Although I was experiencing the same issue on two different computers