Is my Blu-ray drive now "bricked"?

[Slamma]

G'day!

I have a new (2 week old) Samsung SE-506CB external BD writer which I have used a total of three times, and now it will not read BD at all. The three movies I have played to convert to MKV were Live Free And Die Hard, Fury and San Andreas.

It is running via a separate powered USB hub, using new cables, and running the latest firmware and new PowerDVD 15 software. DVD's are still working ok, but BD's have completely stopped loading.

Debug log started at Wed Jan 13 09:21:32 2016 , written by MakeMKV v1.9.8 win(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.9.8 win(x86-release) started
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
003007:0000 Using direct disc access mode
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
DEBUG: Code 2147483648 at VL"xC|)_xx5{=@lf:121265315
DAFD=PAAAADAAAAEABDQkEHwECAQ==
DCE=gok+xXfIOuTl/GadPlx12rS0Fm7uWYqXKv7UAbJmw17mjOfCHbtA3q0D6NKk8npl7nXJsuVwzdefwSNJFpsNlnpDFqzIa6nZfDahmeUpDAulOvw+ys85PW7d8752y7NTLevYXPkE7uFPh83N36eLkN+nrqJapuu7sw==
DCE=Tn7nUQiANQVcis2zDJB38DZc1HMz+bDN+JeCSWL7eDYn7aFkz+aZsQYbgv31dWIZwmBsxRfMWN7VvezmmTVAZzEp0bS2OWSv6kBsNtgS6umRY+0gy4LCavGpz9Xc/91VfnvYLLpiyp3Ji0Vz0fBtvljoPpmyEJEPeA==
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:29396621
001003:0020 DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:29393930
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/AACS/Content001.cer' at offset '0'
001003:0020 DEBUG: Code 0 at VDi/EWNWCI+zHgp:29393930
001003:0020 DEBUG: Code 0 at VDi/EWNWCI+zHgp:213129961
001003:0020 DEBUG: Code 1 at VDi/EWNWCI+zHgp:29395310
005084:0000 Failed to load content hash table, unable to verify integrity of M2TS files.
DISCID=16C86309E75C68484C54B147F18A530555680C7F
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:213130904
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:213130904
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:213130904
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:213130904
001003:0020 DEBUG: Code 100941312 at 'o[,Qu9Zc~p25&7Z:121269731
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'
DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:213130904
001003:0020 DEBUG: Code 100941312 at t:*jz^+x"$<#d$f0G,:121262969
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT HAS NOT SELF-CONFIGURED YET' occurred while reading '/BDMV/STREAM/00099.m2ts' at offset '0'

From the research I've done here, It seems that the BD unit is now "bricked". If this is the case, does this mean that my new BD writer is now worthless and should be thrown out? Or do I just need to wait for an update from MakeMKV which will make it suddenly work again?

To be honest, I find that a BD writer becoming worthless despite using original store purchased BD movies utterly ridiculous. Just my 2c.

Thanks for any replies that can help!

Cheers!

[Woodstock]

"Latest firmware" is likely the problem. This is one reason I do not allow PowerDVD near my computers anymore, because it kept wanting to update the firmware on my drives. The primary reasons for updating firmware is to make the drives enforce new copy protections...

Can it still read BDs using PowerDVD, which uses a different AACS key than MakeMKV? What is the highest AACS version reported by MakeMKV?

[Slamma]

Hi there, thanks for your reply.

No, the Samsung BD writer won't play any BD discs at all ~ it just loads and spins and spins (tried about 10x different BD discs). The highest AACS version is 53 on MakeMKV.

When I say the "latest firmware" with the BD writer, I mean it's what came with it out of the box. I tried to do an update on it, but it said it was already on the newest one, which was "DVD150116".

I'm beginning to think the writer has just failed completely, but I'm not sure 100% as it still reads DVD discs and other installation discs just fine.

Thanks again for your help.

[Slamma]

Just to add, I have tried the BD writer on a 2nd computer, and it is doing the exact same thing, which makes me think the writer isn't working properly.

[Woodstock]

At 2 weeks old, I'd do a warranty claim on it.

[Slamma]

Yeah. I probably will. Just wanted to see if I had done anything wrong so I don't do it again.

Thanks.