Jump to content

ImgBurn Support Forum uses cookies. Read the Privacy Policy for more info. To remove this message, please click the button to the right:    I accept the use of cookies

Photo

Fail to verify after burn


Forum Rules

Read the Guides forum if you don't know how to do something. :readbook:
If you have a question or a problem, check the FAQ and use the Search to see if you can find the answer for yourself. :lightbulb:
If you're having trouble burning double layer media, read Here.
Still stuck? Create a new thread and describe your issue in detail.
Make sure you include a copy of the program's log in your post. No log = :chair:


  • Please log in to reply
11 replies to this topic

#1 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 21 October 2017 - 12:26 PM

Hello everyone. I'm trying to burn a copy of the latest Windows 10 Fall Creators Update ISO (Win10_1709_English_x64.iso). There is no error while burning, but for verification, it failed to complete, prompted me with a few errors. Here are the details:

 

First, I use the Mitsubishi DTW47U1 DVD+RW disc. My burner drive is the LiteOn iHAS322-07. No error during burning. Error appear during verification. Here's the log (burn log and disc info).

 

psdvd08.jpg

I 03:37:39 ImgBurn Version 2.5.8.0 started!
I 03:37:39 Microsoft Windows 8 Unknown x64 Edition (0x00000079) (6.2, Build 9200)
I 03:37:39 Total Physical Memory: 8,329,072 KiB  -  Available: 7,147,856 KiB
I 03:37:39 Initialising SPTI...
I 03:37:39 Searching for SCSI / ATAPI devices...
I 03:37:39 -> Drive 1 - Info: ATAPI iHAS322 ZL13 (F:) (SATA)
I 03:37:39 Found 1 DVD±RW/RAM!
I 03:38:00 Operation Started!
I 03:38:00 Source Device: [0:0:0] ATAPI iHAS322 ZL13 (F:) (SATA)
I 03:38:00 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: MKM-A02-00)
I 03:38:00 Source Media Supported Read Speeds: 2.4x, 4x, 6x, 8x, 12x
I 03:38:00 Source Media Supported Write Speeds: 4x
I 03:38:00 Source Media Sectors: 2,295,104 (Track Path: PTP)
I 03:38:00 Source Media Size: 4,700,372,992 bytes
I 03:38:00 Image File: D:\Huge Installation Files\windows 10 home pro fall creators update 64 bit\Win10_1709_English_x64.iso
I 03:38:00 Image File Sectors: 2,293,634 (MODE1/2048)
I 03:38:00 Image File Size: 4,697,362,432 bytes
I 03:38:00 Image File Volume Identifier: CCCOMA_X64FRE_EN-US_DV9
I 03:38:00 Image File Volume Set Identifier: f0cc000
I 03:38:00 Image File Application Identifier: CDIMAGE 2.56 (01/01/2005 TM)
I 03:38:00 Image File Implementation Identifier: Microsoft CDIMAGE UDF
I 03:38:00 Image File File System(s): ISO9660 (Bootable), UDF (1.02)
I 03:38:00 Read Speed (Data/Audio): MAX / MAX
I 03:38:01 Read Speed - Effective: 4.8x - 12x
I 03:38:01 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2293633)
I 03:38:01 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2293633)
W 03:44:15 Failed to Read Sectors 2049824 - 2049855 - Reason: L-EC Uncorrectable Error
W 03:44:24 Failed to Read Sector 2049824 - Reason: L-EC Uncorrectable Error
W 03:44:24 Sector 2049824 maps to File: \sources\install.wim
E 03:44:43 Failed to Read Sector 2049824 - Reason: L-EC Uncorrectable Error
E 03:44:43 Sector 2049824 maps to File: \sources\install.wim
E 03:44:43 Failed to Verify Sectors!
I 03:44:44 Exporting Graph Data...
I 03:44:44 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS322_ZL13_SATURDAY-OCTOBER-21-2017_3-38_AM_MKM-A02-00.ibg
I 03:44:44 Export Successfully Completed!
E 03:44:44 Operation Failed! - Duration: 00:06:43
I 03:44:44 Average Verify Rate: 10,198 KiB/s (7.5x) - Maximum Verify Rate: 15,570 KiB/s (11.5x)
Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Formatted: Yes
Sessions: 1
Sectors: 2,295,104
Size: 4,700,372,992 bytes
Time: 510:03:29 (MM:SS:FF)
MID: MKM-A02-00
Supported Read Speeds: 4x, 6x, 8x
Current Read Speed: 2.5x - 6x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2295103)
-> LeadOut  (LBA: 2295104)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 0)

Physical Format Information (ADIP):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

I thought it could be bad media. I tried a Verbatim 43228 DVD+RW disc. My burner drive is the same LiteOn iHAS322-07. No error during burning. Error appear during verification. Here's the log (burn log and disc info).

 

dvdplusrw_verbatim_43228_2007_pre.png

I 03:47:52 ImgBurn Version 2.5.8.0 started!
I 03:47:52 Microsoft Windows 8 Unknown x64 Edition (0x00000079) (6.2, Build 9200)
I 03:47:52 Total Physical Memory: 8,329,072 KiB  -  Available: 7,108,128 KiB
I 03:47:52 Initialising SPTI...
I 03:47:52 Searching for SCSI / ATAPI devices...
I 03:47:52 -> Drive 1 - Info: ATAPI iHAS322 ZL13 (F:) (SATA)
I 03:47:52 Found 1 DVD±RW/RAM!
I 03:48:22 Operation Started!
I 03:48:22 Source Device: [0:0:0] ATAPI iHAS322 ZL13 (F:) (SATA)
I 03:48:22 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: MKM-A02-00)
I 03:48:22 Source Media Supported Read Speeds: 2.4x, 4x, 6x, 8x, 12x
I 03:48:22 Source Media Supported Write Speeds: 4x
I 03:48:22 Source Media Sectors: 2,295,104 (Track Path: PTP)
I 03:48:22 Source Media Size: 4,700,372,992 bytes
I 03:48:22 Image File: D:\Huge Installation Files\windows 10 home pro fall creators update 64 bit\Win10_1709_English_x64.iso
I 03:48:22 Image File Sectors: 2,293,634 (MODE1/2048)
I 03:48:22 Image File Size: 4,697,362,432 bytes
I 03:48:22 Image File Volume Identifier: CCCOMA_X64FRE_EN-US_DV9
I 03:48:22 Image File Volume Set Identifier: f0cc000
I 03:48:22 Image File Application Identifier: CDIMAGE 2.56 (01/01/2005 TM)
I 03:48:22 Image File Implementation Identifier: Microsoft CDIMAGE UDF
I 03:48:22 Image File File System(s): ISO9660 (Bootable), UDF (1.02)
I 03:48:22 Read Speed (Data/Audio): MAX / MAX
I 03:48:23 Read Speed - Effective: 12x
I 03:48:23 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2293633)
I 03:48:23 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2293633)
W 03:55:10 Failed to Read Sectors 2293632 - 2293633 - Reason: L-EC Uncorrectable Error
W 03:55:19 Failed to Read Sector 2293632 - Reason: L-EC Uncorrectable Error
W 03:55:19 Sector 2293632 maps to File: \sources\replacementmanifests\microsoft-windows-sxs\en-us\sxsmigplugin.dll.mui
E 03:55:49 Failed to Read Sector 2293632 - Reason: L-EC Uncorrectable Error
E 03:55:49 Sector 2293632 maps to File: \sources\replacementmanifests\microsoft-windows-sxs\en-us\sxsmigplugin.dll.mui
E 03:55:49 Failed to Verify Sectors!
I 03:55:50 Exporting Graph Data...
I 03:55:50 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS322_ZL13_SATURDAY-OCTOBER-21-2017_3-48_AM_MKM-A02-00.ibg
I 03:55:50 Export Successfully Completed!
E 03:55:50 Operation Failed! - Duration: 00:07:26
I 03:55:50 Average Verify Rate: 10,308 KiB/s (7.6x) - Maximum Verify Rate: 16,346 KiB/s (12.1x)
Current Profile: DVD+RW

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Formatted: Yes
Sessions: 1
Sectors: 2,295,104
Size: 4,700,372,992 bytes
Time: 510:03:29 (MM:SS:FF)
MID: MKM-A02-00
Supported Read Speeds: 2.4x, 4x, 6x, 8x, 12x
Current Read Speed: 2.4x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2295103)
-> LeadOut  (LBA: 2295104)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 0)

Physical Format Information (ADIP):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):
Disc ID: MKM-A02-00
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Now, I have tried 2 medias. Perhaps it could be the burner drive at fault? I tried to hookup a USB slim drive - Samsung SE-S084 (H/W:A, Ver.C, F/W=TB00) to my desktop. I did just the "Verify disc" function on both Mitsubishi and Verbatim discs. Error too, but a different error message. Here is the log of the Mistsubishi disc. The Verbatim has the same error message.
 

I 03:57:38 ImgBurn Version 2.5.8.0 started!
I 03:57:38 Microsoft Windows 8 Unknown x64 Edition (0x00000079) (6.2, Build 9200)
I 03:57:38 Total Physical Memory: 8,329,072 KiB  -  Available: 7,056,972 KiB
I 03:57:38 Initialising SPTI...
I 03:57:38 Searching for SCSI / ATAPI devices...
I 03:57:38 -> Drive 1 - Info: ATAPI iHAS322 ZL13 (F:) (SATA)
I 03:57:39 -> Drive 2 - Info: TSSTcorp CDDVDW SE-S084C TB00 (G:) (USB 2.0)
I 03:57:39 Found 2 DVD±RW/RAMs!
I 03:59:37 Operation Started!
I 03:59:37 Source Device: [0:0:0] TSSTcorp CDDVDW SE-S084C TB00 (G:) (USB)
I 03:59:37 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: MKM-A02-00)
I 03:59:37 Source Media Supported Read Speeds: 4x, 6x, 8x
I 03:59:37 Source Media Supported Write Speeds: 3x, 4x
I 03:59:37 Source Media Sectors: 2,295,104 (Track Path: PTP)
I 03:59:37 Source Media Size: 4,700,372,992 bytes
I 03:59:37 Image File: D:\Huge Installation Files\windows 10 home pro fall creators update 64 bit\Win10_1709_English_x64.iso
I 03:59:37 Image File Sectors: 2,293,634 (MODE1/2048)
I 03:59:37 Image File Size: 4,697,362,432 bytes
I 03:59:37 Image File Volume Identifier: CCCOMA_X64FRE_EN-US_DV9
I 03:59:37 Image File Volume Set Identifier: f0cc000
I 03:59:37 Image File Application Identifier: CDIMAGE 2.56 (01/01/2005 TM)
I 03:59:37 Image File Implementation Identifier: Microsoft CDIMAGE UDF
I 03:59:37 Image File File System(s): ISO9660 (Bootable), UDF (1.02)
I 03:59:37 Read Speed (Data/Audio): MAX / MAX
I 03:59:38 Read Speed - Effective: 3.3x - 8x
I 03:59:39 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2293633)
I 03:59:39 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2293633)
W 04:08:47 Failed to Read Sectors 2049824 - 2049855 - Reason: Timeout on Logical Unit
W 04:08:57 Failed to Read Sector 2049824 - Reason: Timeout on Logical Unit
W 04:08:57 Sector 2049824 maps to File: \sources\install.wim
W 04:09:10 Retrying (1)...
W 04:09:20 Retry Failed - Reason: Timeout on Logical Unit
W 04:09:23 Failed to Read Sector 2049824 - Reason: Timeout on Logical Unit
W 04:09:23 Sector 2049824 maps to File: \sources\install.wim
W 04:09:33 Failed to Read Sector 2049825 - Reason: Timeout on Logical Unit
W 04:09:33 Sector 2049825 maps to File: \sources\install.wim
E 04:09:36 Failed to Read Sector 2049825 - Reason: Timeout on Logical Unit
E 04:09:36 Sector 2049825 maps to File: \sources\install.wim
E 04:09:36 Failed to Verify Sectors!
I 04:09:37 Exporting Graph Data...
I 04:09:37 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SE-S084C_TB00_SATURDAY-OCTOBER-21-2017_3-59_AM_MKM-A02-00.ibg
I 04:09:37 Export Successfully Completed!
E 04:09:37 Operation Failed! - Duration: 00:09:58
I 04:09:37 Average Verify Rate: 6,867 KiB/s (5.1x) - Maximum Verify Rate: 10,692 KiB/s (7.9x)

By changing the burner drive, the error message change from "Medium Error / L-EC Uncorrectable Error" to "Hardware Error / Timeout on Logical Unit" ?
 

What could be the possible reason?
 



#2 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,504 posts
  • Gender:Male

Posted 21 October 2017 - 03:11 PM

Did you actually try a burn on the USB drive or just perform a Verify on the two discs burned in the LiteOn?  If the problem is the LiteOn burner not correctly burning, then the USB will fail to Verify the discs, too.  If the USB burns but fails Verify, then there's something else up somewhere.  And it's probably not disc related.

 

 

Before burning in the USB, try using a disc that didn't burn in the LiteOn at all.  If the LiteOn has gone bad, then the last burns to those 2 DVD+RW might have irreparably damaged the media.  If you don't have other media, then I'd recommend a Full Erase of one of those 2 DVD+RW in the USB drive before burning the image, just to be better assured.

 

 

As for the reason, it could be because the image is burning towards the edge of the disc.  I believe the Fall Creators Update ISO is nearly the size of a DVD disc.  (I burned mine to BD-RE because I have a BD drive and BD-RE writes faster than 8x DVD+RW.  So, I'm not entirely sure about the size thing.)  As you approach the outer edge of media, you increase the likelihood of errors occurring.



#3 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 22 October 2017 - 07:14 AM

I only burned the discs on LiteOn. I did not burn on the Samsung. The Samsung is only used to verify. I will try to burn on the Samsung, after solving the issue below:
Now, I have another weird issue. When I put the failed disc (both Mitsubishi and Verbatim) into the Samsung, the tray will auto eject. The LiteOn doesn't have this problem.

The iso file size is big. It's definitely nearing the edge. Do you think it's ok to burn a Windows installation disc on a DL DVD?

#4 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,277 posts
  • Gender:Male
  • Location:United Kingdom

Posted 22 October 2017 - 09:29 AM

Both of those discs were 'MKM-A02-00'... as in, the same thing. You have to ignore the brand name stamped on them.

If the drives still won't burn them after doing a full erase on them, use write once media instead.
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#5 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 22 October 2017 - 12:30 PM

I did a full erase of the Mitsubishi DVD+RW and burned again on my LiteOn drive at 2x speed. Verification complete successfully. Yay. Thanks to everyone for the tips.

I 19:48:33 ImgBurn Version 2.5.8.0 started!
I 19:48:33 Microsoft Windows 8 Unknown x64 Edition (0x00000079) (6.2, Build 9200)
I 19:48:33 Total Physical Memory: 8,329,072 KiB  -  Available: 5,585,800 KiB
I 19:48:33 Initialising SPTI...
I 19:48:33 Searching for SCSI / ATAPI devices...
I 19:48:33 -> Drive 1 - Info: ATAPI iHAS322 ZL13 (F:) (SATA)
I 19:48:33 Found 1 DVD±RW/RAM!
I 19:49:06 Operation Started!
I 19:49:06 Device: [0:0:0] ATAPI iHAS322 ZL13 (F:) (SATA)
I 19:49:06 Media Type: DVD+RW (Disc ID: MKM-A02-00)
I 19:49:06 Media Supported Write Speeds: 4x
I 19:49:06 Quick Erase: No
I 19:49:06 Format Properly: Yes
I 19:49:06 Format Size: Preferred
I 19:49:06 Erasing Disc...
I 20:04:11 Operation Successfully Completed! - Duration: 00:15:05
I 20:04:37 Operation Started!
I 20:04:37 Source File: D:\Huge Installation Files\windows 10 home pro fall creators update 64 bit\Win10_1709_English_x64.iso
I 20:04:37 Source File Sectors: 2,293,634 (MODE1/2048)
I 20:04:37 Source File Size: 4,697,362,432 bytes
I 20:04:37 Source File Volume Identifier: CCCOMA_X64FRE_EN-US_DV9
I 20:04:37 Source File Volume Set Identifier: f0cc000
I 20:04:37 Source File Application Identifier: CDIMAGE 2.56 (01/01/2005 TM)
I 20:04:37 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 20:04:37 Source File File System(s): ISO9660 (Bootable), UDF (1.02)
I 20:04:37 Destination Device: [0:0:0] ATAPI iHAS322 ZL13 (F:) (SATA)
I 20:04:37 Destination Media Type: DVD+RW (Disc ID: MKM-A02-00)
I 20:04:37 Destination Media Supported Write Speeds: 4x
I 20:04:37 Destination Media Sectors: 2,295,104
I 20:04:37 Write Mode: DVD
I 20:04:37 Write Type: DAO
I 20:04:37 Write Speed: 2x
I 20:04:37 Link Size: Auto
I 20:04:37 Lock Volume: Yes
I 20:04:37 Test Mode: No
I 20:04:37 OPC: No
I 20:04:37 BURN-Proof: Enabled
W 20:04:38 Write Speed Miscompare! - Wanted: 2,770 KB/s (2x), Got: 5,540 KB/s (4x)
W 20:04:38 The drive only supports writing these discs at 4x.
I 20:04:38 Book Type Setting: DVD-ROM
I 20:04:38 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 20:04:38 CD/DVD Life Record Count: 69 - CD/DVD Record Count: 3
I 20:04:38 Filling Buffer... (80 MiB)
I 20:04:39 Writing LeadIn...
I 20:04:40 Writing Session 1 of 1... (1 Track, LBA: 0 - 2293633)
I 20:04:40 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2293633)
I 20:18:50 Synchronising Cache...
I 20:18:52 Closing Session...
I 20:18:53 Exporting Graph Data...
I 20:18:53 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS322_ZL13_SUNDAY-OCTOBER-22-2017_8-04_PM_MKM-A02-00_2x.ibg
I 20:18:53 Export Successfully Completed!
I 20:18:53 Operation Successfully Completed! - Duration: 00:14:15
I 20:18:53 Average Write Rate: 5,396 KiB/s (4.0x) - Maximum Write Rate: 5,489 KiB/s (4.1x)
I 20:18:53 Cycling Tray before Verify...
W 20:19:01 Waiting for device to become ready...
I 20:19:12 Device Ready!
I 20:19:13 Operation Started!
I 20:19:13 Source Device: [0:0:0] ATAPI iHAS322 ZL13 (F:) (SATA)
I 20:19:13 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: MKM-A02-00)
I 20:19:13 Source Media Supported Read Speeds: 2.4x, 4x, 6x, 8x, 12x
I 20:19:13 Source Media Supported Write Speeds: 4x
I 20:19:13 Source Media Sectors: 2,295,104 (Track Path: PTP)
I 20:19:13 Source Media Size: 4,700,372,992 bytes
I 20:19:13 Image File: D:\Huge Installation Files\windows 10 home pro fall creators update 64 bit\Win10_1709_English_x64.iso
I 20:19:13 Image File Sectors: 2,293,634 (MODE1/2048)
I 20:19:13 Image File Size: 4,697,362,432 bytes
I 20:19:13 Image File Volume Identifier: CCCOMA_X64FRE_EN-US_DV9
I 20:19:13 Image File Volume Set Identifier: f0cc000
I 20:19:13 Image File Application Identifier: CDIMAGE 2.56 (01/01/2005 TM)
I 20:19:13 Image File Implementation Identifier: Microsoft CDIMAGE UDF
I 20:19:13 Image File File System(s): ISO9660 (Bootable), UDF (1.02)
I 20:19:13 Read Speed (Data/Audio): MAX / MAX
I 20:19:14 Read Speed - Effective: 4.8x - 12x
I 20:19:14 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2293633)
I 20:19:14 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2293633)
I 20:25:53 Exporting Graph Data...
I 20:25:53 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS322_ZL13_SUNDAY-OCTOBER-22-2017_8-04_PM_MKM-A02-00_2x.ibg
I 20:25:53 Export Successfully Completed!
I 20:25:53 Operation Successfully Completed! - Duration: 00:06:39
I 20:25:53 Average Verify Rate: 11,525 KiB/s (8.5x) - Maximum Verify Rate: 16,326 KiB/s (12.1x)


Edited by Skylinestar, 22 October 2017 - 01:11 PM.


#6 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 22 October 2017 - 01:07 PM

After successfully burning the standard Win10 Home/Pro ISO, now I wanna try to burn the Education Edition ISO.

Win10 FCU (1709) Edu Edition 64 bit can't fit in the disc. LOL. Not sure if Microsoft is aware of that. :doh:

xB0593z.jpg



#7 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,277 posts
  • Gender:Male
  • Location:United Kingdom

Posted 22 October 2017 - 01:48 PM

That'll fit on a DVD-R / DVD-RW disc, just not DVD+R / DVD+RW.
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#8 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,504 posts
  • Gender:Male

Posted 22 October 2017 - 02:49 PM

I only burned the discs on LiteOn. I did not burn on the Samsung. The Samsung is only used to verify. I will try to burn on the Samsung, after solving the issue below:
Now, I have another weird issue. When I put the failed disc (both Mitsubishi and Verbatim) into the Samsung, the tray will auto eject. The LiteOn doesn't have this problem.

The iso file size is big. It's definitely nearing the edge. Do you think it's ok to burn a Windows installation disc on a DL DVD?

 

 

Can't say about the auto eject issue.  That seems to be a drive problem.  Or it could be by design.  It may have been made to automatically eject discs it cannot read.  However, you said later on you seemed to have had a problem where the RW's were bad.  And a Full Erase fixed the issue.  So, maybe fully erasing them and getting a successful burn to them will fix the Samsung issue?

 

 

Sometimes, full erases of RW media can fix an issue.  The latest firmware for the Pioneer 2209 BD drive borks writing to Ritek 8x DVD+RW.  They will always fail Verify, whereas the previous firmware did not do that.  If you fully erase the media the 2209 under that firmware wrote in another drive and burn again in that different drive, the media is usable again.

 

 

Years ago, I think on Windows 7, the installation media that came with my new PC was on a DVD-9.  And it will definitely fit on a DVD+R DL, although you're wasting about half the available space on the disc.  But, it is a way to go in the future if you wanted to do that.



#9 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 23 October 2017 - 12:35 PM

I think the Samsung is officially dead. The tray ejects with every types of disc. :outcold: I've tried uninstalling the driver in Device Manager (stock Microsoft driver). Not fixed.



#10 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,504 posts
  • Gender:Male

Posted 23 October 2017 - 03:17 PM

Yeah, I'd have to say the eject issue was some kind of hardware failure, versus intentional.  It was just a theory that it may have done that with discs it can't read.  It shouldn't do that, though, because without an error indication from the drive, you can't tell if this is an intended feature or a hardware failure.

 

 

Pioneer's have a similar issue.  After about 7 to 9 months, the eject function doesn't work on the first attempt.  Neither pressing the eject button or a manual software eject command from ImgBurn will work the first time, 1 in 10 times.  A second attempt works, and it seems that all eject commands issued by ImgBurn as part of a Write operation, before a Verify, work.  It's weird.  :unsure:



#11 Skylinestar

Skylinestar

    ISF Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Malaysia

Posted 24 October 2017 - 01:22 AM

The eject works if I go to my Windows Explorer, right click the Samsung usb external optical drive, and select Eject from the context menu (tested this with no disc in the tray). It seems the communication link is there. However, it just spits out every disc. :outcold:

Is this something that can be repaired with firmware update? I can't find this model Samsung SE-S084 (H/W:A, Ver.C, F/W=TB00 as shown the sticker label on the drive) in firmwarehq. The closest that I can find is http://www.firmwarehq.com/Samsung/SE-S084C/files.html . However, it's dated year 2009. My drive is dated 2010.

Or is this a mechanical failure?



#12 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,504 posts
  • Gender:Male

Posted 24 October 2017 - 02:02 AM

Most likely mechanical failure.  I can't see any firmware update fixing a problem like that.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users