Jump to content

Invalid address for write


Raptor88
 Share

Recommended Posts

Dell XPS 8500, i5, 8GB ram, new Lite-on iHAS124 drive.  Upgraded the drive's firmware from 4L08 to 4L0A.

 

Running Imgburn in test mode, doing a pseudo burn of a VIDEO_TS folder using the "Write files/folders to disc" option.  Getting an I/O Error!  ScsiStatus: 0x02 Interpretation check condition.  Here's one burn log that shows the "Invalid address for write" errors:

 

I 14:41:24 ImgBurn Version 2.5.8.0 started!
I 14:41:24 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 14:41:24 Total Physical Memory: 8,348,672 KiB  -  Available: 6,392,640 KiB
I 14:41:24 Initialising SPTI...
I 14:41:24 Searching for SCSI / ATAPI devices...
I 14:41:24 -> Drive 1 - Info: ATAPI iHAS124   E 4L0A (M:) (SATA)
I 14:41:24 Found 1 DVD±RW/RAM!
I 14:41:49 Operation Started!
I 14:41:49 Building Image Tree...
I 14:41:51 Checking Directory Depth...
I 14:41:51 Calculating Totals...
I 14:41:51 Preparing Image...
I 14:41:52 Checking Path Length...
I 14:41:52 Contents: 18 Files, 2 Folders
I 14:41:52 Content Type: DVD Video
I 14:41:52 Data Type: MODE1/2048
I 14:41:52 File System(s): ISO9660, UDF (1.02)
I 14:41:52 Volume Label: Slave Hunters Chuno Eps 1, 2, 3
I 14:41:52 IFO/BUP 32K Padding: Enabled
I 14:41:52 Region Code: 1, 2, 3, 4, 5, 6, 8
I 14:41:52 TV System: NTSC
I 14:41:52 Size: 3,781,277,696 bytes
I 14:41:52 Sectors: 1,846,327
I 14:41:52 Image Size: 3,781,885,952 bytes
I 14:41:52 Image Sectors: 1,846,624
I 14:41:54 Operation Successfully Completed! - Duration: 00:00:04
I 14:41:54 Operation Started!
I 14:41:54 Source File: -==/\/[bUILD IMAGE]\/\==-
I 14:41:54 Source File Sectors: 1,846,624 (MODE1/2048)
I 14:41:54 Source File Size: 3,781,885,952 bytes
I 14:41:54 Source File Volume Identifier: Slave Hunters Chuno Eps 1, 2, 3
I 14:41:54 Source File Volume Set Identifier: 46AF7538001C2D57
I 14:41:54 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!
I 14:41:54 Source File Implementation Identifier: ImgBurn
I 14:41:54 Source File File System(s): ISO9660, UDF (1.02)
I 14:41:54 Destination Device: [0:0:0] ATAPI iHAS124   E 4L0A (M:) (SATA)
I 14:41:54 Destination Media Type: DVD-R (Disc ID: MCC 03RG20)
I 14:41:54 Destination Media Supported Write Speeds: 6x, 8x, 12x, 16x
I 14:41:54 Destination Media Sectors: 2,298,496
I 14:41:54 Write Mode: DVD
I 14:41:54 Write Type: DAO
I 14:41:54 Write Speed: 8x
I 14:41:54 Link Size: Auto
I 14:41:54 Lock Volume: Yes
I 14:41:54 Test Mode: Yes
I 14:41:54 OPC: No
I 14:41:54 BURN-Proof: Enabled
I 14:41:54 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 14:41:54 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 14:41:54 Filling Buffer... (80 MiB)
I 14:41:55 Writing LeadIn...
I 14:42:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 1846623)
I 14:42:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1846623)
W 14:45:52 Failed to Write Sectors 920480 - 920511 - Reason: Invalid Address For Write
W 14:45:52 Retrying (1 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (2 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (3 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (4 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (5 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (6 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (7 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (8 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (9 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (10 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (11 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (12 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (13 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (14 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (15 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (16 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (17 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (18 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (19 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (20 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
E 14:50:31 Failed to Write Sectors 920480 - 920511 - Reason: Invalid Address For Write
E 14:50:32 Next Writable Address: 0
I 14:50:32 Synchronising Cache...
W 14:50:45 User opted to skip the 'Close Track/Session/Disc' functions.
I 14:50:45 Cycling Tray after Test Write...
E 14:50:47 Failed to Write Image!
I 14:50:47 Exporting Graph Data...
I 14:50:47 Graph Data File: C:\Users\HarrietK\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS124_E_4L0A_FRIDAY-MAY-15-2015_2-41_PM_MCC_03RG20_8x.ibg
I 14:50:47 Export Successfully Completed!
E 14:50:47 Operation Failed! - Duration: 00:08:53
I 14:50:47 Average Write Rate: 3,749 KiB/s (2.8x) - Maximum Write Rate: 10,995 KiB/s (8.1x)
 

Source drive with the VIDEO_TS folder was either the C: spinner or a spinner in a USB3 docking station.  Same error.  Cannot be the media since the burn was in "Test" mode. 

 

I also tried a known working Optiarc drive and it gets the same type of error.

 

Any ideas?

 

Link to comment
Share on other sites

Which controller is that drive attached to?

 

Right click the drive selection drop down box when you're in Write mode and select 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window.

 

Try booting up in safe mode and see if you have the same problem.

Link to comment
Share on other sites

Which controller is that drive attached to?

 

Right click the drive selection drop down box when you're in Write mode and select 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window.

 

Try booting up in safe mode and see if you have the same problem.

Thank you very much for your quick reply!  Here's the result of the Family Tree:

 

I 12:01:08 ImgBurn Version 2.5.8.0 started!

I 12:01:08 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)

I 12:01:08 Total Physical Memory: 8,348,672 KiB  -  Available: 6,300,176 KiB

I 12:01:08 Initialising SPTI...

I 12:01:08 Searching for SCSI / ATAPI devices...

I 12:01:09 -> Drive 1 - Info: ATAPI iHAS124   E 4L0A (M:) (SATA)

I 12:01:09 Found 1 DVD±RW/RAM!

I 12:03:01 Device: [0:0:0] ATAPI iHAS124   E 4L0A (M:) (SATA)

I 12:03:01 Family Tree:

I 12:03:01 -> ACPI x64-based PC

I 12:03:01 -> Microsoft ACPI-Compliant System

I 12:03:01 -> PCI Express Root Complex

I 12:03:01 -> Intel® 7 Series/C216 Chipset Family SATA AHCI Controller (VEN_8086&DEV_1E02 - Intel - iaStorA - v9.3.0.1011)

I 12:03:01 -> CD-ROM Drive (ATAPI iHAS124   E) (Bus Number 5, Target Id 0, LUN 0)

 

I will try in safe mode.

 

BTW, this PC has worked with Imgburn for years.  Could be overheating since when I opened my friend's PC (this one), it was full of dust and the heatsinks were clogged with dust.  The optical drive was replaced with the new Liteon drive for this problem.  Running Windows 8 with the Classic Shell.

 

Thanks,

Raptor88

Edited by Raptor88
Link to comment
Share on other sites

Also forgot to mention that this problem is intermittent.  When it's working, it can complete the test burns successfully many times.  When it's having the problem, it can happen consecutively.

 

All fans in the PC working.  Problem can happen anytime during the day.

Link to comment
Share on other sites

Also forgot to mention that this problem is intermittent.  When it's working, it can complete the test burns successfully many times.  When it's having the problem, it can happen consecutively.

 

All fans in the PC working.  Problem can happen anytime during the day.

 

Also restored a Dec 2014 backup that was done when Imgburn was working fine and before this problem started happening.  Invalid address for write problem started in about March 2015, so I doubt that it is an infection or Windows 8 problem.

Edited by Raptor88
Link to comment
Share on other sites

Haven't tried the test burns in safe mode yet since the problem is not happening in normal mode no matter how many times I've tried it till now.  That's the intermittent nature of my problem.

 

The log from a previous error shows:  Failed to write sectors xxxxxx - xxxxxx.  Reason: Invalid address for write.  (where xxxxxx are numbers)

What exactly causes an invalid address to be created in the first place? 

 

... 1. Is the correct address generated by Imgburn and then gets corrupted somehow?

... 2. How does Imgburn know the address is invalid? (if it created the address in the first place)

 

Trying to understand what could cause an invalid address for write in test mode to help me troubleshoot this problem.

 

Thanks,

Raptor88

Edited by Raptor88
Link to comment
Share on other sites

That isn't an error you normally get first. It typically follows a 'write error' of some sort and I wonder if that initial error isn't being lost somewhere in your system.

 

The error comes directly from the drive and basically means you're trying to write to somewhere you can't.

 

On most discs, sectors need to be written to in sequential order. You can't write sectors 0-15 and then 32-47 or whatever. If you try, you'll get an 'invalid address for write' error back when submitting the command to write 32-47.

 

Something is messing up somewhere but you can't do much to troubleshoot when all you've got is an intermittent issue.

Link to comment
Share on other sites

That isn't an error you normally get first. It typically follows a 'write error' of some sort and I wonder if that initial error isn't being lost somewhere in your system.

 

The error comes directly from the drive and basically means you're trying to write to somewhere you can't.

 

On most discs, sectors need to be written to in sequential order. You can't write sectors 0-15 and then 32-47 or whatever. If you try, you'll get an 'invalid address for write' error back when submitting the command to write 32-47.

 

Something is messing up somewhere but you can't do much to troubleshoot when all you've got is an intermittent issue.

 

Oh, just knowing that the error comes directly from the drive is very helpful.  That means the address Imgburn sends to the drive is getting corrupt between the CPU > Southbridge chip that has the SATA controller > SATA cable > optical drive.  I have replaced the optical drive plus tried an Optiarc drive, and I replaced the SATA cable and plugged the SATA cable into a different SATA port on the motherboard.  So would you say that the problem is probably in the Southbridge chip on the motherboard?  Your best guess is fine.

 

Thanks,

Raptor88

Link to comment
Share on other sites

Not necessarily, your drive could just be messing up the burn and its firmware isn't handling it very well, reporting that error when it should be reporting something else.

 

Thanks for sharing your analysis.  I need to figure out why:

  1. The original optical drive in the Dell XPS 8500 had the problem.
  2. A new Liteon drive updated to the latest firmware has the problem.
  3. A Sony Optiarc drive has the problem.
  4. Replaced the SATA cable and plugged into a different SATA II header on the motherboard has the problem.

I'm testing in safe mode now and will do that all day to see what happens.  One thing I notice is that using the Win8 resource monitor, the network "TCP Connections" graph is maxing out when the normal Win8 is running.  But when in safe mode, the "TCP Connections" drops down to horizontal line number 2 (out of 10 horizontal lines) after about 30 seconds and stays there.  Think that the TCP Connections maxing out in normal Win8 could be the problem?

Edited by Raptor88
Link to comment
Share on other sites

 

Not necessarily, your drive could just be messing up the burn and its firmware isn't handling it very well, reporting that error when it should be reporting something else.

 

Thanks for sharing your analysis.  I need to figure out why:

  1. The original optical drive in the Dell XPS 8500 had the problem.
  2. A new Liteon drive updated to the latest firmware has the problem.
  3. A Sony Optiarc drive has the problem.
  4. Replaced the SATA cable and plugged into a different SATA II header on the motherboard has the problem.

I'm testing in safe mode now and will do that all day to see what happens.  One thing I notice is that using the Win8 resource monitor, the network "TCP Connections" graph is maxing out when the normal Win8 is running.  But when in safe mode, the "TCP Connections" drops down to horizontal line number 2 (out of 10 horizontal lines) after about 30 seconds and stays there.  Think that the TCP Connections maxing out in normal Win8 could be the problem?

 

 

The problem appears to be solved. 

 

Actually prior to posting here, I noticed a high amount of TCP Connections so was wondering if an infection was causing secret internet connections.  Or if it wasn't the TCP Connections, maybe a different infection was causing the problem.  I was thinking about using the Windows "Startup" to disable all of the startup programs or to use Safe mode to do the same + the minimal driver loads.  If it was an infection, then using "Startup" to disable start up programs might not have stopped the problem from happening.  Using Safemode seemed like a more sure way but I was wondering if even that would stop any infection from doing its thing.

 

Luckily Safe mode did appear to stop the problem from happening.  (Intermittent problem so couldn't say for sure.)  A restore of an earlier backup did not resolve the problem so I restored a backup that was done when I first setup the PC for my friend.  Since doing that restore, the problem has not happened.  Will see how it goes in actual use but the problem appears to have been resolved.

 

Thanks for the help,

Raptor88

Edited by Raptor88
Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

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