jeff8 Posted November 2, 2015 Posted November 2, 2015 Hello, I am new to Imgburn and have used it a few times to burn blurays onto my Verbatim discs. However, I have been trying to burn a bluray but the reserve track appears once I start imgburn and does nothing. Here is the log" I 06:08:11 Size: 13,105,845,100 bytesI 06:08:11 Sectors: 6,399,361I 06:08:11 Image Size: 13,107,068,928 bytesI 06:08:11 Image Sectors: 6,399,936I 06:08:11 Operation Successfully Completed! - Duration: 00:00:00I 06:08:15 Operation Started!I 06:08:15 Building Image Tree...I 06:08:15 Calculating Totals...I 06:08:15 Preparing Image...I 06:08:15 Contents: 35 Files, 15 FoldersI 06:08:15 Content Type: BD VideoI 06:08:15 Data Type: MODE1/2048I 06:08:15 File System(s): UDF (2.50)I 06:08:15 Volume Label: Courtney and RyanI 06:08:15 Size: 13,105,845,100 bytesI 06:08:15 Sectors: 6,399,361I 06:08:15 Image Size: 13,107,068,928 bytesI 06:08:15 Image Sectors: 6,399,936I 06:08:15 Operation Successfully Completed! - Duration: 00:00:00I 06:08:27 Operation Started!I 06:08:27 Building Image Tree...I 06:08:27 Calculating Totals...I 06:08:27 Preparing Image...I 06:08:28 Contents: 35 Files, 15 FoldersI 06:08:28 Content Type: BD VideoI 06:08:28 Data Type: MODE1/2048I 06:08:28 File System(s): UDF (2.50)I 06:08:28 Volume Label: Courtney and RyanI 06:08:28 Size: 13,105,845,100 bytesI 06:08:28 Sectors: 6,399,361I 06:08:28 Image Size: 13,107,068,928 bytesI 06:08:28 Image Sectors: 6,399,936I 06:08:28 Operation Successfully Completed! - Duration: 00:00:00I 06:08:43 Operation Started!I 06:08:43 Building Image Tree...I 06:08:43 Calculating Totals...I 06:08:43 Preparing Image...I 06:08:44 Contents: 35 Files, 15 FoldersI 06:08:44 Content Type: BD VideoI 06:08:44 Data Type: MODE1/2048I 06:08:44 File System(s): UDF (2.50)I 06:08:44 Volume Label: Courtney and RyanI 06:08:44 Size: 13,105,845,100 bytesI 06:08:44 Sectors: 6,399,361I 06:08:44 Image Size: 13,107,068,928 bytesI 06:08:44 Image Sectors: 6,399,936I 06:08:58 Operation Successfully Completed! - Duration: 00:00:14I 06:08:58 Operation Started!I 06:08:58 Source File: -==/\/[bUILD IMAGE]\/\==-I 06:08:58 Source File Sectors: 6,399,936 (MODE1/2048)I 06:08:58 Source File Size: 13,107,068,928 bytesI 06:08:58 Source File Volume Identifier: Courtney and RyanI 06:08:58 Source File Volume Set Identifier: 476231150061A721I 06:08:58 Source File Application Identifier: ImgBurn v2.5.8.0I 06:08:58 Source File Implementation Identifier: ImgBurnI 06:08:58 Source File File System(s): UDF (2.50)I 06:08:58 Destination Device: [1:0:0] ASUS BW-16D1HT 1.01 (D:) (SATA)I 06:08:58 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000)I 06:08:58 Destination Media Supported Write Speeds: 4x, 6x, 8x, 10x, 12xI 06:08:58 Destination Media Sectors: 12,219,392I 06:08:58 Write Mode: BDI 06:08:58 Write Type: DAOI 06:08:58 Write Speed: 6xI 06:08:58 Hardware Defect Management Active: NoI 06:08:58 BD-R Verify Not Required: YesI 06:08:58 Link Size: AutoI 06:08:58 Lock Volume: YesI 06:08:58 Test Mode: NoI 06:08:58 OPC: NoI 06:08:58 BURN-Proof: EnabledI 06:08:58 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x) Could it be the discs? They are Verbatim data life plus
LIGHTNING UK! Posted November 2, 2015 Posted November 2, 2015 Boot into safe mode and see if you have the same problem.
jeff8 Posted November 2, 2015 Author Posted November 2, 2015 I will try that. Someone on this forum had a similar problem and this is what they did: I did the following: - Go to Control Panel -> Windows Update -> View Update History -> Installed Updates (link) - Removed the KB3001554 update - Rebooted I can now burn Blu-Ray discs again. Is this recommended?
LIGHTNING UK! Posted November 2, 2015 Posted November 2, 2015 I can't see that update making any difference to ImgBurn.
jeff8 Posted November 4, 2015 Author Posted November 4, 2015 Safe mode worked. I just tried it once and do not know if it will coninually work this way but it did the job when needed. Thank you.
LIGHTNING UK! Posted November 4, 2015 Posted November 4, 2015 If safe mode worked, it's more than likely your drivers for the controller are causing the issue - or a filter driver installed in the I/O chain somewhere.
Recommended Posts