stoneystevenson Posted August 8, 2016 Posted August 8, 2016 Just got 10 of these discs and receiving burn error. Three weeks ago I burned 20 verbatim labeled discs with the same manufacturer ID MEI-T01-001. I had no problem with those. I need to know if the discs are defective for a refund. Also AV was off at time of burning. Thanks... ; //****************************************\\; ImgBurn Version 2.5.8.0 - Log; Monday, 08 August 2016, 18:31:41; \\****************************************//;;I 18:02:02 ImgBurn Version 2.5.8.0 started!I 18:02:02 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)I 18:02:02 Total Physical Memory: 6,289,904 KiB - Available: 5,121,176 KiBI 18:02:02 Initialising SPTI...I 18:02:02 Searching for SCSI / ATAPI devices...I 18:02:02 -> Drive 1 - Info: DiscSoft Virtual 1.0 (N:) (Virtual)I 18:02:03 -> Drive 2 - Info: HL-DT-ST BD-RE WH14NS40 1.03-A0 (F:) (SATA)I 18:02:03 Found 1 BD-ROM XL and 1 BD-RE XL!I 18:04:39 Operation Started!I 18:04:39 Source File: D:\BLU-RAY ISO'S\encrypted.P-NEW US-4.ISOI 18:04:39 Source File Sectors: 24,435,361 (MODE1/2048)I 18:04:39 Source File Size: 50,043,619,328 bytesI 18:04:39 Source File File System(s): NoneI 18:04:39 Destination Device: [3:0:0] HL-DT-ST BD-RE WH14NS40 1.03 (F:) (SATA)I 18:04:39 Destination Media Type: BD-R (Disc ID: MEI-T01-001)I 18:04:39 Destination Media Supported Write Speeds: 2xI 18:04:39 Destination Media Sectors: 24,438,784I 18:04:39 Write Mode: BDI 18:04:39 Write Type: DAOI 18:04:39 Write Speed: MAXI 18:04:39 Hardware Defect Management Active: NoI 18:04:39 BD-R Verify Not Required: YesI 18:04:39 Link Size: AutoI 18:04:39 Lock Volume: YesI 18:04:39 Test Mode: NoI 18:04:39 OPC: NoI 18:04:39 BURN-Proof: EnabledI 18:04:40 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x)I 18:04:58 Filling Buffer... (80 MiB)I 18:04:58 Writing LeadIn...I 18:04:59 Writing Session 1 of 1... (1 Track, LBA: 0 - 24435360)I 18:04:59 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24435360)I 18:04:59 Writing Layer 0... (LBA: 0 - 12219391)W 18:26:37 Failed to Write Sectors 5707552 - 5707583 - Reason: Write ErrorW 18:26:37 Retrying (1 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (2 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (3 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (4 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (5 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (6 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (7 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (8 of 20)...W 18:26:37 Retry Failed - Reason: Invalid Address For WriteW 18:26:37 Retrying (9 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (10 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (11 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (12 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (13 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (14 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (15 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (16 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (17 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (18 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (19 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteW 18:26:38 Retrying (20 of 20)...W 18:26:38 Retry Failed - Reason: Invalid Address For WriteE 18:28:02 Failed to Write Sectors 5707552 - 5707583 - Reason: Write ErrorE 18:28:02 Next Writable Address: 0I 18:28:02 Synchronising Cache...W 18:28:10 User opted to skip the 'Close Track/Session/Disc' functions.E 18:28:10 Failed to Write Image!I 18:28:13 Exporting Graph Data...I 18:28:13 Graph Data File: C:\Users\JEFF\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH14NS40_1.03_MONDAY-AUGUST-08-2016_6-04_PM_MEI-T01-001_MAX.ibgI 18:28:13 Export Successfully Completed!E 18:28:13 Operation Failed! - Duration: 00:23:31I 18:28:13 Average Write Rate: 8,259 KiB/s (1.9x) - Maximum Write Rate: 8,872 KiB/s (2.0x)I 18:31:40 Close Request AcknowledgedI 18:31:40 Closing Down...I 18:31:41 Shutting down SPTI...I 18:31:41 ImgBurn closed!
LIGHTNING UK! Posted August 9, 2016 Posted August 9, 2016 I guess you'd need to try some more verbatim ones with that mid to see if it's just a coincidence that the drive is failing in general now or if it's just the discs. You could try enabling the 'perform opc before write' option in the settings to see if it will help the drive achieve a decent burn on this slight variation of a previously working mid.
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