VideoHelp Forum




+ Reply to Thread
Results 1 to 19 of 19
  1. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Hey all,

    Lite-On LH-18A1P FW: GL0G
    Sys: AMD Sempron 2800 1.6ghz, 704mb ram, 100gb hd

    My burner all of a sudden has giving me two straight coasters, the first time it got to 97% then threw a write error, the second burn it went to 99% then gave me the same write error. Not sure what is causing problems, although have been getting memory errors lately when closing browsers, not sure if related. Appreciate any help. Anyways here is log files:


    Code:
    Windows XP 5.1
    IA32
    WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 11/20/2005 10:48:21 PM 
    ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 11/2/2004 1:54:32 PM 
    
    NT-SPTI used
    Nero Version: 6.6.1.4
    Internal Version: 6, 6, 1, 4d
    
    Recorder:             <LITE-ON DVDRW LH-18A1P>  Version: GL0G - HA 1 TA 0 - 6.6.1.4
     Adapter driver:      <IDE>                     HA 1
     Drive buffer  :      2048kB
     Bus Type      :      via Inquiry data (1) -> ATAPI, detected: ?
     Connected to MMC as unknown drive with class-nr : 1
     Drive is autodetected - recorder class: Std. MMC recorder
    CD-ROM:               <LITE-ON  DVDRW LH-18A1P  >Version: GL0G - HA 1 TA 0 - 6.6.1.4
     Adapter driver:      <IDE>                     HA 1
    
    === Scsi-Device-Map ===
    DiskPeripheral       : MDT MD1000BB-00CAA1              atapi Port 0 ID 0  DMA: Off
    CdRomPeripheral      : LITE-ON DVDRW LH-18A1P           atapi Port 1 ID 0  DMA: On 
    DiskPeripheral       : Maxtor 6B250S0          BANC  viamraid Port 2 ID 0  DMA: Off
    
    === CDRom-Device-Map ===
    LITE-ON DVDRW LH-18A1P     F:   CDRom0
    =======================
    
    AutoRun : 1
    Excluded drive IDs: 
    WriteBufferSize: 83886080 (0) Byte
    ShowDrvBufStat : 0
    BUFE           : 0
    Physical memory     : 703MB (720368kB)
    Free physical memory: 164MB (168116kB)
    Memory in use       : 76 %
    Uncached PFiles: 0x0
    Use Inquiry    : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0) 
    
    21.3.2007
    UDF/ISO compilation
    10:18:52 AM	#1 Phase 112 File dlgbrnst.cpp, Line 1685
    	DVD-Video files reallocation started
    	
    10:18:52 AM	#2 Phase 114 File dlgbrnst.cpp, Line 1685
    	DVD-Video files reallocation completed (no file modified)
    	
    10:18:52 AM	#3 Text 0 File Isodoc.cpp, Line 6475
    	UDF document burn settings
    	------------------------------------------
    	Determine maximum speed : FALSE
    	Simulate                : FALSE
    	Write                   : TRUE
    	Finalize CD             : TRUE
    	Multisession            : FALSE
    	Burning mode            : DAO
    	Mode                    : 1
    	UDF Mode                : UDF/ISO bridge
    	UDF Options             : automatic
    	UDF Revision            : 1.02
    	UDF Partition Type      : physical
    	ISO Level               : 1 (Max. of 11 = 8 + 3 char)
    	Character set           : ISO 9660
    	Joliet                  : FALSE
    	Allow pathdepth more than 8 directories : TRUE
    	Allow more than 255 characters in path  : TRUE
    	Write ISO9660 ;1 file extensions        : TRUE
    	
    10:18:52 AM	#4 Phase 111 File dlgbrnst.cpp, Line 1685
    	DVD-Video files sorted
    	
    10:18:52 AM	#5 Text 0 File ThreadedTransfer.cpp, Line 531
    	ReadBuffer-Pipe got 262144KB of Memory
    	
    10:18:52 AM	#6 Text 0 File Reader.cpp, Line 124
    	Reader running
    	
    10:18:52 AM	#7 Text 0 File Writer.cpp, Line 122
    	Writer LITE-ON  DVDRW LH-18A1P   running
    	
    10:18:52 AM	#8 ISO9660GEN -11 File geniso.cpp, Line 3312
    	First writeable address = 0 (0x00000000)
    	
    10:18:52 AM	#9 ISO9660GEN -11 File geniso.cpp, Line 3312
    	First writeable address = 0 (0x00000000)
    	
    10:18:52 AM	#10 Text 0 File Burncd.cpp, Line 3305
    	Turn on Disc-At-Once, using DVD media
    	
    10:18:53 AM	#11 Text 0 File DlgWaitCD.cpp, Line 281
    	Last possible write address on media:  2298495 (510:46.45, 4489MB)
    	Last address to be written:            2109295 (468:43.70, 4119MB)
    	
    10:18:53 AM	#12 Text 0 File DlgWaitCD.cpp, Line 293
    	Write in overburning mode: NO (enabled: CD)
    	
    10:18:53 AM	#13 Text 0 File DlgWaitCD.cpp, Line 2612
    	Recorder: LITE-ON DVDRW LH-18A1P, Media type: DVD-R
    	 Disc Manufacturer: RITEKF - 1
    	 Disc Application Code: 64, Disc Physical Code: 193
    	
    10:18:53 AM	#14 Text 0 File DlgWaitCD.cpp, Line 459
    	>>> Protocol of DlgWaitCD activities: <<<
    	=========================================
    	
    10:18:53 AM	#15 Text 0 File ThreadedTransferInterface.cpp, Line 847
    	Setup items (after recorder preparation)
    	 0: TRM_DATA_MODE1 ()
    	    2 indices, index0 (150) not provided
    	    original disc pos #0 + 2109296 (2109296) = #2109296/468:43.71
    	    relocatable, disc pos for caching/writing not required/ required, no patch infos
    	    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2109296 blocks [LITE-ON  DVDRW LH-18A1P]
    	--------------------------------------------------------------
    	
    10:18:53 AM	#16 Text 0 File ThreadedTransferInterface.cpp, Line 1059
    	Prepare recorder [LITE-ON  DVDRW LH-18A1P] for write in CUE-sheet-DAO
    	DAO infos:
    	==========
    	 MCN: ""
    	 TOCType: 0x00; Session Closed, disc fixated
    	 Tracks 1 to 1:
    	   1: TRM_DATA_MODE1, 2048/0x00, FilePos             0             0    4319838208, ISRC ""
    	DAO layout:
    	===========
    	 __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
    	       0 |  lead-in |   0 |    0x41 | 0x00
    	       0 |        1 |   0 |    0x41 | 0x00
    	       0 |        1 |   1 |    0x41 | 0x00
    	 2109296 | lead-out |   1 |    0x41 | 0x00
    	
    10:18:53 AM	#17 Text 0 File SCSIPassThrough.cpp, Line 38
    	SPTILockVolume - completed successfully for FCTL_LOCK_VOLUME
    	
    10:18:53 AM	#18 Text 0 File SCSIPassThrough.cpp, Line 83
    	SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME
    	
    10:18:53 AM	#19 Phase 24 File dlgbrnst.cpp, Line 1685
    	Caching of files started
    	
    10:18:53 AM	#20 Text 0 File Burncd.cpp, Line 4145
    	Cache writing successful.
    	
    10:18:53 AM	#21 Phase 25 File dlgbrnst.cpp, Line 1685
    	Caching of files completed
    	
    10:18:53 AM	#22 Phase 36 File dlgbrnst.cpp, Line 1685
    	Burn process started at 16x (22,160 KB/s)
    	
    10:18:53 AM	#23 Text 0 File ThreadedTransferInterface.cpp, Line 2685
    	Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0
    	
    10:18:53 AM	#24 Text 0 File DVDR.cpp, Line 2707
    	Recording mode: Sequential Recording Mode
    	
    10:18:53 AM	#25 Text 0 File DVDR.cpp, Line 2863
    	Start write address at LBA 0
    	DVD high compatibility mode: Yes
    	
    10:18:53 AM	#26 Text 0 File Cdrdrv.cpp, Line 8647
    	---- DVD Structure: Physical Format Information (00h) ----
    	Media Type: 0, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
    	 Book Type: DVD-R   (2), Part Version: 2.0x (5), Extended Part Version: 2.1 (33)
    	 Disc Size: 120 mm,      Maximum Rate: <not specified> (F 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:      26127F h
    	 End Sector Number in Layer 0:                 0 h (LBN: FFFD0000 h, 4193920 MB)
    	 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 60 00 10 20 30 40 50 - 00 00 00 21 00 00 00 00    .`...0@P...!....
    	      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    ................
    	
    10:19:35 AM	#27 Text 0 File Cdrdrv.cpp, Line 1200
    	10:19:35.421 - F: LITE-ON DVDRW LH-18A1P : Queue again later
    	
    10:25:06 AM	#28 SPTI -1135 File SCSIPassThrough.cpp, Line 289
    	F: CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1135)
    	Sense Key:  0x03 (KEY_MEDIUM_ERROR)
    	Sense Code: 0x0C
    	Sense Qual: 0x00
    	CDB Data:   0x2A 00 00 1F CB 20 00 00 20 00 00 00 
    	Sense Area: 0x70 00 03 00 00 00 00 0A 00 00 00 00 0C 
    	Buffer x04780000: Len x10000
    	0x00 00 01 BA 44 E2 BC E0 94 7F 01 89 C3 F8 00 00 
    	0x01 BD 07 EC 81 80 05 23 38 AF 65 3B 80 01 04 84 
    	0x65 E8 28 88 5D 46 44 2B 1C BA 65 9B 2B 6D 01 6F 
    	
    10:25:06 AM	#29 CDR -1135 File Writer.cpp, Line 311
    	Write error
    	F: LITE-ON DVDRW LH-18A1P
    	
    10:25:06 AM	#30 Text 0 File ThreadedTransfer.cpp, Line 228
    	all writers idle, stopping conversion
    	
    10:25:07 AM	#31 Text 0 File DVDR.cpp, Line 3103
    	EndDAO: Last written address was 2083615
    	
    10:25:07 AM	#32 Phase 38 File dlgbrnst.cpp, Line 1685
    	Burn process failed at 16x (22,160 KB/s)
    	
    
    Existing drivers:
    File 'Drivers\CDRALW2K.SYS': Ver=8.0.0.212 , size=2560 bytes, created 2/22/2007 9:29:52 PM 
    File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 11/20/2005 10:48:21 PM 
    File 'Drivers\PXHELP20.SYS': Ver=3.00.43J, size=36624 bytes, created 2/22/2007 9:29:52 PM (Prassi/Veritas driver for win 2K)
    
    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
    Quote Quote  
  2. Member oldandinthe way's Avatar
    Join Date
    Mar 2006
    Location
    With the other crabapples
    Search Comp PM
    The behavior would appear to be consistant with bad media or media incompatibility, based on the point at which the error occurs.

    That said, the fact that you are getting memory errors, suggests you should trouble shoot your system.

    Test memory.
    Scan for virus or spyware
    Possibly restore O/S to known good State. etc etc

    You should also test your drive with some media other than Ritek.
    Quote Quote  
  3. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Originally Posted by oldandinthe way
    The behavior would appear to be consistant with bad media or media incompatibility, based on the point at which the error occurs.

    That said, the fact that you are getting memory errors, suggests you should trouble shoot your system.

    Test memory.
    Scan for virus or spyware
    Possibly restore O/S to known good State. etc etc

    You should also test your drive with some media other than Ritek.
    Yeah keep forgetting to run spyware, have it set for midnight checking but seem to turn off sys before that.

    Just tried a burn with 8x media (ritekG05) and burned with success. Never had any issues with 16x, until now thats why I am confused, have 7 16x disks left. hmm

    Been thinking about installing another HD and re-installing WinXP, its a 160 SATA, but want to use it on another sys, oh well. Thanks for comeback.

    Gcam
    Quote Quote  
  4. Member
    Join Date
    Feb 2004
    Location
    Pleasant Hill, CA
    Search Comp PM
    Originally Posted by gcam
    Just tried a burn with 8x media (ritekG05) and burned with success. Never had any issues with 16x, until now thats why I am confused, have 7 16x disks left. hmm
    This is the issue with so-called "bad" media. It's not that it will generate coasters 100% of the time, it's that they'll *sometimes* produce coasters. And sometimes burn just fine. But you never know. From the reading I've done (and limited use of some "bad" media), you might have a bit better success with those by 16x discs by burning at 8x. But ultimately you'll have better, and consistent, results by using TY or Verbatim media.

    My 2 cents,
    Jim
    Quote Quote  
  5. Member oldandinthe way's Avatar
    Join Date
    Mar 2006
    Location
    With the other crabapples
    Search Comp PM
    Look at the bad disks. Particularly at the outer edges. Notice any physical abnormalities. Often bad media shows unevenness of the dye or even lumps. I have on rare occaisions gotten media which sould have failed quality control if there was any. The eyeball can predict the failures in these case.

    Thats what warranties are for/
    Quote Quote  
  6. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Originally Posted by Jim44
    But you never know. From the reading I've done (and limited use of some "bad" media), you might have a bit better success with those by 16x discs by burning at 8x. But ultimately you'll have better, and consistent, results by using TY or Verbatim media.

    My 2 cents,
    Jim
    Thats true, you never know. Guess I will have to try out the TY's. I have also used prodisc in the past and never had problems with them, but that was two years ago. I'll order up a spindle and see how goes.

    Thanks,

    Gerry
    Quote Quote  
  7. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Originally Posted by oldandinthe way
    Look at the bad disks. Particularly at the outer edges. Notice any physical abnormalities. Often bad media shows unevenness of the dye or even lumps. I have on rare occaisions gotten media which sould have failed quality control if there was any. The eyeball can predict the failures in these case.

    Thats what warranties are for/
    Didnt see any abnormalities, looks normal to me, even with reading glasses. Just will have to try out new media.

    Thanks,

    Gerry
    Quote Quote  
  8. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Should I stick with 8X or go with 16X?

    Gerry
    Quote Quote  
  9. Is This the first time you have burned Ritek F1 since you went to GLOG firmware? That firmware has only been out a couple weeks. May want to revert to GLOF and see what you get.
    Quote Quote  
  10. Member
    Join Date
    Feb 2004
    Location
    Pleasant Hill, CA
    Search Comp PM
    Buying new? 16x is fine, IMO. Depending on what your're burning, you may want to burn at 8x, but for some less-archival stuff that I've burned, burning at 16x has been fine.

    Jim
    Quote Quote  
  11. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Originally Posted by OneSickPup
    Is This the first time you have burned Ritek F1 since you went to GLOG firmware? That firmware has only been out a couple weeks. May want to revert to GLOF and see what you get.
    I had the original fw (gl03), and until now it started toasting, I upgraded to gl0G to see if it would make a difference, but it didnt. Will try revert.

    Gerry
    Quote Quote  
  12. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Update:
    hmm I just tried another burn with the same media (16x ritekF01) but at 8x burn and was successful.

    gcam
    Quote Quote  
  13. Member Krispy Kritter's Avatar
    Join Date
    Jul 2003
    Location
    St Louis, MO USA
    Search Comp PM
    It could also be a dirty or failing media sensor.
    Google is your Friend
    Quote Quote  
  14. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    hmm, and how would I diag that? any idea?
    Quote Quote  
  15. Member oldandinthe way's Avatar
    Join Date
    Mar 2006
    Location
    With the other crabapples
    Search Comp PM
    Clean with a cleaning disk. If dirty will help temporarily.

    If failing, result will be having to replace the drive. When you replace the drive will be a function of how long it takes for the sensor to fail vs your loss of patience with the drive.

    It looks to me like you are in a state where you can wait. Nothing to be gained by any further testing short of other media,
    Quote Quote  
  16. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    ten four, will check it out. The TY's just arrived, so will be testing them out.

    Thanks
    Quote Quote  
  17. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    well i guess it was the media, first TY dvd burned with success at 18X! wow. lets see how long it lasts.
    Quote Quote  
  18. Member [_chef_]'s Avatar
    Join Date
    Nov 2002
    Location
    Germany
    Search Comp PM
    What is this:
    "DiskPeripheral : MDT MD1000BB-00CAA1 atapi Port 0 ID 0 DMA: Off"

    RITEK F1 is not good for your burner, especially at 16x.
    *** Now that you have read me, do some other things. ***
    Quote Quote  
  19. Member
    Join Date
    Jan 2007
    Location
    United States
    Search Comp PM
    Originally Posted by [_chef_
    ]What is this:
    "DiskPeripheral : MDT MD1000BB-00CAA1 atapi Port 0 ID 0 DMA: Off"
    Thats a white label hard drive, from 3btech.net...
    Manufacturer: MDT (Magnetic Data Technology), I bought it as a temporary as I didnt have enough funds at the time, going to replace it this week to a 160gb sata, it has some issues.

    RITEK F1 is not good for your burner, especially at 16x.
    yeah figured that one out after burning 40 dvds, the last ten started with issues, switched to TY and not looking back, for now.

    gcam
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!