Problem writing

[Helpless1]

I suddenly have problems writing BD discs, both BD50 and BD25 with different data of course. Nothing changed to my computer in hardware since when it worked flawless. Used Primeon BD50 discs BD-R DL 2x-8x but also Mediarange BD-R 25 disc. Same error. Given the message I guess it is not the discs but clearly I have no idea what really causes it (otherwise I would not be here). Any help greatly appreciated!

 

Latest log:

 

; //****************************************\\
;   ImgBurn Version 2.5.0.0 - Log
;   Tuesday, 05 April 2016, 10:42:00
; \\****************************************//
;
;
I 10:35:08 ImgBurn Version 2.5.0.0 started!
I 10:35:08 Microsoft Windows ??? Home Edition (6.2, Build 9200)
I 10:35:08 Total Physical Memory: 16,766,700 KB  -  Available: 9,925,200 KB
I 10:35:08 Initialising SPTI...
I 10:35:08 Searching for SCSI / ATAPI devices...
I 10:35:09 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE!
I 10:40:03 Operation Started!
I 10:40:03 Building Image Tree...
I 10:40:04 Calculating Totals...
I 10:40:04 Preparing Image...
I 10:40:05 Contents: 323 Files, 24 Folders
I 10:40:05 Content Type: BD Video
I 10:40:05 Data Type: MODE1/2048
I 10:40:05 File System(s): UDF (2.50)
I 10:40:05 Volume Label: Star Wars The Force Awakens
I 10:40:05 Size: 23,889,555,223 bytes
I 10:40:05 Sectors: 11,665,041
I 10:40:05 Image Size: 23,892,328,448 bytes
I 10:40:05 Image Sectors: 11,666,176
I 10:40:06 Operation Successfully Completed! - Duration: 00:00:02
I 10:40:06 Operation Started!
I 10:40:06 Source File: -==/\/[bUILD IMAGE]\/\==-
I 10:40:06 Source File Sectors: 11,666,176 (MODE1/2048)
I 10:40:06 Source File Size: 23,892,328,448 bytes
I 10:40:06 Source File Volume Identifier: Star Wars The Force Awakens
I 10:40:06 Source File Application Identifier: ImgBurn v2.5.0.0
I 10:40:06 Source File Implementation Identifier: ImgBurn
I 10:40:06 Source File File System(s): UDF (2.50)
I 10:40:06 Destination Device: [4:0:0] HL-DT-ST BD-RE  BH16NS40 1.01 (G:) (ATA)
I 10:40:06 Destination Media Type: BD-R (Disc ID: RITEK-BR2-00) (Speeds: 4x, 6x, 8x, 10x)
I 10:40:06 Destination Media Sectors: 12,219,392
I 10:40:06 Write Mode: BD
I 10:40:06 Write Type: DAO
I 10:40:06 Write Speed: 6x
I 10:40:06 BD-R Verify Not Required: Yes
I 10:40:06 Link Size: Auto
I 10:40:06 Lock Volume: Yes
I 10:40:06 Test Mode: No
I 10:40:06 OPC: No
I 10:40:06 BURN-Proof: Enabled
I 10:40:24 Filling Buffer... (250 MB)
I 10:40:27 Writing LeadIn...
I 10:40:28 Writing Session 1 of 1... (1 Track, LBA: 0 - 11666175)
I 10:40:28 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11666175)
W 10:41:24 Failed to Write Sectors 644640 - 644671 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 10:41:24 Retrying (1 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (2 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (3 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (4 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (5 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (6 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (7 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (8 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (9 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (10 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (11 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (12 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (13 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (14 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (15 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (16 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (17 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (18 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (19 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:25 Retrying (20 of 20)...
W 10:41:25 Retry Failed - Reason: Invalid Address For Write
W 10:41:29 Retrying (21)...
W 10:41:29 Retry Failed - Reason: Invalid Address For Write
E 10:41:31 Failed to Write Sectors 644640 - 644671 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
E 10:41:31 Next Writable Address: 644672
I 10:41:31 Synchronising Cache...
I 10:41:40 Closing Track...
I 10:41:41 Finalising Disc...
E 10:41:56 Failed to Write Image!
I 10:41:56 Exporting Graph Data...
I 10:41:56 Graph Data File: C:\Users\Jaap\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.01_TUESDAY-APRIL-5-2016_10-40_AM_RITEK-BR2-00_6x.ibg
I 10:41:56 Export Successfully Completed!
E 10:41:56 Operation Failed! - Duration: 00:01:50
I 10:41:56 Average Write Rate: 20,464 KB/s (4.6x) - Maximum Write Rate: 25,196 KB/s (5.6x)
I 10:42:00 Close Request Acknowledged
I 10:42:00 Closing Down...
I 10:42:00 Shutting down SPTI...
I 10:42:00 ImgBurn closed!
;
;

Edited April 5, 2016 by Helpless1

[LIGHTNING UK!]

Some sort of cable issue maybe?

 

It's a connection / communication issue.

 

You're also using a really old version of the program there.

[Helpless1]

@Lightning UK

Thanks for the reply!

 

Yeah it says it is a Communication error but since I have this drive for years and not opened the cover it is not very likely that is a cable I think. Nevertheless I will look. I will also download a newer version, thanks, but usually I do not touch anything that works. But now it doesn't anymore so you are right. My best guess would be a driver problem but no idea how that would come to be (maybe W10 doing smth bad..).

 

Anyway will let you know what happens after I checked cables and installed a new version.

[Helpless1]

@Lightning UK

 

Installed the new version and tried the Discovery mode.

Seems to be a driver problem, see log below.

But checking the device Manager says that the device is working properly and the best driver is already installed.

Also the log shows that data is written (disc also shows that so is useless after..). So guess that rules out the cable being faulty.

That is where it ends for me..

So any suggestions are very welcome.

 

Tia

 

 

I 13:41:39 ImgBurn Version 2.5.8.0 started!
I 13:41:39 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 13:41:39 Total Physical Memory: 16,766,700 KiB  -  Available: 9,181,516 KiB
I 13:41:39 Initialising SPTI...
I 13:41:39 Searching for SCSI / ATAPI devices...
I 13:41:39 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI)
I 13:41:39 -> Drive 2 - Info: Optiarc DVD RW AD-7260S 1.03 (I:) (RAID)
I 13:41:39 -> Drive 3 - Info: HL-DT-ST BD-RE  BH16NS40 1.01-A1 (G:) (ATA)
I 13:41:39 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!
I 13:43:03 Operation Started!
I 13:43:03 Source File: -==/\/[DISCOVERY IMAGE]\/\==-
I 13:43:03 Source File Sectors: 12,219,392 (MODE1/2048)
I 13:43:03 Source File Size: 25,025,314,816 bytes
I 13:43:03 Source File Volume Identifier: IMGBURN_DISCOVERY_IMAGE
I 13:43:03 Source File Volume Set Identifier: 12219392_SECTORS
I 13:43:03 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!
I 13:43:03 Source File Implementation Identifier: ImgBurn v2.5.8.0
I 13:43:03 Source File File System(s): ISO9660
I 13:43:03 Destination Device: [4:0:0] HL-DT-ST BD-RE  BH16NS40 1.01 (G:) (ATA)
I 13:43:03 Destination Media Type: BD-R (Disc ID: RITEK-BR2-000)
I 13:43:03 Destination Media Supported Write Speeds: 4x, 6x, 8x, 10x
I 13:43:03 Destination Media Sectors: 12,219,392
I 13:43:03 Write Mode: BD
I 13:43:03 Write Type: DAO
I 13:43:03 Write Speed: 6x
I 13:43:03 Hardware Defect Management Active: No
I 13:43:03 BD-R Verify Not Required: Yes
I 13:43:03 Link Size: Auto
I 13:43:03 Lock Volume: Yes
I 13:43:03 Test Mode: No
I 13:43:04 OPC: No
I 13:43:04 BURN-Proof: Enabled
I 13:43:04 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x)
I 13:43:04 Filling Buffer... (250 MiB)
I 13:43:04 Writing LeadIn...
I 13:43:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 12219391)
I 13:43:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12219391)
W 13:47:00 Failed to Write Sectors 2739392 - 2739423 - Reason: Logical Unit Communication CRC Error (ULTRA-DMA/32)
W 13:47:00 Retrying (1 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Potential Bogus Driver Error Detected!
W 13:47:02 Retrying (2 of 20)...
I 13:47:02 Writing Sectors...
W 13:47:02 Failed to Write Sectors 2739424 - 2739455 - Reason: Invalid Address For Write
W 13:47:02 Retrying (1 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (2 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (3 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (4 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (5 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (6 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (7 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (8 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (9 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (10 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (11 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (12 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (13 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (14 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (15 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (16 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (17 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (18 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (19 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
W 13:47:02 Retrying (20 of 20)...
W 13:47:02 Retry Failed - Reason: Invalid Address For Write
E 13:47:13 Failed to Write Sectors 2739424 - 2739455 - Reason: Invalid Address For Write
E 13:47:13 Next Writable Address: 2739424
I 13:47:14 Synchronising Cache...
I 13:47:19 Closing Track...
I 13:47:20 Finalising Disc...
E 13:47:34 Failed to Write Image!
I 13:47:34 Exporting Graph Data...
I 13:47:34 Graph Data File: C:\Users\Jaap\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.01_TUESDAY-APRIL-5-2016_1-43_PM_RITEK-BR2-000_6x.ibg
I 13:47:34 Export Successfully Completed!
E 13:47:34 Operation Failed! - Duration: 00:04:30
I 13:47:34 Average Write Rate: 23,717 KiB/s (5.4x) - Maximum Write Rate: 26,542 KiB/s (6.0x)
 

Edited April 5, 2016 by Helpless1

[LIGHTNING UK!]

Right click the drive selection box and pick 'family tree'. Close the prompt that comes up and copy + paste everything from the log window again please.

[Helpless1]

Ok, done that. Here comes:

 

; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Tuesday, 05 April 2016, 16:56:49
; \\****************************************//
;
;
I 16:52:57 ImgBurn Version 2.5.8.0 started!
I 16:52:57 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 16:52:57 Total Physical Memory: 16,766,700 KiB  -  Available: 9,687,052 KiB
I 16:52:57 Initialising SPTI...
I 16:52:57 Searching for SCSI / ATAPI devices...
I 16:52:57 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI)
I 16:52:57 -> Drive 2 - Info: Optiarc DVD RW AD-7260S 1.03 (I:) (RAID)
I 16:52:57 -> Drive 3 - Info: HL-DT-ST BD-RE  BH16NS40 1.01-A1 (G:) (ATA)
I 16:52:57 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!
I 16:53:09 Device: [4:0:0] HL-DT-ST BD-RE  BH16NS40 1.01 (G:) (ATA)
I 16:53:09 Family Tree:
I 16:53:09 -> ACPI x64-based PC
I 16:53:09 -> Microsoft ACPI-Compliant System
I 16:53:09 -> PCI Express Root Complex
I 16:53:09 -> Intel® ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26 (VEN_8086&DEV_3A26 - Intel - intelide - v9.1.9.1005)
I 16:53:09 -> IDE Channel (ATA Channel 0)
I 16:53:09 -> CD-ROM Drive (HL-DT-ST BD-RE  BH16NS40 ATA Device) (Channel 0, Target 0, Lun 0)
I 16:53:58 Device: [4:0:0] HL-DT-ST BD-RE  BH16NS40 1.01 (G:) (ATA)
I 16:53:58 Family Tree:
I 16:53:58 -> ACPI x64-based PC
I 16:53:58 -> Microsoft ACPI-Compliant System
I 16:53:58 -> PCI Express Root Complex
I 16:53:58 -> Intel® ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26 (VEN_8086&DEV_3A26 - Intel - intelide - v9.1.9.1005)
I 16:53:58 -> IDE Channel (ATA Channel 0)
I 16:53:58 -> CD-ROM Drive (HL-DT-ST BD-RE  BH16NS40 ATA Device) (Channel 0, Target 0, Lun 0)
I 16:56:49 Close Request Acknowledged
I 16:56:49 Closing Down...
I 16:56:49 Shutting down SPTI...
I 16:56:49 ImgBurn closed!

 

Installed new firmware and reinstalled the driver: same problem.

Tried another program (sorry, do not like that one anyway but wanted to make sure it was not that): also crashes.

Edited April 5, 2016 by Helpless1

[LIGHTNING UK!]

There are a few things I'd try, but you'll have to ignore that you've not touched anything and just go with it. Things can just fail for no reason.

 

So...

 

Try another port on the MB - stick to the Intel chipset and not any 3rd party one that might also be present.

Try another cable (take it out of your other optical drive if need be).

Make sure you have the latest bios installed for your MB.

Try the SATA controller in AHCI mode rather than IDE/ATA.

Try the drive in another PC.

[Helpless1]

Found something more:

 

In the device manager under "Events" tab it says:

 

Device IDE\CdRomHL-DT-ST_BD-RE__BH16NS40________________1.03____\5&29da22f6&0&0.0.0 could not be migrated.

Last Device Instance Id: IDE\CDROMHL-DT-ST_BD-RE__BH12LS30________________1.00____\5&29DA22F6&0&0.0.0
Class Guid: {4D36E965-E325-11CE-BFC1-08002BE10318}
Location Path:
Migration Rank: 0xF000F8000000F020
Present: false
Status: 0xC0000719

 

Looks like a W10 error but again: too difficult for me to solve.

 

Guess this comes from installing the new firmware. So added another problem..

Edited April 5, 2016 by Helpless1