theweasel49 Posted March 4, 2020 Share Posted March 4, 2020 Hello, Could someone please explain to me what happened during this burn? I use Windows 10. I 10:25:49 ImgBurn Version 2.5.8.0 started! I 10:25:49 Microsoft Windows 8 Unknown x64 Edition (0x0000007D) (6.2, Build 9200) I 10:25:49 Total Physical Memory: 33 513 220 KiB - Available: 30 519 604 KiB I 10:25:49 Initialising SPTI... I 10:25:49 Searching for SCSI / ATAPI devices... I 10:25:49 -> Drive 1 - Info: ASUS BW-16D1H-U A204 (F:) (SATA) I 10:25:49 Found 1 BD-RE XL! I 10:26:22 Operation Started! I 10:26:22 Source File: D:\TEMP_BLURAY\sauvegarde_01.iso I 10:26:22 Source File Sectors: 15 094 720 (MODE1/2048) I 10:26:22 Source File Size: 30 913 986 560 bytes I 10:26:22 Source File Volume Set Identifier: 07006BA3 I 10:26:22 Source File Application Identifier: tsMuxeR git-8cc357a I 10:26:22 Source File Implementation Identifier: tsMuxeR 3847de5d I 10:26:22 Source File File System(s): UDF (2.50) I 10:26:22 Destination Device: [0:0:0] ASUS BW-16D1H-U A204 (F:) (SATA) I 10:26:22 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 10:26:22 Destination Media Supported Write Speeds: 2x; 4x; 6x; 8x I 10:26:23 Destination Media Sectors: 24 438 784 I 10:26:23 Write Mode: BD I 10:26:23 Write Type: DAO I 10:26:23 Write Speed: MAX I 10:26:23 Hardware Defect Management Active: No I 10:26:23 BD-R Verify Not Required: Yes I 10:26:23 Link Size: Auto I 10:26:23 Lock Volume: Yes I 10:26:23 Test Mode: No I 10:26:23 OPC: No I 10:26:23 BURN-Proof: Enabled I 10:26:23 Write Speed Successfully Set! - Effective: 35 968 KB/s (8x) I 10:26:54 Filling Buffer... (80 MiB) I 10:26:54 Writing LeadIn... I 10:26:55 Writing Session 1 of 1... (1 Track, LBA: 0 - 15094719) I 10:26:55 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 15094719) I 10:26:55 Writing Layer 0... (LBA: 0 - 12219391) W 10:38:07 Failed to Write Sectors 8730208 - 8730239 - Reason: Invalid Field in CDB W 10:38:07 Retrying (1 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (2 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (3 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (4 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (5 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (6 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (7 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (8 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (9 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (10 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (11 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (12 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (13 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (14 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (15 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:07 Retrying (16 of 20)... W 10:38:07 Retry Failed - Reason: Invalid Field in CDB W 10:38:08 Retrying (17 of 20)... W 10:38:08 Retry Failed - Reason: Invalid Field in CDB W 10:38:08 Retrying (18 of 20)... W 10:38:08 Retry Failed - Reason: Invalid Field in CDB W 10:38:08 Retrying (19 of 20)... W 10:38:08 Retry Failed - Reason: Invalid Field in CDB W 10:38:08 Retrying (20 of 20)... W 10:38:08 Retry Failed - Reason: Invalid Field in CDB E 10:44:00 Failed to Write Sectors 8730208 - 8730239 - Reason: Invalid Field in CDB I 10:44:00 Synchronising Cache... W 10:44:00 Synchronise Cache Failed! - Reason: Invalid Field in CDB W 10:44:07 Retrying (1)... W 10:44:08 Retrying (2)... W 10:44:08 Retrying (3)... W 10:44:08 Retry Failed - Reason: Invalid Field in CDB W 10:44:08 Retrying (4)... W 10:44:08 Retry Failed - Reason: Invalid Field in CDB W 10:44:09 Retrying (5)... W 10:44:09 Retry Failed - Reason: Invalid Field in CDB I 10:44:17 Closing Track... W 10:44:17 Close Track Failed! - Reason: Invalid Field in CDB W 10:44:20 Close Track Failed! - Reason: Invalid Field in CDB I 10:44:20 Finalising Disc... W 10:44:20 Finalise Disc Failed! - Reason: Invalid Field in CDB W 10:44:20 Finalise Disc Failed! - Reason: Invalid Field in CDB E 10:44:20 Failed to Write Image! I 10:44:20 Exporting Graph Data... I 10:44:20 Graph Data File: C:\Users\Thib\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1H-U_A204_MERCREDI-4-MARS-2020_10-26_VERBAT-IMf-000_MAX.ibg I 10:44:20 Export Successfully Completed! E 10:44:20 Operation Failed! - Duration: 00:17:57 I 10:44:20 Average Write Rate: 17 051 KiB/s (3.9x) - Maximum Write Rate: 31 376 KiB/s (7.1x) Link to comment Share on other sites More sharing options...
dbminter Posted March 4, 2020 Share Posted March 4, 2020 Well, you're using the good BD-R from Verbatim and not CMC Verbatm BD-R, so that's a start. That would generally mean there's probably a conflict between your burner's firmware and that kind of media. You could try and see if there's a firmware update for your burner, but there probably isn't. The only other solution is to try a different BD burner from another manufacturer or another model number and see if that helps. I had an ASUS BW-16D1H internal model, I believe. I don't remember if I used it long enough to try BD-R in because my first tests were abysmal with that drive. It constantly destroyed rewritable media! 8x Ritek DVD+RW and Verbatim 2x BD-RE non CMC. So, I sent the drive back for a replacement. That drive did the same thing so it was a firmware/hardware issue. Link to comment Share on other sites More sharing options...
theweasel49 Posted March 5, 2020 Author Share Posted March 5, 2020 2 hours ago, dbminter said: Well, you're using the good BD-R from Verbatim and not CMC Verbatm BD-R, so that's a start. That would generally mean there's probably a conflict between your burner's firmware and that kind of media. You could try and see if there's a firmware update for your burner, but there probably isn't. The only other solution is to try a different BD burner from another manufacturer or another model number and see if that helps. I had an ASUS BW-16D1H internal model, I believe. I don't remember if I used it long enough to try BD-R in because my first tests were abysmal with that drive. It constantly destroyed rewritable media! 8x Ritek DVD+RW and Verbatim 2x BD-RE non CMC. So, I sent the drive back for a replacement. That drive did the same thing so it was a firmware/hardware issue. Thanks for the answer, I already have the latest firmware from the ASUS website... The BD-R I used was actually a Mediarange 50Gb (french amazon link), I know they display "VERBAT-IMf-000" in Imgburn but I'm not sure if they really are the same. But I also have some real Verbatim 25Gb/50Gb (Real package + VERBAT-IMf-000) and they go through the same type of invalid CDB errors. This is already the second drive that I try on this computer, at first I bought a slim laptop BD burner and an external USB case and I had a really rough time to complete any BD burn, high fail rate with a lot of I/O write error / CDB errors. I then read on this forum that slim drive + USB are crap so I told myself OK let's not play it cheap, I sent the slim drive back and bought the Asus BW-16D1H-U PRO USB (link). With this one I managed to write a BD-R daily without a problem for a week, miracle! Except that it didn't last CDB errors came back, only less often than with the previous burner. I kept burning BD-R for the past 2 month with the occasional inexplicable CBD error (super frustrating of course). I tried some tricks I read here and there : change write mode to Incremental instead of SAO / add "perform OPC Before Write" option / reduce burn speed / Close Windows Defender anti-virus during a burn... -> I doubt any of those had influence on the problem. Since I got the ASUS I successfully burned 41 BD-R and failed 15. I also read a lot on forums that USB is unreliable for burners so I thought the problem might come from that. 2 days ago while cleaning my PC tower I discovered 2 unused SATA port on my motherboard, hidden behind my graphic card... the only reason I went for a USB burner in the first place is because I believed there was no more free SATA port on the mb... Yes I am a gigantic fool Anyway I decided to extract the ASUS BW-16D1H-U drive from its USB case and put it directly in the tower connected with a SATA cable. Went OK and I burned a BD-R perfectly afterward. I hoped it was the end of it but NOPE, next burn was the failure in my first post... Are you sure that the problem will go away if I change the burner again? As you can imagine my little Bluray burning adventure is starting to cost me a lot more €€€ than anticipated If the answer is yes do you have any recommendation for brands / models? Link to comment Share on other sites More sharing options...
dbminter Posted March 5, 2020 Share Posted March 5, 2020 No, I can't guarantee anything, unfortunately. I use a VanTech USB 3.0 enclosure with the LG WH16NS60 without problems to the VERBAT-IM BD-R made by Verbatim. So, that's what I'd recommend. My tower doesn't have half height bays, so I had to USB route since most slim models are trash. Even the one that came with mine, while so far no problems writing, is a super slow writer. Writes 2 to 3 times slower than half height drives. You may be tempted to get the cheaper LG WH16NS40. I wouldn't recommend it if you ever plan on writing DL BD-RE or BD-R. I've seen several reports here, backed up by my experience with BD-RE DL, that the NS40 will fail Verify 9 times out of 10 with DL BD media. Which the NS60 does not. But, if you never plan on writing DL BD media, the NS40 passed all other tests I threw at it. Again, can I guarantee switching drives will fix the issue? No. But, I can say you won't know for sure unless you try switching drives. Link to comment Share on other sites More sharing options...
theweasel49 Posted March 5, 2020 Author Share Posted March 5, 2020 Okay, thanks, I'll check it out Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted March 5, 2020 Share Posted March 5, 2020 "Invalid field in CDB" is common after a retry of some sort - but then I'd expect to see a 'write error' before it and you don't appear to have one of those. I wonder if you're somehow missing out on the real error code. Perhaps a driver in the chain is swallowing it up and so it isn't reaching ImgBurn. Do you have anything in your filter driver list? You can view it (and copy+paste it) via the feature on the Tools menu. Link to comment Share on other sites More sharing options...
theweasel49 Posted March 5, 2020 Author Share Posted March 5, 2020 (edited) 8 hours ago, LIGHTNING UK! said: "Invalid field in CDB" is common after a retry of some sort - but then I'd expect to see a 'write error' before it and you don't appear to have one of those. I wonder if you're somehow missing out on the real error code. Perhaps a driver in the chain is swallowing it up and so it isn't reaching ImgBurn. Do you have anything in your filter driver list? You can view it (and copy+paste it) via the feature on the Tools menu. Hello, this is what I have in the Filter Drive Load Order menu : =============================================== Filter Driver Load Order - ImgBurn v2.5.8.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: PxHlpa64 Lower Device Filter: [None Found] Filter Name: PxHlpa64 File Name: C:\WINDOWS\system32\Drivers\PxHlpa64.sys File Version: 3.01.01.0 [3.1.1.0] File Description: Px Engine Device Driver for 64-bit (x86-64) Windows Product Name: PxHlpa64 Product Version: [3.1.1.0] Company Name: Corel Corporation Copyright: Copyright © Corel Corporation or its subsidiaries. All rights reserved. Edited March 5, 2020 by theweasel49 Link to comment Share on other sites More sharing options...
Recommended Posts