"Burn process failed"

[Wendya409]

While burning movies I sometimes get the error message that the burn process failed. This happens about a quarter of the time. Well I accidentally put one of these 'coasters' in my dvd player (thinking it was another disc) and it turned out the movie that had failed to burn on that disc HAD actually burned. And it played fine. So I decided to try some of the other discs that this had happened with and ALL of them except 2 worked perfectly.

So does anyone have any idea why this is happening? It's obviously great that the discs work but I'm confused as to why it would tell me that.

[setarip_old]

Hi!

I'm guessing that the full message referred to having "failed to complete leadout". Although this CAN result in a playable disc, it's usually indicative of a burner that's either dirty or "on the way out".

You might want to try running a DVD/CD cleaning disc on your burner. Maxell makes one that sells for about $10US...

[Wendya409]

Actually looking at the log this is what it says

1:30:04 AM #33 Phase 127 File APIProgress.cpp, Line 278
Generating DVD high compatibility borders

1:30:04 AM #34 CDR -1106 File WriterStatus.cpp, Line 167
Power calibration error
D: LITE-ON DVDRW LH-16W1P

1:30:04 AM #35 TRANSFER -24 File WriterStatus.cpp, Line 167
Could not perform end of Disc-at-once

1:30:04 AM #36 Phase 38 File APIProgress.cpp, Line 278
Burn process failed at 16x (22,160 KB/s)

1:30:04 AM #37 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.

1:30:04 AM #38 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.


Existing drivers:

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

I kept getting this message at first (I mean everytime I tried to burn anything) so I changed the power hook up to my dvdr since I had in other posts that the 'power calibration' thing was the problem. And that seemed to solve the problem for about a week and then I started getting this message again.

Looking at that do you still think that the drive may just be dirty or on the way out? And is there a way to know which of those it is? It's only about 4 weeks old so if there is a chance the drive itself is bad I want to return it while I still have the time! :)

I will try the cleaner too. Thanks for the help!!!

[shrink0]

Just curious, but what media did you use? and did you watch the whole backup disk?

[Wendya409]

I was using RICOH dvd+r and burning at 16x. And yes I have watched the whole process and everything seems the same through the whole process except the message I get at the end. It goes through the lead in and then the whole burn process to 100% then the lead out. Then either the 'burn successful message' or 'burn failed' message pops up and it seems that what message it decides to put up in entirely random.

[setarip_old]

Burn process failed at 16x (22,160 KB/s)Try burning at a LOWER speed -and try using Taiyo-Yuden or Verbatim media.

Now that you've mentioned that the burner is only 4 weeks old, there's no point in using a cleaning DVD/CD. It may, however, be a faulty burner. You'll have a better idea if this is the case, after you've tried burning a few DVDs using better media at a LOWER speed...

[GrofLuigi]

1:30:04 AM #37 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.

1:30:04 AM #38 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.

Anyone know what this is? Is it what I think it is?

GL

[foxyshadis]

I've been having nothing but trouble with nero since updating over the last few months (initially to fix another longstanding problem, which didn't get fixed, and broke a lot more - a later update did fix it, another later one broke it again). Bah, I give up on the whole 7 series and just hope that 8 won't be as horrible.

I find only bizarre workarounds like using Track-At-Once will work anymore, to fix these stupid disc-at-once bugs.

And while I've seen that DRM message, it doesn't seem to be related to what I was burning, which was an audio stream I'd synthesized. Switching to TAO worked.