ninor Posted October 22, 2009 Share Posted October 22, 2009 (edited) Hi guys, I just wasted 5 Verbatim discs trying to back-up a dual layer DVD at 2.4x speed. Can you guys please tell me what am I doing wrong? I was on vacation for the last 2 weeks and prior to vacation I was able to back-up discs without any problems... I haven't changed anything on my computer since! Error log: I 21:13:38 ImgBurn Version 2.5.0.0 started! I 21:13:38 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 21:13:38 Total Physical Memory: 3,406,816 KB - Available: 2,956,840 KB W 21:13:38 Drive J:\ (FAT32) does not support single files > 4 GB in size. I 21:13:38 Initialising SPTI... I 21:13:38 Searching for SCSI / ATAPI devices... I 21:13:39 Found 1 DVD-ROM and 1 DVD±RW! I 21:14:22 Operation Started! I 21:14:22 Source File: removed I 21:14:22 Source File Sectors: 3,827,488 (MODE1/2048) I 21:14:22 Source File Size: 7,838,695,424 bytes I 21:14:22 Source File Volume Identifier: DVD_ROM I 21:14:22 Source File Volume Set Identifier: 356fc000MS UDFBridge I 21:14:22 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 21:14:22 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 21:14:22 Source File File System(s): ISO9660, UDF (1.50) I 21:14:22 Destination Device: [4:1:0] HL-DT-ST DVDRAM GH20NS15 IL00 (E:) (SCSI) I 21:14:23 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x) I 21:14:23 Destination Media Sectors: 4,173,824 I 21:14:23 Write Mode: DVD I 21:14:23 Write Type: DAO I 21:14:23 Write Speed: 2.4x I 21:14:23 Link Size: Auto I 21:14:23 Lock Volume: Yes I 21:14:23 Test Mode: No I 21:14:23 OPC: No I 21:14:23 BURN-Proof: Enabled I 21:14:23 Book Type Setting: DVD-ROM I 21:14:23 Optimal L0 Data Zone Capacity: 1,913,760 I 21:14:23 Optimal L0 Data Zone Method: Copied From Original Disc I 21:14:55 Set L0 Data Zone Capacity Succeeded! I 21:14:55 Filling Buffer... (40 MB) I 21:14:56 Writing LeadIn... I 21:14:58 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 21:14:58 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 21:14:58 Writing Layer 0... (LBA: 0 - 1913759) W 21:22:44 Failed to Write Sectors 724800 - 724831 - Reason: Power On, Reset, or Bus Device Reset Occurred W 21:22:44 Retrying (1 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (2 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (3 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (4 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (5 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (6 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (7 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (8 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (9 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (10 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (11 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (12 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (13 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (14 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (15 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (16 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (17 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (18 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (19 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:22:44 Retrying (20 of 20)... W 21:22:44 Retry Failed - Reason: Invalid Address For Write W 21:24:28 Retrying (21)... W 21:24:28 Retry Failed - Reason: Invalid Address For Write W 21:24:29 Retrying (22)... W 21:24:29 Retry Failed - Reason: Invalid Address For Write W 21:24:30 Retrying (23)... W 21:24:30 Retry Failed - Reason: Invalid Address For Write W 21:24:30 Retrying (24)... W 21:24:30 Retry Failed - Reason: Invalid Address For Write W 21:24:30 Retrying (25)... W 21:24:30 Retry Failed - Reason: Invalid Address For Write W 21:24:31 Retrying (26)... W 21:24:31 Retry Failed - Reason: Invalid Address For Write W 21:24:31 Retrying (27)... W 21:24:31 Retry Failed - Reason: Invalid Address For Write W 21:24:31 Retrying (28)... W 21:24:31 Retry Failed - Reason: Invalid Address For Write E 21:24:34 Failed to Write Sectors 724800 - 724831 - Reason: Power On, Reset, or Bus Device Reset Occurred E 21:24:34 Next Writable Address: 724752 I 21:24:34 Synchronising Cache... W 21:24:37 User opted to skip the 'Close Track/Session/Disc' functions. E 21:24:37 Failed to Write Image! I 21:24:37 Exporting Graph Data... I 21:24:37 Graph Data File: C:\Documents and Settings\Removed\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GH20NS15_IL00_TUESDAY-OCTOBER-20-2009_9-14_PM_MKM-001-00_2.4x.ibg I 21:24:37 Export Successfully Completed! E 21:24:37 Operation Failed! - Duration: 00:10:14 I 21:24:37 Average Write Rate: 2,516 KB/s (1.8x) - Maximum Write Rate: 3,360 KB/s (2.4x) Disc info HL-DT-ST DVDRAM GH20NS15 IL00 (SCSI) Current Profile: DVD+R DL Disc Information: Status: Incomplete Erasable: No Sessions: 1 Free Sectors: 3,548,752 Free Space: 7,267,844,096 bytes Free Time: 788:38:52 (MM:SS:FF) Supported Write Speeds: 2.4x, 4x DVD±R DL Boundary Information: L0 Data Zone Capacity: 1,913,760 Changeable: No Disc Control Blocks Information: HL-DT-ST 0NS15 Physical Format Information (Last Recorded): [b]Disc ID: MKM-001-00[/b] Book Type: DVD+R DL Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 2 Track Path: Opposite Track Path (OTP) Linear Density: 0.293 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 16,580,607 Last Physical Sector in Layer 0: 2,110,367 Performance (Write Speed): Descriptor 1... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 3827519 (0x003A673F) -> RS: 6,853 KB/s (5.1x) - WS: 3,324 KB/s (2.4x) Descriptor 2... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 3827519 (0x003A673F) -> RS: 6,853 KB/s (5.1x) - WS: 5,540 KB/s (4x) Edited October 22, 2009 by ninor Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 22, 2009 Share Posted October 22, 2009 It's probably due to the controller your drive is attached to and bad drivers. Which one is your drive connected to exactly? Intel, nvidia etc? Link to comment Share on other sites More sharing options...
ninor Posted October 22, 2009 Author Share Posted October 22, 2009 It's probably due to the controller your drive is attached to and bad drivers. Which one is your drive connected to exactly? Intel, nvidia etc? My mobo is Asus P5Q Pro which is Socket775 Intel P45 chipset. I don't see how drivers could be bad as I didn't change anything from when I was able to successfully burn back-ups. I did re-install the firmware for my burner and I still get the same error. Should I try plugging my burner into different port on mobo? Or anything else I could do? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 22, 2009 Share Posted October 22, 2009 I know you don't see how they could be bad but you might have just been lucky before. Your system is performing a bus reset, that's not something that happens under normal circumstances. So which controller is the drive actually on? My guess is that you put it on the silicon image controller. Use the intel one and make sure you have the latest Intel Matrix drivers installed (only applies if the bios is configured of ahci or raid mode). Don't forget to do mobo bios updates too. Link to comment Share on other sites More sharing options...
ninor Posted October 22, 2009 Author Share Posted October 22, 2009 I know you don't see how they could be bad but you might have just been lucky before. Your system is performing a bus reset, that's not something that happens under normal circumstances. So which controller is the drive actually on? My guess is that you put it on the silicon image controller. Use the intel one and make sure you have the latest Intel Matrix drivers installed (only applies if the bios is configured of ahci or raid mode). Don't forget to do mobo bios updates too. I'll try that tonight when I get home. Thanks for your help. But what is a bus reset? I did notice that when imgburn fails, computer freezes and mouse stops moving... I also noticed this happens every couple of minutes. Link to comment Share on other sites More sharing options...
ninor Posted October 24, 2009 Author Share Posted October 24, 2009 Lighting... you are my hero man! My burner was plugged into the silicon controller and after plugging it into Intel controller and updating BIOS, I just successfully burnt a disc! Thanks a lot man! Link to comment Share on other sites More sharing options...
Recommended Posts