moldeywaffle Posted February 10, 2016 Posted February 10, 2016 Hello all, I'm very new here and decided to post my problem because Google has turned up no working fixes. I have a 25 disc spindle of VERBAT-IMe-000 discs and an external pioneer bdr-xd05b burner. With this batch of discs and burner I have been able to go through about a third of the spindle with out any problems what so ever. Everything was working flawlessly. All of sudden, though, I start getting this power calibration error before the disc can get to even 1% burn. This was not just a single bad disc. Every time a try to burn now, I get this error. I've tried reducing speed and even bought a laser cleaning disc, to no avail. It is also not a corrupt file, I've tried to burn multiple different iso files and folders and they've all failed. What I found particularly strange is that, as a test, I tried burning something to a spare Verbatim DVD+R DL disc and it worked perfectly. Therefore, it can't be the drive that is the issue. Could it be that the entire bottom 2/3rd of the spindle of BD discs are garbage? Isn't Verbatim supposed to be the best discs out there? Perhaps there is some setting I changed that is messing up BDs but DVDs are fine. I also had to cancel the write b/c the retries were not capping at 20 like normal but going on forever. Any help would be appreciated. I am very confused. I 12:28:33 ImgBurn Version 2.5.8.0 started! I 12:28:33 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 12:28:33 Total Physical Memory: 16,692,716 KiB - Available: 14,271,772 KiB I 12:28:33 Initialising SPTI... I 12:28:33 Searching for SCSI / ATAPI devices... I 12:28:33 -> Drive 1 - Info: PIONEER BD-RW BDR-XD05 3.01-ID34 (H:) (USB 2.0) I 12:28:34 -> Drive 2 - Info: Slimtype DVD A DS8A9SH EAA2 (G:) (SATA) I 12:28:34 Found 1 DVD±RW/RAM and 1 BD-RE XL! I 12:32:40 Operation Started! I 12:32:40 Source File: I:\Yub Nub\ROTJ.iso I 12:32:40 Source File Sectors: 11,078,880 (MODE1/2048) I 12:32:40 Source File Size: 22,689,546,240 bytes I 12:32:40 Source File Volume Identifier: Return of the Jedi I 12:32:40 Source File Volume Set Identifier: 28AE5BE7 Return of the Jedi I 12:32:40 Source File Application Identifier: tsMuxeR 2.6.12 I 12:32:40 Source File Implementation Identifier: tsMuxeR 220e7816 I 12:32:40 Source File File System(s): UDF (2.50) I 12:32:40 Destination Device: [0:0:0] PIONEER BD-RW BDR-XD05 3.01 (H:) (USB) I 12:32:40 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 12:32:40 Destination Media Supported Write Speeds: 2x, 4x, 6x I 12:32:40 Destination Media Sectors: 12,219,392 I 12:32:40 Write Mode: BD I 12:32:40 Write Type: DAO I 12:32:40 Write Speed: 6x I 12:32:40 Hardware Defect Management Active: No I 12:32:40 BD-R Verify Not Required: Yes I 12:32:40 Link Size: Auto I 12:32:40 Lock Volume: Yes I 12:32:40 Test Mode: No I 12:32:40 OPC: No I 12:32:40 BURN-Proof: Enabled I 12:32:40 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x) I 12:32:40 Advanced Settings - Optimal Writing Speed: No I 12:32:40 Filling Buffer... (80 MiB) I 12:32:40 Writing LeadIn... I 12:32:40 Writing Session 1 of 1... (1 Track, LBA: 0 - 11078879) I 12:32:40 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11078879) W 12:32:59 Failed to Write Sectors 1248 - 1279 - Reason: Power Calibration Area Error W 12:32:59 Retrying (1 of 20)... I 12:32:59 Writing Sectors... W 12:33:00 Failed to Write Sectors 1472 - 1503 - Reason: Invalid Address For Write W 12:33:00 Retrying (1 of 20)... I 12:33:00 Writing Sectors... W 12:33:00 Failed to Write Sectors 1696 - 1727 - Reason: Invalid Address For Write W 12:33:00 Retrying (1 of 20)... I 12:33:00 Writing Sectors... W 12:33:01 Failed to Write Sectors 1920 - 1951 - Reason: Invalid Address For Write W 12:33:01 Retrying (1 of 20)... I 12:33:01 Writing Sectors... W 12:33:01 Failed to Write Sectors 2144 - 2175 - Reason: Invalid Address For Write W 12:33:01 Retrying (1 of 20)... I 12:33:01 Writing Sectors... W 12:33:02 Failed to Write Sectors 2368 - 2399 - Reason: Invalid Address For Write W 12:33:02 Retrying (1 of 20)... I 12:33:02 Writing Sectors... W 12:33:02 Failed to Write Sectors 2592 - 2623 - Reason: Invalid Address For Write W 12:33:02 Retrying (1 of 20)... I 12:33:02 Writing Sectors... W 12:33:03 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write W 12:33:03 Retrying (1 of 20)... I 12:33:03 Writing Sectors... W 12:33:03 Failed to Write Sectors 3040 - 3071 - Reason: Invalid Address For Write W 12:33:03 Retrying (1 of 20)... I 12:33:03 Writing Sectors... W 12:33:04 Failed to Write Sectors 3264 - 3295 - Reason: Invalid Address For Write W 12:33:04 Retrying (1 of 20)... I 12:33:04 Writing Sectors... W 12:33:04 Failed to Write Sectors 3488 - 3519 - Reason: Invalid Address For Write W 12:33:04 Retrying (1 of 20)... I 12:33:04 Writing Sectors... W 12:33:05 Failed to Write Sectors 3712 - 3743 - Reason: Invalid Address For Write W 12:33:05 Retrying (1 of 20)... I 12:33:05 Writing Sectors... W 12:33:05 Failed to Write Sectors 3936 - 3967 - Reason: Invalid Address For Write W 12:33:05 Retrying (1 of 20)... I 12:33:05 Writing Sectors... W 12:33:06 Failed to Write Sectors 4160 - 4191 - Reason: Invalid Address For Write W 12:33:06 Retrying (1 of 20)... I 12:33:06 Writing Sectors... W 12:33:06 Failed to Write Sectors 4384 - 4415 - Reason: Invalid Address For Write W 12:33:06 Retrying (1 of 20)... I 12:33:06 Writing Sectors... W 12:33:07 Failed to Write Sectors 4608 - 4639 - Reason: Invalid Address For Write W 12:33:07 Retrying (1 of 20)... I 12:33:07 Writing Sectors... W 12:33:07 Failed to Write Sectors 4832 - 4863 - Reason: Invalid Address For Write W 12:33:07 Retrying (1 of 20)... I 12:33:08 Writing Sectors... W 12:33:08 Failed to Write Sectors 5056 - 5087 - Reason: Invalid Address For Write W 12:33:08 Retrying (1 of 20)... I 12:33:08 Writing Sectors... W 12:33:09 Failed to Write Sectors 5280 - 5311 - Reason: Invalid Address For Write W 12:33:09 Retrying (1 of 20)... I 12:33:09 Writing Sectors... W 12:33:09 Failed to Write Sectors 5504 - 5535 - Reason: Invalid Address For Write W 12:33:09 Retrying (1 of 20)... I 12:33:09 Writing Sectors... W 12:33:10 Failed to Write Sectors 5728 - 5759 - Reason: Invalid Address For Write W 12:33:10 Retrying (1 of 20)... I 12:33:10 Writing Sectors... W 12:33:10 Failed to Write Sectors 5952 - 5983 - Reason: Invalid Address For Write W 12:33:10 Retrying (1 of 20)... I 12:33:10 Writing Sectors... W 12:33:11 Failed to Write Sectors 6176 - 6207 - Reason: Invalid Address For Write W 12:33:11 Retrying (1 of 20)... I 12:33:11 Writing Sectors... W 12:33:11 Failed to Write Sectors 6400 - 6431 - Reason: Invalid Address For Write W 12:33:11 Retrying (1 of 20)... I 12:33:11 Writing Sectors... W 12:33:12 Failed to Write Sectors 6624 - 6655 - Reason: Invalid Address For Write W 12:33:12 Retrying (1 of 20)... I 12:33:12 Writing Sectors... W 12:33:12 Failed to Write Sectors 6848 - 6879 - Reason: Invalid Address For Write W 12:33:12 Retrying (1 of 20)... I 12:33:12 Writing Sectors... W 12:33:13 Failed to Write Sectors 7072 - 7103 - Reason: Invalid Address For Write W 12:33:13 Retrying (1 of 20)... I 12:33:13 Writing Sectors... W 12:33:13 Failed to Write Sectors 7296 - 7327 - Reason: Invalid Address For Write W 12:33:13 Retrying (1 of 20)... I 12:33:13 Writing Sectors... W 12:33:14 Failed to Write Sectors 7520 - 7551 - Reason: Invalid Address For Write W 12:33:14 Retrying (1 of 20)... I 12:33:14 Writing Sectors... W 12:33:14 Failed to Write Sectors 7744 - 7775 - Reason: Invalid Address For Write W 12:33:14 Retrying (1 of 20)... I 12:33:14 Writing Sectors... W 12:33:15 Failed to Write Sectors 7968 - 7999 - Reason: Invalid Address For Write W 12:33:15 Retrying (1 of 20)... I 12:33:15 Writing Sectors... W 12:33:15 Failed to Write Sectors 8192 - 8223 - Reason: Invalid Address For Write W 12:33:15 Retrying (1 of 20)... I 12:33:15 Writing Sectors... W 12:33:16 Failed to Write Sectors 8416 - 8447 - Reason: Invalid Address For Write W 12:33:16 Retrying (1 of 20)... I 12:33:16 Writing Sectors... W 12:33:17 Failed to Write Sectors 8640 - 8671 - Reason: Invalid Address For Write W 12:33:17 Retrying (1 of 20)... I 12:33:17 Writing Sectors... W 12:33:17 Failed to Write Sectors 8864 - 8895 - Reason: Invalid Address For Write W 12:33:17 Retrying (1 of 20)... I 12:33:17 Writing Sectors... W 12:33:18 Failed to Write Sectors 9088 - 9119 - Reason: Invalid Address For Write W 12:33:18 Retrying (1 of 20)... I 12:33:18 Writing Sectors... W 12:33:18 Failed to Write Sectors 9312 - 9343 - Reason: Invalid Address For Write W 12:33:18 Retrying (1 of 20)... I 12:33:18 Writing Sectors... W 12:33:19 Failed to Write Sectors 9536 - 9567 - Reason: Invalid Address For Write W 12:33:19 Retrying (1 of 20)... I 12:33:19 Writing Sectors... W 12:33:19 Failed to Write Sectors 9760 - 9791 - Reason: Invalid Address For Write W 12:33:19 Retrying (1 of 20)... I 12:33:19 Writing Sectors... W 12:33:20 Failed to Write Sectors 9984 - 10015 - Reason: Invalid Address For Write W 12:33:20 Retrying (1 of 20)... I 12:33:20 Writing Sectors... W 12:33:20 Failed to Write Sectors 10208 - 10239 - Reason: Invalid Address For Write W 12:33:20 Retrying (1 of 20)... I 12:33:20 Writing Sectors... W 12:33:21 Failed to Write Sectors 10432 - 10463 - Reason: Invalid Address For Write W 12:33:21 Retrying (1 of 20)... I 12:33:21 Writing Sectors... W 12:33:21 Failed to Write Sectors 10656 - 10687 - Reason: Invalid Address For Write W 12:33:21 Retrying (1 of 20)... I 12:33:21 Writing Sectors... W 12:33:22 Failed to Write Sectors 10880 - 10911 - Reason: Invalid Address For Write W 12:33:22 Retrying (1 of 20)... I 12:33:22 Writing Sectors... W 12:33:22 Failed to Write Sectors 11104 - 11135 - Reason: Invalid Address For Write W 12:33:22 Retrying (1 of 20)... I 12:33:22 Writing Sectors... W 12:33:23 Failed to Write Sectors 11328 - 11359 - Reason: Invalid Address For Write W 12:33:23 Retrying (1 of 20)... I 12:33:23 Writing Sectors... W 12:33:23 Failed to Write Sectors 11552 - 11583 - Reason: Invalid Address For Write W 12:33:23 Retrying (1 of 20)... I 12:33:23 Writing Sectors... W 12:33:24 Failed to Write Sectors 11776 - 11807 - Reason: Invalid Address For Write W 12:33:24 Retrying (1 of 20)... I 12:33:24 Writing Sectors... W 12:33:24 Failed to Write Sectors 12000 - 12031 - Reason: Invalid Address For Write W 12:33:24 Retrying (1 of 20)... I 12:33:24 Writing Sectors... W 12:33:25 Failed to Write Sectors 12224 - 12255 - Reason: Invalid Address For Write W 12:33:25 Retrying (1 of 20)... I 12:33:25 Writing Sectors... W 12:33:26 Failed to Write Sectors 12448 - 12479 - Reason: Invalid Address For Write W 12:33:26 Retrying (1 of 20)... I 12:33:26 Writing Sectors... W 12:33:26 Failed to Write Sectors 12672 - 12703 - Reason: Invalid Address For Write W 12:33:26 Retrying (1 of 20)... I 12:33:26 Writing Sectors... W 12:33:27 Failed to Write Sectors 12896 - 12927 - Reason: Invalid Address For Write W 12:33:27 Retrying (1 of 20)... I 12:33:27 Writing Sectors... W 12:33:27 Failed to Write Sectors 13120 - 13151 - Reason: Invalid Address For Write W 12:33:27 Retrying (1 of 20)... I 12:33:27 Writing Sectors... W 12:33:28 Failed to Write Sectors 13344 - 13375 - Reason: Invalid Address For Write W 12:33:28 Retrying (1 of 20)... I 12:33:28 Writing Sectors... W 12:33:28 Failed to Write Sectors 13568 - 13599 - Reason: Invalid Address For Write W 12:33:28 Retrying (1 of 20)... I 12:33:28 Writing Sectors... W 12:33:29 Failed to Write Sectors 13792 - 13823 - Reason: Invalid Address For Write W 12:33:29 Retrying (1 of 20)... I 12:33:29 Writing Sectors... W 12:33:29 Failed to Write Sectors 14016 - 14047 - Reason: Invalid Address For Write W 12:33:29 Retrying (1 of 20)... I 12:33:29 Writing Sectors... W 12:33:30 Failed to Write Sectors 14240 - 14271 - Reason: Invalid Address For Write W 12:33:30 Retrying (1 of 20)... I 12:33:30 Writing Sectors... W 12:33:30 Failed to Write Sectors 14464 - 14495 - Reason: Invalid Address For Write W 12:33:30 Retrying (1 of 20)... I 12:33:30 Writing Sectors... W 12:33:31 Failed to Write Sectors 14688 - 14719 - Reason: Invalid Address For Write W 12:33:31 Retrying (1 of 20)... I 12:33:31 Writing Sectors... W 12:33:31 Failed to Write Sectors 14912 - 14943 - Reason: Invalid Address For Write W 12:33:31 Retrying (1 of 20)... I 12:33:31 Writing Sectors... W 12:33:32 Failed to Write Sectors 15136 - 15167 - Reason: Invalid Address For Write W 12:33:32 Retrying (1 of 20)... I 12:33:32 Writing Sectors... W 12:33:32 Failed to Write Sectors 15360 - 15391 - Reason: Invalid Address For Write W 12:33:32 Retrying (1 of 20)... I 12:33:32 Writing Sectors... W 12:33:33 Failed to Write Sectors 15584 - 15615 - Reason: Invalid Address For Write W 12:33:33 Retrying (1 of 20)... I 12:33:33 Writing Sectors... W 12:33:33 Failed to Write Sectors 15808 - 15839 - Reason: Invalid Address For Write W 12:33:34 Retrying (1 of 20)... I 12:33:34 Writing Sectors... W 12:33:34 Failed to Write Sectors 16032 - 16063 - Reason: Invalid Address For Write W 12:33:34 Retrying (1 of 20)... I 12:33:34 Writing Sectors... W 12:33:35 Failed to Write Sectors 16256 - 16287 - Reason: Invalid Address For Write W 12:33:35 Retrying (1 of 20)... I 12:33:35 Writing Sectors... W 12:33:35 Failed to Write Sectors 16480 - 16511 - Reason: Invalid Address For Write W 12:33:35 Retrying (1 of 20)... I 12:33:35 Writing Sectors... W 12:33:36 Failed to Write Sectors 16704 - 16735 - Reason: Invalid Address For Write W 12:33:36 Retrying (1 of 20)... I 12:33:36 Writing Sectors... W 12:33:36 Failed to Write Sectors 16928 - 16959 - Reason: Invalid Address For Write W 12:33:36 Retrying (1 of 20)... I 12:33:36 Writing Sectors... W 12:33:37 Failed to Write Sectors 17152 - 17183 - Reason: Invalid Address For Write W 12:33:37 Retrying (1 of 20)... I 12:33:37 Writing Sectors... W 12:33:37 Failed to Write Sectors 17376 - 17407 - Reason: Invalid Address For Write W 12:33:37 Retrying (1 of 20)... I 12:33:37 Writing Sectors... W 12:33:38 Failed to Write Sectors 17600 - 17631 - Reason: Invalid Address For Write W 12:33:38 Retrying (1 of 20)... I 12:33:38 Writing Sectors... W 12:33:38 Failed to Write Sectors 17824 - 17855 - Reason: Invalid Address For Write W 12:33:38 Retrying (1 of 20)... I 12:33:38 Writing Sectors... W 12:33:39 Failed to Write Sectors 18048 - 18079 - Reason: Invalid Address For Write W 12:33:39 Retrying (1 of 20)... I 12:33:39 Writing Sectors... W 12:33:39 Failed to Write Sectors 18272 - 18303 - Reason: Invalid Address For Write W 12:33:39 Retrying (1 of 20)... I 12:33:39 Writing Sectors... W 12:33:40 Failed to Write Sectors 18496 - 18527 - Reason: Invalid Address For Write W 12:33:40 Retrying (1 of 20)... I 12:33:40 Writing Sectors... W 12:33:40 Failed to Write Sectors 18720 - 18751 - Reason: Invalid Address For Write W 12:33:40 Retrying (1 of 20)... I 12:33:40 Writing Sectors... W 12:33:41 Failed to Write Sectors 18944 - 18975 - Reason: Invalid Address For Write W 12:33:41 Retrying (1 of 20)... I 12:33:41 Writing Sectors... W 12:33:41 Failed to Write Sectors 19168 - 19199 - Reason: Invalid Address For Write W 12:33:41 Retrying (1 of 20)... I 12:33:41 Writing Sectors... W 12:33:42 Failed to Write Sectors 19392 - 19423 - Reason: Invalid Address For Write W 12:33:42 Retrying (1 of 20)... I 12:33:42 Writing Sectors... W 12:33:43 Failed to Write Sectors 19616 - 19647 - Reason: Invalid Address For Write W 12:33:43 Retrying (1 of 20)... I 12:33:43 Writing Sectors... W 12:33:43 Failed to Write Sectors 19840 - 19871 - Reason: Invalid Address For Write W 12:33:43 Retrying (1 of 20)... I 12:33:43 Writing Sectors... W 12:33:44 Failed to Write Sectors 20064 - 20095 - Reason: Invalid Address For Write W 12:33:44 Retrying (1 of 20)... I 12:33:44 Writing Sectors... W 12:33:44 Failed to Write Sectors 20288 - 20319 - Reason: Invalid Address For Write W 12:33:44 Retrying (1 of 20)... I 12:33:44 Writing Sectors... W 12:33:45 Failed to Write Sectors 20512 - 20543 - Reason: Invalid Address For Write W 12:33:45 Retrying (1 of 20)... I 12:33:45 Writing Sectors... W 12:33:45 Failed to Write Sectors 20736 - 20767 - Reason: Invalid Address For Write W 12:33:45 Retrying (1 of 20)... I 12:33:45 Writing Sectors... W 12:33:46 Failed to Write Sectors 20960 - 20991 - Reason: Invalid Address For Write W 12:33:46 Retrying (1 of 20)... I 12:33:46 Writing Sectors... W 12:33:46 Failed to Write Sectors 21184 - 21215 - Reason: Invalid Address For Write W 12:33:46 Retrying (1 of 20)... I 12:33:46 Writing Sectors... W 12:33:47 Failed to Write Sectors 21408 - 21439 - Reason: Invalid Address For Write W 12:33:47 Retrying (1 of 20)... I 12:33:47 Writing Sectors... W 12:33:47 Failed to Write Sectors 21632 - 21663 - Reason: Invalid Address For Write W 12:33:47 Retrying (1 of 20)... I 12:33:47 Writing Sectors... W 12:33:48 Failed to Write Sectors 21856 - 21887 - Reason: Invalid Address For Write W 12:33:48 Retrying (1 of 20)... I 12:33:48 Writing Sectors... W 12:33:48 Failed to Write Sectors 22080 - 22111 - Reason: Invalid Address For Write W 12:33:48 Retrying (1 of 20)... I 12:33:48 Writing Sectors... W 12:33:49 Failed to Write Sectors 22304 - 22335 - Reason: Invalid Address For Write W 12:33:49 Retrying (1 of 20)... I 12:33:49 Writing Sectors... W 12:33:49 Failed to Write Sectors 22528 - 22559 - Reason: Invalid Address For Write W 12:33:49 Retrying (1 of 20)... I 12:33:49 Writing Sectors... W 12:33:50 Failed to Write Sectors 22752 - 22783 - Reason: Invalid Address For Write W 12:33:50 Retrying (1 of 20)... I 12:33:50 Writing Sectors... W 12:33:50 Failed to Write Sectors 22976 - 23007 - Reason: Invalid Address For Write W 12:33:50 Retrying (1 of 20)... I 12:33:50 Writing Sectors... W 12:33:51 Failed to Write Sectors 23200 - 23231 - Reason: Invalid Address For Write W 12:33:51 Retrying (1 of 20)... I 12:33:51 Writing Sectors... W 12:33:52 Failed to Write Sectors 23424 - 23455 - Reason: Invalid Address For Write W 12:33:52 Retrying (1 of 20)... I 12:33:52 Writing Sectors... W 12:33:52 Failed to Write Sectors 23648 - 23679 - Reason: Invalid Address For Write W 12:33:52 Retrying (1 of 20)... I 12:33:52 Writing Sectors... W 12:33:53 Failed to Write Sectors 23872 - 23903 - Reason: Invalid Address For Write W 12:33:53 Retrying (1 of 20)... I 12:33:53 Writing Sectors... W 12:33:53 Failed to Write Sectors 24096 - 24127 - Reason: Invalid Address For Write W 12:33:53 Retrying (1 of 20)... I 12:33:53 Writing Sectors... W 12:33:54 Failed to Write Sectors 24320 - 24351 - Reason: Invalid Address For Write W 12:33:54 Retrying (1 of 20)... I 12:33:54 Writing Sectors... W 12:33:54 Failed to Write Sectors 24544 - 24575 - Reason: Invalid Address For Write W 12:33:54 Retrying (1 of 20)... I 12:33:54 Writing Sectors... W 12:33:55 Failed to Write Sectors 24768 - 24799 - Reason: Invalid Address For Write W 12:33:55 Retrying (1 of 20)... I 12:33:55 Writing Sectors... W 12:33:55 Failed to Write Sectors 24992 - 25023 - Reason: Invalid Address For Write W 12:33:55 Retrying (1 of 20)... I 12:33:55 Writing Sectors... W 12:33:56 Failed to Write Sectors 25216 - 25247 - Reason: Invalid Address For Write W 12:33:56 Retrying (1 of 20)... I 12:33:56 Writing Sectors... W 12:33:56 Failed to Write Sectors 25440 - 25471 - Reason: Invalid Address For Write W 12:33:56 Retrying (1 of 20)... I 12:33:56 Writing Sectors... W 12:33:57 Failed to Write Sectors 25664 - 25695 - Reason: Invalid Address For Write W 12:33:57 Retrying (1 of 20)... I 12:33:57 Writing Sectors... W 12:33:57 Failed to Write Sectors 25888 - 25919 - Reason: Invalid Address For Write W 12:33:57 Retrying (1 of 20)... I 12:33:57 Writing Sectors... W 12:33:58 Failed to Write Sectors 26112 - 26143 - Reason: Invalid Address For Write W 12:33:58 Retrying (1 of 20)... I 12:33:58 Writing Sectors... W 12:33:58 Failed to Write Sectors 26336 - 26367 - Reason: Invalid Address For Write W 12:33:58 Retrying (1 of 20)... I 12:33:58 Writing Sectors... W 12:33:59 Failed to Write Sectors 26560 - 26591 - Reason: Invalid Address For Write W 12:33:59 Retrying (1 of 20)... I 12:33:59 Writing Sectors... W 12:33:59 Failed to Write Sectors 26784 - 26815 - Reason: Invalid Address For Write W 12:33:59 Retrying (1 of 20)... I 12:33:59 Writing Sectors... W 12:34:00 Failed to Write Sectors 27008 - 27039 - Reason: Invalid Address For Write I 12:34:00 Abort Request Acknowledged W 12:34:00 Retrying (1 of 20)... I 12:34:00 Synchronising Cache... I 12:34:10 Closing Track... W 12:34:21 Potential 'WaitImmediateIO' Deferred Error - (0/3) - Power Calibration Area Error W 12:34:21 Close Track Failed! - Reason: Power Calibration Area Error W 12:34:26 Close Track Failed! - Reason: Power Calibration Area Error I 12:34:26 Finalising Disc... E 12:34:48 Failed to Write Image! I 12:34:48 Exporting Graph Data... I 12:34:48 Graph Data File: C:\Users\Mike1\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-XD05_3.01_WEDNESDAY-FEBRUARY-10-2016_12-32_PM_VERBAT-IMe-000_6x.ibg I 12:34:48 Export Successfully Completed! E 12:34:48 Operation Aborted! - Duration: 00:02:08 I 12:34:48 Average Write Rate: 683 KiB/s (0.2x) - Maximum Write Rate: 900 KiB/s (0.2x)
dbminter Posted February 10, 2016 Posted February 10, 2016 How old is this drive? Have you burned many BD-R's before? It is entirely possible for a drive to work flawlessly on one media type but fail on another and still need replacing. In fact, my experience has been that when a drive needed replacing, it worked fine for other media but always failed for one particular type. For instance, no error on DVD-R but failing always on DVD+R DL. I've never had a single problematic burn with VERBAT-IMe media. It is entirely possible that your spindle may be bad but only at the 1/3rd mark does it start. I had my 2nd to last batch of DVD-R's where they were 16x but the first half only burned at 8x. The rest burned at 16x. Also, have you tried to power off the drive and powering it back on? A power cycle can sometimes clear up problems that have mysteriously popped up when things were working before. My experience has almost universally been that when things like this crop up, the drive needs replacing.
moldeywaffle Posted February 11, 2016 Author Posted February 11, 2016 (edited) I purchased the drive a little over a month ago, December 26th to be exact. If the drive has indeed failed after such a short amount of time, I will be very upset as I spent quite a bit of money on it. Is pioneer considered a junk brand among the community? I admit I could have perhaps done a bit more research before choosing which drive to buy. As to your second question, I have burnt about 8 blu rays so far, all successfully, all from the same batch of 25 verbatim discs. I've gotten into the hobby of burning BDs recently so this is the only batch of BD discs I've ever worked with. I had the DVD+R DL discs for files that didn't need so much space and burning to those still presents no issue. I have disconnected the drive and reconnected it from the computer if that's what you mean and the issue does still persist. I've been trying to fix this for days. I'm really hoping the drive's not dead. I am going to order another batch of discs and report back with results. Perhaps going with a different type of BD disc would do the trick since you said drives could stop working for some media and still work for others. I'm still a newbie and really only know about BD-R 25g discs. Any recommendations for what type of BD media would be best to try? Also I'm still scratching my head at the never ending "Retrying (1 of 20)" without ever going to (2 of 20). Edit: It looks like BD-RE might be the thing to get for testing purposes as it apparently is re-writable and thus there's no risk of making coasters. Is that accurate to say? And, if they fail It's most likely a drive issue which I'm hoping is not the case. Edited February 11, 2016 by moldeywaffle
dbminter Posted February 11, 2016 Posted February 11, 2016 I've 2 Pioneers, both the same drive, and they've been probably the best I've ever had. The older Pioneer is 2 years old and its only issue is sometimes when the eject button or an eject command is issued, it doesn't work on the first try. Well, there were initial problems burning DVD+R DL but those were eventually fixed a year later with a firmware update. By powering off the drive, I meant, if it's an internal drive, powering off the PC. If it's external, powering off the drive. The drive string of BDR-XD05 makes me think it's an external drive. But that's only a guess. Also, try restarting Windows. Powering off the PC would cycle Windows anyway since you have to shut down Windows, so you may as well just power off the PC entirely. If it's an external drive, cycle its power and then also restart Windows. The only other BD-R I ever tried were Memorex and Sony. Sony's are junk, as per their usual quality result. Memorex's are Ritek made which I had no burn problems with but I had playback issues with them on the Playstation 3. I've had no problems with the VERBAT-IM's on 2 LG's or my Pioneer. In my experience, LG's are fairly lousy readers and I believe they cause Ritek 8x DVD+RW to die before 20 rewrites. Unfortunately, you can't make an equation between something working on a BD-RE and then also working on a BD-R. However, it wouldn't hurt to have one BD-RE test. That way, if it fails on the BD-RE, too, you know there's something wrong with all BD media on this drive. It may work fine on a BD-RE but not on a BD-R. Plus, a full BD-RE test at its maximum 2x rate takes about 45 minutes to fill the entire disc, so it's fairly time consuming. Also, try seeing if there's a firmware update for this drive. In Write mode, right click on the drive in the destination drop down and choose the last option to check for firmware updates. If it is an external drive, be aware that the web site used for this check rarely finds the drive strings for external drives. I've never come across a firmware on that site for any external drive I've ever had. A firmware revision might improve your issue. As for a drive failing after so soon, it's not beyond the realm of possibility. I've had drives that only lasted 6 months before needing replacing. General time frame was a year. My first Pioneer is going on 2 years, which is a surprise to me. I once had a LiteOn DVD writer I had to return immediately after I got it. It wasn't writing properly from the moment I inserted it. My experience with that LiteOn, coupled with my first BD drive being a LiteOn that failed to write BD-RE after 3 months, and the fact that LiteOn's randomly add pauses to DVD+R DL video discs that aren't layer breaks swore me off of LiteOn.
moldeywaffle Posted February 11, 2016 Author Posted February 11, 2016 Unfortunately, you can't make an equation between something working on a BD-RE and then also working on a BD-R. However, it wouldn't hurt to have one BD-RE test. That way, if it fails on the BD-RE, too, you know there's something wrong with all BD media on this drive. It may work fine on a BD-RE but not on a BD-R. Plus, a full BD-RE test at its maximum 2x rate takes about 45 minutes to fill the entire disc, so it's fairly time consuming. Right, but it's also that I don't want to keep throwing out BD discs so getting BD-RE would mean not wasting the disc even if it fails b/c I can format it. I going to order those and report back in a few days. I've also acquired the latest firmware, to no avail, something I should have mentioned in my first post. And, yes, it is an external drive for my laptop.
dbminter Posted February 11, 2016 Posted February 11, 2016 I looked up the BDR-XD05 and one of the problems may be because it's a slim drive. Slim drives are notoriously error prone. If you're going to get an external drive, it should be a full size drive. I've not used a slim drive myself but from reports here and answers from other posters, slim drives are probably pretty much junk. The good thing about BD-RE is after the first format, even if you have a write that fails, there should be no need to reformat the disc. An erase should take care of that. Unless the drive is physically damaging the discs. Because a format takes about 45 minutes. 90 minutes if your drive supports that function my Pioneer doesn't where it takes twice as long to do a format.
moldeywaffle Posted February 16, 2016 Author Posted February 16, 2016 Major Update So I finally received a batch of 10 Verbatim BD-RE discs. I opened up imgburn, went through the long process of formatting and then 2x burning, and everything went smoothly. It was a successful burn. If sticking with BD-RE is the answer here then I suppose that's fine. However, there's no telling if this issue will rear its ugly head once again because my BD-Rs used to work fine and now they don't and the same could happen to these BD-REs. I just can't accept that an entire 2/3rds of a batch of Verbatim BD-Rs were junk and yet that seems to be the case. The only way to know for certain is to buy a another batch and see if the problem persists but for now I think I'll stick to the BD-REs I have left. I will come back to this thread should the same error start to occur with the BD-REs though I'm hoping that doesn't happen. A side question: What I burned to the BD-RE was Return of the Jedi Despecialized. Even though it plays back fine on my computer with PowerDVD, I am wondering if BD-REs will playback properly like a normal Blu-Ray movie in a regular TV Blu Ray player. I don't own one to test with but I want to burn copies for a few friends and I need to know if most TV Blu Ray players will playback BD-REs. The erasable nature of the discs makes me think that they would only work on PCs. Is that correct? What about on the PS4, Xbox, etc.
dbminter Posted February 16, 2016 Posted February 16, 2016 The issue of if BD-RE will play back on a standalone Blu-Ray player is down to a combination of the manufacturer of the BD-RE and your player. For instance, your BD-RE's, if they're Verbatim, are most likely CMC Magnetics discs. CMC Magnetics makes the worst optical media out there. Their recordable DVD's are notoriously high with error rates on this forum. Now, maybe their BD-RE's are okay. I don't know but I don't trust CMC. Anyway, if you want to know, put one in a PC Blu-Ray drive, open ImgBurn to Write mode, and check the info in the right box. If the DID/MID/Disc ID/Manufacturer ID says CMC anywhere in it, then you know it's the evil whose name shall not be spoken. As for playback compatibility issues, unfortunately, you'll only know if you test X disc in Y player. For instance, on the PS3, they don't like RITEK made BD-R or BD-RE. They don't read properly and so playback with skips. However, BD-RE's that Verbatim made themselves, which they stopped making last I checked and switched to CMC, play back fine. Also be aware that as rewritable discs, BD-RE's won't last as long on a shelf as BD-R's. Rewritable discs always have a shorter shelf life than WORM (Write Once Read Many) media. And on the playback compatibility front, BD-R's will generally have a better chance of playing back in a player versus a BD-RE. However, most modern players shouldn't care either way. A PC drive is more forgiving, though, so they'll play back more likely on a PC.
moldeywaffle Posted February 17, 2016 Author Posted February 17, 2016 Thanks for the info on BD-REs. I had no idea about Verbatim's outsourcing of that particular type of disc. Any brands you'd recommend for the future? Back to the issue at hand; I decided, for the hell of it, that I would try one last time to burn to one of my aforementioned BD-Rs that were giving me trouble. Low and behold, it worked. It was a successful burn and the film played back just fine. It was a bit strange because the device buffer never rose above 0%, which I thought would be a major issue, but the media burned just fine. I wasted somewhere around 7 BD-Rs in a row and all of sudden this one decided to work. I feel as though this must be a drive issue, like it has a high fail rate but can sometimes pull through. However, why DVD+Rs and BD-REs burn without issue, I can not say. Thanks for all the help. For the time being, I only wanted to burn Return of the Jedi for a friend and now that I have it on a BD-R, which I know should work on his Blu-Ray player, I'm all set. Sometime in the future I will most likely invest in a more reliable external drive. I'd imagine internal drives are probably the best of the best and what most people use, but if there are any external ones that you know are really good, I could use a recommendation. Thanks again for all the help.
dbminter Posted February 17, 2016 Posted February 17, 2016 Unfortunately, a drive can work with one type media and be fine but still need replacing because it doesn't work with another. For instance, the most common failure with drives is DVD+R DL yet DVD-R and DVD+RW will still work fine. I've seen that from experience. As for external Blu-Ray drives, I have actually just ordered my first one, an ASUS. It hasn't shipped yet so I don't know when it will arrive. As for recommendations of BD-RE's, most manufacturers use CMC for theirs, so I don't recommend them. I got some Panasonics that Panasonic made but my initial impression is iffy. The MID was good Panasonic variety, but my first test burn burned fine but when I went to write to the disc a 2nd time, it died.
dbminter Posted February 17, 2016 Posted February 17, 2016 After the ASUS, I would think about giving this a try. http://www.pioneerelectronics.com/PUSA/Computer/Computer+Drives/BDR-XU03 Only because I need drives I can set vertically due to space constraints. That's why I got the ASUS I am going to try. It's a full size external model that can be set vertically. The above Pioneer is a slim drive so there's always the danger that goes with those. Then there's also this one. http://www.pioneerelectronics.com/PUSA/Computer/Computer+Drives/BDR-XS06 Of course, I'm going with Pioneer drives because I had such success with my last one. This appears to be the drive you were already using. http://www.pioneerelectronics.com/PUSA/Computer/Computer+Drives/BDR-XD05S So, Pioneer still makes it for sale, but be aware that the internal model they sell now, the ones I have, were actually released about 2 years ago. So, Pioneer doesn't appear to have really up to date models. Although the other models I listed may be more recent.
moldeywaffle Posted February 24, 2016 Author Posted February 24, 2016 Thanks man. I'd be interested to hear about your experience with the Asus drive once you've spent sufficient time with it. It seems that only a few external drives are actually full sized ones (from what I've browsed). But like I said, the BD-Rs started working again so I don't need to purchase a new drive just yet, thankfully.
dbminter Posted February 24, 2016 Posted February 24, 2016 Yes, it is becoming harder and harder to find external full height burners. I think it will eventually get to the point where I'll have to buy an internal burner and an external USB 3.0 enclosure to put it in. Essentially build my own external burner from a mixture of internal and external parts. The seller finally just shipped it to me Monday. I think it was because I e-mailed him about the upcoming expected delivery date. I think it prompted him to finally send the drive. Don't know when it will arrive, though, as there's no associated tracking number on the shipment. The estimated delivery window is February 23 through the 26th. Basically, I can't really test it beyond running one test that is essential. Run a rewritable disc burn test to make sure the USB bridge is not prone to the semaphore time out error bug. It's caused by a conflict between the internal drive's USB bridge and the USB controller in your PC. The only fix is to replace either one. That fix is not easy so it's just easier to return the drive and try another one hoping it doesn't happen.
dbminter Posted February 26, 2016 Posted February 26, 2016 Well, the latest update is the package should arrive by UPS Tuesday. However, Amazon.com still lists the package as being delivered by USPS with no tracking number. However, I have a tracking number for UPS so that information seems to be most likely the most accurate. So, maybe I'll get it Tuesday; who knows?
dbminter Posted March 1, 2016 Posted March 1, 2016 Today should be a good day for testing the new drive. It's being delivered today and I have 3 discs I need to make. An 8x RICOH DVD+RW DVD Video disc, so that will be a playback in the PS3 test. A bootable data disc that needs verified contents in Macrium Reflect, so that's a good data read test. Lastly, writes to a formatted BD-RE DL followed by another Macrium Reflect data read verify in Windows. So, this is a fairly good cross section of various types of data and medium, for read and write tests.
dbminter Posted March 1, 2016 Posted March 1, 2016 Okay, drive arrived, it's installed, and is burning the 8x DVD+RW DVD Video disc. I couldn't find any firmware updates for the drive, but I've never seen a check for a firmware update for an external burner ever find one in the 11 years of my using ImgBurn. The good news is there was no semaphore timeout error when the burn started. The burn has completed and the tray cycled as I'm typing this. Verify has started so it's good so far. Verify completed. Haven't had a chance to watch the DVD in my PS3 test for a playback test yet. I'll forward that when I get to it which probably won't be until tomorrow.
dbminter Posted March 1, 2016 Posted March 1, 2016 Burning a 2nd DVD Video I didn't know I needed until now. Burn completed successfully; verify running. Verify seems a bit slow on this drive. It's been 1 minute and it's at 6x. I never paid attention before to how fast verify should be, though. Some drives are just slow readers. LG's are.
dbminter Posted March 1, 2016 Posted March 1, 2016 Performing a read test by reading the software disc that came with the drive to an image file. Then, I'll burn that file to a disc. Read to a file fine. Now to burn the file to a disc. Burn complete fine. Verifying now. Verify completed successfully. So, it seems, thus far, that 8x RICOH DVD+RW write and verify fine and Verbatim DataLife Plus CD-R write and verify fine in this ASUS drive. Next, the really slow 2x write to BD-RE that will be booted from and a Macrium Reflect verify run against its contents as the read test.
dbminter Posted March 1, 2016 Posted March 1, 2016 42 minutes of writing completed to 2x Memorex RITEK BD-RE SL. Verify has begun, 5 minutes have passed; 10 minutes remain. Verify completed successfully. Now to start a Macrium Reflect verify of its contents. Then, it will be out of Windows into the bootable recovery environment for Reflect. I'll also test booting from this USB drive, too. Macrium Reflect verify in Windows completed successfully. And about 22 GB of the available 25 were written to. Now to close down Windows and proceed from there. Another piece of good news. I was having problems with my old USB 2.0 DVD burner. While trying to read data under Windows 8, the drive would just disappear from Windows, killing the read. Powering off and on the drive returned it but it would disappear again after a little bit of reading. On Windows 10, this drive doesn't do that, but it is a USB 3.0 drive. Since it's on a different USB bridge, that could be the case. Or it may have been a Windows 8 only thing. Now that I'm on Windows 10, that problem may have disappeared. However, that drive needed swapping out, anyway. To show its age, it was LightScribe capable. Plus, it was a LiteOn. LiteOn's have a tendency to randomly add pauses into the playback of DVD+R DL's that aren't layer breaks. So, I've been phasing them out of buying in the future. Plus, the last one I had was one of their no longer made BD burners. It stopped writing to BD-RE after 3 months and out of 3 DVD+R DL DVD Video discs, 2 of them had the random pauses added to them. Reburning the same image did not have these pauses in them. But, it was something I'd noticed in LiteOns in the past with the DVD burners from them I used to buy.
dbminter Posted March 1, 2016 Posted March 1, 2016 Drive booted into Reflect recovery environment fine. Verify completed successfully. Now comes some deletion of files from a formatted Verbatim BD-RE DL, followed by a write of files to that same disc. Deletion completed successfully. A little under 21.5 GB is being written to the same disc now. At 2x, this will be about another 40 minute write. So, I'll rejoin this thread when that's done. After that, it will be another read test with another Macrium Reflect verify under Windows. After that, the only test left will be to playback test the 8x RICOH DVD+RW DVD Video in the PS3. I think I might get to it tonight instead of tomorrow, but I'm not sure.
dbminter Posted March 1, 2016 Posted March 1, 2016 Files successfully written to disc. Now performing Macrium Reflect verify. Verify completed successfully. So, all in all, these tests bode well for this drive. I still have to perform the DVD Video playback test. And I still have yet to burn BD-R, Blu-Ray movies, CD-RW, Audio CD, DVD+R DL, and DVD-RW. However I only perform these tests as I come across them. I could always test the rewritables because they can be reused. In fact, I can kill 2 birds with one stone like, for instance, burning an Audio CD to CD-RW. But, the WORM media can only be written to once so I'd be wasting a disc just for a test. So, if I can remember to, I'll test BD-R and DVD+R DL as I come across the need for them. I'll try to remember to post my results of the DVD Video test when I get to it either tonight or tomorrow.
dbminter Posted March 2, 2016 Posted March 2, 2016 Got a chance to test the DVD Video 8x RICOH DVD+RW DVD Video disc. While less than a GB was written to the disc, it played back fine on the PS3. So skips, pauses, hisses, or pops.
dbminter Posted March 3, 2016 Posted March 3, 2016 Had a chance to test a data Blu-Ray to Verbatim DataLife Plus inkjet BD-R. Disc ID: VERBAT-IMe-000. Burn started okay. Will take about 10 minutes, currently at 5.5x at 7% in. Burn completed okay. Verify completed okay. Now reading created BD-R to an image file in the same drive. Approximate time: 10 minutes. Read to an image file okay. Performing verify on some of its contents in other programs. Image files mounted to virtual drive fine. Verifies completed successfully. So, another test down. Just leaves DVD+R DL, data and DVD Video, DVD-RW, Audio CD, and CD-RW tests.
dbminter Posted March 3, 2016 Posted March 3, 2016 Came across a test I hadn't thought of. Needed some Audio CD tracks ripped to MP3 so I used the Asus drive as the source. No problem ripping. MP3 I tested played fine.
dbminter Posted March 5, 2016 Posted March 5, 2016 Had a chance to perform a DVD Video test so I chose to test a 4x Office Depot Ritek DVD-RW. Disc erase completed. LeadIn Write completed successfully. Burning now at 4x. Burnt successfully. Verify completed successfully. Reading to image file. Read successful. Mounted image file successfully. Image contents verified in a separate application. So, good test there.
Recommended Posts