Ran out of memory (Error=8007000E) ?

surfsama · Post by **surfsama** » Sat May 24, 2008 3:53 am

Dang, your problem description was a mirror of mine...hmm. I would do a search to ensure that "setmemorymax" is not in any of your folders. That done, I would start removing plug-ins one-at-a-time and try vdub each time to see if you have a bum plug-in.

Your comp specs seem fine. I have 1gb of ram on my XP laptop and have dubbed in Vdub and rendered in AE without problems.

Anths555 · Post by **Anths555** » Sat May 24, 2008 4:07 am

well im just on my mums computer and its got halkf the power of my computer an is running everything fine scripts open and work like they should
they were working once on my computer but it crashed and i reinstalled windows and it asnt worked since i have reinstalled windows again and still it wont work and vdub mod has stopped working now wonld even open

Anths555 · Post by **Anths555** » Sat May 24, 2008 4:38 am

well i fixed it . it wasnt a softwear problem but hardwear not sure why, removed my graphs card and just running onborad and its working

Corran · Post by **Corran** » Fri May 30, 2008 7:23 am

I had this problem recently, to fix it I re-ran the amvapp installer and only selected the avisynth plugins install option. When asked about backup, I chose to backup the entire folder before replacing option. Previously, I had selected to have the installer only overwrite the plugins that were old.

After the plugin folder was backed up and replaced, avisynth was able to work properly.

In other words, it is a plugin problem. I didn't feel like narrowing the plugin that was causing the issue for me. It is probably a different plugin that is causing a problem for you anyways.

If this is how you are installing your plugins to begin with then one of the default plugins included in the amvapp is causing the problem. First make a new folder and move all the plugins to it. Then, copy only the plugins you are actually using back to the plugin folder.

is4 · Post by **is4** » Wed Aug 13, 2008 6:01 pm

Corran wrote:I had this problem recently, to fix it I re-ran the amvapp installer and only selected the avisynth plugins install option. When asked about backup, I chose to backup the entire folder before replacing option. Previously, I had selected to have the installer only overwrite the plugins that were old.

After the plugin folder was backed up and replaced, avisynth was able to work properly.

In other words, it is a plugin problem. I didn't feel like narrowing the plugin that was causing the issue for me. It is probably a different plugin that is causing a problem for you anyways.

If this is how you are installing your plugins to begin with then one of the default plugins included in the amvapp is causing the problem. First make a new folder and move all the plugins to it. Then, copy only the plugins you are actually using back to the plugin folder.

Confirming that it works for me. It was actually a plugin problem. I think it occurred after copying the content of ffmpegsource_20071006.zip into the plugin directory.

Thanks anyway