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.
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
I have a Sony DRU500A burner and using Nero6 v-6.3.1.17, trying to copy a DVD Video and have been getting a PMA update failure? What does this mean? I have removed Nero and reinstalled it. My burner has the lastest driver. Before I took my burner out of my computer and smash it I thought I would check first if anyone else has encountered this error and found a work around.
-
danoj
Member- Joined:
- Jul 29, 2004
- Messages:
- 1
- Likes Received:
- 0
- Trophy Points:
- 11
Hello, I have same problem. I just bought LG GSA-4120B burner and I could finish only 2 DVDs (Memorex). All other ended with «PMA update failure».
Can anybody explain why ?
My configuration : AMD Barton 2500+, MB K7 Nforce2, Maxtor 120 GB, 512 MB RAM, DVD-ROM Toshiba -
[bold]Program Memory Area Update Failure [/bold]
Are you doing anything with your PC while you are burning? Like listening to music, surfing the web , and so on ? Do you have a lot of applications running in the background ?
Nero is telling you your PC is not feeding the data for the burn . Defragmenting your drive, closing other applications ,using good media and going for a coffee while the burn is in progress may solve your problem !Smiles!!
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
I do know that if your burning, not to do anything else on the computer. The computer take alot of your resources when burning. I usually do control-alt-delete (task manager) and end other programs like a firewall program or other that would use a lot of resources (no system running files). I’m pretty knowledgable when it comes to this kind of stuff, but nobody seems to know why I still get the errors. Some of the problems comes from the type of media I use. I’ve found that my Sony burner only works with Sony or Memorex DVD-R’s. It wont use anything else. Now when using Memorex its working 1 out of 4-5 times. I have not done a defrag lately but I will run one now, then try and burn a backup movie that’s on my HD. I will post another thread with my results. Thankx for the input.
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
Nope, Defraged both drives and still getting the stupid Nero error. Could be a hardware issue.
-
sly1171
Member- Joined:
- Aug 15, 2004
- Messages:
- 2
- Likes Received:
- 0
- Trophy Points:
- 11
I’m running into the same error with my Sony DRU 700A.
If It’s a hardware issue it’s more likely going to be an issue with the RAM chips. I’ll be able to ascertain if this is it tomorrow when I get a new RAM chip that I ordered to resolve a different issue. Another possibility that seems to have come up quite frequently on other forums is the media, but I have some reservations about that theory because I have two spools of the same brand and almost all of the media on the first spool burned just fine. Now I’m having problems with 2/3 of the disks I’ve used.
The PMA Update Error doesn’t occur because of Nero’s inability to keep the buffer full. That’s a Buffer Underrun error. Those are much more rare now thanks to technologies such as Smart-BURN. A PMA Update error, or Program Memory Area Update Error, occurs when the CD or DVD tries to close off the session but can’t write the updated TOC information to the Program Memory Area.
That being said, however, I have absolutely no idea how to prevent it. -
LxOxSxI
Member- Joined:
- Aug 15, 2004
- Messages:
- 7
- Likes Received:
- 0
- Trophy Points:
- 11
Have you thought of updating your nero to .20?
-LxOxSxI
-
ccampbell
Regular member- Joined:
- Mar 24, 2004
- Messages:
- 757
- Likes Received:
- 0
- Trophy Points:
- 26
Those who are having this issue, can you provide a copy of the Nero Log file from the failed write attempt?
Edit the Log file before posting so as not to show your Nero serial key of course.
The PMA area is the ‘Program Memory Area’ on the media. When you begin writing to a disc, in Track-At-Once mode the Lead-In is reseverd, but not written too yet as the data has yet to be written to the disc. And the Lead-in contains information as to where the data is located on the disc so that it can be retrieved later when you go to read the disc.
Till the Lead-In is written, this information is contained in the PMA on the disc. There is a limited number of times that you can write to the PMA, but you it’s impossible to fill that area up before you filled up the disc.
When you are unable to write to the PMA area, it’s normally caused by poor media, dust on the optical head, recording software problems, old firmware on the recorder, or a recorde in need of alignment. But 90% of the time its media related.
Regards,
Craig
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
I went to BestBuy and got a 10 pack of FujiFilm DVD-R 4x and so far no problems. I have heard that some memorex disc are bad. My question is, the disc that I did get the PMA error on, are those bad now?
-
ccampbell
Regular member- Joined:
- Mar 24, 2004
- Messages:
- 757
- Likes Received:
- 0
- Trophy Points:
- 26
Possibly.
If you have a colleague with a different model DVD Recorder, I would suggest seeing if they have trouble writing to that media.
Regards,
Craig
-
At this point I’ve found out that the type of media with the Sony DVD Writer doesn’t have anything to do with error.
You need to set the amount of megs of RAM for Nero to use, your Nero may be set to automatically which may be using to much RAM.
What I did in the Nero Express portion of Nero, I click on the MORE button.
Click on the configure button at the botton of the nero screen.
This will be bring you to a screen with tabs, select the ULTRABUFFER tab
On the drop down box that indicates METHOD, if this is set to automatic, change it to Manual Configuration, this will allow you to enter the amt of meg to let nero use. On the Data buffer size box I entered 50 for 50mb.
This worked for me. I think you should try it.
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
Thanks, I tried that and still didn’t work. Then I went to CompUSA and bought a Memorex 8X DVD Burner and you know what, it works, no PMA errors. I got the Memorex True8X Dual Format and it works great. So if anyone is looking into buying a Sony DVD Burner, dont. After all the problems that I’ve had with that, it’s not worth it. Plus the Sony DRU-500A cost me $300 when I bought it two years ago. This new Memorex drive is $110 at any CompUSA plus it comes with the full version of Nero 6 System Suite which that software alone runs $100. Thank for everyones input, it was a hardware issue.
-
sly1171
Member- Joined:
- Aug 15, 2004
- Messages:
- 2
- Likes Received:
- 0
- Trophy Points:
- 11
I have a Sony DRU-500A and a Sony DRU-700A. I was running into the same issue (see my earlier posts), but I recently found that when I don’t use the Nero Smart Start to launch Nero Burning ROM then I don’t run into the issue. I’ve tried Princo, Sonic and Matrix DVD-Rs and the media doesn’t seem to make any difference at all. If, however, I launch SmartStart first, I seem to run into the issue almost every time.
-
Sgt_USMC
Member- Joined:
- Oct 30, 2002
- Messages:
- 60
- Likes Received:
- 0
- Trophy Points:
- 16
Never heard of that, but you know I thought it was just a program issue at first and even tried burning with other burning softwares and still got the error. Come to find out it was my burner. It doesn’t matter on the media but now it will only burn memorex DVD-RW not any DVD-R’s. Well if anyone has a Sony burner, switch now. PS, the Sony tech support could not figure out my problem.
-
scarng
Member- Joined:
- Jan 29, 2003
- Messages:
- 1
- Likes Received:
- 0
- Trophy Points:
- 11
Same issues with PMA Update Failuer with Memorex DVD-R
(CMC MAG.AF1LOG FILES
Windows XP 5.1
IA32
WinAspi: —
ahead WinASPI: File ‘C:Program FilesAheadNeroWnaspi32.dll’: Ver=2.0.1.68, size=160016 bytes, created 7/22/2004 5:33:44 PM
Nero version: 6.3.1.20
Recorder: <SONY DVD RW DRU-500A> Version: 2.1a — HA 1 TA 0 — 6.3.1.20
Adapter driver: <atapi> HA 1
Drive buffer : 8192kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <SONY DVD RW DRU-500A >Version: 2.1a — HA 1 TA 0 — 6.3.1.20
Adapter driver: <atapi> HA 1=== Scsi-Device-Map ===
DiskPeripheral : WDC WD1200BB-18CAA0 atapi Port 0 ID 0 DMA: On
DiskPeripheral : WDC WD1200BB-00DAA1 atapi Port 0 ID 1 DMA: On
CdRomPeripheral : SONY DVD RW DRU-500A atapi Port 1 ID 0 DMA: On
CdRomPeripheral : SAMSUNG CDRW/DVD SM-352B atapi Port 1 ID 1 DMA: On
DiskPeripheral : fasttx2k Port 3 ID 0 DMA: Off
CdRomPeripheral : Generic DVD-ROM 1.0 d347prt Port 4 ID 0 DMA: Off=== CDRom-Device-Map ===
SONY DVD RW DRU-500A H: CDRom0
SAMSUNG CDRW/DVD SM-352B F: CDRom1
Generic DVD-ROM G: CDRom2
=======================AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (83886080) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 1023MB (1048096kB)
Free physical memory: 519MB (531672kB)
Memory in use : 49 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)12.9.2004
UDF/ISO compilation
1:09:19 PM #1 Phase 112 File dlgbrnst.cpp, Line 1855
DVD-Video files reallocation started1:09:19 PM #2 Phase 114 File dlgbrnst.cpp, Line 1855
DVD-Video files reallocation completed (no file modified)1:09:19 PM #3 Text 0 File Isodoc.cpp, Line 6065
Iso document burn settings
——————————————
Determine maximum speed : TRUE
Simulate : FALSE
Write : TRUE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 2 (Max. of 31 chars)
Character set : ISO 9660
Joliet :FALSE
Allow pathdepth more than 8 directories : FALSE
Allow more than 255 characters in path : FALSE
Write ISO9660 ;1 file extensions : TRUE1:09:19 PM #4 Phase 111 File dlgbrnst.cpp, Line 1855
DVD-Video files sorted1:09:19 PM #5 Text 0 File Reader.cpp, Line 126
Reader running1:09:19 PM #6 Text 0 File Writer.cpp, Line 124
Writer SONY DVD RW DRU-500A running1:09:19 PM #7 ISO9660GEN -11 File geniso.cpp, Line 3899
First writeable address = 0 (0x00000000)1:09:19 PM #8 ISO9660GEN -11 File geniso.cpp, Line 3899
First writeable address = 0 (0x00000000)1:09:19 PM #9 Text 0 File Burncd.cpp, Line 3173
Turn on Disc-at-once, using DVD media1:09:19 PM #10 Text 0 File DlgWaitCD.cpp, Line 247
Last possible write address on media: 2298495 (510:46.45, 4489MB)
Last address to be written: 2152255 (478:16.55, 4203MB)1:09:19 PM #11 Text 0 File DlgWaitCD.cpp, Line 259
Write in overburning mode: NO (enabled: CD)1:09:19 PM #12 Text 0 File DlgWaitCD.cpp, Line 2162
Recorder: SONY DVD RW DRU-500A, Media type: DVD-R
Disc Manufacturer: CMC MA — G. AF1
Disc Application Code: 64, Disc Physical Code: 1931:09:19 PM #13 Text 0 File DlgWaitCD.cpp, Line 420
>>> Protocol of DlgWaitCD activities: <<<
=========================================1:09:19 PM #14 Text 0 File ThreadedTransferInterface.cpp, Line 813
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original disc pos #0 + 2152256 (2152256) = #2152256/478:16.56
relocatable, disc pos for caching/writing not required/required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2152256 blocks [SONY DVD RW DRU-500A ]
—————————————————————1:09:19 PM #15 Text 0 File ThreadedTransferInterface.cpp, Line 984
Prepare recorder [SONY DVD RW DRU-500A ] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: «»
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4407820288, ISRC «»
DAO layout:
===========
__Start_|____Track_|_Idx_|_RecDep_|_CtrlAdr_
0 | lead-in | 0 | 0x00 | 0x41
0 | 1 | 0 | 0x00 | 0x41
0 | 1 | 1 | 0x00 | 0x41
2152256 | lead-out | 1 | 0x00 | 0x411:09:19 PM #16 Phase 24 File dlgbrnst.cpp, Line 1855
Caching of files started1:09:20 PM #17 Text 0 File Burncd.cpp, Line 4183
Cache writing successful.1:09:20 PM #18 Phase 25 File dlgbrnst.cpp, Line 1855
Caching of files completed1:09:20 PM #19 Phase 28 File dlgbrnst.cpp, Line 1855
Speed measurement started1:09:20 PM #20 Text 0 File ThreadedTransferInterface.cpp, Line 2344
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #01:11:21 PM #21 Text 0 File WriterStatus.cpp, Line 115
<SONY DVD RW DRU-500A > start writing Lead-Out at LBA 2152256 (20D740h), lenght 0 blocks1:11:21 PM #22 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion1:11:21 PM #23 Text 0 File dlgbrnst.cpp, Line 1713
Set remaining time: 0:00,000 (0ms) -> OK1:11:21 PM #24 Phase 29 File dlgbrnst.cpp, Line 1806
Speed measurement completed: 26.1x (36,044 KB/s)1:11:21 PM #25 Phase 36 File dlgbrnst.cpp, Line 1855
Burn process started at 4x (5,540 KB/s)1:11:22 PM #26 Text 0 File ThreadedTransferInterface.cpp, Line 2344
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #01:11:22 PM #27 Text 0 File dlgbrnst.cpp, Line 1713
Set remaining time: 13:21,950 (801950ms) -> OK1:11:22 PM #28 Text 0 File DVDR.cpp, Line 1942
Recording mode: Sequential Recording Mode1:11:22 PM #29 Text 0 File Mmc.cpp, Line 20531
Set BUFE: Power-Burn -> ON1:11:22 PM #30 Text 0 File DVDR.cpp, Line 2083
Start write address at LBA 0
DVD high compatibility mode: Yes1:11:22 PM #31 Text 0 File Cdrdrv.cpp, Line 8128
—- DVD Structure: Physical Format Information (00h) —-
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 0 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
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 …………….1:11:24 PM #32 Text 0 File Cdrdrv.cpp, Line 1294
13:11:24.515 — SONY DVD RW DRU-500AH1 T0 : Queue again later1:11:52 PM #33 SCSI -1194 File Cdrdrv.cpp, Line 1442
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x031C0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x73
Sense Qual: 0x04
CDB Data: 0x2A 0x00 0x00 0x00 0x08 0xC0 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0xF1 0x00 0x03 0xFF 0xFF 0x03 0xB0 0x12
0x00 0x00 0x00 0x00 0x73 0x041:11:52 PM #34 CDR -1194 File Writer.cpp, Line 304
PMA update failure1:11:52 PM #35 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion1:11:52 PM #36 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader1:11:52 PM #37 Text 0 File DVDR.cpp, Line 2325
EndDAO: Last written address was 22391:11:52 PM #38 Text 0 File dlgbrnst.cpp, Line 1713
Set remaining time: 0:00,000 (0ms) -> OK1:11:52 PM #39 Text 0 File dlgbrnst.cpp, Line 1713
Set remaining time: 0:00,000 (0ms) -> OK1:11:52 PM #40 Phase 38 File dlgbrnst.cpp, Line 1855
Burn process failed at 4x (5,540 KB/s)Existing drivers:
File ‘DriversPXHELP20.SYS’: Ver=2.02.50a, size=17136 bytes, created 1/8/2004 6:37:02 PM (Prassi/Veritas driver for win 2K)
File ‘Driversatapi.sys’: Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 8/4/2004 1:59:42 AM (Adapter driver for rec)Registry Keys:
HKLMSoftwareMicrosoftWindows NTCurrentVersionWinLogonAllocateCDROMs : 0 (Security Option)
Share This Page
Nov 27, 2007 3:45 PM in response to mlpk625
It came up on what screen?
When you were doing what?
With what?
With what versions of what?
On what computer?
And what recorded device?
Nov 27, 2007 4:07 PM in response to David S.
It came up on what screen?
idvd screen
When you were doing what?
burning and multiplexing stage 4
With what?
G5 tower
With what versions of what?
version 4.0.1
On what computer?
2 Gig dual drive G5
And what recorded device?
built in super drive
could really use your help—this DVD needs to be completed yesterday so thanks for your help!
Nov 27, 2007 4:12 PM in response to mlpk625
mlpk625 wrote:
It came up on what screen?
idvd screen
This isn’t the iDVD forum. The iDVD forum is
here, you’re more likely to get some info there.
That said, it may be media-related (as in related to the DVD itself). Try another disc or another brand, or be sure you’re using the correct kind of media (DVD-R vs. DVD+R, I’m not sure what’s supported).
Message was edited by: Wes Plate
Nov 27, 2007 4:22 PM in response to Wes Plate
here’s part of the problem…i’m sort of being the go-between—our editor is using the final cut pro to do this project—so, i realize i used the term idvd—and since i really don’t know a whole lot about this whole process—i posted it here. . .so, i’m not sure of the how this all works. . .so forgive my ignorance.
we are in the burning stage of this and want to get it off to replication in texas and everytime he goes to burn it all these errors (as posted by me) have come up. as the most recent person posted. . .am i posting these questions on the wrong forum—does he go from final cut pro to idvd when burning? thus, the reason for me to send these questions to that forum. ..i’m so sorry you are all dealing with a complete idiot, trust me, i feel really bad. i don’t like wasting anyone’s time.
Nov 27, 2007 4:37 PM in response to mlpk625
If you are going to replication, I strongly urge you move to DVD SP.
Replication is a beefier process and there are encode rates and treatment of audio that really do make a difference.
Go to the DVD SP forum and ask some questions about what you are doing.