VirtualDub documentation: crashes
Listed below are a few common VirtualDub crashes that are related to third-party drivers. If you get a crash in VirtualDub, one of the entries below may help you track down the problem. The "symbol containing EIP" will appear as the top entry in the estimated call stack, in the form of dll name ! export. If the top entry contains only a name rather than a DLL name and an export name, it's probably a crash in VirtualDub itself and you should reference the Knowledge Base instead.
As usual, the information you get out of a crash dump may be suspect, so a crash in a particular DLL does not mean that that DLL is bad. However, the DLL implicated in the crash dump may give you a clue as to what's going on.
|Operation||Faulting instruction||Crash reason||Symbol containing EIP|
|Compressing to Huffyuv||pxor mm2,mm2||Illegal instruction||HUFFYUV.DLL!DriverProc|
Huffyuv requires a CPU with MMX support, and yours does not support MMX instructions.
|Compressing to DivX 4||fcomip st(0),st(1)||Illegal instruction||DivX!encore|
DivX 4.11 and 4.12 will not work on a Pentium, Pentium MMX, or AMD K6/K6-2/K6-3 due to use of a Pentium Pro instruction.
|Selecting video compression codec||cmp [eax+0c0000h],dl||Access violation||asusasv1!DriverProc|
If you upgrade a Windows 9x system containing an ASUS video card with capture capability to Windows 2000 or XP, you may inherit the ASUSASV1 codec. This codec uses a method of checking for an ASUS video card which does not work under any Windows NT platform and causes host applications to crash. Install the decompression-only ASUSASVD driver from the Asus web site to work around this problem.