Roxio_Central36.exe - Application Error, Error message when exiting application Options

[D.Cummens]

When exiting the main Easy Media Creator application launcher (roxio_central36.exe) I get the following error messsage:


Roxio_Central36.exe - Application Error


The instruction at "0x05d53435" referenced memory at "0x05fa3b28". The memory could not be "read".

Click OK to terminate the program.


I get the same error on both (XP SP2) computers. Any suggestions?

[gaper1]

are you able to use the software without any problems though?

[D.Cummens]

are you able to use the software without any problems though?

Yep, all modules seem to work fine so this is not a "tragic" error. I just adds another step to exiting the program. I does however indicate that all is not well yet with this release...

[H. Sams]

Yep, all modules seem to work fine so this is not a "tragic" error. I just adds another step to exiting the program. I does however indicate that all is not well yet with this release...

I too have this same problem and tried on two computers with WinXP - SP2. Same results. Contacted tech spoke with Daniel and his response is simply live with it. I am not a squeaky wheel but I do when purchasing programs expect that they operate properly and if they don't help me fix it or you fix it. So I guess the bottom line is LIVE WITH IT!

[Jong1]

I too have this same problem and tried on two computers with WinXP - SP2. Same results. Contacted tech spoke with Daniel and his response is simply live with it. I am not a squeaky wheel but I do when purchasing programs expect that they operate properly and if they don't help me fix it or you fix it. So I guess the bottom line is LIVE WITH IT!

John from Roxio has been discussing this problem with me in PM. They are investigating it actively and working on a solution.

[jim666]

John from Roxio has been discussing this problem with me in PM. They are investigating it actively and working on a solution.

I just installed Roxio 10 on my computer today (XP 3 ghz, 2g ram, etc) and also get the same message when exiting. I even went to control panel and tried to "repair" EMC 10 but it didn't help. Otherwise, too, everything is working.

Hope we can eliminate this nuisance.

[Starry173173]

Whatever happened to quality control? Or are some people out there not getting this error?

I tried making this program a DEP exception to see if that would help, but it didn't change anything.

[gi7omy]

Whatever happened to quality control? Or are some people out there not getting this error?

I tried making this program a DEP exception to see if that would help, but it didn't change anything.

That error didn't show up during beta testing and it's not really very common judging by the posts on it. It seems to crop up on some machines but not all

[DanMc]

I get the same message. All the modules that I've tried appear to work. It's annoying that something isnt right.

[Jacob Marley]

That error didn't show up during beta testing and it's not really very common judging by the posts on it. It seems to crop up on some machines but not all

It happens on my PC too, when I exit from VideoConvert. I guess that more users with this problem will comment.

Quality Control? You're having a laugh. The quality of this package is poor and the sort of errors surfacing - including the dreaded deletion of nearly all root directory files (C:\) when reinstalling (not just NTDLR!) - should have been found and cleared at the beta-test stage.

This post has been edited by Jacob Marley: Oct 28 2007, 01:01 AM

[james_hardin]

It happens on my PC too, when I exit from VideoConvert. I guess that more users with this problem will comment.

Quality Control? You're having a laugh. The quality of this package is poor and the sort of errors surfacing - including the dreaded deletion of nearly all root directory files (C:\) when reinstalling (not just NTDLR!) - should have been found and cleared at the beta-test stage.

You are having trouble finding your Reality Orientation and throwing around big words, like QC, won't help…

3 or 4 people in the million or so that are using this software is hardly a problem.

The NTDLR is strange. It effects only XP users and apparently only the English version. Roxio picked up on this from the forum posts and initiated action long before the hue and cry went up. They are working on this to isolate what is causing this and produce a fix that does no other harm.

Yet we have a lot of folks that chime in after all of this is in motion with their 'enlighten opinions'… Wow!

[jim666]

You are having trouble finding your Reality Orientation and throwing around big words, like QC, won't help…

3 or 4 people in the million or so that are using this software is hardly a problem.

The NTDLR is strange. It effects only XP users and apparently only the English version. Roxio picked up on this from the forum posts and initiated action long before the hue and cry went up. They are working on this to isolate what is causing this and produce a fix that does no other harm.

Yet we have a lot of folks that chime in after all of this is in motion with their 'enlighten opinions'… Wow!

The Uniform Commercial Code that enforces consumer rights under the "point of sale" implied warranty is a relief one should pursue if software defects prevent it from perfoming as advertised. No one has to live with a defective product.

[gi7omy]

The Uniform Commercial Code that enforces consumer rights under the "point of sale" implied warranty is a relief one should pursue if software defects prevent it from perfoming as advertised. No one has to live with a defective product.

That is true if and ONLY if the defect is common to over 50% of the articles supplied - the percentage case in this issue is in single figures

It's not a blanket coverage - if 50 people buy tyres from a batch of thousands and they get punctures - does that imply the entire batch is defective?

[jim666]

That is true if and ONLY if the defect is common to over 50% of the articles supplied - the percentage case in this issue is in single figures

It's not a blanket coverage - if 50 people buy tyres from a batch of thousands and they get punctures - does that imply the entire batch is defective?

Have no idea how your laws are in Ireland. Products here are based on individual purchases and batch history does not apply for a single defective product. Otherwise, no one could return anything. Incidentally, in the past I HAVE returned a defective tire (tyre) that seemed vulnerable to punctures. However, I am sure the retailer concerned with customer satisfaction makes the difference between how you are treated. It pays to buy from retutable firms.

[gi7omy]

Certainly if the product is defective - fit your new tyre to a wheel that is buckled and you have NO redress

The same applies to software - if there is a defect outside the app itself, then the defect is not IN the app but elsewhere

[Thutch]

I just installed EMC 10 today and get the same thing.
The instructions at "0x05cc63440" referenced memory at "0x5eb1fd0". The memory could not be "read.
Click OK to terminate the program.

Also when i received the package it was just a CD with no instructions at all. Should EMC previous versions be uninstalled be fore installing this version, or is an install over okay??

Are there any soulutions to the error problem yet?

[fredsaxxon]

This is not an isolated problem. I get the same thing except the references are to 0x06493437 and 0x066e3938 on a Windows Media Center box. And yes, I uninstalled V8 before installing V10.

Nor does the program work reliably for me. Modules sometimes hang up for no reason, other times work OK. "Convert Video" would die EVERY TIME I would try to 'Add Movies' -- until I enabled the 'create error log file' function ... go figure how that would fix it.

I've done the standard "clean" reinstall and that has no effect. (Be aware that you will have to uninstall EVERY module (13!) separately--uninstalling the Suite doesn't remove the individual applications. And then you have to check the Registry for any remnants that got left behind and remove them manually. Now that's user-friendly software).

Version 10 is bloated piece of garbage that seems nowhere close to ready-for-prime-time. I'd go back to Version 8 in a heartbeat if I thought I could completely remove 10 from the Registry and not screw it up worse than it is.

[gi7omy]

No-one ever said it was isolated - what was said is that it's not a common problem and, in most cases, is down to the OS or another app causing the problem.

What is causing it is beyond most of us - as has been said, it doesn't show up on the majority of machines, just some

[Jong1]

No-one ever said it was isolated - what was said is that it's not a common problem and, in most cases, is down to the OS or another app causing the problem.

What is causing it is beyond most of us - as has been said, it doesn't show up on the majority of machines, just some

I think we do know a cause, at least. Roxio and I have discussed it. Other applications (specifically Napster, which used to be part of Roxio, but maybe others) seem to use different versions of the same dll for burn/CDDB lookup and probably the same registry entry, so the applications fight over which 'owns it'.

Don't know if it is Napster's fault or Roxio, or if any other apps are affected, or indeed if there are any other causes. But one cause is fixable if Napster/Roxio get round to it!

This post has been edited by Jong1: Nov 23 2007, 04:31 PM

[gi7omy]

Maybe you and Roxio 'know' - as I said, most of us here don't (unless there's a Roxio icon at the name, we don't work for them) but I have heard nothing so far which may point to where the fault comes from

It never happened on my machine, even during the beta phase