Random write errors/aborts with 7260S

vbimport

#1

Hi,

some time ago i rebuilt my main pc (amd x4, 890GX chipset) and while at it, also bought a new 7260S after reading its fairly good review.
so far everything looked fine - i didnt burn a lot at first.
now that i tried burning a bunch of DVD’s i am having random but regular aborts.

i was using nero 8 originally, but switched to nero 9 meanwhile which didnt have any influence on the errors.
i am also using verbatim DVD+R (both printable and standard labelled) for ages and never had any issues.

as for the actual errors: when burinng Video DVDs, nero just stops randomly saying something about an scsi command that couldnt be performed.
the log file generated after such an aborted burn shows

17:59:15 #25 Text 0 File DVDR.cpp, Line 6267
Drive: Optiarc DVD RW AD-7260S
Book Type request [NEC]: DVD-ROM, write to RAM
select Book Type setting from RAM
Changing the Book Type was finished successfully, return code 0

17:59:15 #26 CDR -1211 File DVDR.cpp, Line 5965
Book Type set to: DVD-ROM

17:59:15 #27 Text 0 File DVDPlusRW.cpp, Line 637
Start write address at LBA 0
DVD high compatibility mode: Yes

17:59:15 #28 Text 0 File ThreadedTransfer.cpp, Line 273
Pipe memory size 83836800

18:03:45 #29 Text 0 File WriterStatus.cpp, Line 245
<H: Optiarc DVD RW AD-7260S> start writing Lead-Out at LBA 2286512 (22E3B0h), length 0 blocks

18:03:45 #30 SPTI -500 File SCSIPassThrough.cpp, Line 215
CdRom1: SCSIStatus(x00) WinError(1117) NeroError(-500)
CDB Data: 0x00 00 00 00 00 00 00 00 00 00 00 00
Sense Key: 0x00 (KEY_NO_SENSE)
Sense Code: 0x00
Sense Qual: 0x00
Sense Area: 0x00 00 00 00 00 00 00 00 00 00 00 00 00

18:03:45 #31 SPTI -1169 File SCSIPassThrough.cpp, Line 215
CdRom1: SCSIStatus(x02) WinError(0) NeroError(-1169)
CDB Data: 0x5B 01 06 00 00 00 00 00 00 00 00 00
Sense Key: 0x02 (KEY_NOT_READY)
Sense Code: 0x04
Sense Qual: 0x08
Sense Area: 0x70 00 02 00 00 00 00 0A 00 00 00 00 04 08 00 80

18:03:47 #32 Text 0 File DVDPlusRW.cpp, Line 904
EndDAO: Last written address 2286512

18:03:47 #33 Text 0 File DVDR.cpp, Line 6267
Drive: Optiarc DVD RW AD-7260S
Book Type request [NEC]: DVD-ROM, write to RAM
select Book Type setting from RAM
Changing the Book Type was finished successfully, return code 0

18:03:47 #34 CDR -500 File ThreadedTransferInterface.cpp, Line 1837
SCSI command aborted
H: Optiarc DVD RW AD-7260S

18:03:47 #35 TRANSFER -24 File ThreadedTransferInterface.cpp, Line 1837
Could not perform end of Disc-at-once

18:03:47 #36 Text 0 File DVDPlusDualLayer.cpp, Line 1452
SetDriveCaps: Set LAST LBA of layer 1 to 0

18:03:47 #37 Phase 38 File dlgbrnst.cpp, Line 1802
Burn process failed at 20x (27.700 KB/s)

write speed isnt the cause since ive tried various speeds and the error also occured at 8x or 16x besides the “default” 20x it picks for verbatim.

they also occured with the stock 1.00 firmware as well as liggy and dees 1.01 “auto”.

any ideas? is it the burner or something about my board/sata setup? anything else i should supply to narrow down whats causing these VERY annoying write errors? ive already created a whole lot of coasters by now and i seriously want to get rid off the issue. the 7260s sounded like a good pick but i have lost most of my faith in it right now.
i can live with the odd coaster, but this drive produces 4-5 in a row right after burning 10+ just fine. pure oddness.

thanks in advance…


#2

Hi,
something i just noticed:
my new board has 2 separate sata interfaces.
1x 6-port interface as part of the amd chipset
1x 2-port so-called gigabyte sata 3.0 interface which seems to be a “rebadged” jmicron oem chip thing.

however, the DDU1681S and AD7260S both run on the gigabyte interface which i never installed the dedicated drivers for. the interface showed up as standard ahci 1.0 compliant sata controller.

after checking the motherboard manual i installed the related drivers from the supplied driver disk and it changed the interface to gigabyte now.

i’ll run some more tests to see if the issue still exists or if the dedicated driver was the reason.
meanwhile 1 more burn failed after 1 successful burn. the error occured right after starting the leadout again acording to the new log, which seems to be the only real thing these random failures have in common.

bye for now…