K3B has always had a notorious problem writing blu ray media. It crashes right at the end of the burn session. The resulting media is readable, but the session does not complete in a normal way. From what I have been able to find on the net, it appears that Red Hat has already come up with a fix for this problem in Fedora. So I have submitted a bug report on the issue -> https://bugs.mageia.org/show_bug.cgi?id=12424
In the past I have also noticed a problem with K3B being slow and not writing at the speed rated for the media in question while Nero writes at the full speed allowed. I have now learned the answer to this issue as well. To make a long story short, Nero is lying. They are both writing at the same speed. In the case of blu rays as opposed to CDs and DVDs, all writes to media get verified in real time as the writing progresses. Any write fails get corrected in real time. This means that the actual write speed can only be 1/2 of the rated write speed. K3B shows the real write speed, Nero shows the combined write/verify speed which is around twice the actual write speed.
I also just replaced a failing three year old Liteon drive [iHBS212] with a new LG drive [WH14NS40]. The LG drive works better with K3B in terms of real write speed, but both exhibit the close session failure. The Liteon drive worked perfectly with Nero 4, the LG drive will not do a successful write in non-multisession mode. It is rumored to work OK in multisession mode, but I haven't had a chance to check on that yet. I have not tried update firmware on the LG drive. I am still trying to recouperate from the losses I have already sustained with useless coasters. The LG drive DOES read the blu ray discs created on the Liteon drive OK and that was a relief.
I have dismantled the old drive and blown it out thoroughly with compressed air and am hoping that might put it back in working order. Saving it for a spare.
I am hoping that this information will prove helpful to anyone struggling with blu ray data disk information.