ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > Living Room

dvd burner crisis

<< < (3/8) > >>

CleverCat:
How about this...

My LG DVD writer suddenly starting rebooting the PC when a disk was inserted! My IT friend tried everything - new cable etc...  It doesn't work in his Grandsons PC either!

Then he tested it in his PC - no problem? :huh:

I've been forced to order a new Lite On (antsy about LG now)...

PaladinMJ:
I think its definately a software issue.. just a feeling I have. Looking for a disc with my live linux on it, hopefully it should let me try and burn a DVD, if it works there I know its a s/w prob and can do more to try and defeat it! I'm afraid of buying a new drive and STILL having to find the problem.

f0dder:
What makes you think it's a software problem?

Use ImgBurn and check tools->Filter Driver Load Order. That will let you see filter drivers attached to the CDROM class... if there's nothing suspicious there, it's most likely not a software issue.

PaladinMJ:
What makes you think it's a software problem?

Use ImgBurn and check tools->Filter Driver Load Order. That will let you see filter drivers attached to the CDROM class... if there's nothing suspicious there, it's most likely not a software issue.
-f0dder (March 19, 2009, 12:17 PM)
--- End quote ---

well i thought it may be a s/w issue because a) the drive still reads b) i updated the chipset drivers in between the last working burn and this problem.  c) hope.
I am starting to believe that the drive is just dead though... I can't find my live CD to test it under there. and  after flashing the drive ImgBurn gave me this:

ImgBurn
---------------------------
DeviceIoControl(FSCTL_LOCK_VOLUME) Failed!
Device: [0:0:0] Optiarc DVD RW AD-7170A 1.04 (G:) (ATA)
Unable to lock volume for exclusive access.
Reason: Access is denied.
Hint: You've got another program running that's using the drive, close it and then click 'Try Again'.
though nothing else was running nor should have been using the drive, so i told imgburn to ignore exclusive access in the settings and it gave me :
0:23:55 Source File Volume Identifier: 20070518
I 10:23:55 Source File Application Identifier: PCLinuxOS release (PCLinuxOS) for Live CD
I 10:23:55 Source File File System(s): ISO9660 (Bootable), Joliet
I 10:23:55 Destination Device: [0:0:0] Optiarc DVD RW AD-7170A 1.04 (G:) (ATA)
I 10:23:55 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 2x, 4x, 6x, 8x, 12x, 16x)
I 10:23:55 Destination Media Sectors: 2,297,888
I 10:23:55 Write Mode: DVD
I 10:23:55 Write Type: DAO
I 10:23:55 Write Speed: MAX
I 10:23:55 Link Size: Auto
I 10:23:55 Test Mode: No
I 10:23:55 OPC: No
I 10:23:55 BURN-Proof: Enabled
I 10:23:56 Filling Buffer... (40 MB)
I 10:23:57 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 32 - 63 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 64 - 95 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (2 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (3 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 128 - 159 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 160 - 191 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (2 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (3 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (4 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (5 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 192 - 223 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (2 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 224 - 255 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (2 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (3 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (4 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (5 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (6 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (7 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (8 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (9 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (10 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 256 - 287 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (1 of 20)...
W 10:24:35 Retry Failed - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:24:35 Retrying (2 of 20)...
I 10:24:35 Writing LeadIn...
W 10:24:35 Failed to Write Sectors 288 - 319 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
etc etc etc...
i looked @tools->Filter Driver Load Order and it looked OK to me, so i guess I'm going to save up for a new drive. are lite on good?

PaladinMJ:
i ran the IntelĀ® Chipset Identification Utility and updated the drivers there too... so i guess it is a dead drive.... :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'(

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version