PC crashing with Virtual Dub

[satanwantsme]

I have an mpg which I am attempting to convert with Virtual Dub to an avi however the conversion gets so far then the PC goes to a blue screen which I cant get rid of without restarting the PC.

The stop message on the blue screen is

Stop: 0x0000008E (0xc0000005,0x80579fa7,0xeb1bfc30,0x00000000)

Ive encountered a similar blue screen earlier today whilst doing the exact same thing and got a different message telling me to run the driver verifier against suspect drivers and to try enabling special pool. I did this and it still crashed but im not really sure how to use these so I might have done something wrong.

Further info which may be of help: Im ultimately trying to convert a NTSC mpg into a PAL mpg. I tried doing this directly through tmpgenc and received similar blue screen errors, so i figured id convert it to avi using virtual dub and then feed the avi into tmpgenc to create the PAL mpg. The problem is not restricted only to this file but to many different video files.

Any ideas on what the problme is or how to fix this?

Thanks

[killingspree]

hi
honestly i do not think this blue screen is related to virtualdub (or tmpegenc) for that matter, but to a general system error. most likely the operations you are trying to do are stressing your system more than usual and therefore cause the blue screen.

if you have any overclocking turned on, do switch it off. also try to run some memeory testing program like memtest or prime95 to see if your memory might be erronous. also think about any new hardware you might have installed that could cause such a problem

ps, also as always, google's your friend ;)

kr
steVe

[jggimi]

Crashes during encoding are typically system instability problems, especially when the crashes occur at different points in the encoding. You got two different BSODs with Vdub, but also got them with TMPGEnc. Like Killingspree, I think this is a hardware problem.

Our PC Harware forum has a sticky thread (http://forum.doom9.org/showthread.php?s=&threadid=54130) that describes how to test your PC for instability trouble.

[satanwantsme]

I dont have any overclocking on but I did get an error when I ran the Prime95 Program, Ive pasted the log below. Does this mean that my PC is broke? Ill try the other tests in that sticky thread later. Thanks

[Mon Feb 14 18:12:18 2005]
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.

AMD Athlon(tm) XP 1700+
CPU speed: 1466.46 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 256 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 65.272 ms.
Best time for 448K FFT length: 69.575 ms.
Best time for 512K FFT length: 73.010 ms.
Best time for 640K FFT length: 96.613 ms.
Best time for 768K FFT length: 129.320 ms.
Best time for 896K FFT length: 146.719 ms.
Best time for 1024K FFT length: 179.542 ms.
Best time for 1280K FFT length: 214.909 ms.
Best time for 1536K FFT length: 246.156 ms.
Best time for 1792K FFT length: 331.328 ms.
Best time for 2048K FFT length: 387.622 ms.
[Mon Feb 14 22:50:08 2005]
FATAL ERROR: Resulting sum was 5.988192788436449e+016, expected: 5.985241972235819e+016
Hardware failure detected, consult stress.txt file.

[jggimi]

The error message you pasted says, right at the end:...consult stress.txt file. Had you done so, you would have seen the following information:WHAT TO DO IF A PROBLEM IS FOUND?
---------------------------------

The exact cause of a hardware problem can be very hard to find.

If you are not overclocking, the most likely cause is an overheating CPU
or memory DIMMs that are not quite up to spec. Another possibility is
you might need a better power supply. Try running MotherBoard monitor
and browse the forums above to see if your CPU is running too hot.
If so, make sure the heat sink is properly attached, fans are operational,
and air flow inside the case is good. For isolating memory problems, try
swapping memory DIMMs with a co-worker's or friend's machine. If the errors
go away, then you can be fairly confidant that memory was the cause of
the trouble. A power supply problem can often be identified by a significant
drop in the voltages when prime95 starts running. Once again the overclocker
forums are a good resource for what voltages are acceptable.

If you are overclocking then try increasing the core voltage, reduce the
CPU speed, reduce the front side bus speed, or change the memory timings
(CAS latency). Also try asking for help in one of the forums above - they
may have other ideas to try.