burnyo Posted January 6, 2011 Posted January 6, 2011 I have PHILIPS SPD2414T and I bought TDK DVD+R double layer discs (I know Verbatim is the best, but I couldn't find any DL Verbatim discs). I tried burning the same movie in DVD format a couple of times, but every time it would stop before reaching 30%. I've tried different writing speeds. It works fine with single layer DVDs and CDs. This is the first time I'm trying to burn any kind of double layer disc. I just want to make sure what is the problem - ImgBurn, DVD burner or TDK's discs. Here's the log: I 23:58:40 Operation Started! I 23:58:40 Building Image Tree... I 23:58:40 Checking Directory Depth... I 23:58:40 Calculating Totals... I 23:58:40 Preparing Image... I 23:58:55 Using Layer Break LBA: 2067406 -> 2067408 (VTS_01, PGC: 1, Chapter: 19, Cell: 19, Vob/Cell ID: 1/19, Time: 01:29:54, SPLIP: Yes -> No) I 23:58:55 Checking Path Length... I 23:58:55 Contents: 14 Files, 2 Folders I 23:58:55 Content Type: DVD Video I 23:58:55 Data Type: MODE1/2048 I 23:58:55 File System(s): ISO9660, UDF (1.02) I 23:58:55 Volume Label: LOTR I 23:58:56 IFO/BUP 32K Padding: Enabled I 23:58:56 Region Code: 1; 2; 3; 4; 5; 6; 8 I 23:58:56 TV System: NTSC I 23:58:56 Size: 8 396 716 032 bytes I 23:58:56 Sectors: 4 099 959 I 23:58:56 Image Size: 8 397 324 288 bytes I 23:58:56 Image Sectors: 4 100 256 I 23:58:57 Operation Successfully Completed! - Duration: 00:00:17 I 23:58:57 Operation Started! I 23:58:57 Source File: -==/\/[bUILD IMAGE]\/\==- I 23:58:57 Source File Sectors: 4 100 256 (MODE1/2048) I 23:58:57 Source File Size: 8 397 324 288 bytes I 23:58:57 Source File Volume Identifier: LOTR I 23:58:57 Source File Volume Set Identifier: 3E26BF54003E9095 I 23:58:57 Source File Application Identifier: IMGBURN V2.5.4.0 - THE ULTIMATE IMAGE BURNER! I 23:58:57 Source File Implementation Identifier: ImgBurn I 23:58:57 Source File File System(s): ISO9660; UDF (1.02) I 23:58:57 Destination Device: [1:0:0] PHILIPS SPD2414T P1.0 (E:) (ATA) I 23:58:57 Destination Media Type: DVD+R DL (Disc ID: RITEK-S04-66) (Speeds: 4x; 6x; 8x) I 23:58:57 Destination Media Sectors: 4 173 824 I 23:58:57 Write Mode: DVD I 23:58:57 Write Type: DAO I 23:58:57 Write Speed: MAX I 23:58:57 Link Size: Auto I 23:58:57 Lock Volume: Yes I 23:58:57 Test Mode: No I 23:58:57 OPC: No I 23:58:57 BURN-Proof: Enabled I 23:58:58 Write Speed Successfully Set! - Effective: 11 080 KB/s (8x) I 23:58:59 Optimal L0 Data Zone Capacity: 2 067 408 I 23:58:59 Optimal L0 Data Zone Method: IFO Cell Boundary I 23:59:38 Set L0 Data Zone Capacity Succeeded! I 23:59:38 Filling Buffer... (20 MB) I 23:59:39 Writing LeadIn... I 23:59:41 Writing Session 1 of 1... (1 Track, LBA: 0 - 4100255) I 23:59:41 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4100255) I 23:59:41 Writing Layer 0... (LBA: 0 - 2067407) W 00:03:35 Failed to Write Sectors 883552 - 883583 - Reason: Write Error W 00:03:35 Retrying (1 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (2 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (3 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (4 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (5 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (6 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (7 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (8 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (9 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (10 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (11 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (12 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (13 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (14 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (15 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (16 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (17 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (18 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (19 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write W 00:03:35 Retrying (20 of 20)... W 00:03:35 Retry Failed - Reason: Invalid Address For Write E 00:04:42 Failed to Write Sectors 883552 - 883583 - Reason: Write Error E 00:04:42 Next Writable Address: 882865 I 00:04:43 Synchronising Cache... W 00:04:47 User opted to skip the 'Close Track/Session/Disc' functions. E 00:04:47 Failed to Write Image! I 00:04:47 Exporting Graph Data... I 00:04:47 Graph Data File: C:\Documents and Settings\chmacka\Application Data\ImgBurn\Graph Data Files\PHILIPS_SPD2414T_P1.0_ÈETVRTAK-06-JANUAR-2011-_23-58_RITEK-S04-66_MAX.ibg I 00:04:47 Export Successfully Completed! E 00:04:47 Operation Failed! - Duration: 00:05:49 I 00:04:47 Average Write Rate: 5 870 KB/s (4.2x) - Maximum Write Rate: 11 185 KB/s (8.1x)
LIGHTNING UK! Posted January 6, 2011 Posted January 6, 2011 It's a drive/firmware/media combo issue. As mentioned here: http://forum.imgburn.com/index.php?showtopic=8000 The software plays no part in the actual burn, all it does is send data to the drive. Success / failure of actually writing that data to the disc is out of its hands.
burnyo Posted January 8, 2011 Author Posted January 8, 2011 I checked and the firmware was up to date. So, after burning 5 TDK DVDs failed (at the same %), I went out and bought Pro4Media's (I've never heard of them) DL DVD since I couldn't find another one. Burning the same data to this DVD succeeded without any problems which means that TDK's DVDs were bad.
LIGHTNING UK! Posted January 8, 2011 Posted January 8, 2011 Not 'bad', just no good for your drive/firmware. Best of luck with whatever you've ended up with now.
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