VDUB crash report

[rjc7394]

My 2-pass wmv -> xvid conversion crashed I think after the first pass. This was my avs script (original resolution was 1920x1080) and I used Sharktooth v3EHR CQM. Never had this problem before. Maybe another open Windows application caused it to crash or codec problem?

directshowsource("C:\bblib_nb_hd\home\admin\Desktop\bblib_nb_hd.wmv", audio=false, fps=29.97)
lanczosresize(1280,720)

The crash log said this:

crasCrash reason: Illegal instruction

Crash context:
An instruction not supported by the CPU was executed at 0f206800...

...while running thread "Processing" (thread.cpp:120).

[LoRd_MuldeR]

The message is quite clear: An instruction not supported by your CPU was executed.

This for example can happen if you try to execute SSE code on an old Pentium II processor. Or SSE2 code on a Pentium III. Et cetera.

It could happen in VirtualDub itself, in one of the VirtualDub Plugins, in Avisynth, in one of the Avisynth Plugins, in one of the Decoders ("Codecs") or in the Encoder :rolleyes:

Would be interesting in which module (i.e. EXE/DLL file) it crashed. This may help us to track down the problem...

[rjc7394]

I made several 2-pass test samples of 25 sec. of the clip using the same avs script and the conversions completed before trying to convert the entire clip and then crashing so I'm kind of baffled.

This is the end of the crash report:

EAX = 00f36932
EBX = 00cd70dc
ECX = 533fc82b
EDX = 00000032
EBP = 093dfd40
DS:ESI = 0023:00000032
ES:EDI = 0023:610f0048
SS:ESP = 0023:093dfc98
CS:EIP = 001b:0f206800 <---------------------
FS = 003b
GS = 0000
EFLAGS = 00010246
FPUCW = ffff027f
FPUTW = ffffffff


Crash reason: Illegal instruction

Crash context:
An instruction not supported by the CPU was executed at 0f206800...

...while running thread "Processing" (thread.cpp:120).

Thread call stack:004bcb8f: VideoSourceAVI::streamGetFrame()
004acfa2: AVIOutputFile::writeIndexedChunk()
0046e72b: Dubber::WriteVideoFrame()
00464898: AVIPipe::getReadBuffer()
0046f12f: Dubber::ThreadRun()
7c911727: ntdll!RtlInitializeCriticalSection [7c900000+11655+d2]
7c90d39a: ntdll!NtFreeVirtualMemory [7c900000+d38e+c]
7c919de5: ntdll!RtlReAllocateHeap [7c900000+194b0+935]
7c812a6b: kernel32!RaiseException [7c800000+12a19+52]
7c90d2aa: ntdll!NtDuplicateObject [7c900000+d29e+c]
7c80de73: kernel32!DuplicateHandle [7c800000+de0e+65]
0052939f: VDThread::StaticThreadStart()
0056b99c: _threadstartex@4()
7c80b699: kernel32!GetModuleFileNameA [7c800000+b4df+1ba]

[LoRd_MuldeR]

Doesn't the crash dialog indicate the module where it crashed?

http://www.nickles.de/stories/images/mn/new2/fullsize/browser-crash-2010-02.jpg

(Like "vcam.ax" in this screenshot)

[rjc7394]

The VirtualDub crash report text file (8 KB) doesn't list any modules. Maybe it crashed because I had other Software Applications running and processor couldn't handle it.

[foxyshadis]

VirtualDub doesn't give you a standard windows crash box unless you say no when it asks if you want more information.

Anyway based on the call stack it looks like a broken decoder. Find out what's doing your decoding and either update it or switch to something else. The instruction referenced is ring-0, which means it's only executable in the kernel or a driver. It's probably a mmx/sse instruction that was somehow corrupted, but it could be that something else entirely scribbled into the decoder's memory space.

[rjc7394]

I got "An out-of-bounds memory access (access violation) occurred in module 'VirtualDubMod'.." after running it again. I just updated XviD to 1.2.2 and I'll try it again or maybe it's another decoder causing the problem or a corrupt file.

1. I ran a single pass on this file a few days ago and it completed but the 2-pass crashed. (I used the regular presets I always use which are posted in the sticky)

2. What's the difference between using fps=29.97 and convertfps in avs script when importing a wmv file, for instance?