|
|
| Hacker |
| Posted: Mar 20 2003, 12:58 PM |
 |
|
Unregistered
|
Hi,
I was using VirtualDub with my old Athlon 750 without problems. Now I have a Duron 1.1 GHz and suddenly VirtualDub started crashing at random when encoding files to DivX.
I am encoding files with audio set to No audio, if that matters.
I cannot find any similarity between the crashes, except that it only happens when using DivX, the file being created (anything.avi) is always 16777216 (2^24) bytes long (maybe some overflow?), I always get a BSOD with a fatal exception (not a VirtualDub crash) and it started happening with the new Duron.
VirtualDubMod (based on the previous version of VirtualDub) exhibits the same problem.
Sometimes I can encode the AVIs normally, then, after a reboot, it doesn't work anymore.
I would be very grateful for any advice you might have.
TIA
Roman
[EDIT]
The system is a Duron 1,1 GHz, mainboard QDI KinetiZ 7E-A, SB Live!, Matrox Marvel G400, 80 + 20 GB Maxtor disks, W98SE.
[/EDIT]
|
|
| fccHandler |
| Posted: Mar 20 2003, 05:59 PM |
|
|
Administrator n00b
Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02
|
The newest DivX 5.03 is buggy and crashes some systems. If you are using 5.03, try uninstalling it and then install the older version 5.02 from this link.
--------------------
May the FOURCC be with you... |
|
| phaeron |
| Posted: Mar 21 2003, 03:35 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
The reason why the file is exactly 16MB is that VirtualDub proactively extends files by 16MB increments during the processing operation, then trims the excess at the end. It isn't at all helpful in determining the cause of your problem. In fact, I'm very surprised the file isn't zero bytes, since usually having the Win98 crash with a file open results in the file being truncated.
|
|
| Hacker |
| Posted: Mar 21 2003, 11:25 AM |
|
|
Unregistered
|
fccHandler.
The newest DivX 5.03 is buggy and crashes some systems. If you are using 5.03, try uninstalling it and then install the older version 5.02
Thank you. I will give it a try and report the results.
phaeron,
The reason why the file is exactly 16MB is that VirtualDub proactively extends files by 16MB increments during the processing operation, then trims the excess at the end. It isn't at all helpful in determining the cause of your problem.
I am sorry, I didn't know that.
I will try and note down the text on the BSODs if it helps more.
In fact, I'm very surprised the file isn't zero bytes, since usually having the Win98 crash with a file open results in the file being truncated.
Oh well, it depends. Rarely it does happen that the resulting file is 0 bytes long, but there are 16 MB of lost clusters.
Thank you and I will report the 5.02 results.
Roman |
|
| Hacker |
| Posted: Mar 23 2003, 12:04 PM |
|
|
Unregistered
|
Hi,
OK, well, I did a bit of testing. I installed DivX 5.02 and tried these combinations:
HuffYUV -> DivX 5.02 - crashes
HuffYUV -> HuffYUV - crashes
DivX 5.02 -> DivX 5.02 - no crashes so far.
So I guess something is wrong with HuffYUV or the way I am using it. I compared the huffyuv.ini from my old machine to the current one and they do not differ, so I guess I am using it the same way I was using it before. I also activated the console debug window, however, I didn't see any error or anything suspicious mentioned there.
Any ideas highly welcome.
TIA
Roman |
|
| Hacker |
| Posted: Apr 8 2003, 11:20 AM |
|
|
Unregistered
|
OK, well, after some more testing it seems that enabling the "always suggest RGB for output" (or what exactly it's called) option fixed the problem.
Roman |
|
|
