VDMod stopped working.

[junglemike]

Hi. I've been using virtualdubmod for years and recently It stopped working. What I mean is when I launch it, it just does nothing, no virtualdubmod.exe process in the task manager, no error report, nothing. I've downloaded the latest version from it's homepage (version 1.5.10.2), extracted to empty folder and tried launching - but still nothing. What can I do?

[setarip_old]

Hi!

Try performing a "System Restore" back to the last time things were working properly...

[plugh]

That's odd - it just stopped working on *one* of my systems, too.

Took several attempts, but through quick use of the Print Screen key I was able to capture an error message. "An out-of-bounds memory access (access violation) occurred in module 'VirtualDubMod'."

Still poking at it to try to figure out what is going on. I've manged to isolate it to something display related so far.

EDIT:
Some more pokin 'n' prodin, discovered that if I enable "Use DirectX for display panes" the app crash goes away, turn it back off and the crashes come back.

Going to run a memory tester overnight...

[foxyshadis]

It's probably a display driver thing, not a hardware issue. On the other hand, it really wouldn't hurt to just leave directx display on.

[plugh]

Yeah, but why suddenly start showing problems? I had been working on an encode, quit for a couple days, came back (no intervening reboot, hibernate, or standby) and blam - it is broke! In fact, I had left the system with VDM running, and when I came back I used the script editor to make a change, save&refresh, and blam, that was all she wrote - no more VDM.

I've checked the system disk; no file mods during the idle period (and I have windows update disabled). The memory test passed, and I also did a full disk scan - also ok. Tried tweaking the display settings, tried emptying the AVS plugin directory, tried simply opening an AVI file, tried disabling VDM cpu optimizations, even tried setting the clock back - no effect.

Tried out the following versions:
VDM 1.5.10.2 - same failures
the build-2542 update - what I've been using
the aud-x VDM build - fails, and ALSO causes DrWatson to fail!?
virtualdub-mpeg2 - _WORKS_

No other app I've tried fails. Darndest thing I've ever seen...

BTW, in all my poking at this, I did actually manage to get a VDM dump once. Here's part of it:
Disassembly:
00000000: 0000 add [eax], al <-- FAULT
00000002: 0000 add [eax], al
00000004: 0000 add [eax], al
00000006: 0000 add [eax], al
00000008: 0000 add [eax], al
....
EAX = 00000008
EBX = 00cffc90
ECX = 01f30b40
EDX = 02b10b40
EBP = 0012ee40
DS:ESI = 0023:00000b40
ES:EDI = 0023:fffff4c0
SS:ESP = 0023:0012ee38
CS:EIP = 001b:00000000
....
Thread traces:

Thread 0000027c (Main thread)
C:\Dvpt\VDub_1.5.x\VirtualDubMod15\VirtualDub\source\VideoSource.cpp(1828)
C:\Dvpt\VDub_1.5.x\VirtualDubMod15\VirtualDub\source\VideoSource.cpp(1846)
....
Thread call stack:
0052cc58: VDMemcpyRect()
004161ba: VDVideoDisplayMinidriverGDI::Update()
00410000: VDVideoDisplayWindow::SyncSetSource()
0040fdd0: VDVideoDisplayWindow::WndProc()
00410310: VDVideoDisplayWindow::SyncUpdate()
77d49491: USER32!GetWindowLongA [77d40000+945d+34]
0040fdbb: VDVideoDisplayWindow::WndProc()
0040fbf8: VDVideoDisplayWindow::StaticWndProc()
77d48734: USER32!GetDC [77d40000+86c7+6d]
77d48816: USER32!GetDC [77d40000+86c7+14f]
77d4b89b: USER32!GetParent [77d40000+b72f+16c]
77d5f3e3: USER32!SendMessageA [77d40000+1f39a+49]
0040fa96: VDVideoDisplayWindow::Update()
00496407: VDProjectUI::UIRefreshInputFrame()
00496d44: VDProjectUI::DisplayRequestUpdate()
00410273: VDVideoDisplayWindow::SyncInit()
...
At this point I am at a loss for anything else to try, other than completly reloading windows. Guess for now I'll leave 'directx display' on until some other symptom of whatever the problem is reveals itself.

PS - The timing is interesting - during that intervening idle period I ordered an AGP video adapter as I want to move off the i865 integrated graphics. Maybe I hurt its feelings :eek:

[squid_80]

Weird. GDI is the very basic rendering mode, used if there's nothing else because it's meant to be safest.

Check whether Allow video overlays (under options) is enabled. Try toggling it on or off, with directx off and see if there's any difference. Failing that, I'd wipe out vdubmod's reg key (HKCU\Software\Freeware\VirtualDubMod).
(You might've done this already, just chucking ideas out.)

[plugh]

BINGO!

Wiped out the registry key (thanks for the suggestion), started VDM, and it is working again! When I did that Edit / Save&Refresh and VDM crashed, I guess it polluted the registry key in some fashion...

I exported the key before deleting it, but I guess there is no maintainer around to send the data to. Anyway -

:thanks:

[minaust]

I'd wipe out vdubmod's reg key (HKCU\Software\Freeware\VirtualDubMod).
(You might've done this already, just chucking ideas out.)

Bingo twice!

I had a different VDMod problem - it suddenly quit writing to disk. No errors, just no writes, no status window. It only affected versions 1.5.10.1 & 1.5.10.2. Killing the registry key fixed me too! :D

[Daniel_BMS]

This information came in very handy here in 2011! I never would have guessed to delete the registry entry all by myself.