BD-R DL burning fails

vbimport

#1

Hi everybody!

I will keep my message as short as I can…

I bought a new Pioneer BDR-S08XLT blu-ray writer. I also bought some BD-R DL spindles from a Japanese e-shop. They are That’s discs with MID TDKBLDRFB (000). I burned a few discs (one digit number) without particular problems (only one file got corrupted). All the other discs failed. The failure percentage was near 90%. They all failed without a single file written on them. I read in a forum (I think it was Club Myce) that many customers had problems with repackaged blu-ray discs so I decided to buy a new disc from a local shop. It was a TDK BD-R DL in a jewel case with MID TDKBLDRFB (000) (the same MID with the That’s discs). It failed too!

I use Ashampoo Burning Studio. I noticed that the buffer bar isn’t completely full when trying to write a disc which will fail. It always gets stuck before reaching 100% when a disc is going to fail.

I also tried a Panasonic disc with MID MEIT01 (001). It failed in the same manner.

I have burned successfully a Verbatim BD-RE (25 GB) disc multiple times with the Pioneer after the BD-R DL failures started and I have also tested the burner with DVD media. I can’t recall if I have used it with CDs. I didn’t have any other issues except the problem with the BD-R DL media.

So what is going on? Does the burner have a problem or the media? Is there a way for proper troubleshooting?

Thank you very much and Merry Christmas to you all!


#2

It sounds like you are using good quality media. You might try the Verbatim DL.

If you want to try another DL blu ray burn, I’d suggest using ImgBurn as the burning program and see if that helps.

What speed have you been burning at? If the discs are rated at 6x, you might try burning at 4x.


#3

[QUOTE=Kerry56;2714344]It sounds like you are using good quality media. You might try the Verbatim DL.

If you want to try another DL blu ray burn, I’d suggest using ImgBurn as the burning program and see if that helps.

What speed have you been burning at? If the discs are rated at 6x, you might try burning at 4x.[/QUOTE]

Hi [B]Kerry56[/B]!

The label of That’s discs spindle says 4x, but according to Opti Drive the discs support 2x, 4x, 6x and 8x. Ashampoo lists all these 4 different writing speeds, but I have tried only 2x and 4x with no luck. I have read that some people had issues with repackaged discs that have bought from Japanese retailers. That’s why I bought a TDK disc in a jewel case from a local store. As I said the TDK disc has the same MID with the That’s discs and it failed too.

I also bought some Panasonic BD-R DL discs from another Japanese online shop that support 2x writing speed according to both their label and Opti Drive. I tried to burn the first one but it failed without any files written on it [B]as it happened with the That’s and TDK discs[/B].

[B]I tried ImgBurn[/B] with the That’s discs but nothing changed. I don’t think that this is a software issue…

[B]But is it possible for the writer to burn well DVDs (including dual layer ones), BD-RE discs and have a problem [U]only[/U] with BD-R DLs or is it [U]definitely[/U] a media issue?[/B]


#4

Both TDKBLDRFB (000) and MEIT01 (001) DL media are problematic. You may obtain better results using the BDR-S08J-BK.


#5

[QUOTE=mariner8611;2714364]Both TDKBLDRFB (000) and MEIT01 (001) DL media are problematic. You may obtain better results using the BDR-S08J-BK.

Well I’m not thinking of changing the writer. I just bought it. (As I said it’s a [B]BDR-S08XLT[/B] which I believe it is a good writer).

But is there a possibility to be problematic in a way that makes it unable to write BD-R DL media but be OK with the other media types? Or is it definitely a media problem?


#6

It is possible for some drives to have issues with certain mid codes. This could be a writing strategy mismatch.

You could try the Verbatim discs, but we got a report about six months ago that Verbatim was switching to Panasonic for their DL blu ray media: http://club.myce.com/f33/verbatim-stopped-manufacturing-bluray-media-see-new-mid-codes-332766/


#7

[QUOTE=Kerry56;2714377]It is possible for some drives to have issues with certain mid codes. This could be a writing strategy mismatch.

You could try the Verbatim discs, but we got a report about six months ago that Verbatim was switching to Panasonic for their DL blu ray media: http://club.myce.com/f33/verbatim-stopped-manufacturing-bluray-media-see-new-mid-codes-332766/[/QUOTE]

What confuses me is that the first That’s discs were burned OK - if you exclude a corrupted file - and they had the same MID with the other ones that failed.

If the drive had issues with that MID, shouldn’t all the discs with the same MID fail?


#8

A completed burn doesn’t necessarily mean it was a particularly good burn. Absolute failures aren’t all that common though. Are you certain you don’t have other issues? Have you tried a different SATA port on the motherboard, or a different SATA data cable?

Do you have the latest firmware in this drive? The 1.30 was released in August of this year. http://www.pioneer-optical.eu/Download_Firmware-Download.asp


#9

[QUOTE=Kerry56;2714385]A completed burn doesn’t necessarily mean it was a particularly good burn. Absolute failures aren’t all that common though. Are you certain you don’t have other issues? Have you tried a different SATA port on the motherboard, or a different SATA data cable?

Do you have the latest firmware in this drive? The 1.30 was released in August of this year. http://www.pioneer-optical.eu/Download_Firmware-Download.asp[/QUOTE]

I have the latest firmware version now, yes. The problem started before I installed the latest version and continued after it.

I haven’t tried a different SATA port, but could this be the issue? As I said it burns OK other types of media like DVDs (DVD-RE & DVD+R DL) and BD-REs.

The only file written on the discs is a hidden desktop.ini file and nothing else… Then the recording fails…


#10

I’m just tossing a few ideas out there and seeing what sticks. I only mentioned the SATA port since you said you had problems with the buffer. There are only a limited number of things to try and improve the situation.

I don’t suppose the Imgburn log file shows anything useful? You can find it in ImgBurn under Help.


#11

That’s the info from ImgBurn for the drive and the disc (Panasonic):

PIONEER BD-RW BDR-S08 1.30 (ATA)
Current Profile: BD-R

Disc Information:
Status: Empty
State of Last Session: Empty
Erasable: No
Free Sectors: 24.438.784
Free Space: 50.050.629.632 bytes
Free Time: 5430:52:34 (MM:SS:FF)
Next Writable Address: 0
MID: MEI-T01-001
Supported Write Speeds: 2x

BD Disc Information (L0):
Disc ID: MEI-T01-001
Disc Type: BD-R
Disc Size: 120 mm
Disc Class: 0
Disc Version: 1
Disc Time Stamp: 12/2005
Number of Layers: 2
Layer Type: Writable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50 nm (25 GB Per Layer)
Push-Pull Polarity: Positive
Recorded Mark Polarity: HTL
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 131.072
Last PAA of Data Zone: 1.658.494

BD Disc Information (L1):
Disc ID: MEI-T01-001
Disc Type: BD-R
Disc Size: 120 mm
Disc Class: 0
Disc Version: 1
Disc Time Stamp: 12/2005
Number of Layers: 2
Layer Type: Writable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50 nm (25 GB Per Layer)
Push-Pull Polarity: Positive
Recorded Mark Polarity: HTL
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 2.535.808
Last PAA of Data Zone: 4.063.230

Format Capacities:
DT: 0x01 - NB: 24438784 (0x0174E800) - TDP: 413696
FT: 0x00 - NB: 23652352 (0x0168E800) - TDP: 24576
FT: 0x32 - NB: 23652352 (0x0168E800) - TDP: 0
FT: 0x32 - NB: 11200512 (0x00AAE800) - TDP: 0
FT: 0x32 - NB: 24307712 (0x0172E800) - TDP: 0

Performance (Write Speed):
Descriptor 1…
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 24438783 (0x0174E7FF)
-> RS: 8.990 KB/s (2x) - WS: 8.990 KB/s (2x)

And here is the log file from the last burning attempt which I had to abort because the procedure stalls:

I 20:06:01 ImgBurn Version 2.5.8.0 started!
I 20:06:01 Microsoft Windows Vista Business x64 Edition (6.0, Build 6002 : Service Pack 2)
I 20:06:01 Total Physical Memory: 12.572.852 KiB  -  Available: 7.747.212 KiB
W 20:06:01 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.
I 20:06:01 Initialising SPTI...
I 20:06:01 Searching for SCSI / ATAPI devices...
I 20:06:05 -> Drive 1 - Info: ASUS DRW-1814BL 1.14 (D:) (ATA)
I 20:06:09 -> Drive 2 - Info: PIONEER BD-RW   BDR-S08 1.30-ID43 (E:) (ATA)
I 20:06:09 -> Drive 3 - Info: YRC C1QZ4LA 1.03 (H:) (SCSI)
I 20:06:09 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!
I 20:06:50 Operation Started!
I 20:06:50 Building Image Tree...
I 20:06:50 Checking Directory Depth...
I 20:06:50 Calculating Totals...
I 20:06:50 Preparing Image...
I 20:06:50 Checking Path Length...
I 20:06:50 Contents: 50 Files, 16 Folders
I 20:06:50 Content Type: Data
I 20:06:50 Data Type: MODE1/2048
I 20:06:50 File System(s): ISO9660, UDF (1.02)
I 20:06:50 Volume Label:
I 20:06:50 Size: 55.772.595.433 bytes
I 20:06:50 Sectors: 27.232.741
I 20:06:50 Image Size: 55.773.429.760 bytes
I 20:06:50 Image Sectors: 27.233.120
I 20:06:50 Operation Successfully Completed! - Duration: 00:00:00
I 20:07:00 Operation Started!
I 20:07:00 Building Image Tree...
I 20:07:00 Checking Directory Depth...
I 20:07:00 Calculating Totals...
I 20:07:00 Preparing Image...
I 20:07:00 Checking Path Length...
I 20:07:00 Contents: 45 Files, 15 Folders
I 20:07:00 Content Type: Data
I 20:07:00 Data Type: MODE1/2048
I 20:07:00 File System(s): ISO9660, UDF (1.02)
I 20:07:00 Volume Label: 
I 20:07:00 Size: 47.260.481.015 bytes
I 20:07:00 Sectors: 23.076.432
I 20:07:00 Image Size: 47.261.286.400 bytes
I 20:07:00 Image Sectors: 23.076.800
I 20:07:00 Operation Successfully Completed! - Duration: 00:00:00
I 20:08:02 Operation Started!
I 20:08:02 Building Image Tree...
I 20:08:03 Checking Directory Depth...
I 20:08:03 Calculating Totals...
I 20:08:03 Preparing Image...
I 20:08:03 Checking Path Length...
I 20:08:03 Contents: 45 Files, 15 Folders
I 20:08:03 Content Type: Data
I 20:08:03 Data Type: MODE1/2048
I 20:08:03 File System(s): ISO9660, UDF (1.02)
I 20:08:03 Volume Label:
I 20:08:03 Size: 47.260.481.015 bytes
I 20:08:03 Sectors: 23.076.432
I 20:08:03 Image Size: 47.261.286.400 bytes
I 20:08:03 Image Sectors: 23.076.800
I 20:08:06 Operation Successfully Completed! - Duration: 00:00:03
I 20:08:06 Operation Started!
I 20:08:06 Source File: -==/\/[BUILD IMAGE]\/\==-
I 20:08:06 Source File Sectors: 23.076.800 (MODE1/2048)
I 20:08:06 Source File Size: 47.261.286.400 bytes
I 20:08:06 Source File Volume Identifier:
I 20:08:06 Source File Volume Set Identifier: 4398A10101601FB3
I 20:08:06 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!
I 20:08:06 Source File Implementation Identifier: ImgBurn
I 20:08:06 Source File File System(s): ISO9660; UDF (1.02)
I 20:08:06 Destination Device: [4:0:0] PIONEER BD-RW   BDR-S08 1.30 (E:) (ATA)
I 20:08:06 Destination Media Type: BD-R (Disc ID: MEI-T01-001)
I 20:08:06 Destination Media Supported Write Speeds: 2x
I 20:08:06 Destination Media Sectors: 24.438.784
I 20:08:06 Write Mode: BD
I 20:08:06 Write Type: DAO
I 20:08:06 Write Speed: 2x
I 20:08:06 Hardware Defect Management Active: No
I 20:08:06 BD-R Verify Not Required: Yes
I 20:08:06 Link Size: Auto
I 20:08:06 Lock Volume: Yes
I 20:08:06 Test Mode: No
I 20:08:06 OPC: No
I 20:08:06 BURN-Proof: Enabled
I 20:08:06 Write Speed Successfully Set! - Effective: 8.990 KB/s (2x)
I 20:08:06 Advanced Settings - Optimal Writing Speed: No
I 21:01:01 Abort Request Acknowledged


#12

You’re getting a warning message in Imgburn that I haven’t seen before.

[I]W 20:06:01 Duplex Secure’s SPTD driver can have a detrimental effect on drive performance.
[/I]


#13

[QUOTE=Kerry56;2714403]You’re getting a warning message in Imgburn that I haven’t seen before.

[I]W 20:06:01 Duplex Secure’s SPTD driver can have a detrimental effect on drive performance.
[/I]
http://forums.techguy.org/multimedia/972450-warning-imgburn-sptd-driver-how.html[/QUOTE]

Correct me if I’m wrong, but I think it has to do with the SPTD driver of Daemon tools and it isn’t a problem.


#14

Just pointing out the warning.

And Daemon tools has had a [B]long[/B] history of causing problems in optical drives. Do a Google search on the subject.

I never used Daemon tools myself, which is why I’ve never seen this error message in ImgBurn. When I needed a virtual drive, I always used Slysoft’s free program VirtualClone Drive. Windows 8, which I’m using now, has the ability to mount ISO’s natively.


#15

I may switch to another program, but I’m afraid that’s not the problem. I had Daemon Tools installed when I burned successfully the first That’s BD-R DLs.


#16
  1. [li]I uninstalled Daemon Tools and then the SPTD driver by using the official [B]installer/uninstaller[/B]. I don’t get the warning message from ImgBurn any more, but burning a Panasonic disc failed the same way as usual (with only the hidden desktop.ini file written on it).
    [/li][li]I also connected the Pioneer drive to another SATA port with no luck.
    [/li][li]As I said trying to burn a BD-R DL disc with Ashampoo fails with only a hidden dekstop.ini file written on it and trying to burn it with ImgBurn has no effect. The procedure stalls and I have to abort.
    [/li][li]To my surprise I was able to burn a [B]Test Disc[/B] with [B]Opti Drive[/B]. This is a screenshot from the creation of the disc (taken at the end of the procedure):
    [/li]


    I verified the test disc and the result was [B]0[/B] “Read error” and [B]0[/B] “Verify errors”.

    [B]So why Ashampoo and ImgBurn fail to burn data on these discs and Opti Drive succeeds to write the test data on them?[/B]

#17

The ODC screenshot seems…umm…well, normal, given the drive’s ability to verify the disc during the write process, though that doesn’t reflect what ImgBurn (and Ashampoo, I assume) do by writing continuously.

To reflect what the other software does by default, a setting can be changed in ODC: somewhere in the options, under Write Functions -> Streaming -> Enable check box. Enabling this means there will not be in-burn verification (only normal recalibrations will occur during the burn), and the burn will appear to occur at a ‘normal’ speed. If the burn succeeded in ODC, then it might still be some odd software conflict within the system.

(Conversely, to have ImgBurn try to match what ODC did in your screenshot would be a bit of a chore; an option to allow BD-R verification would have to be checked, and you would have to have ImgBurn pre-format the disc before the burn by doing a quick erase. That sounds rather difficult and may not be worth your time.)

Also…

It is possible the drive is broken. Or it is possible that something like the power supply within your system is causing some situation that the drive cannot handle with the difficult BD-R DL media, but can surprisingly tolerate for single layer BD-R and DVD+R DL. Is there any way to try another drive, or to try the current drive in another system?

Also also…

So when the burns fail, does the software tell you there was a failure, or does it just hang (as in the case above) and leave you with the barely-written disc?

One last also…

What are your system specifications? List hardware and software, if possible.


#18

[QUOTE=Albert;2714505]The ODC screenshot seems…umm…well, normal, given the drive’s ability to verify the disc during the write process, though that doesn’t reflect what ImgBurn (and Ashampoo, I assume) do by writing continuously.

To reflect what the other software does by default, a setting can be changed in ODC: somewhere in the options, under Write Functions -> Streaming -> Enable check box. Enabling this means there will not be in-burn verification (only normal recalibrations will occur during the burn), and the burn will appear to occur at a ‘normal’ speed. If the burn succeeded in ODC, then it might still be some odd software conflict within the system.

(Conversely, to have ImgBurn try to match what ODC did in your screenshot would be a bit of a chore; an option to allow BD-R verification would have to be checked, and you would have to have ImgBurn pre-format the disc before the burn by doing a quick erase. That sounds rather difficult and may not be worth your time.)

Also…

It is possible the drive is broken. Or it is possible that something like the power supply within your system is causing some situation that the drive cannot handle with the difficult BD-R DL media, but can surprisingly tolerate for single layer BD-R and DVD+R DL. Is there any way to try another drive, or to try the current drive in another system?

Also also…

So when the burns fail, does the software tell you there was a failure, or does it just hang (as in the case above) and leave you with the barely-written disc?

One last also…

What are your system specifications? List hardware and software, if possible.[/QUOTE]

The system is powered by a new 750 Watt Corsair PSU. Here are its specs:

I don’t have another blu-ray writer but I know it would be a good idea to try to burn the discs with another device… I’ll see what I can do. I’ll ask around to see if someone has one.

[B]I’m trying to figure out if it’s a drive problem or just an issue of the BD-R DLs itself![/B]

I don’t believe it’s a power issue… I don’t experience any problems under 100% CPU or GPU load or any kind of BSODs…

Ashampoo pops a message about a disc failure. ImgBurn seems to do nothing. I waited about an hour and then I tried to abort the writing, but the abortion also seemed to take much time, so I did a hard reset. The disc was still blank!


#19

While the process sorta hangs in ImgBurn, does the drive seem to be busy at all? As if it is still trying to do something, but just can’t? Like maybe the LED on the drive is still lit or blinking to indicate that it’s burning/accessing the disc, or you can maybe hear faint noises from the drive?


#20

[QUOTE=Albert;2714543]While the process sorta hangs in ImgBurn, does the drive seem to be busy at all? As if it is still trying to do something, but just can’t? Like maybe the LED on the drive is still lit or blinking to indicate that it’s burning/accessing the disc, or you can maybe hear faint noises from the drive?[/QUOTE]

No. The Led is off with ImgBurn. The same thing goes to Ashampoo, with the difference that Ashampoo after some minutes closes the disc (at that time the LED blinks) and a pop up message follows about the failure.