Tech Support > Computer Hardware > CD/DVD > Burn fails at 17% almost everytime - WHY!!!
Burn fails at 17% almost everytime - WHY!!!
Posted by Charlie Foster on April 4th, 2004


Greetings,

I am having problems with DVD burning using Nero 6.3.1.6. Almost everytime
I burn a backup copy of a DVD with Nero Recode 2, the process will fail at
17%. This has happened with 2 burners (Plextor 708A & Pioneer A-07U). At
first I thought it was the Plextor, so I got the Pioneer and the same thing
happens, failing at 17%. I went as far a reformatting the harddrive
(thinking a well hidden virus) and reinstalling everything. The first 2
burns went OK, then the dreaded 17% fail. I tried the Plextor with firmware
1.03, 1.04, and 1.06. The Pioneer came with firmware 1.09 (Feb 2004
manufacture date). I used various media, Memorex, TDK, and Princo discs.
The burn set at 2x. The temp video file folder is on the same drive as the
program. File system is NTFS. I have another computer using the same Nero
program with a Pioneer A-06U and have had not 1 failure. I don't know what
is happening or what is causing the failure.

Any help or suggestions greatly appreciated,

Charlie

Here is an excerpt from the log file:

3:29:31 PM #19 Phase 36 File APIProgress.cpp, Line 266
Burn process started at 2x (2,770 KB/s)

3:29:31 PM #20 Text 0 File ThreadedTransferInterface.cpp, Line 2342
Verifying disc position of item 0 (relocatable, disc pos, no patch infos,
orig at #0): write at #0

3:29:31 PM #21 Text 0 File DVDR.cpp, Line 1619
Recording mode: Sequential Recording Mode

3:29:31 PM #22 Text 0 File Mmc.cpp, Line 19864
Set BUFE: supported -> ON

3:29:31 PM #23 Text 0 File DVDR.cpp, Line 1760
Start write address at LBA 0

DVD high compatibility mode: No

3:29:31 PM #24 Text 0 File Cdrdrv.cpp, Line 8002

---- DVD Structure: Physical Format Information (00h) ----

Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050

Book Type: DVD-R (2), Part Version: 5

Disc Size: 120 mm, Maximum Rate: 10.08 Mbps (2 h)

Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer
Type: recordable

Linear Density: 0,267 um/bit, Track Density: 0,74 um/track

Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW,
DVD+R/+RW)

End Physical Sector Number of Data Area: 0 h

End Sector Number in Layer 0: 0 h

Data in Burst Cutting Area (BCA) does not exist

Start sector number of the current Border-Out: 0 h

Start sector number of the next Border-In: 0 h

Media Specific [16..63]:

00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................



3:29:33 PM #25 Text 0 File Cdrdrv.cpp, Line 1289
15:29:33.828 - PIONEER DVD-RW DVR-107D\H1 T0 : Queue again later

3:30:25 PM #26 Text 0 File Cdrdrv.cpp, Line 1289
15:30:25.421 - PIONEER DVD-RW DVR-107D\H1 T0 : Queue again later

3:51:13 PM #27 SCSI -1064 File Cdrdrv.cpp, Line 1437
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x03810000

Status: 0x04 (0x01, SCSI_ERR)

HA-Status 0x00 (0x00, OK)

TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)

Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)

Sense Code: 0x21

Sense Qual: 0x02

CDB Data: 0x2A 0x00 0x00 0x05 0x16 0x00 0x00 0x00 0x20 0x00 0x00 0x00

Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0E

0x00 0x00 0x00 0x00 0x21 0x02

3:51:13 PM #28 CDR -1064 File Writer.cpp, Line 304
Invalid block address

3:51:13 PM #29 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion

3:51:13 PM #30 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader

3:51:14 PM #31 Text 0 File DVDR.cpp, Line 1970
EndDAO: Last written address was 333311

3:51:14 PM #32 Phase 38 File APIProgress.cpp, Line 266
Burn process failed at 2x (2,770 KB/s)

3:51:14 PM #33 Text 0 File AudioCompilationImpl.cpp, Line 828
DRM: DRM burn session terminated.

3:51:14 PM #34 Text 0 File AudioCompilationImpl.cpp, Line 857
DRM: Closing entire DRM handling. Bye.


Existing drivers:

File 'Drivers\CDRALW2K.SYS': Ver=5.3.5.10, size=23436 bytes, created
4/1/2004 2:43:54 PM

File 'Drivers\ASPI32.SYS': Ver=4.71 (0001), size=17005 bytes, created
8/14/2002 4:03:36 PM


Registry Keys:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs :
0 (Security Option)

15:51:15 File NeroRecorder.cpp, Line 3072
Disc info:

15:51:15 File burn_dvdfiles.cpp, Line 304
Compile DVD: exit



Posted by Thomas A. Horsley on April 4th, 2004


Sounds like the problems I used to have on my old motherboard.
I think some chipsets just don't work well with DVD burning
for some reason.

My old board was an abit KT7A-RAID (dvd would never work), my
new one is an asus P4C800-E (same OS, same software, same DVD
burner - works flawlessly).
--
<URL:http://home.att.net/~Tom.Horsley> Free Software and Politics <<==+

Posted by Charlie Foster on April 4th, 2004


Thanks for the input. My Mobo is an ASUS P4PE raid 533fsb P4 2.53Mhz
processor 512mb ram, XP Pro. The other machine that works flawlessly is an
ASUS A7V8X 400fsb, Athlon XP2200 clocked at 1.800Mhz, 512mb ram, XP Home.
Anti-virus is diabled.

Maybe this info should have been included and may be of some help.

Charlie


"Thomas A. Horsley" <tom.horsley@att.net> wrote in message
news:ulllbie7e.fsf@att.net...


Posted by Kapitan Klink on April 5th, 2004


tom.horsley@att.net (Thomas A. Horsley) wrote in message news:<ulllbie7e.fsf@att.net>...
Those onboard RAID controllers are supposed to be a pain in the ass
sometimes.

I have heard stories of people with the KT133 / KT133A chipsets
getting problems after updating their VIA 4-in-1 drivers...

I have an non-RAID Abit kt7a (v1.3) and a BTC 1004 dvd writer, which
some people have called a problem drive, and I have not yet made a
coaster in approx 50 DVD burns, and many more DVD rewrites. I have
been buying random Verbatim, Intenso, Packard Bell, Ritek 4x DVD-R /
+R, 2.4x -RW and +RW media and they all work! They all play fine in my
standalone divx DVD player too. (Ellion DVX-520c).
I have yet to find any 4x DVD+RW media supported by this drive
however.

A lot of people on the BTC forum report having cured problems by
replacing Nvidia chipset drivers with stock Microsoft ones.

I hesitate to suggest obvious things such as not having the writer
sharing an ide channel with a hard drive, setting the drive to
udma/pio, master/slave etc...


Similar Posts