LIGHTNING UK! Posted September 27, 2008 Posted September 27, 2008 I know lots of you are seeing ' Program Memory Area Update Failure ' (or ' PMA Update Failure ') type errors and today I've spent a while figuring out why you seem to be complaining that it's just with ImgBurn and other programs don't show the error. The answer is simple, they just ignore it / don't tell you about it. The error seems to occur most frequently for people burning DVD+R in LiteOn and Samsung drives. It doesn't seem to matter much if you're using junk media or top of the line Verbatim stuff. Here's a typical example of a log from ImgBurn where the 'Program Memory Area Update Failure' error is shown: I 13:35:35 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1920718)I 13:40:01 Synchronising Cache... I 13:40:07 Closing Track... I 13:40:10 Finalising Disc... W 13:40:28 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Program Memory Area Update Failure W 13:40:28 Finalise Disc Failed! - Reason: Program Memory Area Update Failure W 13:40:28 Retrying (1 of 3)... So anyway, what you'll see as you scroll down through this post is the raw I/O captured by special software as it flows from the drive to the burning application. It allows me to see I/O errors that the burning apps may or may not display. As a bit of background info, when you see 'SENSE' in the left column it basically means the drive errored out. Some are to be expected, some aren't. The codes within the data to the right of that (know as 'sense data' or 'sense area') tell the program what the problem was. The code for the 'Program Memory Area Update Failure' error is 73 04. Application : CDBurnerXP v4.2.2.984 Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 51 00 00 00 00 00 00 00 86 00 READ DISC INFO IN 00 20 05 01 01 01 02 20 00 00 00 00 00 00 00 00 00 00 00 00 00 23 05 40 00 00 00 00 00 00 00 00 . ..... .............#.@........ 00 00 00 00 .... CMD 35 02 00 00 00 00 00 00 00 00 SYNC CACHE ok CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 ok CMD 00 00 00 00 00 00 TEST UNIT READY ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error Application : Ashampoo Burning Studio 6 Free v6.71 Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 80 ff ff 00 00 medium error CMD 1e 00 00 00 00 00 MEDIA REMOVAL ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 43 02 00 00 00 00 00 03 24 00 READ TOC/PMA IN 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ SENSE 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 invalid cdb CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 25 00 00 00 00 00 00 00 00 00 READ CAPACITY IN 00 00 00 00 00 00 08 00 ........ SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 80 ff ff 00 00 medium error Application : Nero v8.3.6.0 Reported a successful burn? : No Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff a7 not ready CMD 51 00 00 00 00 00 00 00 20 00 00 00 READ DISC INFO IN 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 51 00 00 00 00 00 00 00 20 00 00 00 READ DISC INFO IN 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 51 00 00 00 00 00 00 00 20 00 00 00 READ DISC INFO IN 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................ SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error CMD 46 02 00 00 00 00 00 00 cc 00 00 00 GET CONFIG IN 00 00 00 40 00 00 00 1b 00 00 03 38 00 15 00 00 00 16 00 00 00 2b 00 00 00 1b 01 00 00 1a 00 00 ...@.......8.........+.......... 00 14 00 00 00 13 00 00 00 12 00 00 00 11 00 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00 ................................ 00 02 00 00 .... CMD 46 02 00 00 00 00 00 00 cc 00 00 00 GET CONFIG IN 00 00 00 40 00 00 00 1b 00 00 03 38 00 15 00 00 00 16 00 00 00 2b 00 00 00 1b 01 00 00 1a 00 00 ...@.......8.........+.......... 00 14 00 00 00 13 00 00 00 12 00 00 00 11 00 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00 ................................ SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error Application : BurnAware Free v2.1.3.1 Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 00 00 medium error CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 03 00 00 00 20 00 REQUEST SENSE SENSE 70 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 35 02 00 00 00 00 00 00 00 00 SYNC CACHE ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 00 00 medium error Application : CloneCD v5.3.1.3 Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 00 00 medium error CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 51 00 00 00 00 00 00 00 20 00 READ DISC INFO IN 00 20 05 01 01 01 02 20 00 00 00 00 00 00 00 00 00 00 00 00 00 23 05 40 00 00 00 00 00 00 00 00 . ..... .............#.@........ CMD 00 00 00 00 00 00 TEST UNIT READY ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 00 00 medium error Application : CloneDVD v2.9.1.9 Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 51 00 00 00 00 00 00 00 20 00 READ DISC INFO IN 00 20 05 01 01 01 02 20 00 00 00 00 00 00 00 00 00 00 00 00 00 23 05 40 00 00 00 00 00 00 00 00 . ..... .............#.@........ CMD 00 00 00 00 00 00 TEST UNIT READY ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error Application : InfraRecorder v0.45.0.0 (Unicode) Reported a successful burn? : Yes Was it actually successful? : No Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff ff 00 00 not ready CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 5a 00 30 00 00 00 00 00 02 00 MODE SENSE 30 IN 00 16 .. CMD 00 00 00 00 00 00 TEST UNIT READY ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 73 04 00 00 00 00 medium error Application : BwgBurn v0.7.1 Reported a successful burn? : No Was it actually successful? : No BwgBurn seemed to use the 'Incremental' Write Type rather than 'DAO/SAO' as all the other application have done. This can make a difference to certain drives (and I mean individual ones, not a certain brand/model!) on certain media but really it's just fluke. Phase Data Description ----- ------------------------------------------------------------------------------------------------------ -------------------------------- CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff fc 00 00 not ready CMD 5c 00 00 00 00 00 00 00 0c 00 READ BUFFER CAP IN 00 0a 00 00 00 15 80 00 00 00 00 00 ............ CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff fc 00 00 not ready CMD 5c 00 00 00 00 00 00 00 0c 00 READ BUFFER CAP IN 00 0a 00 00 00 15 80 00 00 00 00 00 ............ CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 70 00 02 00 00 00 00 0a 00 00 00 00 04 08 00 80 ff fc 00 00 not ready CMD 5c 00 00 00 00 00 00 00 0c 00 READ BUFFER CAP IN 00 0a 00 00 00 15 80 00 00 00 00 00 ............ CMD 00 00 00 00 00 00 TEST UNIT READY SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 0c 00 00 00 00 00 00 00 write error CMD 1e 00 00 00 00 00 MEDIA REMOVAL ok CMD 00 00 00 00 00 00 TEST UNIT READY ok CMD 00 00 00 00 00 00 TEST UNIT READY ok SENSE 71 00 03 00 00 00 00 0a 00 00 00 00 0c 00 00 00 00 00 00 00 write error Although BwgBurn did pick up on the 'Write Error' code (0C 00) and display it to the user, I personally don't like the way it KILLS your machine when sending I/O commands in a loop with no delay between them when there's absolutely no reason to. So to sum up, the only application (along side ImgBurn) that does what it's supposed to and actually tell you about the error is Nero v8.3.6.0. If you're using one of the other apps and thinking it's wonderful because you're not getting the PMA error, think again... you are! Now, take your rose tinted specs off and use a program that doesn't keep you in the dark about potential problems with your burns.
Night_Raven Posted September 27, 2008 Posted September 27, 2008 Thank you for your effort. Very nice to know all this.
nxpa76 Posted January 26, 2009 Posted January 26, 2009 so what can I do if I'm experiencing this problem??? thanks in advance.
mmalves Posted January 26, 2009 Posted January 26, 2009 Making your own thread and posting a log of the failed burn would be a good start
uradodah Posted March 22, 2009 Posted March 22, 2009 Making your own thread and posting a log of the failed burn would be a good start I know this is a late post based on date of the original - but it appears that the topic is still active. With that said, "nxpa76" appears to be asking a valid question IMHO. While I'm thankful that the research was done for us - and posted for everyone else to see - it doesn't do a whole lot to actually *help* anyone. I just started experiencing this issue and am doing research on it to get better educated. This info does help, no question. However, telling someone to use a better burning application that tells us about the error instead of ignoring it doesn't help anyone. It doesn't explain WHY we're getting the issue and WHAT can be done to RESOLVE it. In my case, I'm already using Verbatim discs - and always have. The overwhelmingly 'typical' or standard response on this forum appears to be 'use a better media'. Well - I'm already doing that. So - this information doesn't do a whole lot for me. 1. I'm already using an application that doesn't mask or gloss over the OPC or PMA issue. Thanks ImgBurn! 2. I'm already using a high quality media and don't use anything other than Verbatim. Please help me understand how this info helps me actually attempt to resolve my issue based on these 2 facts. If I'm missing something, great. I'll offer my apologies in advance. I *have* posted specific, detailed information about my errors in a separate post and have gotten responses that have been VERY helpful. However, nobody has offered any possible root causes for this error - nor has anyone offered advice on possible solutions...outside of enabling OPC. All of this said, I appreciate your time and attempts to provide assistance to all of us!
Cynthia Posted March 22, 2009 Posted March 22, 2009 It doesn't explain WHY we're getting the issue and WHAT can be done to RESOLVE it. The problem is in the Lite-On burners and the only one who can resolve it is Lite-On itself. Today they seems to be more interested in creating and selling faster and faster burners. In stead they should take a moment and try to solve the current issues with their burners. LUK posted in a thread over at CDFreaks that was used to try out new firmware for the Lite-On writers and no reply. http://club.cdfreaks.com/f44/liteon-dh20a3...tml#post2133216 Even the latest models, like iHAS422 suffers from this problem. The only working solution is to avoid Lite-On burners if you plan to use +R media.
uradodah Posted March 22, 2009 Posted March 22, 2009 Cynthia, Thanks for the reply. My post was meant from a more 'generic' perspective - meaning - not focused on any one specific drive. I currently have a Matshita drive and am experiencing this issue. You posted some helpful information in the topic I created specific to my issue. Thanks for that as well. I guess, where I'm coming from, is what does this error really mean - OTHER THAN attributing it to the quality of media being used? Does it mean that a firmware update (if available) may help resolve the issue? Does it mean the drive is likely dying and needs to be replaced? Does it mean a good lens cleaning may help - and if so - any idea on how to clean the lens in a slot-load notebook drive? That's what I'm after. Thus far, through searching here (and I could have missed something), searching Google and reading a ton of info from other sites/forums, the majority of the posts just tell people to 'buy a better quality media'. I'm trying to look past that since it's not an issue for everybody every time. I know it's hard to accurately diagnose (if not impossible) every problem someone has related to this issue. However, a few educated guesses would definitely help! For example, in my case, if you 'experts' believe my Matshita drive may be (or is likely) on a slippery slope to its eventual death, I could call Dell to begin the process of getting it replaced prior to my warranty expiring. This kind of info also helps reduce the likelihood of producing 'average' burns that work *for now* only to start burning expensive coasters down the road because we didn't take proactive steps ahead of time. I hope you can understand where I'm coming from. The information in this topic - and in this forum - is top-notch and informative. I just think it's too easy at times to fall back on the 'old faithful' solution - 'go buy a better quality media'.
Cynthia Posted March 22, 2009 Posted March 22, 2009 I guess, where I'm coming from, is what does this error really mean - OTHER THAN attributing it to the quality of media being used? Does it mean that a firmware update (if available) may help resolve the issue? Does it mean the drive is likely dying and needs to be replaced? Does it mean a good lens cleaning may help - and if so - any idea on how to clean the lens in a slot-load notebook drive? You own problem is this: E 03:19:06 Failed to set L0 Data Zone Capacity!E 03:19:06 Reason: Power Calibration Area Error This guy in this thread had more or less the same issue - only that his burner reported a different error message - but it failed to set the L0 Data Zone Capacity. He is also using 'less good' media that could indicate a reason for the problem. W 22:09:44 Failed to set L0 Data Zone Capacity!W 22:09:44 Reason: No Seek Complete A firmware update solved his issue. I just think it's too easy at times to fall back on the 'old faithful' solution - 'go buy a better quality media'. In your case there have been no new firmware released for your burner in at least 1.5 year and I doubt there ever will be any new one released as it's that long since it was released. So what to do - buy better media? It will not help you as you already use the best media. You have already got the burner replaced and still same issue. That leaves just one option left - replace it with a better brand of burner. The years that I have been in DVD forums - the Matshita burners have been the most frequent burners to have burning problems. So why do they still put them in computers? Because they are cheap and computer companies want to make the computers as cheap as possible. To put in a better brand of burner usually costs more and consumers tend to buy the cheapest computer that they can find. With the prices of todays DVD burners - go for a good burner and it will save you the price of many burned coasters.
OpTicaL Posted March 31, 2009 Posted March 31, 2009 (edited) A update from what I reported in this thread. What's interesting is that this error occurs whenever I burn a DVD5 under 4GiB. Anything I burn close to the 4.36GiB limit this error never occurs. I've noticed this in other people's reports as well. Edited March 31, 2009 by OpTicaL
atomicrabbit Posted August 7, 2009 Posted August 7, 2009 (edited) What's interesting is that this error occurs whenever I burn a DVD5 under 4GiB. Anything I burn close to the 4.36GiB limit this error never occurs. I've noticed this in other people's reports as well. Ok this is the first time I've seen this error before and I find your post interesting because it's only been happening to me with a 3.67gb DVD Video. Don't know why it's happening but I've already made 4 coasters Any help? Has this been solved yet? I'm using ImgBurn v2.5.0.0 with a Samsung SH-S203B burner and Verbatim DVD+R's (although it's been said that media type/quality is unrelated) EDIT: See my post here: http://forum.imgburn.com/index.php?showtop...st&p=100994 Edited August 7, 2009 by atomicrabbit
Cynthia Posted June 4, 2010 Posted June 4, 2010 Noticed that my Lite-On eSAU108 didn't trigger the 'Program Memory Area Update Failure' error, while my older firmware on the iHAS120 did trigger it. I wonder if this bug has been fixed in recent firmwares. I 15:43:19 ImgBurn Version 2.5.1.3 Beta started!I 15:43:19 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 15:43:19 Total Physical Memory: 4 193 460 KB - Available: 2 273 380 KB I 15:43:19 Initialising SPTI... I 15:43:19 Searching for SCSI / ATAPI devices... I 15:43:20 -> Drive 1 - Info: PIONEER DVD-RW DVR-115D 1.22 (M:) (ATA) I 15:43:20 -> Drive 2 - Info: PIONEER DVD-RW DVR-118L 1.02 (N:) (ATA) I 15:43:20 -> Drive 3 - Info: ATAPI iHAS120 6 7L0M (O:) (SATA) I 15:43:20 -> Drive 4 - Info: PHANTOM DVD-RAM DVDR V10 88.0 (R:) (SCSI) I 15:43:20 -> Drive 5 - Info: PIONEER DVD-RW DVR-216D 1.09 (P:) (SATA) I 15:43:20 -> Drive 6 - Info: Optiarc DVD RW AD-7200A 1.09 (H:) (USB) I 15:43:27 -> Drive 7 - Info: Slimtype eSAU108 4 2L01 (I:) (USB) I 15:43:27 Found 2 DVD±RWs, 4 DVD±RW/RAMs and 1 BD-RE/HD DVD-RAM! I 15:44:00 Operation Started! I 15:44:00 Source File: -==/\/[DISCOVERY IMAGE]\/\==- I 15:44:00 Source File Sectors: 1 920 719 (MODE1/2048) I 15:44:00 Source File Size: 3 933 632 512 bytes I 15:44:00 Source File Volume Identifier: DISCOVERY_IMAGE I 15:44:00 Source File File System(s): None I 15:44:00 Destination Device: [0:0:0] Slimtype eSAU108 4 2L01 (I:) (USB) I 15:44:00 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 3x; 4x; 6x; 8x) I 15:44:00 Destination Media Sectors: 2 295 104 I 15:44:00 Write Mode: DVD I 15:44:00 Write Type: DAO I 15:44:00 Write Speed: MAX I 15:44:00 DVD+R Reserve Track: Yes I 15:44:00 Link Size: Auto I 15:44:00 Lock Volume: Yes I 15:44:00 Test Mode: No I 15:44:00 OPC: Yes I 15:44:00 BURN-Proof: Enabled I 15:44:00 Write Speed Successfully Set! - Effective: 11 080 KB/s (8x) I 15:44:00 Book Type Setting: DVD-ROM I 15:44:00 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 15:44:47 Filling Buffer... (40 MB) I 15:44:47 Writing LeadIn... I 15:44:48 Writing Session 1 of 1... (1 Track, LBA: 0 - 1920718) I 15:44:48 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1920718) I 15:53:26 Synchronising Cache... I 15:53:29 Closing Track... I 15:53:30 Finalising Disc... I 15:53:51 Exporting Graph Data... I 15:53:51 Graph Data File: C:\Users\Cynthia\AppData\Roaming\ImgBurn\Graph Data Files\DISCOVERY_IMAGE_Slimtype_eSAU108_4_2L01_DEN-4-JUNI-2010_15-44_YUDEN000-T02-00_MAX.ibg I 15:53:51 Export Successfully Completed! I 15:53:51 Operation Successfully Completed! - Duration: 00:09:51 I 15:53:51 Average Write Rate: 7 430 KB/s (5.4x) - Maximum Write Rate: 10 777 KB/s (7.8x) I 17:01:04 ImgBurn Version 2.5.1.3 Beta started!I 17:01:04 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 17:01:04 Total Physical Memory: 4 193 460 KB - Available: 2 376 984 KB I 17:01:04 Initialising SPTI... I 17:01:04 Searching for SCSI / ATAPI devices... I 17:01:04 -> Drive 1 - Info: PIONEER DVD-RW DVR-115D 1.22 (M:) (ATA) I 17:01:04 -> Drive 2 - Info: PIONEER DVD-RW DVR-118L 1.02 (N:) (ATA) I 17:01:04 -> Drive 3 - Info: ATAPI iHAS120 6 7L0M (O:) (SATA) I 17:01:04 -> Drive 4 - Info: PHANTOM DVD-RAM DVDR V10 88.0 (R:) (SCSI) I 17:01:05 -> Drive 5 - Info: PIONEER DVD-RW DVR-216D 1.09 (P:) (SATA) I 17:01:05 -> Drive 6 - Info: Optiarc DVD RW AD-7200A 1.09 (H:) (USB) I 17:01:05 -> Drive 7 - Info: Slimtype eSAU108 4 2L01 (I:) (USB) I 17:01:05 Found 2 DVD±RWs, 4 DVD±RW/RAMs and 1 BD-RE/HD DVD-RAM! I 17:01:15 Operation Started! I 17:01:15 Source File: -==/\/[DISCOVERY IMAGE]\/\==- I 17:01:15 Source File Sectors: 1 920 719 (MODE1/2048) I 17:01:15 Source File Size: 3 933 632 512 bytes I 17:01:15 Source File Volume Identifier: DISCOVERY_IMAGE I 17:01:15 Source File File System(s): None I 17:01:15 Destination Device: [4:0:0] ATAPI iHAS120 6 7L0M (O:) (SATA) I 17:01:15 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 4x; 6x; 8x) I 17:01:15 Destination Media Sectors: 2 295 104 I 17:01:15 Write Mode: DVD I 17:01:15 Write Type: DAO I 17:01:15 Write Speed: MAX I 17:01:15 DVD+R Reserve Track: Yes I 17:01:15 Link Size: Auto I 17:01:15 Lock Volume: Yes I 17:01:15 Test Mode: No I 17:01:15 OPC: Yes I 17:01:15 BURN-Proof: Enabled I 17:01:15 Write Speed Successfully Set! - Effective: 11 080 KB/s (8x) I 17:01:15 Book Type Setting: DVD-ROM I 17:01:15 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 17:01:51 Filling Buffer... (40 MB) I 17:01:51 Writing LeadIn... I 17:01:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 1920718) I 17:01:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1920718) I 17:08:18 Synchronising Cache... I 17:08:25 Closing Track... I 17:08:26 Finalising Disc... W 17:08:44 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Program Memory Area Update Failure W 17:08:44 Finalise Disc Failed! - Reason: Program Memory Area Update Failure W 17:08:44 Retrying (1 of 3)... I 17:09:05 Exporting Graph Data... I 17:09:06 Graph Data File: C:\Users\Cynthia\AppData\Roaming\ImgBurn\Graph Data Files\DISCOVERY_IMAGE_ATAPI_iHAS120_6_7L0M_DEN-4-JUNI-2010_17-01_YUDEN000-T02-00_MAX.ibg I 17:09:06 Export Successfully Completed! I 17:09:06 Operation Successfully Completed! - Duration: 00:07:45 I 17:09:06 Average Write Rate: 10 029 KB/s (7.2x) - Maximum Write Rate: 11 165 KB/s (8.1x)
djmasturbeat Posted December 25, 2010 Posted December 25, 2010 this seems to affect my LG (HL) BD burner as well. this came as an add-on to another issue (Cannot Write Medium - Incompatible Format) but i saw this topics problem at the very beginning of a bad burn. (my other thread) http://forum.imgburn.com/index.php?showtopic=16745&st=0&gopid=126661entry126661 log pertaining to this topic, too: I 09:20:15 Source File Volume Set Identifier: 3D994A8500A1811D I 09:20:15 Source File Application Identifier: ImgBurn v2.5.4.0 I 09:20:15 Source File Implementation Identifier: ImgBurn I 09:20:15 Source File File System(s): UDF (2.50) I 09:20:16 Destination Device: [1:0:0] HL-DT-ST BD-RE WH10LS30 1.00 (E:) (ATA) I 09:20:16 Destination Media Type: BD-R (Disc ID: VERBAT-IMw-000) (Speeds: 2x) I 09:20:16 Destination Media Sectors: 12,219,392 I 09:20:16 Write Mode: BD I 09:20:16 Write Type: DAO I 09:20:16 Write Speed: MAX I 09:20:16 BD-R Verify Not Required: Yes I 09:20:16 Link Size: Auto I 09:20:16 Lock Volume: Yes I 09:20:16 Test Mode: No I 09:20:16 OPC: No I 09:20:16 BURN-Proof: Enabled I 09:20:16 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 09:20:46 Filling Buffer... (124 MB) I 09:20:54 Writing LeadIn... W 09:20:59 Failed to Write Sectors 0 - 31 - Reason: Program Memory Area Update Failure W 09:20:59 Retrying (1 of 20)... I 09:20:59 Writing LeadIn... I 09:20:59 Writing Session 1 of 1... (1 Track, LBA: 0 - 10584479) I 09:20:59 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 10584479) I 10:01:43 Synchronising Cache... I 10:01:50 Closing Track... I 10:01:51 Finalising Disc... W 10:01:56 Finalise Disc Failed! - Reason: Cannot Write Medium - Incompatible Format Unfortunately my understanding is LG will not do ANY fw updates for this drive
laurik Posted September 30, 2012 Posted September 30, 2012 (edited) Ho there, only now i saw that exist this thread, i just opened a one that have a similar issue http://forum.imgburn.com/index.php?showtopic=20582 Thnks Ale Edited September 30, 2012 by laurik
AlbertEinstein Posted May 13, 2018 Posted May 13, 2018 (edited) First post in 2008, last post before mine in 2012. So, I'm gonna bump it again. I just got the same type of error message today. And in my personal opinion this has: absolutely nothing to do with bad media. It is just my opinion, however, based upon the ratio of good burns to bad burns I get with most of the media (RiData) and the burner I use them with (LG-WH10LS30). This has to be one of the most disappointing errors to ever receive. The entire disc was burned successfully, brimming with 25+ GB of data. The only thing that failed is the closing process. Or, at least that's my perception of things. So, I have 25+ GB of data but a "ghost" TOC. Wonderful. Now, I'm learning something brand new from just reading this 10 year old thread (thank God the Internet is forever). Even though burn failures do not always (ever?) produce textual data in .log file, there is always the fall back to the actual output window itself, as shown by laurik in the screenshot above. I questioned/complained about this many times and no one ever thought to mention capturing the actual log window??? Anyhow, Here's a screen capture of the error message window and my log output window: Okay, The website keeps saying, "You are not allowed to use that image exension on this community." ???? It's a simple .png file extension. Are we erroneously detecting profanity in imgur's randonmly generated URLs?? I'll tinker with this but the link is there. I just can't show it inline with the post. https://imgur.com/wrPVBHq The first error message (before the burn) was followed up with a successful finish on retry #1 of 20. The failed attempts after the burn only tried 8x...why not 20? Were all attempts after 3 on my command? I can't remember but that would answer my question if so. The last 3 or 4 burns (from the same media spindle, 25-pack) I've done were without issues. Edited May 13, 2018 by AlbertEinstein
Recommended Posts