VSO Software Forum

If you are getting an error similar to this in your log file :

011-06-27 19:31:16 Warning Cannot get stream information. Maybe file format [AVCHD/BDMV] was misdetected due to incorrect file extension.
2011-06-27 19:31:16 Warning Stream information exception: "Access violation at address 7721FC47 in module 'ntdll.dll'. Write of address 00000014"

or

2011-06-11 19:06:46 Info Une erreur est survenue durant la conversion
2011-06-11 19:06:46 Warning Cannot get stream information. Maybe file format [AVCHD/BDMV] was misdetected due to incorrect file extension.
2011-06-11 19:06:46 Warning Stream information exception: "Access violation at address 76F28DA9 in module 'ntdll.dll'. Write of address 00000014"

It is most likely because you have updated your Nvidia video card to the latest driver update. This latest update seems to cause problems.

Revert to version 260.99 or 270.61 and you should not have a problem.

Well, no offense, but is it really clear that this is a bug in the Nvidia drivers? The fact that the driver causes the access violation doesn't really mean that there's a bug in the driver. It can also mean that an application calls a driver interface with invalid values.
Honestly, I think chances are that this is an issue in the BlueRay Converter instead. And downgrading to an obsolete driver just to work around an application bug might be a temporary solution, but surely not the final one.
So putting the blame on the driver without any further investigation seems to be a little overhasty.

I agree Oxdeadbeef. I don't know who's side the problem is on yet...

I wished there was any progress on this issue, as the problems persists with 280.19.
Was the problem at least root caused after all this time?

I have been having this same problem - However it doesnt happen if I choose DVD as the output (but does do it for all others, like XBOX, MKV etc)

I just upgraded to 280.19 drivers and rebooted and its the same issue.

Weird!

hopefully this problem will be corrected in coming version (1-2 weeks)

Some output profiles don't use cuda, so the problem doesn't occur.

post edited

a correction for the nvidia compatibility problem is coming