I/O Error w RecordNow Premier 8 and ImgBurn 2.1.0.0, 2 Verbat DL coasters!

[HatchetMan]

What causes this I/O error??? I was going from Original to Verbatim DVD+R DL, rippped with DVDDecrypter in File Mode. Then tried burning with RecordNow Premier 8 and coastered. Then opened with PGCEdit 7.4 to burn with ImgBurn 2.1.0.0, another coaster!!! Burnt many Verbatim DL's, first time coastering and with same movie twice in a row. Please help me to resolve. Thanks!

[redwudz]

Make sure DMA is enabled for all drives: Control Panel>System>Hardware>Device Manager>IDE ATA/ATAPI controllers. If you see PIO on any of them, uninstall that channel and reboot.

That's the most common cause.

Less likely is a very full source drive or a badly fragmented drive. That's if it's a hardware problem, which is what the error usually means.

[HatchetMan]

Make sure DMA is enabled for all drives: Control Panel>System>Hardware>Device Manager>IDE ATA/ATAPI controllers. If you see PIO on any of them, uninstall that channel and reboot.

That's the most common cause.

Less likely is a very full source drive or a badly fragmented drive. That's if it's a hardware problem, which is what the error usually means.

No PIO, only DMA.
85GB Free and defragmented before second attempt

[VegasBud]

HatchetMan,

Without a burn log there isn't much to work with, but I do have at least one question. As far as I can tell, the most recent official firmware for your drive is 8.26, but you have 8.29. Correct me if I'm wrong, but isn't 8.29 a unofficial modified firmware that just came out a few days ago? If so, is this the first time you've tried burning DL with the new firmware?

[HatchetMan]

8.26 first coaster, 8.29 second coaster. Good eye though!
Also, I have burnt SL discs at 8X and 12X since no prob at all.

//****************************************\\
; ImgBurn Version 2.1.0.0 - Log
; Friday, 20 October 2006, 21:04:39
; \\****************************************//
;
;
I 20:31:47 ImgBurn Version 2.1.0.0 started!
I 20:31:47 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)
W 20:31:47 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled!
I 20:31:47 Initialising Patin-Couffin...
I 20:31:47 Patin-Couffin - VSO Software - Version 1.35.0.0 - Internal Revision 35
I 20:31:47 Searching for SCSI / ATAPI devices...
I 20:31:47 Found 1 DVD-ROM, 1 DVD±RW and 2 DVD±RW/RAMs!
I 20:31:48 Operation Started!
I 20:31:48 Source File: D:\Movies\DVD_OutPut\MALCOLM_X.ISO
I 20:31:48 Source File Sectors: 4,046,464 (MODE1/2048)
I 20:31:48 Source File Size: 8,287,158,272 bytes
I 20:31:48 Source File Volume Identifier: MALCOLM_X
I 20:31:48 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 20:31:48 Source File Implementation Identifier: mkisofs
I 20:31:48 Source File File System(s): ISO9660, UDF (1.02)
I 20:31:48 Destination Device: [0:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)
I 20:31:48 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)
I 20:31:48 Destination Media Sectors: 4,173,824
I 20:31:48 Write Mode: DVD
I 20:31:48 Write Type: DAO
I 20:31:48 Write Speed: 4x
I 20:31:48 Link Size: Auto
I 20:31:48 Test Mode: No
I 20:31:48 BURN-Proof: Enabled
I 20:31:48 User Specified L0 Data Zone Capacity: 2,023,232
I 20:32:05 Filling Buffer...
I 20:32:06 Writing LeadIn...
I 20:32:07 Writing Image...
I 20:32:07 Writing Layer 0... (LBA: 0 - 2023231)
I 20:45:04 Writing Layer 1... (LBA: 2023232 - 4046463)
W 20:56:40 Failed to Write Sectors 3820288 - 3820319 - Write Error
W 20:56:40 Retrying (1 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (2 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (3 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (4 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (5 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (6 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (7 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (8 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (9 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (10 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (11 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (12 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (13 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (14 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (15 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (16 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (17 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (18 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (19 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 20:56:45 Retrying (20 of 20)...
W 20:56:45 Retry Failed - Invalid Address For Write
W 21:01:34 Retrying (21)...
W 21:01:34 Retry Failed - Invalid Address For Write
W 21:01:35 Retrying (22)...
W 21:01:35 Retry Failed - Invalid Address For Write
W 21:01:38 Retrying (23)...
W 21:01:38 Retry Failed - Invalid Address For Write
W 21:01:39 Retrying (24)...
W 21:01:39 Retry Failed - Invalid Address For Write
W 21:01:44 Retrying (25)...
W 21:01:44 Retry Failed - Invalid Address For Write
W 21:01:44 Retrying (26)...
W 21:01:44 Retry Failed - Invalid Address For Write
W 21:01:44 Retrying (27)...
W 21:01:44 Retry Failed - Invalid Address For Write
W 21:01:45 Retrying (28)...
W 21:01:45 Retry Failed - Invalid Address For Write
W 21:01:45 Retrying (29)...
W 21:01:45 Retry Failed - Invalid Address For Write
W 21:01:45 Retrying (30)...
W 21:01:45 Retry Failed - Invalid Address For Write
W 21:01:45 Retrying (31)...
W 21:01:45 Retry Failed - Invalid Address For Write
W 21:01:45 Retrying (32)...
W 21:01:45 Retry Failed - Invalid Address For Write
W 21:01:46 Retrying (33)...
W 21:01:46 Retry Failed - Invalid Address For Write
W 21:01:46 Retrying (34)...
W 21:01:46 Retry Failed - Invalid Address For Write
E 21:02:05 Failed to Write Sectors 3820288 - 3820319 - Write Error
I 21:02:05 Synchronising Cache...
I 21:02:06 Closing Track...
I 21:02:09 Finalising Disc...
E 21:04:11 Failed to Write Image!
E 21:04:11 Operation Failed! - Duration: 00:32:23
I 21:04:11 Average Write Rate: 4,251 KB/s (3.1x) - Maximum Write Rate: 5,592 KB/s (4.0x)
I 21:04:39 Close Request Acknowledged
I 21:04:39 Closing Down...
I 21:04:39 Shutting down Patin-Couffin...
I 21:04:39 ImgBurn closed!
;
;
; //****************************************\\

[HatchetMan]

HatchetMan,

Without a burn log there isn't much to work with, but I do have at least one question. As far as I can tell, the most recent official firmware for your drive is 8.26, but you have 8.29. Correct me if I'm wrong, but isn't 8.29 a unofficial modified firmware that just came out a few days ago? If so, is this the first time you've tried burning DL with the new firmware?

Yes and No, 8.29 is offical Buffalo based on Pioneer 1.29. But still, only this Malcolm X disc giving me caoasters, not any others? I also ran it through FixVTS, still coastered...

[VegasBud]

HatchetMan,

I don't know what to tell you...that's helpful, anyways. The only thing that stands out is the two burns you're showing failed at the exact same sector. I've seen burns fail in the same area, but I've never seen 2 burns fail precisely at the same sector. That pretty much rules out the media being the problem (not that bad verbatim DLs was likely anyway).

ImgBurn isn't reporting anything unusual at all, right up until the burn hits a brick wall. It sounds like something happening in the drive more than anything else. If you got the same results with the previous firmware, then it's unlikely to be firmware related.

I see the material you're trying to burn is about 97% capacity of the disk. Have you ever successfully burned a source this large before? It could be a problem, but shouldn't be, at least enough to be the cause of an abrupt failure at the same sector on separate burns. Still, if this is a new record for capacity burning for you, you could try downsizing a little. The consistent failure point you're experiencing is about 91.5% of capacity. Theoretically, if you can drop the size from 97% of capacity to 91% (maximum), or 90% (safer), the burn will finish before it hits the brick wall.

No, FixVTS isn't going to solve a problem like this. At this point it's all just sectors failing to be written. The content of the sectors is important when it comes to playback, but during the burn, it doesn't matter at all.

[VegasBud]

HatchetMan,

After some sleep, which seems to have increased my ability to think, I see that the log you posted was from 10 minutes before your first post, so the error message pictures and the log are from the same burn. In that case, it's not surprising at all that the failure is at the same sector.

Since only this one dvd/movie is giving you problems, and it is larger than most, you could still try cutting the source's size a little, but it shouldn't be necessary with the media and burner you're using.

As a measure of how rare your problem is, even google, when using 'verbatim dl "Invalid Address For Write" dvr-111', only has 13 hits, none of them like your situation.

[GKar]

I had same problem with same media on 2 different drives (Nec 3540 and 3550) using imageburn 2.1.0.0, used Nero 6.6.1.4 and burns were successful...I think its a problem with choosing the proper 2nd layer point, Nero seems to do it right automatically.

[VegasBud]

GKar,

The only way a bad layer break selection would cause a burn failure like HatchetMan's is if it made the second layer larger than the first, which is outside of the +R DL specification, and wouldn't be allowed by PgcEdit or ImgBurn. The log shows the layer break was correctly set by PgcEdit and accepted by ImgBurn.

I don't suppose you still have the ImgBurn/Nero logs from your experience? Maybe it would help in this case. Was your source material also near DL capacity?

[MaxBlack]

FWIW the first time I tried ImgBurn on a Verbatim DL I got the same problem & errors as you HatchetMan, in my case a Pio 109. LUK thought I got a bad disc, but I remain concerned that there's something ImgBurn doesn't like about either Pioneers or DL discs.

I use RecordNow 7.3 and the only coasters it's made for me have been owing to "pilot error".

[MOVIEGEEK]

Try ForceASPI drivers

[HatchetMan]

I hadn't had probs b4 or since. This may be 7.71GB, but I have burned up to 7.80GB, never a coaster. Just burned 7.65GB & a 7.68GB without any probs either (both ripped same way - with DVDDecrypter). No read errors on any of them. How could both RecordNow and ImgBurn get 94% and just decide to quit on Malcolm X but not on Hatari! or Fiddler on the Roof?