vskeide Posted October 10, 2013 Posted October 10, 2013 Hello! I have tried searching the forums for similar problems with a solution for some time now without succes. Hopefully someone out there knows what could be the cause of my problems! Up until now i have had no problems creating dl blu rays with imgburn, but after a update som months ago i suddenly started creating coasters. As i did not have time to sort out the issue then, i just stopped creating discs for a while. I decided to try again today, and noticed a new update had arrived and hoped this might sort out the problem, but in stead i have now created 3 more coasters. I do not have the expertise(or time to become an expert on this specific issue atm), so hopefully someone can give me an answer to where the problem lies. My drive should have the latest firmware. My log file is as follows: I 10:21:51 ImgBurn Version 2.5.8.0 started! I 10:21:51 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 10:21:51 Total Physical Memory: 4 193 520 KiB - Available: 1 485 548 KiB I 10:21:51 Initialising SPTI... I 10:21:51 Searching for SCSI / ATAPI devices... I 10:21:52 -> Drive 1 - Info: Optiarc DVD RW AD-7200S 1.06 (H:) (ATA) I 10:21:52 -> Drive 2 - Info: ASUS BW-12B1LT 1.03 (D:) (RAID) I 10:21:52 -> Drive 3 - Info: MagicISO Virtual DVD-ROM 1.0A (E:) (Unknown) I 10:21:52 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 BD-RE! I 10:23:35 Operation Started! I 10:23:35 Source File: L:\Nedlastingar6\Pacific.Rim.2013.1080p.BluRay.3D.AVC.DTS-HD.MA.7.1-PublicHD.iso I 10:23:35 Source File Sectors: 21 826 528 (MODE1/2048) I 10:23:35 Source File Size: 44 700 729 344 bytes I 10:23:35 Source File Volume Identifier: PACIFIC_RIM I 10:23:35 Source File Volume Set Identifier: 8D070A052E39C509_VOLUME_SET_ID I 10:23:35 Source File Application Identifier: APPLICATION_ID I 10:23:35 Source File Implementation Identifier: IMPLEMENTATION_ID I 10:23:35 Source File File System(s): UDF (2.50) I 10:23:35 Destination Device: [5:0:0] ASUS BW-12B1LT 1.03 (D:) (RAID) I 10:23:35 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 10:23:35 Destination Media Supported Write Speeds: 4x I 10:23:35 Destination Media Sectors: 24 438 784 I 10:23:35 Write Mode: BD I 10:23:35 Write Type: DAO I 10:23:35 Write Speed: 2x I 10:23:35 Hardware Defect Management Active: No I 10:23:35 BD-R Verify Not Required: Yes I 10:23:35 Link Size: Auto I 10:23:35 Lock Volume: Yes I 10:23:35 Test Mode: No I 10:23:35 OPC: No I 10:23:35 BURN-Proof: Enabled W 10:23:37 Write Speed Miscompare! - Wanted: 8 991 KB/s (2x), Got: 17 980 KB/s (4x) W 10:23:37 The drive only supports writing these discs at 4x. I 10:24:33 Filling Buffer... (40 MiB) I 10:24:34 Writing LeadIn... I 10:24:36 Writing Session 1 of 1... (1 Track, LBA: 0 - 21826527) I 10:24:36 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21826527) I 10:24:36 Writing Layer 0... (LBA: 0 - 12219391) I 10:47:51 Writing Layer 1... (LBA: 12219392 - 21826527) W 10:48:43 Failed to Write Sectors 12481312 - 12481343 - Reason: Timeout on Logical Unit W 10:48:43 Retrying (1 of 20)... W 10:48:43 Retry Failed - Reason: Invalid Address For Write W 10:48:43 Retrying (2 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (3 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (4 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (5 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (6 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (7 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (8 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (9 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (10 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (11 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (12 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (13 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (14 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (15 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (16 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (17 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (18 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (19 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 10:48:44 Retrying (20 of 20)... W 10:48:44 Retry Failed - Reason: Invalid Address For Write W 12:16:55 Retrying (21)... W 12:16:57 Retry Failed - Reason: Invalid Address For Write W 12:16:59 Retrying (22)... W 12:16:59 Retry Failed - Reason: Invalid Address For Write W 12:17:03 Retrying (23)... W 12:17:03 Retry Failed - Reason: Invalid Address For Write E 12:17:06 Failed to Write Sectors 12481312 - 12481343 - Reason: Timeout on Logical Unit E 12:17:06 Next Writable Address: 0 I 12:17:06 Synchronising Cache... I 12:17:16 Closing Track... I 12:17:19 Finalising Disc... E 12:17:40 Failed to Write Image! I 12:17:40 Exporting Graph Data... I 12:17:40 Graph Data File: C:\Users\Vebjørn\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-12B1LT_1.03_10-OKTOBER-2013_10-23_VERBAT-IMd-000_2x.ibg I 12:17:40 Export Successfully Completed! E 12:17:40 Operation Failed! - Duration: 01:54:05 I 12:17:40 Average Write Rate: 3 698 KiB/s (0.8x) - Maximum Write Rate: 28 771 KiB/s (6.6x)
LIGHTNING UK! Posted October 10, 2013 Posted October 10, 2013 It looks like your drive is having trouble burning to the discs you're using. There's nothing ImgBurn can do to prevent that from happening, it's hardware having a problem with hardware. It's up to you if you want to try some different discs or try a different drive. Crossflashing your ASUS to the latest LiteOn firmware might give you better results. Check the MyCE forums for info on that, I'm sure it's covered somewhere.
vskeide Posted October 10, 2013 Author Posted October 10, 2013 Thanks for a very quick answer, excellent support! Could it be a issue with the drive itself(or some controller to the drive)? I have burned 40+ discs without problems before using the excact same disks...
LIGHTNING UK! Posted October 10, 2013 Posted October 10, 2013 There's no way for me to say for sure either way without trying other hardware/media to narrow down where the issue is. The error should be coming from the drive itself. What controller is the drive attatched to? Right click the drive selection box and click 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the log window please.
vskeide Posted October 11, 2013 Author Posted October 11, 2013 Here is a new log from another failed write today. The family tree is at the bottom: I 10:23:04 ImgBurn Version 2.5.8.0 started! I 10:23:04 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 10:23:04 Total Physical Memory: 4 193 520 KiB - Available: 2 508 088 KiB I 10:23:04 Initialising SPTI... I 10:23:04 Searching for SCSI / ATAPI devices... I 10:23:05 -> Drive 1 - Info: Optiarc DVD RW AD-7200S 1.06 (H:) (ATA) I 10:23:05 -> Drive 2 - Info: ASUS BW-12B1LT 1.03 (D:) (RAID) I 10:23:05 -> Drive 3 - Info: MagicISO Virtual DVD-ROM 1.0A (E:) (Unknown) I 10:23:05 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 BD-RE! I 10:27:36 Operation Started! I 10:27:36 Source File: L:\Nedlastingar6\Pacific.Rim.2013.1080p.BluRay.3D.AVC.DTS-HD.MA.7.1-PublicHD.iso I 10:27:36 Source File Sectors: 21 826 528 (MODE1/2048) I 10:27:36 Source File Size: 44 700 729 344 bytes I 10:27:36 Source File Volume Identifier: PACIFIC_RIM I 10:27:36 Source File Volume Set Identifier: 8D070A052E39C509_VOLUME_SET_ID I 10:27:36 Source File Application Identifier: APPLICATION_ID I 10:27:36 Source File Implementation Identifier: IMPLEMENTATION_ID I 10:27:36 Source File File System(s): UDF (2.50) I 10:27:36 Destination Device: [5:0:0] ASUS BW-12B1LT 1.03 (D:) (RAID) I 10:27:36 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 10:27:36 Destination Media Supported Write Speeds: 4x I 10:27:36 Destination Media Sectors: 24 438 784 I 10:27:36 Write Mode: BD I 10:27:36 Write Type: DAO I 10:27:36 Write Speed: 4x I 10:27:36 Hardware Defect Management Active: No I 10:27:36 BD-R Verify Not Required: Yes I 10:27:36 Link Size: Auto I 10:27:36 Lock Volume: Yes I 10:27:36 Test Mode: No I 10:27:36 OPC: No I 10:27:36 BURN-Proof: Enabled I 10:27:37 Write Speed Successfully Set! - Effective: 17 980 KB/s (4x) I 10:29:19 Filling Buffer... (80 MiB) I 10:29:21 Writing LeadIn... I 10:29:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 21826527) I 10:29:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21826527) I 10:29:22 Writing Layer 0... (LBA: 0 - 12219391) W 10:49:15 Failed to Write Sectors 9801408 - 9801439 - Reason: Write Error W 10:49:15 Retrying (1 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (2 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (3 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (4 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (5 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (6 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (7 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (8 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (9 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (10 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (11 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (12 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (13 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (14 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (15 of 20)... W 10:49:18 Retry Failed - Reason: Invalid Address For Write W 10:49:18 Retrying (16 of 20)... W 10:49:19 Retry Failed - Reason: Invalid Address For Write W 10:49:19 Retrying (17 of 20)... W 10:49:19 Retry Failed - Reason: Invalid Address For Write W 10:49:19 Retrying (18 of 20)... W 10:49:19 Retry Failed - Reason: Invalid Address For Write W 10:49:19 Retrying (19 of 20)... W 10:49:19 Retry Failed - Reason: Invalid Address For Write W 10:49:19 Retrying (20 of 20)... W 10:49:19 Retry Failed - Reason: Invalid Address For Write W 11:05:32 Retrying (21)... W 11:05:34 Retry Failed - Reason: Invalid Address For Write W 11:05:44 Retrying (22)... W 11:05:44 Retry Failed - Reason: Invalid Address For Write W 11:05:45 Retrying (23)... W 11:05:45 Retry Failed - Reason: Invalid Address For Write W 11:05:46 Retrying (24)... W 11:05:46 Retry Failed - Reason: Invalid Address For Write W 11:05:47 Retrying (25)... W 11:05:47 Retry Failed - Reason: Invalid Address For Write W 11:05:47 Retrying (26)... W 11:05:47 Retry Failed - Reason: Invalid Address For Write W 11:05:48 Retrying (27)... W 11:05:48 Retry Failed - Reason: Invalid Address For Write W 11:05:48 Retrying (28)... W 11:05:48 Retry Failed - Reason: Invalid Address For Write W 11:05:48 Retrying (29)... W 11:05:48 Retry Failed - Reason: Invalid Address For Write W 11:05:49 Retrying (30)... W 11:05:49 Retry Failed - Reason: Invalid Address For Write W 11:05:49 Retrying (31)... W 11:05:49 Retry Failed - Reason: Invalid Address For Write W 11:05:50 Retrying (32)... W 11:05:50 Retry Failed - Reason: Invalid Address For Write W 11:05:50 Retrying (33)... W 11:05:50 Retry Failed - Reason: Invalid Address For Write W 11:05:50 Retrying (34)... W 11:05:50 Retry Failed - Reason: Invalid Address For Write W 11:05:50 Retrying (35)... W 11:05:50 Retry Failed - Reason: Invalid Address For Write W 11:05:51 Retrying (36)... W 11:05:51 Retry Failed - Reason: Invalid Address For Write W 11:05:51 Retrying (37)... W 11:05:51 Retry Failed - Reason: Invalid Address For Write W 11:05:51 Retrying (38)... W 11:05:51 Retry Failed - Reason: Invalid Address For Write W 11:05:51 Retrying (39)... W 11:05:51 Retry Failed - Reason: Invalid Address For Write W 11:05:51 Retrying (40)... W 11:05:51 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (41)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (42)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (43)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (44)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (45)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (46)... W 11:05:52 Retry Failed - Reason: Invalid Address For Write W 11:05:52 Retrying (47)... W 11:05:53 Retry Failed - Reason: Invalid Address For Write W 11:05:53 Retrying (48)... W 11:05:53 Retry Failed - Reason: Invalid Address For Write W 11:05:53 Retrying (49)... W 11:05:53 Retry Failed - Reason: Invalid Address For Write E 11:07:25 Failed to Write Sectors 9801408 - 9801439 - Reason: Write Error E 11:07:25 Next Writable Address: 0 I 11:07:25 Synchronising Cache... W 11:07:32 User opted to skip the 'Close Track/Session/Disc' functions. E 11:07:32 Failed to Write Image! I 11:07:32 Exporting Graph Data... I 11:07:32 Graph Data File: C:\Users\Vebjørn\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-12B1LT_1.03_11-OKTOBER-2013_10-27_VERBAT-IMd-000_4x.ibg I 11:07:32 Export Successfully Completed! E 11:07:32 Operation Failed! - Duration: 00:39:56 I 11:07:32 Average Write Rate: 8 590 KiB/s (2.0x) - Maximum Write Rate: 17 787 KiB/s (4.1x) I 11:08:47 Device: [5:0:0] ASUS BW-12B1LT 1.03 (D:) (RAID) I 11:08:47 Family Tree: I 11:08:47 -> ACPI x64-based PC I 11:08:47 -> Microsoft ACPI-kompatibelt system I 11:08:47 -> PCI bus I 11:08:47 -> Intel® 82801 PCI Bridge - 244E (VEN_8086&DEV_244E - Intel - pci) I 11:08:47 -> Silicon Image SiI 3114 SoftRaid 5 Controller (VEN_1095&DEV_3114 - Silicon Image - Si3114r5) I 11:08:47 -> CD-ROM-stasjon (ASUS BW-12B1LT SCSI CdRom Device) (Bus Number 0, Target ID 0, LUN 0)
LIGHTNING UK! Posted October 11, 2013 Posted October 11, 2013 Ah, that one gave you a proper 'Write Error'. (refer back to 'post #2') I assume you have no spare SATA ports on your Intel controller and that's why you've connected it to a Silicon Image chipset based card?
vskeide Posted October 11, 2013 Author Posted October 11, 2013 Yeah, that was the initial reason, but as you mention it. It might have been changed from the Intel controller to the SI controller when i installed som new drives some time back. I'll try to change that and see if that does any difference! Thanks for looking into this btw! I'll get back when i have tried a new burn.
Cynthia Posted October 11, 2013 Posted October 11, 2013 If you don't use that SI card for RAID purpose, but only want to use it for optical discs - flash it to a IDE BIOS status.
vskeide Posted October 12, 2013 Author Posted October 12, 2013 Ok, i'll keep that in mind, currently there are some drives connected to it as well, so will not be using it solely for optical discs. But thanks for the advice Status per now is that when I moved it to the Intel controller it completed a burn without errors on a BD-RE TDK media. So next up will be to try my last Verbatim BD-r and see if the problem is solved. Will keep you posted once I have had time to tryI!
vskeide Posted October 14, 2013 Author Posted October 14, 2013 So today I got around to try the Verbatim DL media again, Since the TDK BD-RE worked great I had my hopes up and was positive this was going to work after changing to the Intel on-board SATA controller. BUT, it did not. In fact it gave me a write error before finishing 1% of the movie. I cannot simply fathom what could be wrong after burning lots and lots of discs, using the excact same media, and now all of a sudden it does not work. I guess i cannot blame the burner or the software either since it completed a burn to the BD-RE. Did i just get lucky with the BD-RE maybe? I'll have to test some more burns with the TDK media to be sure, and have ordered some TDK BD-R media to test that as well.. Any further input or suggestions would be appreciated.. *sigh* Log for the last burn: I 22:35:08 ImgBurn Version 2.5.8.0 started! I 22:35:08 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 22:35:08 Total Physical Memory: 4 193 520 KiB - Available: 1 322 032 KiB I 22:35:08 Initialising SPTI... I 22:35:08 Searching for SCSI / ATAPI devices... I 22:35:16 -> Drive 1 - Info: ASUS BW-12B1LT 1.03 (D:) (ATA) I 22:35:17 -> Drive 2 - Info: Optiarc DVD RW AD-7200S 1.06 (H:) (ATA) I 22:35:17 -> Drive 3 - Info: MagicISO Virtual DVD-ROM 1.0A (E:) (Unknown) I 22:35:17 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 BD-RE! I 22:36:56 Operation Started! I 22:36:56 Source File: L:\Nedlastingar6\The Great Gatsby 2013. 3D Blu-ray AVC DTS-HD MA 5.1-HDW.iso I 22:36:56 Source File Sectors: 21 671 968 (MODE1/2048) I 22:36:56 Source File Size: 44 384 190 464 bytes I 22:36:56 Source File Volume Identifier: THE_GREAT_GATSBY I 22:36:56 Source File Volume Set Identifier: 8D04C8F043E29F95_VOLUME_SET_ID I 22:36:56 Source File Application Identifier: APPLICATION_ID I 22:36:56 Source File Implementation Identifier: IMPLEMENTATION_ID I 22:36:56 Source File File System(s): UDF (2.50) I 22:36:56 Destination Device: [1:0:0] ASUS BW-12B1LT 1.03 (D:) (ATA) I 22:36:56 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 22:36:56 Destination Media Supported Write Speeds: 4x I 22:36:56 Destination Media Sectors: 24 438 784 I 22:36:56 Write Mode: BD I 22:36:56 Write Type: DAO I 22:36:56 Write Speed: MAX I 22:36:56 Hardware Defect Management Active: No I 22:36:56 BD-R Verify Not Required: Yes I 22:36:56 Link Size: Auto I 22:36:56 Lock Volume: Yes I 22:36:56 Test Mode: No I 22:36:56 OPC: No I 22:36:56 BURN-Proof: Enabled I 22:36:57 Write Speed Successfully Set! - Effective: 17 980 KB/s (4x) I 22:38:42 Filling Buffer... (80 MiB) I 22:38:43 Writing LeadIn... I 22:38:44 Writing Session 1 of 1... (1 Track, LBA: 0 - 21671967) I 22:38:44 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21671967) I 22:38:44 Writing Layer 0... (LBA: 0 - 12219391) W 22:39:00 Failed to Write Sectors 64992 - 65023 - Reason: Write Error W 22:39:00 Retrying (1 of 20)... W 22:39:01 Retry Failed - Reason: Invalid Address For Write W 22:39:01 Retrying (2 of 20)... W 22:39:01 Retry Failed - Reason: Invalid Address For Write W 22:39:01 Retrying (3 of 20)... W 22:39:01 Retry Failed - Reason: Invalid Address For Write W 22:39:01 Retrying (4 of 20)... W 22:39:01 Retry Failed - Reason: Invalid Address For Write W 22:39:01 Retrying (5 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (6 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (7 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (8 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (9 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (10 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (11 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (12 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (13 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (14 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (15 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (16 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (17 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (18 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (19 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:39:02 Retrying (20 of 20)... W 22:39:02 Retry Failed - Reason: Invalid Address For Write W 22:40:42 Retrying (21)... W 22:40:42 Retry Failed - Reason: Invalid Address For Write W 22:40:43 Retrying (22)... W 22:40:43 Retry Failed - Reason: Invalid Address For Write E 22:40:46 Failed to Write Sectors 64992 - 65023 - Reason: Write Error E 22:40:46 Next Writable Address: 0 I 22:40:46 Synchronising Cache... W 22:40:54 User opted to skip the 'Close Track/Session/Disc' functions. E 22:40:54 Failed to Write Image! I 22:40:54 Exporting Graph Data... I 22:40:54 Graph Data File: C:\Users\Vebjørn\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-12B1LT_1.03_14-OKTOBER-2013_22-36_VERBAT-IMd-000_MAX.ibg I 22:40:54 Export Successfully Completed! E 22:40:54 Operation Failed! - Duration: 00:03:58 I 22:40:54 Average Write Rate: 1 074 KiB/s (0.2x) - Maximum Write Rate: 17 673 KiB/s (4.0x)
LIGHTNING UK! Posted October 14, 2013 Posted October 14, 2013 Without trying the media in another drive, you can't really rule out the drive as being the issue. Drives/firmware often prefer certain discs over others. Have you looked into cross flashing it to a LiteOn and using the latest firmware for the LiteOn model? It may fix the issue. Of course that doesn't really make sense if it's burnt 'VERBAT-IMd-000' perfectly fine in the past. Did you get a new spindle of discs? Are you sure they're the same MID (i.e. 'VERBAT-IMd-000') as before? Crossflash to a Liteon, keep the drive for scanning and invest in a new Pioneer drive or something.
vskeide Posted October 21, 2013 Author Posted October 21, 2013 Yes. the MID was exactly the same as the ones i have burnt before. Have now tried with the TDK DL BD-R discs I recently purchased, and a Verbatim dl BD-RE, and they both burned successfullt. So my conclusion is that it might be a bad batch/spindle(is that posible?), or that my burner suddenly has gone tired of the Verbatim discs and refuses to burn them anymore..anyways. Problem solved for now, and hoping the TDK's will burn consistently. Thanks for all the help and input! Much appreciated:)
spinningwheel Posted October 23, 2013 Posted October 23, 2013 So my conclusion is that it might be a bad batch/spindle(is that posible?)
LIGHTNING UK! Posted October 23, 2013 Posted October 23, 2013 If that drive supports it, you should probably do a few quality scans on the ones that don't error out during the write process. Even a seemingly successful burn can be rubbish quality - and the disc will then probably be unreadable in a relatively short period of time.
Recommended Posts