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

I/O Error! Reason: Incorrect Function


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
23 replies to this topic

#1 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 10 January 2018 - 03:44 AM

Fresh install of Windows 10 and for some reason I can't get it to burn a DVD. I've tried other software and even tried burning a data DVD with windows and it will not burn a DVD, but will burn a CD. Reads DVD's just fine. Get this error immediately when trying to burn with IMGBURN. I've tried updates, installing motherboard drivers, and no luck. Works fine if I use the same burners with a usb adapter, but get this error while connected with SATA. Also, when I install my old hard drive with the old installation of Windows 10, everything works fine. Just won't work on this new install. Any ideas?

 

 

 

I 19:30:19 ImgBurn Version 2.5.8.0 started!
I 19:30:19 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 19:30:19 Total Physical Memory: 16,714,564 KiB  -  Available: 14,033,480 KiB
I 19:30:19 Initialising SPTI...
I 19:30:19 Searching for SCSI / ATAPI devices...
I 19:30:19 -> Drive 1 - Info: ATAPI iHAS124   F CL9M (I:) (SATA)
I 19:30:20 -> Drive 2 - Info: ATAPI iHAS124   F CL9M (G:) (SATA)
I 19:30:20 -> Drive 3 - Info: ATAPI iHAS124   F CL9M (H:) (SATA)
I 19:30:20 Found 3 DVD±RWs!
I 19:31:22 Operation Started!
I 19:31:22 Source File: D:\ConvertXtoDVD\Gangster.Land.2017.BDRip.XviD.AC3-EVO.iso
I 19:31:22 Source File Sectors: 1,103,376 (MODE1/2048)
I 19:31:22 Source File Size: 2,259,714,048 bytes
I 19:31:22 Source File Volume Identifier: Gangster.Land.2017.BDRip.XviD.AC3-EVO
I 19:31:22 Source File Volume Set Identifier: 4C297284________Gangster.Land.2017.BDRip.XviD.AC3-EVO
I 19:31:22 Source File Implementation Identifier: VsoSoftware
I 19:31:22 Source File File System(s): ISO9660, UDF (1.02)
I 19:31:22 Destination Device: [0:0:0] ATAPI iHAS124   F CL9M (I:) (SATA)
I 19:31:22 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3)
I 19:31:22 Destination Media Supported Write Speeds: 6x, 8x, 12x, 16x
I 19:31:22 Destination Media Sectors: 2,298,496
I 19:31:22 Write Mode: DVD
I 19:31:22 Write Type: DAO
I 19:31:22 Write Speed: MAX
I 19:31:22 Link Size: Auto
I 19:31:22 Lock Volume: Yes
I 19:31:22 Test Mode: No
I 19:31:22 OPC: No
I 19:31:22 BURN-Proof: Enabled
I 19:31:22 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x)
I 19:31:22 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 19:31:23 Filling Buffer... (80 MiB)
I 19:31:23 Writing LeadIn...
W 19:31:23 Failed to Write Sectors 0 - 31 - Reason: Incorrect function.
W 19:31:23 Retrying (1 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (2 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (3 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (4 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (5 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (6 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (7 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (8 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (9 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (10 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (11 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (12 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (13 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (14 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (15 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (16 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (17 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (18 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (19 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
W 19:31:23 Retrying (20 of 20)...
W 19:31:23 Retry Failed - Reason: Incorrect function.
E 19:36:57 Failed to Write Sectors 0 - 31 - Reason: Incorrect function.
I 19:36:57 Synchronising Cache...
W 19:37:00 User opted to skip the 'Close Track/Session/Disc' functions.
E 19:37:00 Failed to Write Image!
E 19:37:01 Operation Failed! - Duration: 00:05:37
I 19:37:01 Average Write Rate: N/A - Maximum Write Rate: N/A
 



#2 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

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

Posted 10 January 2018 - 05:39 AM

Right click the drive selection box and pick family tree.

Close the message box that pops up and then copy and paste everything from the log window please
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!

#3 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 10 January 2018 - 06:36 AM

Thanks for the reply.

 

I 22:35:43 ImgBurn Version 2.5.8.0 started!
I 22:35:43 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 22:35:43 Total Physical Memory: 16,714,564 KiB  -  Available: 13,971,744 KiB
I 22:35:43 Initialising SPTI...
I 22:35:43 Searching for SCSI / ATAPI devices...
I 22:35:43 -> Drive 1 - Info: ATAPI iHAS124   F CL9M (F:) (SATA)
I 22:35:43 -> Drive 2 - Info: ATAPI iHAS124   F CL9M (D:) (SATA)
I 22:35:43 -> Drive 3 - Info: ATAPI iHAS124   F CL9M (E:) (SATA)
I 22:35:43 Found 3 DVD±RWs!
I 22:35:51 Device: [0:0:0] ATAPI iHAS124   F CL9M (F:) (SATA)
I 22:35:51 Family Tree:
I 22:35:51 -> ACPI x64-based PC
I 22:35:51 -> Microsoft ACPI-Compliant System
I 22:35:51 -> PCI Express Root Complex
I 22:35:51 -> Standard SATA AHCI Controller (VEN_8086&DEV_8C02 - Intel - storahci - v10.0.15063.332)
I 22:35:51 -> CD-ROM Drive (ATAPI iHAS124   F) (Bus Number 1, Target Id 0, LUN 0)
 



#4 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

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

Posted 10 January 2018 - 11:59 AM

Have you possibly installed some software that's preventing access to the drive?

The 'WRITE' commands are being blocked by something.

Have you tried booting into safe mode to see if you run into the same issue?

Failing that, go for another reinstall of the OS and check it functions correctly from a clean version - i.e. before you install *anything* else.
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 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 10 January 2018 - 01:33 PM

I've tried reinstalling 3-4 times, and even tried going back to Windows 7. Still get the same error. I've also tried with only installing IMGBURN but still nothing. The other day it was working after I installed the chipset driver and worked for a whole day or two, but then last night it just started the same thing

 

Things I've tried:

 

Safe mode

Clean install of Windows 10 and 7 with only IMGBURN installed.

Windows updates

Driver updates

Different Hard Drives on clean install

Different DVD drives

 

External burner works.

Old installations of Windows work with same hardware setup.

I even tried installing fresh copy of Windows on my laptop, and still get this error message, and that's a whole different setup. Same result, internal burner gets this error, but external burner works great.

 

I've lost a lot of sleep over this. Hopefully someone can help.



#6 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 10 January 2018 - 01:52 PM

Just to clarify. I have had this system for about 4 years now. No issues what so ever in the past. Only thing I did was install a new case, install new burners, and a new SSD with clean install of Windows 10. Everything else is the same. Even updated the BIOS thinking that would help but still nothing.



#7 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

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

Posted 10 January 2018 - 03:22 PM

Which motherboard do you have? Have you tried the current / correct Intel Rapid Storage Tech drivers for it?

I assume all 3 drives behave the same way?
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 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 10 January 2018 - 03:31 PM

ASUS 287-K motherboard.

 

Tried all drivers from original disk and even the drivers from the website.

Yes, all drives behaving the same.



#9 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 11 January 2018 - 02:30 AM

Okay borrowed a desktop from a friend. Fresh install of windows 10. Only install is imgburn and still getting this God forsaken error! I don't understand. Been using this software for years and never an issue. I uninstalled it, and tried to burn the image with the windows disk burner and it won't burn it either. That's 3 computers now with the same result.

#10 dbminter

dbminter

    ISF God

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

Posted 11 January 2018 - 03:30 AM

Are you using the same SATA cable with this drive in each of the 3 PC's you've tried?  If you put this burner in an enclosure and it works and you tried 3 different PC's, if you used the same SATA cable, one would think it's either the SATA cable or the burner itself that is the problem.  It can't be the SATA controller on the mobo because it keeps happening across different PC's.  So, it has to be something that is common across all 3 PC's and being carried over/replicated on each machine.  That would be either the cable or the drive itself.

 

 

However, this doesn't explain why the drive works on your one system image where Windows 10 was installed before and the drive was working okay.  And you've restored this system where Windows 10 was working with this drive and tested it again to make sure it's still working on that system image?



#11 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 11 January 2018 - 03:58 AM

Yes I'm actually using it on a previous image now and all 3 drives are burning perfectly.

As for the other installs, it was all different hardware so yes it was different cables and such. One of the installs was a laptop with a burner, so no cables were involved. This really makes no sense to me and has been driving me crazy!

My latest test was a new install of Windows 7 x64 and didn't install anything extra. Burned an image file with the included windows burning software. It worked fine. Then installed imgburn and I get this error. Uninstalled imgburn and now the built in software is not working anymore.

#12 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 11 January 2018 - 04:01 AM

I've tried other software and didn't work, but now that I think about it, it was after I installed imgburn. I'm not sure, but that's really the only common denominator here. But once installed, nothing works to burn a DVD. Burns Cds just fine though.

#13 dbminter

dbminter

    ISF God

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

Posted 11 January 2018 - 04:06 AM

I was just going suggest, test the .EXE you downloaded of ImgBurn.  If you're willing to test it/have an image you can restore from to test with, try uninstalling ImgBurn on the image of Windows that works and reinstalling ImgBurn.  If it fails again, then it could be a corrupt ImgBurn .EXE installer when it was downloaded, if you're using the same executable in all tests.  While it seems unlikely to be the case, it could be the case.  And, at this point, the only common denominator is installing ImgBurn.  If it's already pre-installed, it seems to work.  If you install it, it doesn't.  However, this doesn't explain why the enclosure works.  Unless the installer just happens to be corrupt to the point where it works but doesn't work right and only just happens to fail on SATA.  Again, highly unlikely, but what else can you test at this point?  And what else have you got to lose at this point, too?



#14 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 11 January 2018 - 04:19 AM

I tried a different exe and even used a previous version of one I had on an old USB stick. Still get the same problem. I'm afraid to even try on this setup that's working because right now it's all I have to use right now. I feel like I have tried everything but it has to be something so dumb. I just can't seem to figure it out though.

#15 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 11 January 2018 - 04:21 AM

Can't remember if I mentioned this, but on a new install of windows 10, it would work after I did a system update that it downloaded when I first install. It worked fine for a day or so but then just stopped working out of nowhere.

#16 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 12 January 2018 - 03:12 AM

Reinstalled windows 10. Installed Nero and it burns iso files fine. Imgburn does not work still. Tried CDburnerXP and it doesn't work either. Nero still works though. I just don't understand. Also, this is a different pc. It's an HP with all original hardware installed.

#17 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

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

Posted 12 January 2018 - 07:02 AM

It's very strange that every command appears to be working ok, except for the actual 'WRITE' one.

As I said before, the 'Incorrect function' message is from the OS rather than the drive. The OS (or some sort of driver) is messing with how things normally work. That fact you've had this issue on multiple machines is interesting... if it was genuinely an issue, I'd expect a lot more 'noise' here on the forum about it.

I can't think of any reason why a 100% clean install of Windows 10 (with nothing but all windows updates) wouldn't work fine.

You've definitely tried booting the machine into safe mode and running ImgBurn from there yeah?

Perhaps try adjusting the SPTI enumeration method in the settings (on the I/O tab) to the other options. If Nero works (and assuming it isn't using a lower level driver to bypass whatever the issue is, maybe only one method of enumerating the drives is being blocked / broken.
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!

#18 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 12 January 2018 - 01:23 PM

It doesn't recognize the drive when I change those settings

#19 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

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

Posted 12 January 2018 - 07:29 PM

What?!

So if you set the enum method 'Device Class' or 'Drive Letter', you get 'no devices found' ?

Your system is not well!

I did a fresh install of Window 10 1709 (Build 16299) earlier today inside VMWare and all 3 of the enum methods work just fine.

Do you get any errors when attempting to use the other enumeration methods? If so, please copy + paste everything from the Log window so I can see them.
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!

#20 Whitemus

Whitemus

    ISF Newbie

  • Members
  • Pip
  • 14 posts
  • Location:USA

Posted 13 January 2018 - 08:57 PM

I misunderstood that, so I was wrong. I did try those other enumeration settings and still getting this error though.

I did a fresh install of Windows 7 home premium and everything worked fine. Then upgraded to Windows 10 and back to the same error. This is on the test desktop that I've been using. All factory setup from HP that had originally windows 7 installed on it.

I'm lost at this point. I was hoping someone would see this post and point out something so dumb that I was missing and call me an idiot so I could laugh about it and move on lol. Apparently it's a little more than that. I really don't know what to try next so any suggestions would be great. I'm going to use Windows 7 for now until I can get this working on my test computer.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users