DVR-115D invalid address for write on 360 backup

vbimport

#1

I’ve been trying and trying, but I can’t for the life of me get this to work. I’ve just made 3 coasters of Verbatim DVD+R DL, and it would have been 4 if I hadn’t tried the internal burner on my other computer, a Macbook. However, the Matshita didn’t fail me, fortunately. The PC with the drives listed is an older one. The motherboard is a Gigabyte GA-7N400L1 with an Athlon XP 2600+. I’m running XP SP2.

I’ve tried to burn it on my old burner, a Pioneer DVR-110D, with no luck. It got a bit past the layer break (~50-60%) and then got an error. I thought it was the burner, as I’d been having it burn coasters of late, but I don’t use it very often so I’m not sure how long it’s been going on. I don’t have a log from the failed burn on the 110D.

Imagine my surprise as my brand new DVR-115D (stock firmware 1.13) also failed. I had just wired it up! Not one to give up, but not wanting to waste expensive discs, I sought out a firmware update. I found the 1.18 firmware and enabled riplock patch, bitsetting, flashing same version, and rpc1 using MediaCodeSpeedEdit. I flashed the new firmware successfully and rebooted. I still wasn’t game yet, so I tried a burn on the Matshita on the Macbook. That backup worked, so I decided to have another look at the 115D in the morning.

Fast forward to today. Not wanting a repeat, I defragmented my hard drives, as I read that it may have something to do with failed burns. I also made a new admin account to use for the burn. I logged out of my regular account into the new one for the 115D burn. This burn also failed.

One thing I noticed is the average write speed was a bit lower than the 2.4x I selected, something like 1.3x. Could this be causing the problems? All of the previous burns were also at 2.4x, including the one on the Matshita that ended up working. I’ve read that the newer Pioneer drives, including the 115D can burn DL at 4x with no ill effect, but I was worried about the faster associated data decay with higher burn rates.

I’m kind of at a loss here. I am beginning to suspect something else may be wrong, but I’m not sure how to tell. I’ll post my logs here, hopefully there’s something I’ve missed.

The ImgBurn log follows, and is attached. I hoped that retrying a lot might help at the end, that’s why there are so many. :stuck_out_tongue: Wishful thinking, I guess.

I 13:57:17 ImgBurn Version 2.4.1.0 started!

I 13:57:17 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 13:57:17 Total Physical Memory: 1,048,052 KB - Available: 724,192 KB

I 13:57:17 Initialising SPTI…

I 13:57:17 Searching for SCSI / ATAPI devices…

E 13:57:18 Failed to check for ImgBurn update!

I 13:57:18 Found 1 CD-RW, 1 DVD-ROM and 1 DVD±RW!

I 14:01:34 Operation Started!

I 14:01:34 Source File: C:\gta4-icon.dvd

I 14:01:34 Source File Sectors: 3,825,924 (MODE1/2048)

I 14:01:34 Source File Size: 7,835,492,352 bytes

I 14:01:34 Source File Volume Identifier: XGD2DVD_NTSC

I 14:01:34 Source File Volume Set Identifier: 34672923

I 14:01:34 Source File Implementation Identifier: Sonic Scenarist 3.1

I 14:01:34 Source File File System(s): ISO9660, UDF (1.02)

I 14:01:34 Destination Device: [1:0:0] PIONEER DVD-RW DVR-115D 1.18 (D:) (ATA)

I 14:01:34 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)

I 14:01:34 Destination Media Sectors: 4,173,824

I 14:01:34 Write Mode: DVD

I 14:01:34 Write Type: DAO

I 14:01:34 Write Speed: 2.4x

I 14:01:34 Link Size: Auto

I 14:01:34 Test Mode: No

I 14:01:34 OPC: No

I 14:01:34 BURN-Proof: Enabled

I 14:01:34 Optimal L0 Data Zone Capacity: 1,913,760

I 14:01:34 Optimal L0 Data Zone Method: Copied From Original Disc

I 14:01:58 Filling Buffer… (40 MB)

I 14:01:59 Writing LeadIn…

I 14:02:01 Writing Session 1 of 1… (1 Track, LBA: 0 - 3825923)

I 14:02:01 Writing Track 1 of 1… (MODE1/2048, LBA: 0 - 3825923)

I 14:02:01 Writing Layer 0… (LBA: 0 - 1913759)

I 14:22:00 Writing Layer 1… (LBA: 1913760 - 3825923)

W 14:29:14 Failed to Write Sectors 2582496 - 2582527 - Reason: Invalid Address For Write

W 14:29:14 Retrying (1 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (2 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (3 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (4 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (5 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (6 of 20)…

W 14:29:14 Retry Failed - Reason: Invalid Address For Write

W 14:29:14 Retrying (7 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (8 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (9 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (10 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (11 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (12 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (13 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (14 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (15 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (16 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (17 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (18 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (19 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:29:15 Retrying (20 of 20)…

W 14:29:15 Retry Failed - Reason: Invalid Address For Write

W 14:38:45 Retrying (21)…

W 14:38:45 Retry Failed - Reason: Invalid Address For Write

W 14:38:48 Retrying (22)…

W 14:38:48 Retry Failed - Reason: Invalid Address For Write

W 14:38:50 Retrying (23)…

W 14:38:50 Retry Failed - Reason: Invalid Address For Write

W 14:38:51 Retrying (24)…

W 14:38:51 Retry Failed - Reason: Invalid Address For Write

W 14:38:51 Retrying (25)…

W 14:38:51 Retry Failed - Reason: Invalid Address For Write

W 14:38:52 Retrying (26)…

W 14:38:52 Retry Failed - Reason: Invalid Address For Write

W 14:38:53 Retrying (27)…

W 14:38:53 Retry Failed - Reason: Invalid Address For Write

W 14:38:53 Retrying (28)…

W 14:38:53 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (29)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (30)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (31)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (32)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (33)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:54 Retrying (34)…

W 14:38:54 Retry Failed - Reason: Invalid Address For Write

W 14:38:55 Retrying (35)…

W 14:38:55 Retry Failed - Reason: Invalid Address For Write

W 14:38:55 Retrying (36)…

W 14:38:55 Retry Failed - Reason: Invalid Address For Write

W 14:38:55 Retrying (37)…

W 14:38:55 Retry Failed - Reason: Invalid Address For Write

W 14:38:56 Retrying (38)…

W 14:38:56 Retry Failed - Reason: Invalid Address For Write

W 14:38:56 Retrying (39)…

W 14:38:56 Retry Failed - Reason: Invalid Address For Write

W 14:38:56 Retrying (40)…

W 14:38:56 Retry Failed - Reason: Invalid Address For Write

W 14:38:57 Retrying (41)…

W 14:38:57 Retry Failed - Reason: Invalid Address For Write

W 14:38:57 Retrying (42)…

W 14:38:57 Retry Failed - Reason: Invalid Address For Write

W 14:38:57 Retrying (43)…

W 14:38:57 Retry Failed - Reason: Invalid Address For Write

W 14:38:57 Retrying (44)…

W 14:38:57 Retry Failed - Reason: Invalid Address For Write

W 14:38:57 Retrying (45)…

W 14:38:57 Retry Failed - Reason: Invalid Address For Write

W 14:38:58 Retrying (46)…

W 14:38:58 Retry Failed - Reason: Invalid Address For Write

W 14:38:58 Retrying (47)…

W 14:38:58 Retry Failed - Reason: Invalid Address For Write

W 14:38:58 Retrying (48)…

W 14:38:58 Retry Failed - Reason: Invalid Address For Write

W 14:38:59 Retrying (49)…

W 14:38:59 Retry Failed - Reason: Invalid Address For Write

W 14:38:59 Retrying (50)…

W 14:38:59 Retry Failed - Reason: Invalid Address For Write

W 14:38:59 Retrying (51)…

W 14:38:59 Retry Failed - Reason: Invalid Address For Write

W 14:38:59 Retrying (52)…

W 14:38:59 Retry Failed - Reason: Invalid Address For Write

W 14:39:00 Retrying (53)…

W 14:39:00 Retry Failed - Reason: Invalid Address For Write

W 14:39:00 Retrying (54)…

W 14:39:00 Retry Failed - Reason: Invalid Address For Write

W 14:39:01 Retrying (55)…

W 14:39:01 Retry Failed - Reason: Invalid Address For Write

E 14:39:03 Failed to Write Sectors 2582496 - 2582527 - Reason: Invalid Address For Write

I 14:39:03 Synchronising Cache…

W 14:39:21 User opted to skip the ‘Close Track/Session/Disc’ functions.

E 14:39:21 Failed to Write Image!

I 14:39:21 Exporting Graph Data…

I 14:39:21 Graph Data File: C:\Documents and Settings emp\Application Data\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-115D_1.18_FRIDAY-MAY-09-2008_2-01_PM_MKM-001-00_2.4x.ibg

I 14:39:21 Export Successfully Completed!

E 14:39:21 Operation Failed! - Duration: 00:37:47

I 14:39:21 Average Write Rate: 2,325 KB/s (1.7x) - Maximum Write Rate: 3,360 KB/s (2.4x)


#2

@ aspeno,

Welcome to the Forum.

For both the Pioneer DVR-110D and the Pioneer DVR-115D to function are operate correctly requires the use of an Ultra DMA (80-Conductor) IDE/ATA Cable (http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.html) and operate in the Ultra DMA Mode 4 (http://club.cdfreaks.com/f61/troubleshooting-enabling-checking-dma-windows-vista-xp-2000-me-9x-101616/). You might be using the required Ultra DMA (80-Conductor) IDE/ATA Cable and have both your Pioneer DVR-110D and the Pioneer DVR-115D operating in the Ultra DMA Mode 4 but unfortunately from the information provided in your initial posting thread it is unknown if you are but these are areas to check.

Regards,
bjkg


#3

I’ve checked out the properties in Device Manager and it’s running in Ultra DMA 4.

Also, I should have mentioned that the discs used are Verbatim +R DLs made in Singapore, so they probably aren’t the culprit.


#4

[QUOTE=aspeno;2053887]I’ve been trying and trying, but I can’t for the life of me get this to work. I’ve just made 3 coasters of Verbatim DVD+R DL, and it would have been 4 if I hadn’t tried the internal burner on my other computer, a Macbook. However, the Matshita didn’t fail me, fortunately. The PC with the drives listed is an older one. The motherboard is a Gigabyte GA-7N400L1 with an Athlon XP 2600+. I’m running XP SP2.

I 13:57:17 ImgBurn Version 2.4.1.0 started!

I 13:57:17 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 13:57:17 Total Physical Memory: 1,048,052 KB - Available: 724,192 KB

I 13:57:17 Initialising SPTI…

I 13:57:17 Searching for SCSI / ATAPI devices…

E 13:57:18 Failed to check for ImgBurn update!

I 13:57:18 Found 1 CD-RW, 1 DVD-ROM and 1 DVD±RW!

I 14:01:34 Operation Started!

I 14:01:34 Source File: C:[B]gta4-icon.dvd[/B]

I 14:01:34 Source File Sectors: 3,825,924 (MODE1/2048)

I 14:01:34 Source File Size: 7,835,492,352 bytes

I 14:01:34 Source File Volume Identifier: XGD2DVD_NTSC

I 14:01:34 Source File Volume Set Identifier: 34672923

I 14:01:34 Source File Implementation Identifier: Sonic Scenarist 3.1

I 14:01:34 Source File File System(s): ISO9660, UDF (1.02)

I 14:01:34 Destination Device: [1:0:0] PIONEER DVD-RW DVR-115D 1.18 (D:) (ATA)

I 14:01:34 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)

I 14:01:34 Destination Media Sectors: 4,173,824

I 14:01:34 Write Mode: DVD

I 14:01:34 Write Type: DAO

I 14:01:34 Write Speed: 2.4x

[/QUOTE]

The only thing you really get as an answer is: :cop:

What reveals google about “your” image file??

Here is the answer!