Can not burn ISO using built in Win 7 ISO burner
I am using a SATA Lite-On DVD-W LH-20A1L, it can burn to ALL DVD media types. I did a firmware update to the DVD burner about 1 month ago to BL06. I am running an MSI P6N Diamond motherboard with the latest nVidia chipset drivers, 15.51. The motherboard is running the latest available firmware, 1.3.
Looking through Event Logs I am seeing:
Log Name: System
Source: cdrom
Date: 10/27/2009 8:50:56 PM
Event ID: 7
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Kickass
Description:
The device, \Device\CdRom3, has a bad block.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="cdrom" />
<EventID Qualifiers="49156">7</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-27T11:50:56.372100000Z" />
<EventRecordID>15150</EventRecordID>
<Channel>System</Channel>
<Computer>Kickass</Computer>
<Security />
</System>
<EventData>
<Data>\Device\CdRom3</Data>
<Binary>030080000100000000000000070004C0000100009C0000C000000000000000000000100000000000165A010000000000FFFFFFFF00000000580000C402000000FE200A1248020000000000000401000000F0FA0380FAFFFFE051660580FAFFFF0000000000000000C023840780FAFFFF0000000000000000000000000000000028000000020000000100000000000000700003000000000A00000000110500000000000000000000</Binary>
</EventData>
</Event>
And
Log Name: System
Source: nvstor64
Date: 10/27/2009 8:27:57 PM
Event ID: 4
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Kickass
Description:
Command to device was aborted.
Device: \Device\RaidPort2
Model: Config Disk
Firmware Version: RGL1
Serial Number: 0000000__________0_F
Port: 1Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvstor64" />
<EventID Qualifiers="49374">4</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-27T11:27:57.607600000Z" />
<EventRecordID>15031</EventRecordID>
<Channel>System</Channel>
<Computer>Kickass</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort2</Data>
<Data>Config Disk</Data>
<Data>RGL1</Data>
<Data>0000000__________0_F</Data>
<Data>1</Data>
<Binary>0000000005002800000000000400DEC0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
And a Warning:
Log Name: System
Source: nvstor64
Date: 10/27/2009 8:20:07 PM
Event ID: 129
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Kickass
Description:
Reset to device, \Device\RaidPort2, was issued.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvstor64" />
<EventID Qualifiers="32772">129</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-27T11:20:07.561700000Z" />
<EventRecordID>14880</EventRecordID>
<Channel>System</Channel>
<Computer>Kickass</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort2</Data>
<Binary>0F001800010000000000000081000480040000000000000000000000000000000000000000000000000000000000000000000000810004800000000000000000</Binary>
</EventData>
</Event>
It has done BSOD dumps during the burn as well:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 10/27/2009 8:25:29 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Kickass
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000000000000a, 0x0000000000000002, 0x0000000000000000, 0xfffff880012ecfa5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102709-83398-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-27T11:25:29.000000000Z" />
<EventRecordID>14961</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Kickass</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000d1 (0x000000000000000a, 0x0000000000000002, 0x0000000000000000, 0xfffff880012ecfa5)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">102709-83398-01</Data>
</EventData>
</Event>
I am only using the built in Windows ISO burner. I have NO other burning software installed. I am using JVC DVD-Rs, single layer. I have successfully burnt to this same drive when I was running Windows XP, I used Nero 7 OEM to do my burning then.
The ISO burn program gives the following message after it makes a coaster:
The disc image didn't burn successfully because an error occurred. (Error code: 0x80004005)
I have uninstalled the drive in device manager and rebooted and Windows reinstalled it with no problems. A burn attempt after this still fails.
I have tried to burn the ISO as a file and then burn the ISO image on a different PC, the normal data burn to DVD failed also.
Please help!
All Replies
- Another issue I have had since moving to Win7 that I might as well bring up while I am at it is that the SATA optical drive won't play normal, commercially bought DVDs. My IDE optical drive will without any problems. But my SATA will pop the drawer open and say please insert a disc. I used my IDE optical drive to install Win7 originally. I read a long time ago that people had problems getting it to install from a SATA optical drive so I didn't even try.
- Hi Vfighter,
let's focus on the problem one by one.
Based on my known, the following factors can cause Error code: 0x80004005.
1. This writeable media has already file system.
2. This writeable media has been formatted with open session.
Could you please try to use an unformatted blank media to burn ISO file via Windows Disc Image Burner?
Hope it helps.
Thanks. - These are brand new, unused discs right off the spindle.
- HI Vfighter,
Can you try to burn other files directly in Windows Explorer without formatting it?
Thanks. - You keep talking about formatting the DVD-R. I am not doing anything to "prep" the disc before burning. When I burnt it through Windows Explorer I told it to treat it like a DVD and finalize the disc, this I guess is sort of "formatting" it. But I am NOT using something like Easy CD Creator's DirectCD or anything like that. I am just using the built in Windows disc burning utilities. I will try to burn some other files to a DVD-R and see what happens.
- Tried to burn some normal files. Size was enough to take up the full DVD-R. Used built in Win7 burner. Blue screen of death. storport.sys The same thing that pops up on all the other BSODs.
- Any ideas other than reinstall OS? Anyone?
- Today while I was burning a set of WINPE disks x86 and AMD64 as part of the WAIK process, I ran into the same error after the discs had burned, and it was in the process of verifying the disc after burning. I tested my discs and they appear to be find. So you may just want to check and see if the Burn disc set from ISO's you made work.
Otherwise you may want to check with the manufacture and see if it is possible you need to flash the firmware on the Drive (Edit: I see you had done this about a month ago, may want to contact the Manufacture, and see if they are seeing similar problems with W7 and their drive). Otherwise you may want to try a third party utility. Just some ideas for you.
Could try this Utlity http://www.ntfs.com/iso_burner_free.htm
- I tried Active ISO Burner. I tried all 3 Transport types: SPTI (which was flagged by Windows as incompatible), SPTD, and ASPI. All 3 failed. Burned nothing, but made the discs non burnable. Anymore ideas?
- I would say from here you should try removing this burner, and install a known good one that you know works with 7 or a brand new one all together. There are some hit and miss message boards describing the same problem all over the web. If you can't get the burning process to work with a different drive, then there may be something in your installation that is fouling it up. DVD burners are cheap these days, so that is the route I would try, at least initially.
