Jump to content

Sudden DL burning problem!


Scythe

Recommended Posts

Hey People,

 

Until yesterday IMGBURN worked like a charm, but suddenly, when trying go burn a Philips Double Layer dvd for an xbox360 game, it acts weird.

First, after selecting the file, the dvd in the drive starts spinning and stopping minutes long. I also got a I/0 error, and something with invalid field parameters. yeah I know, Verbatim dvd's are the best as I read in these forums, but these same Philips dvd's had no problem before! I use a LG burner.

 

Could the file be corrupted or is it something within IMGburn (oh yeah, I have the updated version, also uninstalled it and donwloaded again, no results)

 

Thans for your help.

 

Here's the log:

 

I 13:48:51 ImgBurn Version 2.3.2.0 started!

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

I 13:48:51 Total Physical Memory: 261.132 KB - Available: 58.364 KB

W 13:48:51 Drive F:\ (FAT32) does not support single files > 4 GB in size.

I 13:48:51 Initialising SPTI...

I 13:48:51 Searching for SCSI / ATAPI devices...

I 13:48:51 Found 1 CD-RW and 1 DVD±RW/RAM!

I 13:49:28 Operation Started!

I 13:49:28 Source File: D:\360Games\FlatOut.Ultimate.Carnage.PAL.XBOX360-FW\uitgepakt\fw-flatout.dvd

I 13:49:28 Source File Sectors: 3.697.696 (MODE1/2048)

I 13:49:28 Source File Size: 7.572.881.408 bytes

I 13:49:28 Source File Volume Identifier: XGD2DVD_NTSC

I 13:49:28 Source File Implementation Identifier: Sonic Scenarist 3.1

I 13:49:28 Source File File System(s): ISO9660; UDF (1.02)

I 13:49:28 Destination Device: [1:0:0] HL-DT-ST DVDRAM GSA-4163B A101 (X:) (ATA)

I 13:49:28 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 4x)

I 13:49:28 Destination Media Sectors: 3.827.520

I 13:49:28 Write Mode: DVD

I 13:49:28 Write Type: DAO

I 13:49:28 Write Speed: 2x

I 13:49:28 Link Size: Auto

I 13:49:28 Test Mode: No

I 13:49:28 BURN-Proof: Enabled

I 13:49:28 Optimal L0 Data Zone Capacity: 1.913.760

I 13:49:28 Optimal L0 Data Zone Method: Copied From Original Disc

I 13:53:21 Filling Buffer... (20 MB)

I 13:53:22 Writing LeadIn...

W 13:53:22 Failed to Write Sectors 32 - 63 - Invalid Address For Write

W 13:53:22 Retrying (1 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (2 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (3 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (4 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (5 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (6 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (7 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (8 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (9 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (10 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (11 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (12 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (13 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (14 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (15 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (16 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (17 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (18 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (19 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

W 13:53:22 Retrying (20 of 20)...

W 13:53:22 Retry Failed - Invalid Address For Write

E 13:53:25 Failed to Write Sectors 32 - 63 - Invalid Address For Write

E 13:53:25 Next Writable Address: 0

I 13:53:25 Synchronising Cache...

I 13:53:26 Closing Track...

Link to comment
Share on other sites

The software doesn't even really come into it. The drive is erroring out, not the program.

 

There's no magical cure for it, you just update the drives firmware and use discs that it likes.

 

If they're all failing now, *something* about them must be different and your drive just doesn't like it.

 

Remember that the brand name doesn't mean anything, it's the dye that's important and brands often use multiple dyes.

 

The one these philips discs are using is RICOHJPN-D01-67. There's nothing to say your last lot weren't using something different.

 

Drives do deteriorate over time too, not to mention getting dusty. So basically there are loads of reasons why the drive might work one minute and not the next. The software is just about the only constant thing. You could use it 3 million times and it'll perform exactly the same the first time as it would the 3 millionth.

 

btw, you really should consider getting some more RAM for that PC! It'll be running like a dog compared to how it could be.

Link to comment
Share on other sites

Thanks for the quick reply., but I found out my burner is working fine. As a test I burned an audio cd from mp3 using Nero7, all works well. Afterwards I tried Imgburn again, same problem occurs. It stoppes immediately at the beginning. It says Selecting L0 data zone settings or something. Also, I have to stop Imgburn with the CTRL-ALT-DEl taskthingy. And Nero doesn't accept the ISO's... oh well...

Link to comment
Share on other sites

CDs are easy to burn. As LIGHTNING says, your burner probably doesn't like the DL discs you're using. You're a bit behind with firmware updates - download and update from A101 to A106:

 

http://lgodd.lge.com/fwdrv/DVD-WRITER/GSA4163A106.exe

 

Firmware updates often improve burning for specific dyes, so you might find an improvement.

Link to comment
Share on other sites

I installed the software you linked to, it DID improve something: the dvd isn't spinning slow/fast anymore, but I still got the I/O error. After I clicked on Cancel a few times, Imgburn started to finalizethe dvd, even though it's empty...

Link to comment
Share on other sites

You answered yourself in post 1.

 

Buy some Verbatims - they'll be better. I run this exact drive and have not had a bad burn. No use flogging a dead horse.

 

Regards

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.