Jump to content
cvmanjoo

Disc Brun Fails.

Recommended Posts

Friends,

 

Log goes like this...

; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Monday, 24 August 2015, 22:16:22
; \\****************************************//
;
;
I 22:06:09 ImgBurn Version 2.5.8.0 started!
I 22:06:09 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 22:06:09 Total Physical Memory: 7,273,388 KiB  -  Available: 3,364,984 KiB
I 22:06:09 Initialising SPTI...
I 22:06:09 Searching for SCSI / ATAPI devices...
I 22:06:10 -> Drive 1 - Info: ASUS DRW-24B5ST 1.00 (F:) (SATA)
I 22:06:10 Found 1 DVD±RW/RAM!
I 22:10:43 Operation Started!
I 22:10:43 Source File: E:\Setups\MSDN\Windows 10\en_windows_10_multiple_editions_x64_dvd_6846432.iso
I 22:10:43 Source File Sectors: 1,994,069 (MODE1/2048)
I 22:10:43 Source File Size: 4,083,853,312 bytes
I 22:10:43 Source File Volume Identifier: J_CCSA_X64FRE_EN-US_DV5
I 22:10:43 Source File Volume Set Identifier: dcafe780MS UDFBridge
I 22:10:43 Source File Application Identifier: CDIMAGE 2.53 (01/01/2005 TM)
I 22:10:43 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 22:10:43 Source File File System(s): ISO9660 (Bootable), UDF (1.02)
I 22:10:43 Destination Device: [1:0:0] ASUS DRW-24B5ST 1.00 (F:) (SATA)
I 22:10:43 Destination Media Type: DVD+R (Disc ID: MCC-004-00)
I 22:10:43 Destination Media Supported Write Speeds: 6x, 8x, 12x, 16x
I 22:10:43 Destination Media Sectors: 2,295,104
I 22:10:43 Write Mode: DVD
I 22:10:43 Write Type: DAO
I 22:10:43 Write Speed: MAX
I 22:10:43 DVD+R Reserve Track: No
I 22:10:43 Link Size: Auto
I 22:10:43 Lock Volume: Yes
I 22:10:43 Test Mode: No
I 22:10:43 OPC: No
I 22:10:43 BURN-Proof: Enabled
I 22:10:43 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x)
I 22:10:43 Book Type Setting: N/A (Reason: Invalid Field in CDB)
I 22:10:43 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 22:10:43 CD/DVD Life Record Count: 35 - CD/DVD Record Count: 5
I 22:10:43 Filling Buffer... (80 MiB)
I 22:10:45 Writing LeadIn...
W 22:11:23 Failed to Write Sectors 0 - 31 - Reason: The request could not be performed because of an I/O device error.
W 22:11:23 Retrying (1 of 20)...
W 22:11:23 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 22:11:23 Retrying (2 of 20)...
W 22:11:39 Retry Failed - Reason: Not Ready To Ready Change - Medium May Have Changed
W 22:11:39 Retrying (3 of 20)...
W 22:12:11 Retry Failed - Reason: The request could not be performed because of an I/O device error.
W 22:12:11 Retrying (4 of 20)...
W 22:12:12 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 22:12:12 Retrying (5 of 20)...
W 22:12:27 Retry Failed - Reason: Not Ready To Ready Change - Medium May Have Changed
W 22:12:27 Retrying (6 of 20)...
I 22:13:01 Writing LeadIn...
I 22:13:02 Writing Session 1 of 1... (1 Track, LBA: 0 - 1994068)
I 22:13:02 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1994068)
W 22:13:52 Failed to Write Sectors 247904 - 247935 - Reason: The request could not be performed because of an I/O device error.
W 22:13:52 Retrying (1 of 20)...
W 22:13:52 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 22:13:52 Retrying (2 of 20)...
W 22:14:10 Retry Failed - Reason: Not Ready To Ready Change - Medium May Have Changed
W 22:14:10 Retrying (3 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (4 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (5 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (6 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (7 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (8 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (9 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (10 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (11 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (12 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (13 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (14 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (15 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (16 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (17 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (18 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (19 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:11 Retrying (20 of 20)...
W 22:14:11 Retry Failed - Reason: Invalid Address For Write
W 22:14:13 Retrying (21)...
W 22:14:13 Retry Failed - Reason: Invalid Address For Write
W 22:14:15 Retrying (22)...
W 22:14:15 Retry Failed - Reason: Invalid Address For Write
W 22:14:16 Retrying (23)...
W 22:14:16 Retry Failed - Reason: Invalid Address For Write
W 22:14:16 Retrying (24)...
W 22:14:16 Retry Failed - Reason: Invalid Address For Write
E 22:14:34 Failed to Write Sectors 247904 - 247935 - Reason: The request could not be performed because of an I/O device error.
E 22:14:34 Next Writable Address: 247392
I 22:14:34 Synchronising Cache...
I 22:14:46 Closing Track...
W 22:15:18 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Power On, Reset, or Bus Device Reset Occurred
W 22:15:18 Close Track Failed! - Reason: Power On, Reset, or Bus Device Reset Occurred
W 22:15:37 Close Track Failed! - Reason: Power On, Reset, or Bus Device Reset Occurred
I 22:15:37 Finalising Disc...
W 22:15:37 Finalise Disc Failed! - Reason: Not Ready To Ready Change - Medium May Have Changed
E 22:15:39 Finalise Disc Failed! - Reason: Not Ready To Ready Change - Medium May Have Changed
E 22:15:39 Failed to Write Image!
I 22:15:39 Exporting Graph Data...
I 22:15:39 Graph Data File: C:\Users\cvman\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-24B5ST_1.00_MONDAY-AUGUST-24-2015_10-10_PM_MCC-004-00_MAX.ibg
I 22:15:39 Export Successfully Completed!
E 22:15:39 Operation Failed! - Duration: 00:04:56
I 22:15:39 Average Write Rate: 5,389 KiB/s (4.0x) - Maximum Write Rate: 11,092 KiB/s (8.2x)
I 22:16:22 Close Request Acknowledged
I 22:16:22 Closing Down...
I 22:16:22 Shutting down SPTI...
I 22:16:22 ImgBurn closed!

Whats wrong in this? Is it Disc or Drive or Windows? Its Windows 10 but log says Windows 8..
I dont want to waste another disc.

Please let me know the solution for this,

 

Thanks to everyone.
 

Share this post


Link to post
Share on other sites

Until a new version of ImgBurn is released, ImgBurn will return that Windows 10 is Windows 8.  It's a somewhat technical story.  :)

 

 

As for what's wrong, have you ever used these discs before in this drive?  It could be the drive doesn't like the discs.  You're using quality MCC so it's most likely not the media causing the problem.  How long have you had this drive?  If it's new, then, it would be relatively unlikely to be a bad drive, but you never know.  If you don't want to waste discs, try a rewritable DVD.  If you get the same error on those, since you used both DVD+R and a rewritable, you can most likely lay the problem on something to do with the drive.  Either the drive itself or some issue with it and your computer or Windows.  If the rewritable works, then it's probably that that Asus drive doesn't like those kind of DVD+R from Mitsubishi Chemical Corporation.

 

 

Did you upgrade an older version of Windows to Windows 10?  Did burning work before under the older version of Windows?

 

 

Also I don't know why the image file is 4 GB in size yet returns CDIMAGE.  That seems to indicate to me it's a CD image, but no CD image is 4 GB as CD's usually max out at like 800 MB.  However, it is a Windows 10 installation image from Microsoft, so MS could have read it as some kind of CDIMAGE file system type.  Why it has multiple editions on it I can only guess.  :wink:

 

 

I'm no expert on drive error messages, but the ones I see seem to indicate something physically wrong with the drive.  That it keeps wanting to turn off/reset/eject itself when it's trying to burn.

 

 

Also, though it probably won't help, I would also recommend a shut down of Windows, powering off the PC for a minute so that the power cycles, turn it back on, and restart Windows before trying again.  Sometimes a simple power cycle of a drive can fix odd issues.

Share this post


Link to post
Share on other sites

Right click the drive selection box and click 'family tree'.

 

Close the prompt that comes up and then copy and paste everything from the log window please.

Share this post


Link to post
Share on other sites

Until a new version of ImgBurn is released, ImgBurn will return that Windows 10 is Windows 8.  It's a somewhat technical story.  :)

 

I know; I was expecting that answer :)

 

 As for what's wrong, have you ever used these discs before in this drive?

 

Yes I used same drive with same type of discs, Perhaps those are from same stack.

 

 How long have you had this drive?

 

Around 2 to 2.5 Years. I not able find new firmware as of now. :(

 

If you don't want to waste discs, try a rewritable DVD.

 

Yes I want to check with rewritable discs. Will post the log shortly.

 

Did you upgrade an older version of Windows to Windows 10?

 

No fresh Install.

 

Did burning work before under the older version of Windows?

 

Yes 100% worked fine.

 

Also I don't know why the image file is 4 GB in size yet returns CDIMAGE

 

Only Microsoft can answer this :P

 

 

Also, though it probably won't help, I would also recommend a shut down of Windows, powering off the PC for a minute so that the power cycles, turn it back on, and restart Windows before trying again.  Sometimes a simple power cycle of a drive can fix odd issues.

 

I was thinking same and let you know the results.

 

 

For Lightning UK.

 

Right click the drive selection box and click 'family tree'.

Close the prompt that comes up and then copy and paste everything from the log window please.

I 00:21:57 ImgBurn Version 2.5.8.0 started!
I 00:21:57 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 00:21:57 Total Physical Memory: 7,273,388 KiB  -  Available: 4,072,316 KiB
I 00:21:57 Initialising SPTI...
I 00:21:57 Searching for SCSI / ATAPI devices...
I 00:21:57 -> Drive 1 - Info: ASUS DRW-24B5ST 1.00 (F:) (SATA)
I 00:21:57 Found 1 DVD±RW/RAM!
I 00:24:31 Device: [1:0:0] ASUS DRW-24B5ST 1.00 (F:) (SATA)
I 00:24:31 Family Tree:
I 00:24:31 -> ACPI x64-based PC
I 00:24:31 -> Microsoft ACPI-Compliant System
I 00:24:31 -> PCI Express Root Complex
I 00:24:31 -> Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller (VEN_8086&DEV_1E02 - Intel - iaStorA - v9.3.0.1029)
I 00:24:31 -> CD-ROM Drive (ASUS DRW-24B5ST) (Bus Number 4, Target Id 0, LUN 0)

Hope this Help me and you and all members of this fourm who have similar type of problem.

 

Sorry for late reply.

 

Thank you all,

Edited by cvmanjoo

Share this post


Link to post
Share on other sites

Since you've had this drive for 2 to 2 and a half years now, I'd be worried that it's dying at this point.  However, you said it worked before installing Windows 10.  Could be a driver that isn't updated for a drive that old?  Just a guess.

Share this post


Link to post
Share on other sites

9.3 is a really old driver version for the controller. Try installing a more up to date version of the Intel rapid storage technology software.

Share this post


Link to post
Share on other sites

×

Important Information

By using this site, you agree to our Terms of Use.