Gardenerr Posted Wednesday at 09:17 PM Posted Wednesday at 09:17 PM Hello, I have a stack of Verbatim BD-R DLs which I bought a couple years ago and have used on and off since then, without any issues. However, beginning a couple weeks ago, any attempts to burn to these discs leads to an error like the following: Quote I 05:20:21 ImgBurn Version 2.5.8.0 started! I 05:20:21 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 05:20:21 Total Physical Memory: 8,243,660 KiB - Available: 5,133,244 KiB I 05:20:22 Initialising SPTI... I 05:20:22 Searching for SCSI / ATAPI devices... I 05:20:22 -> Drive 1 - Info: BUFFALO Optical Drive 2.00 (D:) (USB 2.0) I 05:20:22 Found 1 BD-RE XL! I 05:20:59 Operation Started! I 05:20:59 Building Image Tree... I 05:20:59 Calculating Totals... I 05:20:59 Preparing Image... I 05:21:00 Contents: 9 Files, 15 Folders I 05:21:00 Content Type: BD Video I 05:21:00 Data Type: MODE1/2048 I 05:21:00 File System(s): UDF (2.50) I 05:21:00 Volume Label: [Not Configured] I 05:21:00 Size: 30,478,893,196 bytes I 05:21:00 Sectors: 14,882,279 I 05:21:00 Image Size: 30,479,941,632 bytes I 05:21:00 Image Sectors: 14,882,784 I 05:21:00 Operation Successfully Completed! - Duration: 00:00:00 I 05:21:09 Operation Started! I 05:21:09 Building Image Tree... I 05:21:12 Calculating Totals... I 05:21:12 Preparing Image... I 05:21:12 Contents: 9 Files, 15 Folders I 05:21:12 Content Type: BD Video I 05:21:12 Data Type: MODE1/2048 I 05:21:12 File System(s): UDF (2.50) I 05:21:12 Volume Label: Test I 05:21:12 Size: 30,478,893,196 bytes I 05:21:12 Sectors: 14,882,279 I 05:21:12 Image Size: 30,479,941,632 bytes I 05:21:12 Image Sectors: 14,882,784 I 05:21:13 Operation Successfully Completed! - Duration: 00:00:03 I 05:21:13 Operation Started! I 05:21:13 Source File: -==/\/[BUILD IMAGE]\/\==- I 05:21:13 Source File Sectors: 14,882,784 (MODE1/2048) I 05:21:13 Source File Size: 30,479,941,632 bytes I 05:21:13 Source File Volume Identifier: Test I 05:21:13 Source File Volume Set Identifier: 5C722AA400E31767 I 05:21:13 Source File Application Identifier: ImgBurn v2.5.8.0 I 05:21:13 Source File Implementation Identifier: ImgBurn I 05:21:13 Source File File System(s): UDF (2.50) I 05:21:13 Destination Device: [0:0:0] BUFFALO Optical Drive 2.00 (D:) (USB) I 05:21:13 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 05:21:13 Destination Media Supported Write Speeds: 2x, 4x, 6x I 05:21:13 Destination Media Sectors: 24,438,784 I 05:21:13 Write Mode: BD I 05:21:13 Write Type: DAO I 05:21:13 Write Speed: 6x I 05:21:13 Hardware Defect Management Active: No I 05:21:13 BD-R Verify Not Required: Yes I 05:21:13 Link Size: Auto I 05:21:13 Lock Volume: Yes I 05:21:13 Test Mode: No I 05:21:13 OPC: No I 05:21:13 BURN-Proof: Enabled I 05:21:13 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x) I 05:22:00 Filling Buffer... (80 MiB) I 05:22:03 Writing LeadIn... I 05:22:04 Writing Session 1 of 1... (1 Track, LBA: 0 - 14882783) I 05:22:04 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 14882783) I 05:22:04 Writing Layer 0... (LBA: 0 - 12219391) W 05:31:12 Waiting for buffers to recover... (LBA: 3853792) W 05:31:22 Waiting for hard disk activity to reach threshold level... I 05:31:33 Writing Sectors... I 05:44:21 Writing Layer 1... (LBA: 12219392 - 14882783) W 05:44:28 Failed to Write Sectors 12245248 - 12245279 - Reason: Write Error W 05:44:28 Retrying (1 of 20)... W 05:44:29 Retry Failed - Reason: Invalid Address For Write W 05:44:29 Retrying (2 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (3 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (4 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (5 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (6 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (7 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (8 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (9 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (10 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (11 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (12 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (13 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (14 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (15 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (16 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (17 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (18 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (19 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:44:30 Retrying (20 of 20)... W 05:44:30 Retry Failed - Reason: Invalid Address For Write W 05:45:21 Retrying (21)... W 05:45:21 Retry Failed - Reason: Invalid Address For Write W 05:45:21 Retrying (22)... W 05:45:21 Retry Failed - Reason: Invalid Address For Write E 05:47:41 Failed to Write Sectors 12245248 - 12245279 - Reason: Write Error E 05:47:41 Next Writable Address: 3853792 This always happens when it is beginning to write to the second layer. I have used two separate drives and the errors occur on both. Afterwards when I turn the failed disc over, I see small bubbles have appeared where it has attempted to write to the second layer: The obvious conclusion would be that the discs are bad, but I have not heard of the first dozen discs in a stack being fine and the others being unusable. I've also never seen this "bubble" issue before. Before I spend another $100 on new double-layer Blu-rays I'd like to know if bad discs definitely are the culprit, and it is not something wrong with the way my computer is trying to author the disc. Thank you.
dbminter Posted Wednesday at 10:14 PM Posted Wednesday at 10:14 PM I've not used that drive before or any BD-R DL discs, but I did notice something that might be worth trying. I see the device is listed as USB 2.0, but that may be a cosmetic bug in ImgBurn listing USB 3.x as 2.0. Blu-Ray burners need USB 3.x connection speeds to operate at optimum capacity. If you know the device is connected to a USB 2.x port or using a USB 2.x cable, try using a USB 3.x cable on a USB 3.x port and see if that helps.
Gardenerr Posted Wednesday at 10:44 PM Author Posted Wednesday at 10:44 PM (edited) Thanks for the suggestion. However, the drive itself (BRXL-PC6U2) is an external with built-in 2.0 cables. My other external (BRXL-PTGU2V) also comes with 2.0 attached. The ports on my desktop are 3.0. Edited Wednesday at 10:45 PM by Gardenerr
dbminter Posted Wednesday at 10:53 PM Posted Wednesday at 10:53 PM I saw a USB BD burner recently that also said it was 2.x. I'd always heard you needed USB 3.x to properly use them, but that may not be the case. It was my only suggestion other than this. I wouldn't invest in another batch of BD-R DL thinking you had a bad batch unless you have successfully burned these BD-R DL before in this drive. And even if they have, Verbatim made a running change in their branded BD-R SL that make them junk now. I can't say for sure, but that may have happened with the BD-R DL. Are your Verbatim BD-R DL the DataLife Plus variety? If they are, they should be good. I plan on testing some of those for the first time next month.
Gardenerr Posted Wednesday at 11:00 PM Author Posted Wednesday at 11:00 PM (edited) I've used both of these drives for years without issue, as well as many other discs from this particular stack. I just am surprised that some discs at the top of the spindle I bought worked fine whereas others in the same set suddenly have issues. I guess the warping in the photo leaves no other explanation though. I saw your 2025 post about Verbatim being low-quality now; what a shame. The spindle I'm currently trying to use is from 2024, I think -- don't think they were DataLife. What brand do you suggest instead? Edited Wednesday at 11:05 PM by Gardenerr
dbminter Posted Wednesday at 11:35 PM Posted Wednesday at 11:35 PM If these discs worked before in this drive before and if you got discs in this current stack to work but now they're not, the issue is probably 1 of 2 things: 1.) you got a bad batch of discs part way through your current stack 2.) your drive most likely needs replacing I would be more willing to bet on #2 versus #1. The cheapest solution is probably to get another stack and see if they work any better. I've never used BD-R DL before. Only BD-RE DL. The Verbatim BD-R DL I were using weren't that great over 10 years ago. I'd write to them for yearly backups and then write a year later and they wouldn't complete writes for a 2nd time. So, I really can't recommend any BD-R DL. I've got bookmarked some Verbatim DataLife Plus BD-R DL as Verbatim DataLife BD-R SL are the only ones I trust now.
Gardenerr Posted 17 hours ago Author Posted 17 hours ago (edited) I grabbed a BD-DL disc from a different spindle and it burned fine -- clearly just an issue with the discs themselves. I've just never experienced half a stack being bad as opposed to the whole thing, but I guess that's what happened here. Thank you for your help! Edited 17 hours ago by Gardenerr
dbminter Posted 16 hours ago Posted 16 hours ago I'm glad it was an easy fix! I have seen cases in my own experience before where a spindle was fine part of the way through but bad in the rest. I can see it happening. A spindle might use up the last few discs from one batch, which was good, but the next batch pressed might be bad. So, the remaining discs added to that cake stack could theoretically be bad.
Gardenerr Posted 2 hours ago Author Posted 2 hours ago (edited) Spoke too soon -- the disc finished writing, it did write to the second layer, but was not able to write data at the edges of either layer. I know you point to the either the discs or the drives as the problem, but it does not seem right to me. I've two different sets of discs, and trialed on two different drives. The only commonality is my Windows configuration; the Buffalo drives have no firmware of their own to my knowledge. I guess this becomes very difficult to diagnose. Are there any threads or guides to checking or refreshing Windows's disc-writing capabilities? Edited 2 hours ago by Gardenerr
dbminter Posted 1 hour ago Posted 1 hour ago Actually, it makes more sense that there's a disc or drive issue. I've never encountered a case where a Windows error prevented writing optical media. It was always a drive or media issue. I've been experimenting with a Buffalo MediaStation BD XL burner. It uses an LG BH burner inside it with no firmware updates available. And it seems borked to writing CD's. It will only write CD's of 100 MB or less. Anything larger and it will return invalid write addresses or if it's a nearly full CD image, semaphore timeout issues. Those are usually firmware errors only fixable by firmware updates. I know LG's WH16NS40 initially had problems writing to BD-R/RE DL media. I know from experience 9 times out of 10, BD-RE DL would fail and others here reported BD-R DL media were known failures on the NS40. However, that was 10 years ago and firmware updates have come out since then.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now