Flawless115 Posted March 10, 2006 Posted March 10, 2006 (edited) I bought my PC about one year ago and have backed up several DVDs fine up to this point, even the "hard-to-back-up" DVDs that other people have had trouble with. However, within the past week, I have had error messages come up while burning an image from two different movies. When I use CloneDVD, the message I get says that the media is bad and that I should change the media and try again. I have included an ImgBurn log from the latest disc I tried to back up. Any help with this problem is greatly appreciated. I 12:17:04 ImgBurn Version 1.2.0.0 started! I 12:17:04 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 12:17:04 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 12:17:04 Initialising ASPI... I 12:17:04 WNASPI32.DLL - Adaptec's ASPI Layer - ASPI for Win32 (95/NT) DLL - Version 4.6.0.1021 I 12:17:04 Searching for SCSI / ATAPI devices... I 12:17:04 Found 10 DVD-ROMs and 1 DVD?RW! I 12:17:29 Operation Started! I 12:17:29 Source File: C:\Documents and Settings\My Documents\VAREKAI.ISO I 12:17:29 Source File Sectors: 2,142,230 (MODE1/2048) I 12:17:29 Source File Size: 4,387,287,040 bytes I 12:17:29 Source File Application Identifier: ELBY CLONEDVD I 12:17:29 Source File Implementation Identifier: ELABORATE BYTES I 12:17:29 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 CD21 (E:) (ATA) I 12:17:29 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 12:17:29 Destination Media Sectors: 2,295,104 I 12:17:29 Write Mode: DVD I 12:17:29 Write Type: DAO I 12:17:29 Write Speed: 8x I 12:17:29 Link Size: Auto I 12:17:29 Test Mode: No I 12:17:29 BURN-Proof: Enabled I 12:17:29 Filling Buffer... I 12:17:30 Writing LeadIn... I 12:19:49 Writing Image... W 12:20:12 Failed to Write Sectors 24992 - 25023 - Write Error W 12:20:12 Retrying (1 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (2 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (3 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (4 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (5 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (6 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (7 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (8 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (9 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (10 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (11 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (12 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (13 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (14 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (15 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (16 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (17 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (18 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (19 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (20 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write E 12:20:24 Failed to Write Sectors 24992 - 25023 - Write Error I 12:20:24 Synchronising Cache... I 12:20:25 Closing Track... I 12:20:31 Finalising Disc... E 12:20:54 Failed to Write Image! E 12:20:59 Operation Failed! - Duration: 00:03:25 I 12:20:59 Average Write Rate: 1,470 KB/s (1.1x) - Maximum Write Rate: 3,324 KB/s (2.4x) Edited March 24, 2006 by Flawless115
Kenadjian Posted March 10, 2006 Posted March 10, 2006 Two quick suggestions. 1 any reason why you are using ASPI instead of SPTI? 2 Have you tried a different brand of media? Also, you might want to update your firmware, the latest is GD30, here is the link. http://forum.rpc1.org/dl_firmware.php?cate...4&manufactor=24 Oh, last but not least, check your DMA settings.
cornholio7 Posted March 10, 2006 Posted March 10, 2006 W 12:17:04 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! have you disabled it?
Flawless115 Posted March 10, 2006 Author Posted March 10, 2006 W 12:17:04 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! have you disabled it? Yeah, it's disabled.
Flawless115 Posted March 10, 2006 Author Posted March 10, 2006 Two quick suggestions. 1 any reason why you are using ASPI instead of SPTI? 2 Have you tried a different brand of media? Also, you might want to update your firmware, the latest is GD30, here is the link. http://forum.rpc1.org/dl_firmware.php?cate...4&manufactor=24 Oh, last but not least, check your DMA settings. I suppose there is no particular reason I'm using ASPI as opposed to SPTI. I'll try that. As far as the media, this is the same media I've been using for the past year and it's worked well--I haven't had any problems up to this point. I considered updating my firmware, but I've read that unless you know what you're doing, you may potentially damage the drive. The last thing I want to do is have to go and buy a new DVD Writer. As far as the DMA settings, DMA is enabled.
Flawless115 Posted March 10, 2006 Author Posted March 10, 2006 (edited) I changed the I/O setting from ASPI to SPTI and I still got the same error as before (log shown below) along with the following window: Also, I tried to upgrade my firmware, and for some reason, when I tried to execute the gd30.exe file, it wouldn't execute. I 17:24:36 ImgBurn Version 1.2.0.0 started! I 17:24:36 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 17:24:36 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 17:24:36 Initialising SPTI... I 17:24:36 Searching for SCSI / ATAPI devices... I 17:24:36 Found 10 DVD-ROMs and 1 DVD?RW! I 17:25:20 Operation Started! I 17:25:20 Source File: C:\Documents and Settings\My Documents\VAREKAI.ISO I 17:25:20 Source File Sectors: 2,142,230 (MODE1/2048) I 17:25:20 Source File Size: 4,387,287,040 bytes I 17:25:20 Source File Application Identifier: ELBY CLONEDVD I 17:25:20 Source File Implementation Identifier: ELABORATE BYTES I 17:25:20 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 CD21 (E:) (ATA) I 17:25:20 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 17:25:20 Destination Media Sectors: 2,295,104 I 17:25:20 Write Mode: DVD I 17:25:20 Write Type: DAO I 17:25:20 Write Speed: 8x I 17:25:20 Link Size: Auto I 17:25:20 Test Mode: No I 17:25:20 BURN-Proof: Enabled I 17:25:20 Filling Buffer... I 17:25:20 Writing LeadIn... I 17:26:37 Writing Image... W 17:26:46 Failed to Write Sectors 7040 - 7071 - Write Error W 17:26:46 Retrying (1 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (2 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (3 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (4 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (5 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (6 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (7 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (8 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (9 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (10 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (11 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (12 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (13 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (14 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (15 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (16 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (17 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (18 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (19 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (20 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write E 17:27:23 Failed to Write Sectors 7040 - 7071 - Write Error I 17:27:23 Synchronising Cache... I 17:27:24 Closing Track... Edited March 24, 2006 by Flawless115
Kenadjian Posted March 11, 2006 Posted March 11, 2006 As far as the media, this is the same media I've been using for the past year and it's worked well--I haven't had any problems up to this point.Did you just recently buy a new batch? Have you burnt any out of the current successfully? If not, please humour me and try something else. As far as the DMA settings, DMA is enabled. Not that I don't believe you, but how did you confirm this? Are the buffers full when it fails to write? Questions questions questions.
LIGHTNING UK! Posted March 11, 2006 Posted March 11, 2006 I realise the 'Write Speed' is low (going by the log), but I don't think enough data has been burnt to confirm that a DMA problem. The program has barely started burning when it errors out. If the firmware update didn't fix anything, buy some different / better discs. The ones you're running are not very good. On top of that, they're really 16x discs and your drive is limiting to 12x at best. That should tell you something.
Flawless115 Posted March 11, 2006 Author Posted March 11, 2006 As far as the media, this is the same media I've been using for the past year and it's worked well--I haven't had any problems up to this point. Did you just recently buy a new batch?Have you burnt any out of the current successfully? If not, please humour me and try something else. As a matter of fact, it is a new batch. As far as whether I've been able to burn any successfully, probably only one. I'll try another batch. Should I move to a different brand? Or should I continue to buy the same kind in hopes that it is just a bad batch that I bought? As far as the DMA settings, DMA is enabled. Not that I don't believe you, but how did you confirm this?To confirm that DMA is enabled I went to the following window. Are the buffers full when it fails to write? No, the buffers are pretty clean. Questions questions questions.
LIGHTNING UK! Posted March 11, 2006 Posted March 11, 2006 Get some totally different discs. Buy them online somewhere and find some with a decent DYE (i.e. don't go by the name on them alone). Look for Taiyo Yuden or MCC (often branded by verbatim). You can also pretty much ignore that DMA box, it means nothing. You can read more about that in the FAQ.
Flawless115 Posted March 15, 2006 Author Posted March 15, 2006 (edited) All, I did some "testing" and here's what I came up with. First of all, I managed to successfully upgrade my firmware to GD30. I read somewhere that you can't upgrade firmware while virtual drives are enabled. I disabled all of my virtual drives and the firmware upgrade worked fine. To rule out the possibility that my dilemma was firmware-related, I tried to burn another image. This time ImgBurn managed to burn 14% before bombing out like before. Therefore, although the image wasn't completely recorded, I did manage to get further along. Here's the log: I 19:00:59 ImgBurn Version 1.2.0.0 started! I 19:00:59 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 19:00:59 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 19:00:59 Initialising SPTI... I 19:00:59 Searching for SCSI / ATAPI devices... I 19:01:00 Found 1 DVD-ROM and 1 DVD?RW! I 19:02:06 Operation Started! I 19:02:06 Source File: C:\MUMMY43.ISO I 19:02:06 Source File Sectors: 2,141,504 (MODE1/2048) I 19:02:06 Source File Size: 4,385,800,192 bytes I 19:02:06 Source File Implementation Identifier: DVD Shrink I 19:02:06 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 GD30 (E:) (ATA) I 19:02:06 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 19:02:06 Destination Media Sectors: 2,295,104 I 19:02:06 Write Mode: DVD I 19:02:06 Write Type: DAO I 19:02:06 Write Speed: 8x I 19:02:06 Link Size: Auto I 19:02:06 Test Mode: No I 19:02:06 BURN-Proof: Enabled I 19:02:06 Filling Buffer... I 19:02:10 Writing LeadIn... W 19:04:28 Failed to Write Sectors 0 - 31 - Power Calibration Area Is Full W 19:04:28 Retrying (1 of 20)... W 19:05:03 Retry Failed - Session Fixation Error Writing Lead In W 19:05:03 Retrying (2 of 20)... I 19:05:21 Writing LeadIn... I 19:05:22 Writing Image... W 19:08:59 Failed to Write Sectors 314528 - 314559 - Write Error W 19:09:00 Retrying (1 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (2 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (3 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (4 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (5 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (6 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (7 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (8 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (9 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (10 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (11 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (12 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (13 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (14 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (15 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (16 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (17 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (18 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (19 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (20 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:14 Retrying (21)... W 19:09:14 Retry Failed - Invalid Address For Write E 19:09:17 Failed to Write Sectors 314528 - 314559 - Write Error I 19:09:17 Synchronising Cache... I 19:09:18 Closing Track... I 19:09:28 Finalising Disc... E 19:10:09 Failed to Write Image! E 19:10:10 Operation Failed! - Duration: 00:08:02 I 19:10:10 Average Write Rate: 2,688 KB/s (1.9x) - Maximum Write Rate: 3,326 KB/s (2.4x) Secondly, I went back and check some of my previously-burned discs that were successful (these were discs from prior batches, not the current batch of discs). DVD Decrypter gives the Disc ID of the disc upon insertion, and as it turned out, the previous discs were Taiyo Yudens (see example below under Disc ID). Here's the tricky part. I checked the very last successful burn I had (the first disc out of the current batch) and it had a Disc ID of RITEK-R03-02 (like the one used above in the log). This was the only successful burn I had out of the current batch of RITEKs. Therefore, my conclusion is this: the successful RITEK burn was purely coincidental since every single RITEC disc I've used up to this point has resulted in a coaster and all of the discs I used prior to this batch have all been Tayio Yudens and they've all burned "flawlessly." Up until now, I didn't know too much about Media ID's so I simply went to a local retailer (here in the U.S.) and bought a pack of Fujifilm DVD+R's thinking they were good discs since they were Fujifilm. This is a classic example of how brands make no difference. Once batch of Fujifilm discs could be RITEKs and another could be Tayio Yudens. I ordered a new batch of authentic Tayio Yudens today from the internet, so when they come, if my burner starts burning properly again, I suppose I can conclude that it was the media that was the root of the problem. What say you? Edited March 22, 2006 by Flawless115
lfcrule1972 Posted March 15, 2006 Posted March 15, 2006 I agree with LUK! above, that Media ID is not the best, I would be surprised if you had any problems with the Taiyo Yudens - I have been using the TYG02 dye for ages now and no issues at all on either my BenQ or my NEC burner.
Flawless115 Posted March 16, 2006 Author Posted March 16, 2006 (edited) OK, I'm completely baffled! I just got a fresh batch of TYs (YUDEN000-T02-00) today. I tried to re-burn one of the images that had failed before. I burned it at 8x and I still got the same problem. I reset the maximum writing speed on all of my burning applications to 4x. Then, I used CloneDVD to burn the same image (in File mode, not ISO) and it supposedly burned successfully (according to CloneDVD). When I tried to play the disc in my stand-alone players it didn't work. I wanted to try and back-up a completely different disc, so I created a new image and tried to burn it with ImgBurn at 4x (thinking that writing at 8x might have been the problem) and I keep getting the same type of error as before (I won't bother posting the log since it is, essentially, the same type of error that shows up). My question now is, has my burner seen its last days? I've read on other forums that the Philips 8631 has caused headaches for many people. They've been forced to call Dell and have the drive replaced. Up until this point, I've been pretty lucky, I suppose. HELP! Edited March 24, 2006 by Flawless115
polopony Posted March 17, 2006 Posted March 17, 2006 considering the Taiyo Yudens are failing if you can get a replacement burner for the one you have jump on it ,If you cant get a replacement buy a reputable drive NEC, Pioneer ,or a BenQ they supposedly are good these days and theres also Plextor to consider. For less than a $100 you can get a Plex and for the most part for less than $50 you can get a great drive .I have an NEC 3500 that I bought 2 -3 years ago and coupled with Yudens and Verbatim Mcc dye I cant remember the last time I burned a coaster. Its worth a couple of bucks to not have to deal with the headaches and frustration good luck
Flawless115 Posted March 17, 2006 Author Posted March 17, 2006 (edited) I've contacted Dell about my problem. After going through the loops they put you through, they're convinced its the medai and not the drive. Is YUDEN000-T02-00 media that bad of a media that I should have a bunch of coasters, cause that's what I'm getting? My burner can write CDs perfectly fine. Is that a sign that the burner works fine and it could be the media that's causing the problem? Edited March 17, 2006 by Flawless115
Kenadjian Posted March 17, 2006 Posted March 17, 2006 There is a good chance that your drive just doesn't like those discs, it's not because they are crap, it's just media/drive compatibility. I had simular problem with TYs with my LG4120 just did not like them. Swaped to verbs with MCC dye and my drive loves them, just the way it is.
Flawless115 Posted March 24, 2006 Author Posted March 24, 2006 (edited) Well, here's the long and short of it all (for those interested). A technician from DELL finally came out and replaced my Philips 8631 with a Philips 8701 (not exactly what I anticipated, but it's better than nothing). Thus far, I've burned seven different discs using three different media types (breakdown shown below) and all seven burns have been successful (using both ImgBurn and CloneDVD). Verbatim 16X DVD-R (MCC 03RG20) [1 disc burned] Verbatim 16X DVD+R (MCC-004-000) [4 discs burned] Taiyo Yuden 8X DVD+R (YUDEN000-T02-000) [2 disc burned] Therefore, my conclusion is the following: Although DELL support kept telling me that they believed it was the media that was causing the problem, I believe it was the drive. While I cannot prove my case beyond any doubt, the evidence is strongly in my favor. Edited March 24, 2006 by Flawless115
Recommended Posts