1650 Failed DL burn

vbimport

#1

Anyone have any ideas why this happened? The disc was ripped using dvddecrypter / 1650 drive. I tried twice with the same results. On the second attempt I was sure to scan the disc using a disc from the middle of the spindle. I also rebooted the PC before doing the second burn.

I have successfully burned DL stuff ripped using a different drive

I 19:19:28 ImgBurn Version 1.2.0.0 started!
I 19:19:28 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 2)
I 19:19:28 Initialising SPTI…
I 19:19:28 Searching for SCSI / ATAPI devices…
I 19:19:28 Found 1 DVD-ROM and 1 DVD±RW!
I 19:20:01 Operation Started!
I 19:20:01 Source File: I:\THE_ISLAND.MDS
I 19:20:01 Source File Sectors: 3,728,150 (MODE1/2048)
I 19:20:01 Source File Size: 7,635,251,200 bytes
I 19:20:01 Source File Implementation Identifier: Daikin U.S. Comtec Lab
I 19:20:01 Destination Device: [1:0:0] BENQ DVD DD DW1650 BCDC (D:) (ATAPI)
I 19:20:01 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x)
I 19:20:01 Destination Media Sectors: 4,173,824
I 19:20:01 Write Mode: DVD
I 19:20:01 Write Type: DAO
I 19:20:01 Write Speed: MAX
I 19:20:01 Link Size: Auto
I 19:20:01 Test Mode: No
I 19:20:01 BURN-Proof: Enabled
I 19:20:01 Optimal L0 Data Zone Capacity: 1,992,368
I 19:20:01 Optimal L0 Data Zone Method: Copied From Original Disc
I 19:20:02 Filling Buffer…
I 19:20:02 Writing LeadIn…
I 19:20:28 Writing Image…
I 19:20:28 Writing Layer 0… (LBA: 0 - 1992367)
W 19:41:27 Failed to Write Sectors 1968864 - 1968895 - Write Error
W 19:41:27 Retrying (1 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (2 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (3 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (4 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (5 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (6 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (7 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (8 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (9 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (10 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (11 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (12 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (13 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (14 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (15 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (16 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (17 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (18 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (19 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
W 19:41:27 Retrying (20 of 20)…
W 19:41:27 Retry Failed - Invalid Address For Write
E 19:42:54 Failed to Write Sectors 1968864 - 1968895 - Write Error
I 19:42:54 Synchronising Cache…
I 19:42:55 Closing Track…
I 19:42:57 Finalising Disc…


#2

With my first defective DW1650 (already RMAd), I had four (!) failed burns with Verbatim MKM001 2,4x DVD+R DL discs. I feel your pain, those discs are not cheap… :frowning:

Haven’t burned any DL media on my new DW1650 yet, I’m kinda reluctant after that costly incident (about half the price of the drive itself :)). Do you have problems with single layer media also? If not, try to disable WOPC for your DL burns.

BenQ should really improve both RW and DL write quality and stability with the next firmware.


#3

Yup, all extensive tests/reviews I’ve read so far underline exact that issues.


#4

I did successfully burn some dl media. This is the first disc that was ripped using the 1650. I feel that the ripping process may be at fault here. In decrypter I set the iso write mode to packet instead of sao.

I was able to do a dl test burn successfully. The question is how close is test burn mode to an actual burn? I dont feel very confident at this point…


#5

Thanks for the head’s up on DL, i’ll stick with my 1640 for verbatim DL, have had 0 problems with burning with the 1640 until proven 1650 firmwares become available.


#6

I have a success rate of 2 out of 3 using DW1650. I have only used Memorex 2.4x DL media so far.

I have used ImgBurn 1.2.0.0 for all the burns.

Initially I had setup the 1650 in a ADS Pyro Firewire/USB2.0 enclosure. Single layer DVD burned fine, but my first DL burn (Memorex 2.4x) failed while trying to write the 2nd layer. Unfortunately I didn’t save the log.

Now I have the 1650 as secondry master and I got successful burns for 2 Memorex 2.4x DL media. I didn’t see anything different for the burner buffer between Pyro Firewire and IDE connections. So I don’t know whether the burn failed because of the external enclosure or bad media.

I also noticed that Qsuite 2.1 QScan was throughing an error when the drive was connected via Firewire, but no error when using the IDE connection.

QScan says both the Memorex 2.4x and Verbatim 2.4x DL media to be not safe for burns using 2.4x speed. I get a big spike for TE and FE when the layer changes.

Both of my Memorex 2.4x DL got 79-80 quality score using 1650 and only 43 when using Lite-On DVD-ROM.

All of my Iso images are created using DVD Decrypter and Lite-On DVD-ROM.

Thanks,

DPal.


#7

Interestingly enough, my results are similar to yours, albeit with MKM 001 Verbatims. I also have a 1650, getting marginal results on DL media (at 4X), and my Liteon 1635 (at 4 X) is scoring about 40 on the quality scans. What gives with all these new drives and low scores? I only burn DL Verbatims. Seems like all the new drives are going backwards for DL media. If I can’t start getting better results soon, I’m going to go back to my old Sony DRU-700a, which is really a Liteon. It’s slow as the dickens, but at least it was solid and dependable for results.

DH


#8

See this thread about swapping strategies to fix firmware problems –

http://club.cdfreaks.com/showthread.php?t=175030