Jump to content

Verify fails, no matter the input file, in the same place every time


jcumbie

Recommended Posts

All of a sudden, imgburn is not able to verify my discs. The discs seem to work but all have at least one error, and it is always the same exact LBA #. The log is trimmed, but I have been trying many different images, some of which I have previously burned just fine. I have removed and reconnected the drive, tried shutting down programs that are running (nothing new has been installed since it broke). I have a HP 1040r MH21 drive. I cant find firmware anywhere for it, but I dont see why I would need it considering it has been burning my backups just fine. I have tried setting the layerbreak manually.

 

Is my hardware going out on me?

 

 

; //****************************************\\

; ImgBurn Version 2.5.0.0 - Log

; Friday, 25 September 2009, 14:42:16

; \\****************************************//

;

;

I 13:24:47 ImgBurn Version 2.5.0.0 started!

I 13:24:47 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 13:24:47 Total Physical Memory: 3,013,932 KB - Available: 2,269,828 KB

W 13:24:47 Drive D:\ (FAT32) does not support single files > 4 GB in size.

W 13:24:47 DVD43 can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled!

I 13:24:47 Initialising SPTI...

I 13:24:47 Searching for SCSI / ATAPI devices...

I 13:24:48 Found 1 DVD-ROM and 1 DVD

Link to comment
Share on other sites

I guess you disabled this one?

 

W 13:24:47 DVD43 can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled!

Yes I did try it without dvd43 running. I havent tried disabling antivirus and burning a disk yet, but I'm not sure what difference that would make.

 

I ran it again just in case anyway. Apparently imgburn doesnt produce a log for verification jobs unless it is attached to a burn, because it didnt record the verify information. I did get errors again, while DVD43 was completely closed. They are only miscompare errors. I am going to try to verify a disk that burned and verified successfully in the past, and try to narrow it down to either a burning issue or a verification issue.

 

 

Also, I tried memtest. Let it run for 7 hours (left and came back). It reported 6 passes and 0 errors.

Edited by jcumbie
Link to comment
Share on other sites

I am going to try to verify a disk that burned and verified successfully in the past, and try to narrow it down to either a burning issue or a verification issue.

According to this post

 

http://forum.slysoft.com/showthread.php?t=27742

 

your burner is a rebadged Lite-On. That should make it possible to use a tool such as Nero DiscSpeed/Opti Drive Control/DVDInfoPro to do a quality scan of the disc. If you get terrible results - you know it's the burning phase (=burner/firmware/media) that is a joke.

 

http://www.cdspeed2000.com/

 

Use 8x as scanning speed for the first two programs and 4x for DVDInfoPro. You get most accurate results that way.

 

:)

Link to comment
Share on other sites

Try uninstalling dvd43, disabling it might not be enough (buggy). You might want to double check your filter drivers once you've done that too (do it via the 'Tools' menu in ImgBurn).

Filter drivers:

 

upper device filter redbook

upper class filter none found

device cd/dvd-rom device

lower class filter pxhelp20

lower class filter dvd43llh

lower class filter elbycdfl

lower class filter imapi

 

 

If that helps any. The only thing about the idea that dvd43 is the problem is that it has been installed since waaaay before I ever started burning with imgburn. And I have never disabled it in the past, even though imgburn gave the warning it has never broke anything, or interrupted the verify.

 

It appears that the burn phase is what has gone sour. I was able to verify a disc I burnt a month or so ago, no problem. The bad part is that this burner has less than 6 months of use in my computer, so if the burner has gone bad it did so very quickly.

 

 

This log info is from the gui, since this information doesnt show up in the actual log file, sorry if it doesnt look normal.

 

I 04:55:45 ImgBurn Version 2.5.0.0 started!

I 04:55:45 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 04:55:45 Total Physical Memory: 3,013,932 KB - Available: 1,890,952 KB

W 04:55:45 Drive D:\ (FAT32) does not support single files > 4 GB in size.

I 04:55:45 Initialising SPTI...

I 04:55:45 Searching for SCSI / ATAPI devices...

I 04:55:46 Found 1 DVD-ROM and 1 DVD

Link to comment
Share on other sites

I am going to try to verify a disk that burned and verified successfully in the past, and try to narrow it down to either a burning issue or a verification issue.

According to this post

 

http://forum.slysoft.com/showthread.php?t=27742

 

your burner is a rebadged Lite-On. That should make it possible to use a tool such as Nero DiscSpeed/Opti Drive Control/DVDInfoPro to do a quality scan of the disc. If you get terrible results - you know it's the burning phase (=burner/firmware/media) that is a joke.

 

http://www.cdspeed2000.com/

 

Use 8x as scanning speed for the first two programs and 4x for DVDInfoPro. You get most accurate results that way.

 

:)

I'm not sure how to use the programs you told me about. I tested the media for CRC errors in DVDInfoPro and it came back completely clean (this was a disc that did not verify in imgburn). I am burning the test disc for opti drive now.

 

The test disc in opti drive wont burn. It crashes opti burn... maybe because it isnt registered? I dont know. Windows screen pops up and says Opti Burn has encountered an error and needs to close, every time I try to burn the test disc. Even after a restart of the computer.

 

But, I have it doing a disc quality check on one of the discs that didnt verify in imgburn.

 

Another thing to mention, the discs that wont verify in imgburn come back as bad rips in abgx360 (while the image file used to burn them comes back all green), so it doesnt look like imgburn's verify is reporting incorrectly..

Edited by jcumbie
Link to comment
Share on other sites

DVDInfoPro scan of a bad disc is clean as well. I have to admit I am lost as to what exactly these programs are doing.

 

I'm probably way off, but it appears that the disc is fine when verified except against the image. It's like imgburn is altering the image, maybe correcting it, when it shouldnt be.

Link to comment
Share on other sites

That's not something ImgBurn does to an image file, it's what buggy filter drivers could do though so that's why I said to remove DVD43 and make sure its driver has gone from your filter drivers list.

Lightning. I understand what you mean. I have removed DVD43 completely from the system and tried again. Same problem so far.

 

To elaborate on what I was asking. Why is it that when the other programs mentioned (dvdinfopro, etc) scan the discs that imgburn and abgx say are bad (wont verify), dvdinfopro says it is a good disc, and reports no errors? What is dvdinfopro checking? abgx and imgburn are verifying the disc against an image file, and reporting it as a bad disc, while dvdinfopro does some other sort of verification (never asking for an image to verify against).

 

Since I last posted, I still have not been able to test the original drive in another machine. However, I have come across a Sony DRU-830A and installed it. I updated the firmware from SS20 to SS25, and although it seems to be able to verify discs with ABGX, it is having an issue burning DL discs. It is'nt showing that it is 'writing layer 0' and layer 1 like the other drive used to. Instead it just says 'writing track 1', and fails at around 4.9 billion bytes written, with the following error. Also, the drive seems to take a long time to read dual layer discs and it slows the entire computer down to a crawl when the disc is inserted.

 

I 00:27:02 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923)

W 00:51:44 Failed to Write Sectors 2237344 - 2237375 - Reason: Write Error

W 00:51:44 Retrying (1 of 20)...

W 00:51:44 Retry Failed - Reason: Invalid Address For Write

W 00:51:44 Retrying (2 of 20)...

W 00:51:44 Retry Failed - Reason: Invalid Address For Write

Edited by jcumbie
Link to comment
Share on other sites

Full log from disc I just tried:

 

I 19:47:34 ImgBurn Version 2.5.0.0 started!

I 19:47:34 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 19:47:34 Total Physical Memory: 3,013,932 KB - Available: 2,082,120 KB

W 19:47:34 Drive D:\ (FAT32) does not support single files > 4 GB in size.

I 19:47:53 Initialising SPTI...

I 19:47:53 Searching for SCSI / ATAPI devices...

I 19:47:54 Found 1 DVD

Link to comment
Share on other sites

Sorry for double/triple posting. I tried something else with positive results. The original DVD burner connected to the computer with a USB adapter is able to burn and verify no problem. I'm wondering if something else I did while trying to get the Sony drive working, fixed the original drive.

 

I did a bunch of stuff trying to get the DRU-830A to work. Among them, I reinstalled the drivers for my ide/atapi controller, because that was a suggestion in another thread for fixing the DRU-830A. I'm going to put the drive back into the computer and try again.

 

Anyhow, here is the log from the last burn.

 

I 20:31:40 Searching for SCSI / ATAPI devices...

I 20:31:40 Found 1 DVD

Link to comment
Share on other sites

Not sure what ultimately fixed me, but my old burner is working fine again. Woo Hoo! Saves me some $.

 

I 21:58:51 ImgBurn Version 2.5.0.0 started!

I 21:58:51 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 21:58:51 Total Physical Memory: 3,013,932 KB - Available: 2,300,772 KB

W 21:58:51 Drive D:\ (FAT32) does not support single files > 4 GB in size.

I 21:58:51 Initialising SPTI...

I 21:58:51 Searching for SCSI / ATAPI devices...

I 21:58:52 Found 1 DVD

Edited by jcumbie
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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