Jump to content

I/O ERROR, Head Select Fault - Device Issue?


keefmastaflex
 Share

Recommended Posts

Hi all,

 

I am attempting to burn an image (.cue file) to a DVD-R. I am receiving an I/o error and seem to be stuck on how to proceed. Searching has not provided an exact path forward, so my hope is the community can advise.

 

Here is an image of what I see after selecting the source, and trying to "Load" the E: drive:

image.png.b91ee5cf9a24fcc6d8b55a63deacc101.png

 

I believe the "Head Select Fault" error means Imgburn cannot connect to the DVD drive, and the I/O error is similar. Here are my troubleshooting steps so far:

  • Confirmed if firmware is updated (Firmware HQ does not have my drive, and Device Manager shows Driver: 10.0.19041.1266, being the "latest")
  • I have different discs from the spindle (Maxwell dvd-r's, 16x speed max)
  • I have reduced write speed to 1x, 2x, 2.4x, etc
  • Checked Device Manager for faults (all are clear)
  • Uninstalled the DVD drive, rebooted & re-installed

What should my next steps be? It does not seem like a software or media issues, but related to the dvd drive itself.

 

Appreciate any responses in advance!

Link to comment
Share on other sites

I'm not entirely sure why you're trying to burn a .CUE file to a DVD-R.  .CUE files are expressly for CD burning.  In fact, I don't think you can even write a .BIN/CUE to a DVD-R.  They're expressly for CD-R.

 

That may be why it's not working, but I'd like to take a look at the Log file that generated that Invalid field in CDB to check for other things.  Under Help, choose the ImgBurn log option.  Open the .LOG file and find the portion containing the failed burn.  Copy and paste the entire portion of that log to a post here so I can look at it.

Link to comment
Share on other sites

1 minute ago, dbminter said:

I'm not entirely sure why you're trying to burn a .CUE file to a DVD-R.  .CUE files are expressly for CD burning.  In fact, I don't think you can even write a .BIN/CUE to a DVD-R.  They're expressly for CD-R.

 

That may be why it's not working, but I'd like to take a look at the Log file that generated that Invalid field in CDB to check for other things.  Under Help, choose the ImgBurn log option.  Open the .LOG file and find the portion containing the failed burn.  Copy and paste the entire portion of that log to a post here so I can look at it.

Here is the output of the log:

; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Friday, 16 December 2022, 18:15:28
; \\****************************************//
;
;
I 18:06:53 ImgBurn Version 2.5.8.0 started!
I 18:06:53 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 18:06:53 Total Physical Memory: 8,300,072 KiB  -  Available: 5,972,644 KiB
I 18:06:54 Initialising SPTI...
I 18:06:54 Searching for SCSI / ATAPI devices...
I 18:06:54 -> Drive 1 - Info: MATSHITA DVD-RAM UJ8A7AS 1.00 (E:) (SATA)
I 18:06:54 Found 1 DVD±RW/RAM!
I 18:15:27 Close Request Acknowledged
I 18:15:27 Closing Down...
I 18:15:27 Shutting down SPTI...
I 18:15:28 ImgBurn closed!
;
;
; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Friday, 16 December 2022, 17:57:55
; \\****************************************//
;
;
I 17:33:05 ImgBurn Version 2.5.8.0 started!
I 17:33:05 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 17:33:05 Total Physical Memory: 8,300,072 KiB  -  Available: 4,821,832 KiB
I 17:33:05 Initialising SPTI...
I 17:33:05 Searching for SCSI / ATAPI devices...
I 17:33:05 -> Drive 1 - Info: MATSHITA DVD-RAM UJ8A7AS 1.00 (E:) (SATA)
I 17:33:05 Found 1 DVD±RW/RAM!
I 17:57:55 Close Request Acknowledged
I 17:57:55 Closing Down...
I 17:57:55 Shutting down SPTI...
I 17:57:55 ImgBurn closed!
;
;
; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Friday, 16 December 2022, 17:24:49
; \\****************************************//
;
;
I 16:39:08 ImgBurn Version 2.5.8.0 started!
I 16:39:08 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 16:39:08 Total Physical Memory: 8,300,072 KiB  -  Available: 4,607,912 KiB
I 16:39:08 Initialising SPTI...
I 16:39:08 Searching for SCSI / ATAPI devices...
I 16:39:12 -> Drive 1 - Info: MATSHITA DVD-RAM UJ8A7AS 1.00 (E:) (SATA)
I 16:39:12 Found 1 DVD±RW/RAM!
I 17:24:48 Close Request Acknowledged
I 17:24:48 Closing Down...
I 17:24:48 Shutting down SPTI...
I 17:24:48 ImgBurn closed!

I have not been able to attempt a burn because of the error messages. I would feel super silly if I should be using a cd-r, and that is why I cannot burn the file LOL.

Link to comment
Share on other sites

Yes, no actual writing was done and I think that's because you're trying to burn a BIN/CUE to a CD-R.

 

What is the file size of the BIN (I'm guessing it's a BIN.) you're trying to burn?  If it's like 800 MB or so or less, then it's a CD image and you should try a CD-R.  If it's like 1 GB or more, then it's definitely an image set that needs a DVD.

 

At this point, I'd try burning to a CD-R or CD-RW and see what happens.  Then proceed from there.

Link to comment
Share on other sites

2 hours ago, dbminter said:

Yes, no actual writing was done and I think that's because you're trying to burn a BIN/CUE to a CD-R.

 

What is the file size of the BIN (I'm guessing it's a BIN.) you're trying to burn?  If it's like 800 MB or so or less, then it's a CD image and you should try a CD-R.  If it's like 1 GB or more, then it's definitely an image set that needs a DVD.

 

At this point, I'd try burning to a CD-R or CD-RW and see what happens.  Then proceed from there.

I think you are right wth the .cue file, I will pick up some CD-R's and give them a try.

 

I am having the same error when attempting to burn an .iso to the DVD-R as well. Here is the log using that .iso file:

; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Friday, 16 December 2022, 21:08:31
; \\****************************************//
;
;
I 21:05:45 ImgBurn Version 2.5.8.0 started!
I 21:05:45 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 21:05:45 Total Physical Memory: 8,300,072 KiB  -  Available: 5,615,808 KiB
I 21:05:45 Initialising SPTI...
I 21:05:45 Searching for SCSI / ATAPI devices...
I 21:05:46 -> Drive 1 - Info: MATSHITA DVD-RAM UJ8A7AS 1.00 (E:) (SATA)
I 21:05:46 Found 1 DVD±RW/RAM!
I 21:08:31 Close Request Acknowledged
I 21:08:31 Closing Down...
I 21:08:31 Shutting down SPTI...
I 21:08:31 ImgBurn closed!

In addition, I tried using Windows disc burner and received error code: 0x80004005. Disabling Firewall & defender seems to be the common pre-requisites, but I am still unable to do anything.

Link to comment
Share on other sites

Firewall and Defender tweaks won't do anything to help here.

 

I have to wonder if your device even supports DVD-R.  It's listed as a DVD-RAM device.  I know my first DVD-R burner in 2002 wrote DVD-R and DVD-RAM but I couldn't find any specific information on UJ8A7AS.

 

Unfortunately, error code 0x80004005 is basically when Windows doesn't know what the Hell went wrong.  It's a junk error code.  I found at least 9 different instances where it can pop up via a web search; none were related to optical discs.

 

I would have to question the burner itself.  It seems to be really old as I could find no dedicated hardware page for it.  What I would do in your case is get a USB external burner.  Easy to set up.  Just plug it in and see if it works.

 

Given you're apparently getting the same error from ImgBurn regardless of .CUE or .ISO as a source, I would say it's something to do with your DVD-RAM device.  Plus, given that even Windows won't properly write to it, that also seems the culprit is the DVD-RAM burner, in some capacity or another.

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

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