Error 0x73ddllc7 (accidentally posted under photo impact)

[Mitch Hurricane]

Ok, I haven't even tried to capture anything and this error came up just playing with the sample files Ulead provides.

I told VS 10 + that I didn't want to save the project and the 0x73ddllc7 error popped up. I checked the forum and others have had this same problems with VS as far back as March. They didn't seem to get any answers then. Has anyone got a fix for this? I don't want to do any REAL work with this program just to find that this error will pop up and shut things down.

I have windows Xp and the exact error says : The instruction at 0x73ddllc7 referenced memory at 0x00000004. The memory could not be read.

Thanks again,

Mitch

[Ken Berry]

That sort of error message is usually associated with one of two things: 1) a conflict with another program trying to address that memory address at the same time. This is usually correct simply by rebooting the computer and running the program again.

2) OR it can be indicative that you may have a faulty stick of RAM (i.e. that particular RAM address cannot be addressed at all or is starting to become defective). There are a variety of free RAM tests out there which a Google search should find. The Microsoft Knowledge Base also contains one, though I am sorry I don't have the URL to hand. But download a test and let it run its full course several times.

I had this exact problem a couple of years ago with an almost new stick of RAM. Luckily I ran the diagnostic before the 3 month warranty ran out...

[Mitch Hurricane]

Thanks Ken,

I ran the program right after it happened but this time I ran it in my video editing profile. (Thanks to a tutorial) It had no problems there. I signed back in to my normal profile afterward and it was working again, although I did notice that some of the sample vid clips Ulead provided are now missing. They might come back when I reboot.

I'll check that RAM issue as well. This is a new comp (2 weeks old)

Thanks again , much appreciated.

Mitch

[heinz-oz]

With my last rebuilt of my internet machine, I got two consecutive replacements of a faulty memory stick which were also faulty. Just because something is new doesn't mean it's fault free.

Another possibility not touched on by Ken in his otherwise excellent advise is the fact that memeory is frequently swapped out by the OS to HDD (swap file) If you have a system managed swap file, it will grow and shrink with the demand placed on it by the OS. It will also physically but transparently to the user, move around on the HDD as well because of certain disk space previously allotted to the swap file and later released are now occupied by some program or data.

What I'm trying to say is this, even though your problem could be due to a faulty memory stick but could also be caused by a faulty cluster on you HDD.

It is exactly for that reason that I advocate the use of a partition, preferably on a physically different drive from the system disk, solely holding the swap file and the min max settings set to 2x to 2.5x physical RAM. It prevents the swap file from getting fragmented and the HDD in turn getting fragmented by the swap file.

[Mitch Hurricane]

Thanks Heinz,

I'll definitely look in to partitioning my HD.

Mitch