VirtualDubMod crashes on start

[Sagekilla]

For whatever reason, VirtualDubMod has been crashing on me the minute I start it. I didn't change any of the original files, it just crashes. Poof! Gone. The error report says that Kernel32.dll (The dll responsible for i/o, memory management and the like) is the faulting module which I don't like at all.

Anyone have a clue as to why my VDM is crashing even though I've done nothing to change my setup? I didn't install any new drivers lately either.

[Sagekilla]

Well the news seems to be getting worse and worse.. I tried opening an avisynth file in Media Player Classic and I get a "Ran out of memory (Error=8007000E)" error. No exotic filters, only trim, crop, and resize. x264 doesn't open the script either. I get this: x264 [error]: could not open input file 'source.avs'


Any thoughts?

[setarip_old]

Hi!

Chances are one of the VirtualDubMOD files has been corrupted. Try downloading a fresh, complete package, uninstalling/deleting ALL of the files in your VirtualDubMOD directory - and then installing the new package...

[Sagekilla]

Well now, isn't that odd.. I wiped my VDM install clean, and popped a fresh one in a new folder. Now I'm getting a MS visual C++ runtime error.

[setarip_old]

Is it indicating a specific .DLL file in the error message?

[Sagekilla]

Nope. It's just a msvc error.

http://img.photobucket.com/albums/v621/Sagekilla/msvcerror.png

[setarip_old]

That's often indicative of a corrupted .DLL... Perhaps a "System Restore" back to the last time things were working properly...

[Sagekilla]

That's often indicative of a corrupted .DLL... Perhaps a "System Restore" back to the last time things were working properly...

I'll try restoring back to my latest (January 20th) and I'll report back on any results.

[Sagekilla]

Well, I did a system restore to two days ago and VirtualDubMod and Avisynth still refuse to work properly. I still receive the same two errors from mpc and VDM

[Sagekilla]

I've resolved the issue. It was actually Avisynth that was reacting badly... I'm still trying to figure out why it happened, but if I add any more dlls or scripts to my plugins folder, avisynth crashes.

[qyot27]

With the AviSynth problem, I sometimes get the 'Ran out of memory' issue if I have too many (or in some cases, just certain) plugins in its autoload folder. It doesn't matter if they get called in the script or not.

For example, I noticed it when I installed ffdshow and allowed the AviSynth loader to be put in too. Simply removing it returned things to normal (although either this was fixed on ffdshow's side or it was the result of some other conflict that's been remedied, since I don't seem to experience that problem now). To test it, just create a new folder and move all - or at least a fair chunk - of the plugins there and see if that resolves it. Then you can at least slowly add them back in and see which one trips the error.

[setarip_old]

@sagekillaI've resolved the issue. It was actually Avisynth that was reacting badlyGlad to hear you've tracked it down ;>}

BTW - Your initial post here doesn't mention AviSynth...

[Deaf Raiders]

I also have a problem with this using with AutoGK heres my error: An out-of-bounds memory access (access violation) occurred in module 'VIRTUA~1'.

is there any solution for my problem?

[alicizmar]

Hmm...now that sounds like it might be (guessing by the "VIRTUA") a virtual memory problem.
Just skipping rocks, but try a System Restore and/or adding some room to the page file.

[Deaf Raiders]

its not because if it was it pop up on the task bar and VIRTUA~1 refers to a program.

[alicizmar]

Ahh...
Perhaps a module in VDubMod?
Have you tried a reinstall?

[Deaf Raiders]

yeah 5 times

[jeffy]

@Deaf Raiders
Try to remove ffdshow, if the error is gone, reinstall the latest tryout version.
Then try uninstalling & installing AviSynth.
Report back.

EDIT:
Try different source files, the problem might be in the file itself.

[foxyshadis]

Also did you clear out the plugins folders? Maybe the registry keys, too.

[Deaf Raiders]

Also did you clear out the plugins folders? Maybe the registry keys, too.

How do i do that?

[foxyshadis]

Under the virtualdub folder, there are a few folders starting with "plugin", try just scrapping all of those or renaming them .bak. That's the most likely reason I can think of. To try the registry, open regedit and open HKEY_CURRENT_USER, then Software, then Freeware, then Virtualdub. You can delete that entire key or anything inside it, vdub will recreate it with defaults. Be careful what you do in regedit, you're messing with the main system database.

ffs, now my regedit won't open properly.

[Deaf Raiders]

Ok i know regedit. Now one of the problems i have, is the latest VirtualDub 1.7.7 why can't i use that with AutoGK, cos v1.5 that comes with AutoGK has never worked for me.

Raiders

[jeffy]

Ok i know regedit. Now one of the problems i have, is the latest VirtualDub 1.7.7 why can't i use that with AutoGK, cos v1.5 that comes with AutoGK has never worked for me.

Raiders

The application in AutoGK is VirtualDubMod, not VirtualDub. There are some functional differences between the two.