Invalid Address For Write / Failed To Write Sectors / Write Error

[Tape It Up Reproductions]

Hello...

I've tried searching for this topic already, but the several threads DO NOT seem to represent my exact issue.
On my 64-bit Lenovo desktop PC, with an LG BP50NB40 slimline Blu-Ray burner, I keep running into failed Blu-Ray burns. I'm using 25GB single-layer discs and burning from an ISO.
I started with FlexDisc brand, and then switched to HP -- so I am confident it is not a disc compatibility issue.
This can be further confirmed by the fact that I put the same Blu-Ray burner, with the same HP discs, on a 64-bit HP desktop PC, and it burned the same ISO perfectly.
Both computers are using the most recent version of ImgBurn (2.5.8.0), and both are using Windows 10 Home. 
What's interesting is on the Lenovo PC, I burned a 4.7GB ISO to an Optimum brand DVD-R perfectly. It's only crashing with Blu-Rays.

Here's the most recent crashed log from the Lenovo computer:

Quote

I 22:18:39 ImgBurn Version 2.5.8.0 started!
I 22:18:39 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 22:18:39 Total Physical Memory: 11,480,692 KiB  -  Available: 5,563,116 KiB
I 22:18:39 Initialising SPTI...
I 22:18:39 Searching for SCSI / ATAPI devices...
I 22:18:40 -> Drive 1 - Info: PLDS DVD-RW DH16AFSH DL31 (D:) (SATA)
I 22:18:40 -> Drive 2 - Info: HL-DT-ST BD-RE BP50NB40 1.00 (F:) (USB 2.0)
I 22:18:40 Found 1 DVD±RW/RAM and 1 BD-RE XL!
I 22:19:20 Operation Started!
I 22:19:21 Source File: C:\Users\cjthe\Desktop\CoryMalmLaKD21.ISO
I 22:19:21 Source File Sectors: 8,387,264 (MODE1/2048)
I 22:19:21 Source File Size: 17,177,116,672 bytes
I 22:19:21 Source File Volume Identifier: CoryMalmLaKD21
I 22:19:21 Source File Volume Set Identifier: 5311BB6C________CoryMalmLaKD21
I 22:19:21 Source File Application Identifier: moycomm.dll 5.0.0.46
I 22:19:21 Source File Implementation Identifier: XXXSoftware
I 22:19:21 Source File File System(s): UDF (2.50)
I 22:19:21 Destination Device: [0:0:0] HL-DT-ST BD-RE BP50NB40 1.00 (F:) (USB)
I 22:19:21 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 22:19:21 Destination Media Supported Write Speeds: 2x, 4x, 6x
I 22:19:21 Destination Media Sectors: 12,219,392
I 22:19:21 Write Mode: BD
I 22:19:21 Write Type: DAO
I 22:19:21 Write Speed: MAX
I 22:19:21 Hardware Defect Management Active: No
I 22:19:21 BD-R Verify Not Required: Yes
I 22:19:21 Link Size: Auto
I 22:19:21 Lock Volume: Yes
I 22:19:21 Test Mode: No
I 22:19:21 OPC: No
I 22:19:21 BURN-Proof: Enabled
I 22:19:21 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x)
I 22:19:47 Filling Buffer... (80 MiB)
I 22:19:47 Writing LeadIn...
I 22:19:50 Writing Session 1 of 1... (1 Track, LBA: 0 - 8387263)
I 22:19:50 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 8387263)
W 22:35:25 Failed to Write Sectors 7772160 - 7772191 - Reason: Write Error
W 22:35:25 Retrying (1 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (2 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (3 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (4 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (5 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (6 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (7 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (8 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (9 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (10 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (11 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:25 Retrying (12 of 20)...
W 22:35:25 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (13 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (14 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (15 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (16 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (17 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (18 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (19 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:26 Retrying (20 of 20)...
W 22:35:26 Retry Failed - Reason: Invalid Address For Write
W 22:35:29 Retrying (21)...
W 22:35:29 Retry Failed - Reason: Invalid Address For Write
W 22:35:30 Retrying (22)...
W 22:35:30 Retry Failed - Reason: Invalid Address For Write
W 22:35:31 Retrying (23)...
W 22:35:31 Retry Failed - Reason: Invalid Address For Write
W 22:35:32 Retrying (24)...
W 22:35:32 Retry Failed - Reason: Invalid Address For Write
W 22:35:32 Retrying (25)...
W 22:35:33 Retry Failed - Reason: Invalid Address For Write
W 22:35:34 Retrying (26)...
W 22:35:34 Retry Failed - Reason: Invalid Address For Write
E 22:35:35 Failed to Write Sectors 7772160 - 7772191 - Reason: Write Error
E 22:35:35 Next Writable Address: 0
I 22:35:35 Synchronising Cache...
W 22:35:40 User opted to skip the 'Close Track/Session/Disc' functions.
E 22:35:40 Failed to Write Image!
I 22:35:40 Exporting Graph Data...
I 22:35:40 Graph Data File: C:\Users\cjthe\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BP50NB40_1.00_MONDAY-AUGUST-23-2021_10-19_PM_CMCMAG-BA5-000_MAX.ibg
I 22:35:40 Export Successfully Completed!
E 22:35:40 Operation Failed! - Duration: 00:16:20
I 22:35:40 Average Write Rate: 16,466 KiB/s (3.8x) - Maximum Write Rate: 22,785 KiB/s (5.2x)

And here's the successful log from the HP computer:

Quote

I 21:30:20 ImgBurn Version 2.5.8.0 started!
I 21:30:20 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 21:30:20 Total Physical Memory: 6,275,696 KiB  -  Available: 3,574,236 KiB
I 21:30:20 Initialising SPTI...
I 21:30:20 Searching for SCSI / ATAPI devices...
I 21:30:21 -> Drive 1 - Info: hp CDDVDW TS-H653TN H6DA (E:) (SATA)
I 21:30:21 -> Drive 2 - Info: HL-DT-ST BD-RE BP50NB40 1.00 (J:) (USB 2.0)
I 21:30:21 Found 1 DVD±RW/RAM and 1 BD-RE XL!
I 21:30:26 Operation Started!
I 21:30:26 Source File: C:\Users\CJ\Desktop\CoryMalmLaKD21.ISO
I 21:30:26 Source File Sectors: 8,387,264 (MODE1/2048)
I 21:30:26 Source File Size: 17,177,116,672 bytes
I 21:30:26 Source File Volume Identifier: CoryMalmLaKD21
I 21:30:26 Source File Volume Set Identifier: 5311BB6C________CoryMalmLaKD21
I 21:30:26 Source File Application Identifier: moycomm.dll 5.0.0.46
I 21:30:26 Source File Implementation Identifier: XXXSoftware
I 21:30:26 Source File File System(s): UDF (2.50)
I 21:30:26 Destination Device: [0:0:0] HL-DT-ST BD-RE BP50NB40 1.00 (J:) (USB)
I 21:30:26 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 21:30:26 Destination Media Supported Write Speeds: 2x, 4x, 6x
I 21:30:26 Destination Media Sectors: 12,219,392
I 21:30:26 Write Mode: BD
I 21:30:26 Write Type: DAO
I 21:30:26 Write Speed: MAX
I 21:30:26 Hardware Defect Management Active: No
I 21:30:26 BD-R Verify Not Required: Yes
I 21:30:26 Link Size: Auto
I 21:30:26 Lock Volume: Yes
I 21:30:26 Test Mode: No
I 21:30:26 OPC: No
I 21:30:26 BURN-Proof: Enabled
I 21:30:28 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x)
I 21:31:02 Filling Buffer... (80 MiB)
I 21:31:05 Writing LeadIn...
I 21:31:12 Writing Session 1 of 1... (1 Track, LBA: 0 - 8387263)
I 21:31:12 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 8387263)
I 21:47:44 Synchronising Cache...
I 21:47:47 Closing Track...
I 21:47:48 Finalising Disc...
I 21:51:12 Exporting Graph Data...
I 21:51:12 Graph Data File: C:\Users\CJ\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BP50NB40_1.00_MONDAY-AUGUST-23-2021_9-30_PM_CMCMAG-BA5-000_MAX.ibg
I 21:51:12 Export Successfully Completed!
I 21:51:13 Operation Successfully Completed! - Duration: 00:20:46
I 21:51:13 Average Write Rate: 16,926 KiB/s (3.9x) - Maximum Write Rate: 23,443 KiB/s (5.3x)
I 21:51:13 Cycling Tray before Verify...
W 21:51:37 Waiting for device to become ready...
I 21:51:41 Device Ready!
I 21:51:42 Operation Started!
I 21:51:42 Source Device: [0:0:0] HL-DT-ST BD-RE BP50NB40 1.00 (J:) (USB)
I 21:51:42 Source Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 21:51:42 Source Media Supported Read Speeds: 1x, 2x, 4x, 6x
I 21:51:42 Source Media Supported Write Speeds: 2x, 4x, 6x
I 21:51:42 Source Media Sectors: 8,387,264
I 21:51:42 Source Media Size: 17,177,116,672 bytes
I 21:51:42 Image File: C:\Users\CJ\Desktop\CoryMalmLaKD21.ISO
I 21:51:42 Image File Sectors: 8,387,264 (MODE1/2048)
I 21:51:42 Image File Size: 17,177,116,672 bytes
I 21:51:42 Image File Volume Identifier: CoryMalmLaKD21
I 21:51:42 Image File Volume Set Identifier: 5311BB6C________CoryMalmLaKD21
I 21:51:42 Image File Application Identifier: moycomm.dll 5.0.0.46
I 21:51:42 Image File Implementation Identifier: XXXSoftware
I 21:51:42 Image File File System(s): UDF (2.50)
I 21:51:42 Read Speed (Data/Audio): MAX / MAX
I 21:51:43 Read Speed - Effective: 2x - 6x
I 21:51:44 Verifying Session 1 of 1... (1 Track, LBA: 0 - 8387263)
I 21:51:44 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 8387263)
I 22:08:10 Exporting Graph Data...
I 22:08:10 Graph Data File: C:\Users\CJ\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BP50NB40_1.00_MONDAY-AUGUST-23-2021_9-30_PM_CMCMAG-BA5-000_MAX.ibg
I 22:08:10 Export Successfully Completed!
I 22:08:10 Operation Successfully Completed! - Duration: 00:16:26
I 22:08:10 Average Verify Rate: 17,029 KiB/s (3.9x) - Maximum Verify Rate: 23,553 KiB/s (5.4x)
I 22:16:44 Close Request Acknowledged
I 22:16:44 Closing Down...
I 22:16:44 Shutting down SPTI...
I 22:16:44 ImgBurn closed!

Any help you can provide would be greatly appreciated. I'm sure this must be either a firmware or software issue, but I'm not well-versed enough in the intricacies of ImgBurn settings to know what to adjust. Thank you!

Edited August 24, 2021 by TapeItUp
clarified the optical media used for a successful 4.7GB ISO burn

[LIGHTNING UK!]

Hmm that’s a tough one.

So you’re moving the usb drive between machines and it’s behaving differently?

How many burns have you tried on each machine? What percentage of those have failed on each machine?

As drives are self contained, it shouldn’t really be possible for them to behave differently in different machines.

Maybe it’s power related? Does the drive just take power from usb? If so, it’s probably from 2 ports yeah? Are they both usb 3 on both machines?

[dbminter]

Yes, with all the available information, I'd say there's an issue with the USB port or controller on the PC where the burns are failing.  Did you try connecting the USB BD burner to different USB ports on the PC where it's failing?

[Tape It Up Reproductions]

On 8/24/2021 at 1:30 AM, LIGHTNING UK! said:

Hmm that’s a tough one.

So you’re moving the usb drive between machines and it’s behaving differently?

How many burns have you tried on each machine? What percentage of those have failed on each machine?

As drives are self contained, it shouldn’t really be possible for them to behave differently in different machines.

Maybe it’s power related? Does the drive just take power from usb? If so, it’s probably from 2 ports yeah? Are they both usb 3 on both machines?

I've tried probably half a dozen burns on the Lenovo and they all fail at various stages regardless of disc brand. This machine HAS worked in the past.
I only did one burn on the HP computer and it worked flawlessly.
I'd say 0 for 6 vs. 1 for 1 is a pretty good indicator without pissing money away on discs for continued experimentation, lol.

The drive does use two USB ports. They're USB3 on the Lenovo and USB2 on the HP.

Edited August 27, 2021 by Tape It Up Reproductions

[Tape It Up Reproductions]

On 8/24/2021 at 9:39 AM, dbminter said:

Yes, with all the available information, I'd say there's an issue with the USB port or controller on the PC where the burns are failing.  Did you try connecting the USB BD burner to different USB ports on the PC where it's failing?

I will try that tomorrow and update the thread. The drive didn't move ports between the time it was working and the time it stopped on the Lenovo, but I suppose it could be that those ports are losing their oomph or something.

Thanks!

[ianymaty]

Maybe driver update from Windows Updates botched something... They sometimes do quirks.

Try with the latest drivers for USB ports from the manufacturer's site.

[dbminter]

Also, just to rule out the possibility it's the cause, are you using the same USB cable with this drive on both the PC that works and the one that doesn't?  If you're using a different USB cable on the PC that works but not on the PC that doesn't, it could be the cable.  Most people don't use different cables on different devices, but I'm ruling it out here in case it is.

[Tape It Up Reproductions]

Thanks everyone.
Yes I'm using the Y-cord USB that came with the drive, on both computers. So that's not the issue.

I also just plugged the drive into two different USB ports on the rear of my Lenovo and still got a failure.
Granted, one was a USB 2.0 and the other was a 3.0 ... but I just realized the drive itself uses two 2.0 ports, so in theory, that shouldn't matter... right?

Just for good measure, I plugged the drive into the two USB 2.0 ports on the front of the Lenovo, as I'm almost positive they use a different bus off the mobo. (My dogs are being particularly fussy and in my face, so not an idea evening to open the case up). The drive failed on these ports, too.

I went to the Device Manager and right-clicked, "Update Drivers" for every single item under Universal Serial Bus controllers; all said the best drivers were already installed. I had Windows Update do a check; nothing new available. And they all look pretty generic, so I'm not sure I'd know what specific hardware manufacturer and model I'd want to search the web for drivers on. I'll also point out that no other USB drives on this computer have been acting up; occasionally I'll have a WiFi drop, but that's an onboard chip, not coming from a USB dongle. 

I'm at a loss here. At some point this weekend I'll burn a few more copies on the HP, to see if the successful burn was just a fluke. I'm about to bite the bullet and just buy a replacement drive, but I don't want to dunk $$$ if 1) it's not going to resolve the issue, and/or 2) there's some kind of software or firmware fix.

[dbminter]

If it's a BD drive, do not connect to USB 2.x.  USB 2.x does not have the necessary speed to keep up with communicating to a BD drive and will, almost always, fail to burn if you connect a BD drive by USB 2.x.

 

Trying to replace the drive with something other than the same manufacturer and model might be the only solution.  Since the drive works on one PC but not on the other, there is something "wrong" on the PC where it doesn't work.  Now, this may be as simple as there is a conflict between the USB bridge inside your BD drive and the USB controller on your mobo.  If that's the case, the only solution is to replace the bridge, the controller on the mobo, or the drive.  Replacing the drive is far easier and cheaper than replacing the USB bridge or the controller on the mobo or getting a whole new mobo, of which you're not sure it will work.

 

You know it's not the drive or cable as the BD drive works on one computer but not the other.  So, whichever device it's failing on is the culprit.  Now, whether that's down to a hardware error or a software error from some kind of corruption in Windows configuration or a bad driver update or corrupt driver, you could spend years trying to nail that down and get nowhere.

[Tape It Up Reproductions]

19 minutes ago, dbminter said:

If it's a BD drive, do not connect to USB 2.x.  USB 2.x does not have the necessary speed to keep up with communicating to a BD drive and will, almost always, fail to burn if you connect a BD drive by USB 2.x.

 

Trying to replace the drive with something other than the same manufacturer and model might be the only solution.  Since the drive works on one PC but not on the other, there is something "wrong" on the PC where it doesn't work.  Now, this may be as simple as there is a conflict between the USB bridge inside your BD drive and the USB controller on your mobo.  If that's the case, the only solution is to replace the bridge, the controller on the mobo, or the drive.  Replacing the drive is far easier and cheaper than replacing the USB bridge or the controller on the mobo or getting a whole new mobo, of which you're not sure it will work.

 

You know it's not the drive or cable as the BD drive works on one computer but not the other.  So, whichever device it's failing on is the culprit.  Now, whether that's down to a hardware error or a software error from some kind of corruption in Windows configuration or a bad driver update or corrupt driver, you could spend years trying to nail that down and get nowhere.

It's interesting you say not to use 2.x because that was my thinking too -- but the USB plugs provided with the drive both have white tips, not blue. And considering it's got two plugs coming off one cable... I kinda just assumed it was deliberately designed to be 2.x compatible while still ensuring it drew sufficient power by pulling off two ports at once.

I'm seriously considering just getting a SATA case-mounted Blu-Ray burner, and replacing the OEM DVD-RAM drive in my tower. Granted, the only BD-R drive in my price range is an LG, same as my slimline USBx2 model (which was a gift, hence the portable form factor)... But based on what you're saying, it sounds like that might not matter if I'm using SATA direct and bypassing USB altogether. Thoughts?

[dbminter]

Well, there's no guarantee, but SATA is a separate connection methodology on the mobo versus the USB.  So, you may have better luck connecting directly by SATA.  It has other advantages, too.  For instance, if you have a communication failure over USB for different reasons, the drive may simply just stop doing anything.  SATA connected drives will generally return some kind of error.

 

I also was wondering what you were talking about when you said a Y cable.  That must be one end for connecting by USB 2.x and the other by USB 3.0?

 

What I do is buy a half height, e.g. internal, 5.25" BD drive and put it in an external USB enclosure.  I use the LG WH16NS60 BD drive and the VanTec USB 3.0 enclosure for my purposes.

[Tape It Up Reproductions]

I'm looking at the WH16NS40 (no real desire for UHD) so good to know you've had luck with one in the same family.

 And, no -- the Y cable is a standard USB-micro B on one end, and two USB2.0 A-male on the other end.

[dbminter]

Wait, you've been connecting this BD drive by USB 2.x?  Those cables have white ends which indicates USB 2.x connections.  It shouldn't even be working right at all on either PC if you do that.  Try not using that cable at all but a dedicated USB 3.0 cable on a USB 3.0 port on the PC where the burns are failing.  See if that helps.

 

Don't get the WH16NS40 if you plan on burning BD-R DL or BD-RE DL.  It absolutely will fail 90% of the time, regardless of media and the drive's claims it can burn double layer BD discs.  It cannot do it properly.  I know this from experience with multiple copies of the NS40 over years of use.  That's why I got the NS60.  It can.  I don't care for UHD either, but that's now why I got it.