Nero Errors using "Verify Written Data"

I'm running Windows XP and using Nero 5.5.10.7b Enterprise Edition to burn CD's on a Plextor 24/10/40A CDRW. I'm burning to 80 min. Misui CDR's at 24X speed.
The burner is the primary slave on the IDE cable and not using DMA.

A lot of what I burn are drive images created with Drive Image 2002 or Norton's Ghost broken down into 640MB sizes. I turn on the option in Nero to "Verify Written Data" as I need these images to be exact. More often than not I get an error at the end of the burn stating the Verify has failed. Upon copying the images from the CD back to a secondary drive and doing a restore of the image to it's primary drive, it always fails.

I've tried just doing just a simulation which can run fine but then the actual burn error's on the Verify.

Tried with and without the wizard with the same results.
The syntax for the image files are xx-xx-xx.gho (example of a ghost image)

The Nero settings I'm using are:

Multisession:
No Multisession

ISO:
ISO Level 2
Mode1
ISO 9960
Joliet
Allow pathdepth of more than 8 directories
Allow more than 255 characters in path
Do not add the '1' ISO file version extension

Burn
Finalize CD
Write speed "24X "
Write Method "Track-at-once "
BurnProof is enabled

And finally of course the "Verify Written Data" is enabled as I need these images exact for quick system recovery.

Any suggestions at to what might be causing this or what I'm doing wrong?

 

Look in the Nero folder and see what further information you can gather on this error from RobotError.log and NeroHistory.log.

 

The only log I find is Nerohistory.log and what it tells me is:
#29 Phase 81 File dlgbrnst.cpp, Line 1653
Data verification failed

I've also save the log at the end of an unsucessfull burn but basically it tells me the same thing. That the Data Verification failed.

????

 

That doesn't give us much to go on.

Try reducing the size of the files, using ASCII mode, and Disk-At-Once. Try a slower burn speed.

Wish I could be more helpful.

Any idea what that dlgbrnst.cpp is? Is that the file you are burning?

I suppose an alternative is to zip the file and burn that. It may be a peculiarity of that file type.

 

Nicmos,

I had that to happen to me with one of my burning programs. I think it has something to do with the fact that it is an image file period. Not regular data files. Plus if you also compressed it.

Once I turned off the verify feature, the burn was successful.

Don't know if this helps any.

 

That verification feature seems to be overkill, anyway. Nero informs you during the burn process if any errors occur and I have never had a burn, out of several hundred, that showed no errors during the burn and was not perfect.

Turning off the verification is worth a try in case that is actually causing the problem, and I'll bet the rent that if the burn concludes without any error messages, it was successful (though that didn't seem to be the case, the damage may have been done late in the process by the verification attempt itself).

The only way to know for sure is try it. I know I never use verification any more even on the most important burns and immediately delete the source as soon as I see files on the CD.

 

Thanks for everyones help. I'ts given me some food for thought and a few things to try.

 

Data verification is done after the burn is complete so it cannot cause a problem with the burned CD. If you run scandisk on a burned CD using Nero Tools it usually indicates a bad sector on the last burned sector. This is normal and probably is caused by the lead-out at the end of a burn. Maybe this is why data verification fails.
Try doing critical burns at 1 step below maximum speed. Try to read the burned CD at less than meximum speed.
Also look for TY (Taiyo Yuden?) media.It is sold under several brands. You can identify it because it is made in Japan. Most Fuji media is TY.

 

Sorry, but I have to disagree here, since it locked up my whole computer when I burned an image file, & it got to the verification process. Only after I disabled the verify was I able to sucessfully complete the burn, & the computer be able to read the disk, even at a lower than maximum burn rate. Yes, I tried the lower burn rate. It did exactly the same thing, however not all computers are alike, even when the same OS, & burning program is installed.

My husband & I run the same OS, and mostly the same programs, and our comps are inherently different in reactions to some of the simplest things.

I use Memorex CD\R's. Have never had hardly any bad ones with them with either Nero, NTI, or MusicMatch. 1 or 2 bad out of 100 maybe. That's a pretty darn good average.

 

I found that enabling "Determine Maximum Speed" - Burn Tab - although slowing down the burn process had also eliminated any failed burnt process.

 

I'm doing some testing now using Easy CD Creator 5 to see if the results turn out the same. For whatever reason the images are fine (using Nero or Easy CD) until they get burned . I would suspect my burner but it is relatively new and I have no problem with any other types of burns.

I've tried burning at a slower speed, turn off verify because it is causing the problem, use ASCII mode and Disk-At-Once, use ISO level 1, to no avail.

Sadly the results are the same. When the images are xcopied to a 2nd drive and then restored they usually fail. It must be the nature of the image and how the burning software handls it.

 

I believe I've resolved this issue.

Turns out it was a faulty CD-ROM on the test system that I was using to xcopy image to the 2nd hard drive for the restore.

Swapped out the faulty unit and things work fine now.

 

Good you figured it out. The possibilities were dwindling. Thanks for letting us know.