Welly Posted November 9, 2008 Posted November 9, 2008 Having burnt a number of discs with Dvd Decyprtor i started to get a verifying problem. I upgraded to IMGburn and still have the same problem. i'm using Phillips DVD-R and never had a problem till half way throuogh a 100 stack and it consistantly throws up the errors. I have upgrade firmware on the writer and i'm still none the wiser. Can any one help Disc burns fine, just won't verify I 11:18:41 Device Ready! I 11:18:42 Operation Started! I 11:18:42 Source Device: [1:0:0] TSSTcorp CDDVDW SH-S203D SB01 (E:) (ATA) I 11:18:42 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: MBI 01RG40) (Speeds: 4x, 6x, 8x, 12x, 16x) I 11:18:42 Image File: D:\Videos\Films\gts.nrg I 11:18:42 Image File Sectors: 2,280,304 (MODE1/2048) I 11:18:42 Image File Size: 4,670,062,592 bytes I 11:18:42 Image File Volume Identifier: ***** I 11:18:42 Image File Volume Set Identifier: 396910EAC696EF15 I 11:18:42 Image File Application Identifier: NERO BURNING ROM I 11:18:42 Image File Implementation Identifier: Nero I 11:18:42 Image File File System(s): ISO9660, UDF (1.02) I 11:18:42 Read Speed (Data/Audio): 8x / 8x I 11:18:42 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2280303) I 11:18:42 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2280303) W 11:20:24 Failed to Read Sector 69672 - Reason: Timeout on Logical Unit W 11:20:24 Sector 69672 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:20:41 Failed to Read Sector 69674 - Reason: Timeout on Logical Unit W 11:20:41 Sector 69674 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:20:52 Failed to Read Sector 69675 - Reason: Timeout on Logical Unit W 11:20:52 Sector 69675 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:21:02 Failed to Read Sector 69676 - Reason: Timeout on Logical Unit W 11:21:02 Sector 69676 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:21:16 Failed to Read Sector 69677 - Reason: Timeout on Logical Unit W 11:21:16 Sector 69677 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:21:26 Failed to Read Sector 69678 - Reason: Timeout on Logical Unit W 11:21:26 Sector 69678 maps to File: \VIDEO_TS\VTS_01_1.VOB W 11:22:10 Failed to Read Sector 69705 - Reason: Timeout on Logical Unit W 11:22:10 Sector 69705 maps to File: \VIDEO_TS\VTS_01_1.VOB The pop up error i recieve is: Scsi Status:0x02 Interpretation: Check condition CDB: 28 00 00 01 10 4B 00 00 01 00 Interpretation: Read (10) - sector: 69707 Sense Area: 70 00 04 00 00 00 00 0A 00 00 00 00 3E 02 00 00 00 00 Interpretation: Timeout on Logical Unit
LIGHTNING UK! Posted November 9, 2008 Posted November 9, 2008 Your drive is making duff burns and it then can't read back what it just wrote. What speed are you burning at? Try 8x or 12x. If all else fails, ditch the media and buy some Verbatim / Taiyo Yuden discs instead.
Welly Posted November 9, 2008 Author Posted November 9, 2008 Your drive is making duff burns and it then can't read back what it just wrote. What speed are you burning at? Try 8x or 12x. If all else fails, ditch the media and buy some Verbatim / Taiyo Yuden discs instead. Typically burn at 8x. 12x fails within a few minutes. Must have burnt 100+ dvds without fail without changing any settings so on that basis do you reckon it could be the burner itself? Its not that old
LIGHTNING UK! Posted November 9, 2008 Posted November 9, 2008 Try some Verb DVD+R or Taiyo Yuden DVD-R/DVD+R first before going down the 'is the drive broken?' route.
Welly Posted November 10, 2008 Author Posted November 10, 2008 Not had a chance to get any othe rmedia bar some Maxell's This is at 4x I 00:10:55 Operation Started! I 00:10:55 Source Device: [1:0:0] TSSTcorp CDDVDW SH-S203D SB01 (E:) (ATA) I 00:10:55 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: MBI 01RG40) (Speeds: 4x, 6x, 8x, 12x, 16x) I 00:10:55 Image File: D:***** I 00:10:55 Image File Sectors: 2,165,536 (MODE1/2048) I 00:10:55 Image File Size: 4,435,017,728 bytes I 00:10:55 Image File Volume Identifier: ****** I 00:10:55 Image File Volume Set Identifier: 3969BCF3C696430C I 00:10:55 Image File Application Identifier: NERO BURNING ROM I 00:10:55 Image File Implementation Identifier: Nero I 00:10:55 Image File File System(s): ISO9660, UDF (1.02) I 00:10:55 Read Speed (Data/Audio): 8x / 8x I 00:10:55 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2165535) I 00:10:55 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2165535) W 00:16:33 Miscompare at LBA: 904066, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:16:33 Device: 0xB7 W 00:16:33 Image File: 0xC0 W 00:16:33 Total Errors in Sector: 2,019 I 00:16:33 Verifying Sectors... W 00:16:34 Miscompare at LBA: 904067, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:16:34 Device: 0xBC W 00:16:34 Image File: 0xC5 W 00:16:34 Total Errors in Sector: 2,022 I 00:16:34 Verifying Sectors... W 00:16:55 Miscompare at LBA: 920578, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:16:55 Device: 0xCB W 00:16:55 Image File: 0xD4 W 00:16:55 Total Errors in Sector: 2,015 I 00:16:55 Verifying Sectors... W 00:16:57 Miscompare at LBA: 920579, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:16:57 Device: 0xD0 W 00:16:57 Image File: 0xD9 W 00:16:57 Total Errors in Sector: 2,017 I 00:16:57 Verifying Sectors... W 00:17:08 Miscompare at LBA: 938018, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:17:08 Device: 0xD1 W 00:17:08 Image File: 0xDA W 00:17:08 Total Errors in Sector: 2,016 I 00:17:08 Verifying Sectors... W 00:17:09 Miscompare at LBA: 938019, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:17:09 Device: 0xD6 W 00:17:09 Image File: 0xDF W 00:17:09 Total Errors in Sector: 2,018 I 00:17:09 Verifying Sectors... W 00:17:22 Miscompare at LBA: 977250, Offset: 7, File: \VIDEO_TS\VTS_01_2.VOB W 00:17:22 Device: 0x92 W 00:17:22 Image File: 0x9C W 00:17:22 Total Errors in Sector: 2,018 I 00:17:22 Verifying Sectors...
Welly Posted November 10, 2008 Author Posted November 10, 2008 Just knocked out a clean burn and verify using a maxell at 4x but can't get it to do it again using the same image
Welly Posted November 27, 2008 Author Posted November 27, 2008 Really starting to annoy me now. Have brought a new burner. Reformatted my system Changed media to Verbatim Still won't verify. Any help?
volvofl10 Posted November 27, 2008 Posted November 27, 2008 post a log file from the new drive with the new verbatims please
Welly Posted November 28, 2008 Author Posted November 28, 2008 I 00:54:25 ImgBurn Version 2.4.2.0 started! I 00:54:25 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3) I 00:54:25 Total Physical Memory: 3,602,860 KB - Available: 3,068,268 KB I 00:54:25 Initialising SPTI... I 00:54:25 Searching for SCSI / ATAPI devices... I 00:54:25 Found 2 DVD
Cynthia Posted November 28, 2008 Posted November 28, 2008 There is a SB02 version of the firmware. http://www.samsungodd.com/Eng/Firmware/FWD...earchWord=s223f How is the SATA writer attached? Tried to use another SATA connection on the mother board? Tried to run a test of the RAM?
Welly Posted November 28, 2008 Author Posted November 28, 2008 Firmware now upgraded. I do have another burner that is already up on SB02 with the same problem Both connected to the MB directly using normal cables. (MB is a GB S series if thats any help) RAM checks fine with WMD (Windows Mem Diag)
dontasciime Posted November 28, 2008 Posted November 28, 2008 Firmware now upgraded.I do have another burner that is already up on SB02 with the same problem Both connected to the MB directly using normal cables. (MB is a GB S series if thats any help) RAM checks fine with WMD (Windows Mem Diag) Also check memory with memtest+ the windows one passed a known stick of broken memory in a few systems my mate built
Welly Posted November 29, 2008 Author Posted November 29, 2008 Do you know the model of the GB MB? I do it's a GA-M68SM-S2 This one Running a AMD dual core With 4 gig of ram. I have only just plugged in the stick strip and tried with different variations of single strip, two sticks and swapped locations etc. This is the thing that bugging me, it always worked fine then one day it just went tits up.
Welly Posted November 29, 2008 Author Posted November 29, 2008 (edited) As it happens i was doing some googling last night and decided to remove the Nvida PCI drivers and seems to have done the trick. *Edit* no it hasnt Edited November 29, 2008 by Welly
Recommended Posts