LG GCE-8481B making lovely coasters - grrrr...

[caffeinated]

Okay, I've got less than a month left on my OEM warranty. This drive has functioned properly in the past so I wanted to consult the experts. It was sent as a replacement when my LG GCE-8320B crapped out.

Here is my setup:
Primary master: Maxtor 60 GB 7200 hard disk
Primary slave: Maxtor 80 GB 7200 hard disk
Secondary master: LG CD-RW GCE-8481B
Secondary slave: LG DVD GDR-8161B

I've tried to copy original disks, data, and now to create a CD from an ISO. The software I've encountered problems with is EasyCDCreator 5.3.5.10 (latest patch...) and winbackup (latest version).

The drive starts out at 24X write and by the time it hits 50% completion it stops having crawled along at 1X for several minutes. It then tries to write in a final flurry and then stops; the disk is ejected and errors are reported. Here are the EasyCDCreator errors:

E800419898: Write error - (03/0C/00)
E80041899: Write error - buffer underrun occurred - (06/C5/00)
E80041925: TrackWriter error - Command retry failed - (T7118)

I am particularly concerned by this last error.

Any thoughts would be appreciated - I'm getting very tired of making coasters...

[dodecahedron]

i'm no expert but it does seem to me like your drive is on the blink, taking advantage of the warranty and RMAing it sounds good.

[caffeinated]

i'm no expert but it does seem to me like your drive is on the blink, taking advantage of the warranty and RMAing it sounds good.

I'm really annoyed about this. By the way, thanks for responding so quickly, your polyhedral greatness! Seriously though, I do appreciated it. I originally had trouble with my LG GCE-8320B and so NCIX.com replaced it with the refurbished LG GCE-8481B that I currently have. I've noticed that my drive has only a single LED, which is not the case with the same drives on the lge.com site or in the many reviews I have come across around the web. It pisses me off that they always replace OEM drives with refurbished drives. Oh well, I guess I'll RMA it as you suggest.

Just one more question, however: Is my configuration sound? I was told by a guy in a local computer store that I should have the CD-RW and the DVD drives on different IDEs. He suggested something like:

Primary master: Maxtor 60 GB 7200 hard disk
Primary slave: LG CD-RW GCE-8481B
Secondary master: Maxtor 80 GB 7200 hard disk
Secondary slave: LG DVD GDR-8161B

Can you think of any reason why this would help/affect my situation?

Thanks again!

[Inertia]

Your LG GCE-8481B drive has SuperLink, and if it is enabled and the drive is operating properly it should not be possible to have a buffer underrun error. In the burn dialog "Record CD Setup" in Easy CD Creator, is the "Buffer underrun prevention" box checked?

Have you tried a different high quality media such as Taiyo Yuden (branded as Fuji in the U.S., with "Made in Japan" on the label)?

Have you verified that DMA is enabled for your LG drives per How to enable DMA in Windows XP (with pictures)?

Your IDE setup is OK, and shouldn't be causing a problem.

[caffeinated]

Your LG GCE-8481B drive has SuperLink, and if it is enabled and the drive is operating properly it should not be possible to have a buffer underrun error. In the burn dialog "Record CD Setup" in Easy CD Creator, is the "Buffer underrun prevention" box checked?

Yes, the Buffer underrun prevention box is checked.

Have you tried a different high quality media such as Taiyo Yuden (branded as Fuji in the U.S., with "Made in Japan" on the label)?

No, I am using Memorex 700 MB bulk disks

Have you verified that DMA is enabled for your LG drives per How to enable DMA in Windows XP (with pictures)?

Yes, and both of my drives indicate Ultra DMA Mode 2

Your IDE setup is OK, and shouldn't be causing a problem.

Thanks for your guidance. So it looks like my drive may be defective then - unless it is the media that is to blame. This may in fact be the problem. I've also noted that this drive is not on the list of Roxio-supported drives. Damn, so many variables to control and eliminate!
Perhaps I had best start by trying higher quality media?

BTW: What do you think about the single LED light? Curious, eh?

Do you think that there is any point in doing a firmware upgrade?

[TheWizard]

LG went to single LED's with the GCE-8480B, I believe. All drives since then have had 1 LED. This may be only for OEM drives, but I think some retail drives have 1 LED as well.

[Inertia]

I assume the LG GCE-8481B drive didn't come with Easy CD Creator. If your drive isn't supported by Easy CD Creator, you're lucky it is even recognized as a burner. Lack of support for the burner model could cause an improper implementation of the buffer underrun prevention.

It is supported by Nero, and you might try a trial copy of Nero and the suggested Fuji (Taiyo Yuden) media to see if it makes a difference before you return the drive.

[dodecahedron]

By the way, thanks for responding so quickly, your polyhedral greatness!

you're most welcome, caffeinated

i must say, my polyhedral greatness is very pleased with your appreciation of all things polyhedral!

To answer your question, oh great polyhedral one ....

http://www.cdrlabs.com/phpBB/viewtopic. ... 7476#47476
this was way back, i think even before i officially became a "CD-RW Polygon"

[jmbrown12]

The Roxio supported recorders database shows your recorder supported in version 5.1.1.104 Basic and version 5.3.1.154 Platinum. Easy CD Creator will usually show the other two errors when a buffer underrun occurs.

[caffeinated]

I assume the LG GCE-8481B drive didn't come with Easy CD Creator. If your drive isn't supported by Easy CD Creator, you're lucky it is even recognized as a burner. Lack of support for the burner model could cause an improper implementation of the buffer underrun prevention.

Well, my LG GCE-8320B came with ECD Creator so naturally I thought that the replacement would work with it. I have since been informed that it is supported by Roxio.

It is supported by Nero, and you might try a trial copy of Nero and the suggested Fuji (Taiyo Yuden) media to see if it makes a difference before you return the drive.

I will try this option, but the thought of having to fork out more cash for higher quality CD media isn't sitting well.

[caffeinated]

i must say, my polyhedral greatness is very pleased with your appreciation of all things polyhedral!

Best Burns voice: "Excellent."

[...]even before i officially became a "CD-RW Polygon"

Don't sell yourself short. You are at least a three dimensional deity!

[caffeinated]

The Roxio supported recorders database shows your recorder supported in version 5.1.1.104 Basic and version 5.3.1.154 Platinum. Easy CD Creator will usually show the other two errors when a buffer underrun occurs.

Thanks for this - it wasn't on the list when I checked with Roxio. Curious.

[caffeinated]

The Roxio supported recorders database shows your recorder supported in version 5.1.1.104 Basic and version 5.3.1.154 Platinum. Easy CD Creator will usually show the other two errors when a buffer underrun occurs.

Thanks for this - it wasn't on the list when I checked with Roxio. Curious.

Okay, I found it using the search engine. Not listed where I'd expect however. Still think that's curious!

Right, so I've purchased a 10 pack of Fuji 80 min/ 700 MB (made in Japan) so I'll let you know how the burn attempt went later on today...

[caffeinated]

Okay, I uninstalled ECDC 5.3.5.10 basic and installed Nero 5.5. Using the aforementioned Fujifilm media, I got the following series of messages during a burn simulation:

1:01:13 PM HL-DT ST CD-RW GCE-8481B
Buffer Underrun Protection activated
1:01:14 PM Caching of files started
1:01:14 PM Caching of files completed
1:01:14 PM Simulation started at 48X (7,200 KB/s)
1:02:17 PM HL-DT ST CD-RW GCE-8481B
Write error
1:02:17 PM HL-DT ST CD-RW GCE-8481B
Invalid write state
1:02:17 PM HL-DT ST CD-RW GCE-8481B
Could not perform EndTrack
1:02:19 PM Simulation failed at 48X (7,200 KB/s)

Onto another simulation... I'll update my finding shortly.

BTW:

I noticed that NERO reports my firmware version to be 1.01. Is there any point in flashing to the current 1.05? Would that violate any warranty?
It also says that my burner supports Mr. Rainer! I didn't think that it did

[Inertia]

caffeinated,

You have done all that you could be reasonably expected to do to test the drive, and it is still malfunctioning. I would return it. I agree that it stinks that LG will only replace defective drives with refurbished (factory reconditioned) drives. Thus your replacement will be a bad drive that hopefully has been fixed. This doesn't raise confidence that it is equal to a new drive in performance, especially when in your case a refurbished replacement failed again during the warranty period. Two straight failures in one year is not impressive.

I wouldn't consider reflashing the drive at this point, as firmware upgrades should marginally improve a drive's operation and media compatiblity, not make the difference between functioning or not. To further make a firmware upgrade unattractive at this point, LG states in its firmware update policy at http://www.lgeservice.com/readme(ew)-GCE-8481B.htm that if the update fails for any reason and damages the drive, it is the customer's responsiblity and not that of LG.

Send it back as is. If it were me, since your second drive failed again I would complain about receiving a reconditioned drive and would request a new drive under the circumstances.

[caffeinated]

caffeinated,

You have done all that you could be reasonably expected to do to test the drive, and it is still malfunctioning. I would return it. I agree that it stinks that LG will only replace defective drives with refurbished (factory reconditioned) drives. Thus your replacement will be a bad drive that hopefully has been fixed. This doesn't raise confidence that it is equal to a new drive in performance, especially when in your case a refurbished replacement failed again during the warranty period. Two straight failures in one year is not impressive.

I wouldn't consider reflashing the drive at this point, as firmware upgrades should marginally improve a drive's operation and media compatiblity, not make the difference between functioning or not. To further make a firmware upgrade unattractive at this point, LG states in its firmware update policy at http://www.lgeservice.com/readme(ew)-GCE-8481B.htm that if the update fails for any reason and damages the drive, it is the customer's responsiblity and not that of LG.

Send it back as is. If it were me, since your second drive failed again I would complain about receiving a reconditioned drive and would request a new drive under the circumstances.

Thanks for the feedback and advice, Inertia, but I actually got it to copy an audio CD using Nero. I'm starting to think that the ISO file in my earlier attempts is corrupted. Does anyone know how to test the integrity of an Iso file?

Heh, this would almost be fun if only it didn't waste so much time.

Now I want to try out my original cheaper media again. I'll tinker some more with it this evening and report back.

[dodecahedron]

caffeinated, like Inertia said, you've done plenty and beyond the call of duty. time to RMA the drive before the warranty expires.

as for flashing to a newer firmware, i believe (i could be wrong but this used to be true) flashing a drive will void your warranty.
more precisely, in the help/instruction file for the firmware flashing, LG disclaims any problems that might arise from a bad flash.
so there's no call for you to take any chances by flashing, and nor should you. if that's LG's policy, then it's LG's responsibility to get you a working drive (in the warranty period anyways) without your risking it.
(OK i now see that Inertia wrote more or less everything i did oh well)

try creating a data CD in Nero instead of burning an ISO file.
this way the quality of the ISO file is not an issue. assuming Nero is not corrupted (no reason it should be) it will create the data CD fine. if it doesn't burn well, it's the drive's fault.

[Inertia]

Try using the freeware IsoBuster to extract the ISO file to the hard drive. Once the contents are extracted, they can be burned directly from the hard drive.

IsoBuster should also allow you to determine if the file is corrupted.

[caffeinated]

Try using the freeware IsoBuster to extract the ISO file to the hard drive. Once the contents are extracted, they can be burned directly from the hard drive.

IsoBuster should also allow you to determine if the file is corrupted.

I recreated the ISO using Nero after extracting the files to the desktop using IsoBuster. The first burn failed at 32X using the Memorex media

Relevant part of Memorex burn log:

1:52:41 PM #14 Phase 24 File dlgbrnst.cpp, Line 1571
Caching of files started

1:54:28 PM #15 Phase 25 File dlgbrnst.cpp, Line 1571
Caching of files completed

1:54:28 PM #16 Phase 36 File dlgbrnst.cpp, Line 1571
Burn process started at 32x (4,800 KB/s)

1:54:28 PM #17 Text 0 File ThreadedTransferInterface.cpp, Line 1948
Verifying CD position of item 0 (relocatable, CD pos, no patch infos, orig at #0): write at #0

1:54:28 PM #18 Text 0 File Mmc.cpp, Line 17168
Set BUFE: supported -> ON

1:57:10 PM #19 SCSI -1135 File Cdrdrv.cpp, Line 1381
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x03D50000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x0C
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x02 0x86 0xC3 0x00 0x00 0x1F 0x00 0x00 0x00
Sense Data: 0x71 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x0C 0x00

1:57:10 PM #20 MMC -1135 File Writer.cpp, Line 335
Write error

1:57:10 PM #21 Text 0 File ThreadedTransfer.cpp, Line 222
all writers idle, stopping conversion

1:57:11 PM #22 Text 0 File ThreadedTransfer.cpp, Line 216
conversion idle, stopping reader

1:57:11 PM #23 CDR -201 File WriterStatus.cpp, Line 188
Invalid write state

1:57:11 PM #24 TRANSFER -18 File WriterStatus.cpp, Line 188
Could not perform EndTrack

1:57:34 PM #25 Text 0 File Mmc.cpp, Line 12134
Fixation : Second step for unclosed Sessions

1:57:54 PM #26 Phase 38 File dlgbrnst.cpp, Line 1571
Burn process failed at 32x (4,800 KB/s)

1:57:54 PM #27 Text 0 File Scsicmd.cpp, Line 402
SCSI not using temporary buffers
20 out of 20 temporary buffers allocated

The second burn using the Fujifilm media succeeded at 48X (took about 6 minutes)


Relevant part of Fujifilm burn log:

2:05:14 PM #14 Phase 24 File dlgbrnst.cpp, Line 1571
Caching of files started

2:06:54 PM #15 Phase 25 File dlgbrnst.cpp, Line 1571
Caching of files completed

2:06:54 PM #16 Phase 36 File dlgbrnst.cpp, Line 1571
Burn process started at 48x (7,200 KB/s)

2:06:54 PM #17 Text 0 File ThreadedTransferInterface.cpp, Line 1948
Verifying CD position of item 0 (relocatable, CD pos, no patch infos, orig at #0): write at #0

2:06:54 PM #18 Text 0 File Mmc.cpp, Line 17168
Set BUFE: supported -> ON

2:11:08 PM #19 Text 0 File ThreadedTransfer.cpp, Line 222
all writers idle, stopping conversion

2:11:35 PM #20 Phase 37 File dlgbrnst.cpp, Line 1571
Burn process completed successfully at 48x (7,200 KB/s)

2:11:35 PM #21 Text 0 File Scsicmd.cpp, Line 402
SCSI not using temporary buffers
20 out of 20 temporary buffers allocated

So by all accounts it appears to be the media, eh? Any more subtle problems that anyone can see on inspection of the log files? Any help/suggestions appreciated.

PS - why is SCSI mentioned? I have IDE drives!

[Inertia]

I'm glad you finally had some success. Your problem does seem to have been media related, and possibly combined with a problem disc image file.

One not-so-subtle problem seen in the log file is that a 48x burn should take about 3 minutes (as indicated in the Nero burn dialog after completion). Although you have set the speed for 48x, something is causing the burn to slow down. DMA not being activated is the most common cause, but you have already indicated that DMA is enabled. Make sure that your hard drive is defragmented and the Windows/Temp directory is emptied before you start a burn.

I would suggest running the CD Speed (part of the Nero Toolkit) burn rate test to see if it indicates a problem. Insert a blank CD-R disc in the burner and click on Start. CD Speed with run the Write Transfer Speed test without writing anything to the blank CD-R. If the green line (burn speed) doesn't increase in a straight line up to a rate of 48x at the end of the disc, something is wrong. The yellow line (RPM) should be relatively straight and flat across the burn without any significant decrease.

Using CD Speed, you should run the Extra | ScanDisc test with the disc that you burned. If the blocks are all green, then the burn quality is OK. If any yellow blocks show up, this is a sign of a less than successful burn.

[caffeinated]

One not-so-subtle problem seen in the log file is that a 48x burn should take about 3 minutes (as indicated in the Nero burn dialog after completion). Although you have set the speed for 48x, something is causing the burn to slow down. DMA not being activated is the most common cause, but you have already indicated that DMA is enabled. Make sure that your hard drive is defragmented and the Windows/Temp directory is emptied before you start a burn.

My system is regularly defragged (Norton Speed Disk 2002, NTFS) and the Windows/Temp directory only contains the zonealarm tmp file.

I would suggest running the CD Speed (part of the Nero Toolkit) burn rate test to see if it indicates a problem. Insert a blank CD-R disc in the burner and click on Start. CD Speed with run the Write Transfer Speed test without writing anything to the blank CD-R. If the green line (burn speed) doesn't increase in a straight line up to a rate of 48x at the end of the disc, something is wrong. The yellow line (RPM) should be relatively straight and flat across the burn without any significant decrease.

Using CD Speed, you should run the Extra | ScanDisc test with the disc that you burned. If the blocks are all green, then the burn quality is OK. If any yellow blocks show up, this is a sign of a less than successful burn.

I attempted to run CD Speed tests using different media but none would complete without errors. Each time I got the following results:

Nero CD Speed Test results

General Information
Operating System Windows XP Professional
Drive HL-DT-STCD-RW GCE-8481B
Firmware Version 1.01
Serial Number
Disc Blank
Capacity 79:59.72

Log

Time Elapsed Action
[06:55:56] Starting Write Transfer Rate Test
[06:57:33] Error - NO ADDITIONAL SENSE INFORMATION (000000)

The lines plunged and the tests terminated at about the 10 min mark.

As for the Extra -> Scandisk test, the program failed to advance after 9 errors were detected and a speed of 3.7X was indicated. Despite the flashing LED, this test would not complete (i.e. I left it to continue for about 30 minutes - both file check and surface test were selected - but the disk map remained grayed out).

I now think that the only reasonable conclusion is that this drive is defective. So unless there is anything more that you suggest I try, I'll be RMAing it on Monday.

[dodecahedron]

I now think that the only reasonable conclusion is that this drive is defective. So unless there is anything more that you suggest I try, I'll be RMAing it on Monday.

yes, it really seems the only thing left to do.
if the drive can't to the CDSpeed transfer rate test (simulate a burn) successfully with various media, that's it!

good luck with the RMA stuff.
let us know how it goes.

[Inertia]

PS - why is SCSI mentioned? I have IDE drives!

IDE optical devices such as burners conform to the ATAPI standard. ATAPI is a "SCSI-like" standard that works through ASPI (Advanced SCSI Programming Interface) or operating system drivers to enable IDE devices to communicate with the system as if they were SCSI devices. As the name indicates, ASPI was first developed for use with SCSI drives, and this is why SCSI terminology is still used with ATAPI devices.

Normally, major burning programs should work OK with WinXP without the need for supplementary ASPI drivers. However, since you won't be returning the drive until Monday, I would try installing ForceASPI to see if it has any effect on your problem. Sometimes, a simple ASPI fix will cause problems to disappear.

Go to cyrus-troy Downloads and download the ASPI Check and Force ASPI programs.

Unzip (extract) ForceASPI, read the Index.htm file carefully, and run the program. ForceASPI will repair and/or properly install the version 4.60 (1021) ASPI layer, which is probably the most stable and proven version.

Reboot, and run ASPI Check to verify that version 4.60 (1021) is properly installed. After verification, try the CD Speed test again to see if there is any improvement or change. If nothing changes and you want to remove the ASPI drivers, ForceASPI allows easy removal following the instructions provided. Leaving the drivers installed should cause no problems and may allow some programs to operate that otherwise wouldn't work with standard WinXP drivers.

spelling

[caffeinated]

PS - why is SCSI mentioned? I have IDE drives!

IDE optical devices such as burners conform to the ATAPI standard. ATAPI is a "SCSI-like" standard that works through ASPI (Advanced SCSI Programming Interface) or operating system drivers to enable IDE devices to communicate with the system as if they were SCSI devices. As the name indicates, ASPI was first devoped for use with SCSI drives, and this is why SCSI terminology is still used with ATAPI devices.

Normally, major burning programs should work OK with WinXP without the need for supplementary ASPI drivers. However, since you won't be returning the drive until Monday, I would try installing ForceASPI to see if it has any effect on your problem. Sometimes, a simple ASPI fix will cause problems to disappear.

Go to cyrus-troy Downloads and download the ASPI Check and Force ASPI programs.

Unzip (extract) ForceASPI, read the Index.htm file carefully, and run the program. ForceASPI will repair and/or properly install the version 4.60 (1021) ASPI layer, which is probably the most stable and proven version.

Reboot, and run ASPI Check to verify that version 4.60 (1021) is properly installed. After verification, try the CD Speed test again to see if there is any improvement or change. If nothing changes and you want to remove the ASPI drivers, ForceASPI allows easy removal following the instructions provided. Leaving the drivers installed should cause no problems and may allow some programs to operate that otherwise wouldn't work with standard WinXP drivers.

Thanks, Inertia!

I've already RMAed the drive, but I appreciate your suggestion. I'll report back about how the new drive is working and if the problem persists, then I'll try using Force ASPI.

[thebuck]

hi
it would seem that i am having a similar problem. But i do not get errors 100% of the time. some times it works and sometimes it does not. i get the same error as was posted earlier.

4:17:15 AM #19 CDR -1135 File Writer.cpp, Line 301
Write error

4:17:15 AM #20 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion

4:17:15 AM #21 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader

4:17:15 AM #22 CDR -201 File WriterStatus.cpp, Line 196
Invalid write state
HL-DT-ST CD-RW GCE-8481B\H3 T0

4:17:15 AM #23 TRANSFER -18 File WriterStatus.cpp, Line 196
Could not perform EndTrack

4:17:15 AM #24 Text 0 File Mmc.cpp, Line 14243
<HL-DT-STCD-RW GCE-8481B > start Close Session

4:17:17 AM #25 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 0:00,000 (0ms) -> OK

4:17:17 AM #26 Phase 38 File dlgbrnst.cpp, Line 1800
Burn process failed at 48x (7,200 KB/s)

i used to recieve write error, then noticed that nero said my system aspi was corrupt. so i used a program that a friend sent me to fix this. Nero said all was fine again, and it was i burned a few cds but now i get the new "could not preform endtrack" error. i have made plenty of coasters so if anyone has any suggestions, it would be greatly appriciated.