Invalid write state LITE-ON LTR-52327S W2K5 Nero 7 Noname CDR

Discussion in 'Nero discussion' started by tonib95, Aug 27, 2006.

  1. tonib95

    tonib95 Member

    Joined:
    Aug 27, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    Can anyone tell me why after burning with the same NoName CDR blanks 2 Times in a row I get the dreaded "Invalid write state" failure.
    Nothing has changed, same batch CDR, same type files from same partition.
    Any ideas I don't want to waste any more CDs and need too back up the rest.


    Windows 2000 5.0
    IA32
    WinAspi: -
    ahead WinASPI: File 'F:\Cd\Nero\Nero 7\Core\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 25-09-2005 19:11:20

    NT-SPTI used
    Nero Version: 7.0.0.0
    Recorder: <LITE-ON LTR-52327S> Version: QS09 - HA 1 TA 1 - 7.0.0.0
    Adapter driver: <IDE> HA 1
    Drive buffer : 2048kB
    Bus Type : default (0) -> ATAPI, detected: ?
    CD-ROM: <LITEON CD-ROM LTN526D >Version: 9S01 - HA 1 TA 0 - 7.0.0.0
    Adapter driver: <IDE> HA 1

    === Scsi-Device-Map ===
    DiskPeripheral : Maxtor 6L200M0 atapi Port 0 ID 0 DMA: Off
    DiskPeripheral : Maxtor 6Y120L0 atapi Port 2 ID 0 DMA: On
    DiskPeripheral : Maxtor 4D040H2 atapi Port 2 ID 1 DMA: On
    CdRomPeripheral : LITEON CD-ROM LTN526D atapi Port 3 ID 0 DMA: On
    CdRomPeripheral : LITE-ON LTR-52327S atapi Port 3 ID 1 DMA: On
    CdRomPeripheral : SCSIVAX DVD/CD-ROM 2.7a vax347s Port 4 ID 0 DMA: Off
    CdRomPeripheral : Generic DVD-ROM 1.0 d347prt Port 5 ID 0 DMA: Off

    === CDRom-Device-Map ===
    LITEON CD-ROM LTN526D D: CDRom0
    LITE-ON LTR-52327S E: CDRom1
    SCSIVAX DVD/CD-ROM J: CDRom2
    Generic DVD-ROM K: CDRom3
    =======================

    AutoRun : 1
    Excluded drive IDs:
    WriteBufferSize: 83886080 (0) Byte
    ShowDrvBufStat : 0
    BUFE : 0
    Physical memory : 959MB (982252kB)
    Free physical memory: 621MB (635920kB)
    Memory in use : 35 %
    Uncached PFiles: 0x0
    Use Inquiry : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    27.8.2006
    CD-ROM (ISO)
    13:31:46 #1 Text 0 File Isodoc.cpp, Line 6410
    Iso document burn settings
    ------------------------------------------
    Determine maximum speed : TRUE
    Simulate : FALSE
    Write : TRUE
    Finalize CD : TRUE
    Multisession : FALSE
    Burning mode : TAO
    Mode : 1
    ISO Level : 2 (Max. of 31 chars)
    Character set : ISO 9660
    Joliet : TRUE
    Allow pathdepth more than 8 directories : TRUE
    Allow more than 255 characters in path : TRUE
    Write ISO9660 ;1 file extensions : TRUE

    13:31:46 #2 Text 0 File Burncd.cpp, Line 3007
    LITE-ON LTR-52327S
    Buffer underrun protection activated

    13:31:46 #3 Text 0 File ThreadedTransfer.cpp, Line 525
    ReadBuffer-Pipe got 81920KB of Memory

    13:31:46 #4 Text 0 File Reader.cpp, Line 124
    Reader running

    13:31:46 #5 Text 0 File Writer.cpp, Line 113
    Writer E: LITE-ON LTR-52327S running

    13:31:46 #6 ISO9660GEN -11 File Geniso.cpp, Line 3304
    First writeable address = 0 (0x00000000)

    13:31:47 #7 Text 0 File Burncd.cpp, Line 3301
    Turn on Track-At-Once, using CD-R/RW media

    13:31:47 #8 Text 0 File DlgWaitCD.cpp, Line 277
    Last possible write address on media: 359848 ( 79:59.73)
    Last address to be written: 350877 ( 78:00.27)

    13:31:47 #9 Text 0 File DlgWaitCD.cpp, Line 289
    Write in overburning mode: NO (enabled: CD)

    13:31:47 #10 Text 0 File DlgWaitCD.cpp, Line 2568
    Recorder: LITE-ON LTR-52327S;
    CDR code: 00 97 27 18; OSJ entry from: Plasmon Data systems Ltd.
    ATIP Data:
    Special Info [hex] 1: C0 00 80, 2: 61 1B 12 (LI 97:27.18), 3: 4F 3B 4A (LO 79:59.74)
    Additional Info [hex] 1: 00 00 80 (invalid), 2: 00 80 00 (invalid), 3: 00 80 80 (invalid)

    13:31:47 #11 Text 0 File DlgWaitCD.cpp, Line 456
    >>> Protocol of DlgWaitCD activities: <<<
    =========================================

    13:31:47 #12 Text 0 File ThreadedTransferInterface.cpp, Line 846
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 ()
    2 indices, index0 (150) not provided
    original disc pos #0 + 350878 (350878) = #350878/77:58.28
    relocatable, disc pos for caching/writing not required/ required, no patch infos
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 350876 blocks [E: LITE-ON LTR-52327S]
    --------------------------------------------------------------

    13:31:48 #13 Text 0 File ThreadedTransferInterface.cpp, Line 1058
    Prepare recorder [E: LITE-ON LTR-52327S] for write in TAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x00; Session Closed, disc fixated
    Tracks 1 to 1:
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 307200 718905344, ISRC ""
    DAO layout:
    ===========
    __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
    -150 | lead-in | 0 | 0x41 | 0x00
    -150 | 1 | 0 | 0x41 | 0x00
    0 | 1 | 1 | 0x41 | 0x00
    350878 | lead-out | 1 | 0x41 | 0x00

    13:31:48 #14 Text 0 File ThreadedTransferInterface.cpp, Line 1126
    Removed 2 run-out blocks from end of track 1. Length: 350878 -> 350876.

    13:31:48 #15 Text 0 File SCSIPassThrough.cpp, Line 34
    SPTILockVolume - completed successfully for FCTL_LOCK_VOLUME

    13:31:48 #16 Phase 24 File dlgbrnst.cpp, Line 1724
    Caching of files started

    13:31:48 #17 Text 0 File Burncd.cpp, Line 4129
    Cache writing successful.

    13:31:48 #18 Phase 25 File dlgbrnst.cpp, Line 1724
    Caching of files completed

    13:31:48 #19 Phase 28 File dlgbrnst.cpp, Line 1724
    Speed measurement started

    13:31:48 #20 Text 0 File ThreadedTransferInterface.cpp, Line 2669
    Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

    13:35:00 #21 Text 0 File ThreadedTransfer.cpp, Line 228
    all writers idle, stopping conversion

    13:35:01 #22 Phase 29 File dlgbrnst.cpp, Line 1673
    Speed measurement completed: 24.4x (3.660 KB/s)

    13:35:01 #23 Text 0 File Burncd.cpp, Line 4195
    Can only write at 24x instead of 32x,

    because speed of source data is too slow

    13:35:01 #24 Phase 36 File dlgbrnst.cpp, Line 1724
    Burn process started at 24x (3.600 KB/s)

    13:35:01 #25 Text 0 File ThreadedTransferInterface.cpp, Line 2669
    Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

    13:35:02 #26 Text 0 File MMC.cpp, Line 21541
    Set BUFE: Buffer underrun protection -> ON , SMART-BURN : ON

    13:36:58 #27 SPTI -1114 File SCSIPassThrough.cpp, Line 306
    CdRom1: SCSIStatus(x02) WinError(0) NeroError(-1114)
    Sense Key: 0x06 (KEY_UNIT_ATTENTION)
    Sense Code: 0x29
    Sense Qual: 0x00
    CDB Data: 0x2A 00 00 00 00 00 00 00 20 00 00 00
    Sense Area: 0x70 00 06 00 00 00 00 0A 00 00 00 00 29
    Buffer x0a060000: Len x10000
    0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    13:36:58 #28 CDR -1114 File Writer.cpp, Line 302
    Reset occurred
    E: LITE-ON LTR-52327S

    13:36:58 #29 Text 0 File ThreadedTransfer.cpp, Line 228
    all writers idle, stopping conversion

    13:36:58 #30 Text 0 File ThreadedTransfer.cpp, Line 222
    conversion idle, stopping reader

    13:36:58 #31 CDR -201 File WriterStatus.cpp, Line 200
    Invalid write state
    E: LITE-ON LTR-52327S

    13:36:58 #32 TRANSFER -18 File WriterStatus.cpp, Line 200
    Could not perform EndTrack

    13:36:58 #33 Text 0 File MMC.cpp, Line 16273
    <LITE-ON LTR-52327S > start Close Session

    13:36:58 #34 Phase 38 File dlgbrnst.cpp, Line 1724
    Burn process failed at 24x (3.600 KB/s)


    Existing drivers:
    File 'Drivers\CDR4_2K.SYS': Ver=5.3.2.31, size=58000 bytes, created 10-11-2005 04:01:49
    File 'Drivers\CDRALW2K.SYS': Ver=5.3.2.31, size=23420 bytes, created 10-11-2005 04:01:49

    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
     
    Last edited: Aug 27, 2006
  2. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    DMA needs to be on for all drives...here is a guide: http://forums.afterdawn.com/thread_view.cfm/260038

    Reduce your burn speed to 16X and always use quality media.

    These are Roxio's drivers, they interfere big time with Nero...I suggest removing Roxio in it's entirety from your system via this clean tool: http://www.softpedia.com/get/Tweak/Uninstallers/Roxio-Zap.shtml

    EDIT: Remove your serial number, it is at the top of your log and begins with 4C82
     
    Last edited: Aug 27, 2006
  3. tonib95

    tonib95 Member

    Joined:
    Aug 27, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    Thanks LOCOENG for your reply , and I will try the things you have written.
    But I have not changed anything between it worked and didn't work, so I still don't understand why or why ?

     
    Last edited: Aug 27, 2006
  4. MaxBurn

    MaxBurn Regular member

    Joined:
    Sep 9, 2005
    Messages:
    1,027
    Likes Received:
    0
    Trophy Points:
    46
    Besides what loco said, this error
    suggests a hardware problem. Check the cables on the drive, at both ends. You may have a loose or bad IDE cable, or the drive itself could be going out.
    Roxio can cause bad conflicts too.

    Who knows why things just suddenly stop working when nothing has changed? Hardware, software, and human interface all combine to put in lots of variables.
     
  5. tonib95

    tonib95 Member

    Joined:
    Aug 27, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    Thanks both of you for taking the time to post.
    Having tried the ideas Roxio out burn speed down etc etc
    + new drivers to the burner, I gave up and bought a LH GSA 4167B.
    Burnt OK first time.
    Liteon must have died.

    Thanks again.
     
  6. MaxBurn

    MaxBurn Regular member

    Joined:
    Sep 9, 2005
    Messages:
    1,027
    Likes Received:
    0
    Trophy Points:
    46
    @tonib95
    Glad you got it to work. Sometimes it is the burner thats bad, but we try to only suggest that as a last resort. I think many a burner has been replaced when it really wasnt bad, but in your case, it looks like it was the right thing to do. A hardware error reported in nero usually means some major problem was going on with the burner.
     
  7. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    Glad your problems were resolved with a new drive...it's always nice to get a new drive, gives me that warm and cozy feeling when I install it. As Max stated, a new drive is usually the last suggestion because it is usually the more expensive route. Anywho, happy burning.
     

Share This Page