Wildfire
25th July 2003, 10:19
When I enable the "Faster read access in VirtualdubMod" option, the program continually crashes in the early stages of any encoding-session. Windows XP bluescreens with a STOP error, "BAD_POOL_CALLER"
STOP: 0x000000C2 (0x00000007, 0x000000CD4, 0x00000011, 0xE25BA750)
Those were the codes I got when it last crashed on me. Using Google I found a tip to look for the memory range in which the last code -0xE25BA750- remained as that could be the device/driver causing the problem. In my case, it was the nForce2 chipset and its drivers. So after a complete uninstall and reinstall of the nForce2 drivers, I tried encoding again. With XVid VDubMod crashed but without a BSOD (at least that was a small improvement), with DivX5 it BSOD'ed again.
Disabling the 'faster read access'-function restores normal non-crashing functionality with both DivX5 and XVid.
Anyone else have problems with this VDubMod function?
--edit--
Hmmm, I see the function is only used for Matroska - which I don't use. But I assume it's still not good that VDubMod crashes with this function enabled. Or does it only work correctly when using Matroska? If so, users will need to disable it everytime they want to do a non-Matroska encoding...
STOP: 0x000000C2 (0x00000007, 0x000000CD4, 0x00000011, 0xE25BA750)
Those were the codes I got when it last crashed on me. Using Google I found a tip to look for the memory range in which the last code -0xE25BA750- remained as that could be the device/driver causing the problem. In my case, it was the nForce2 chipset and its drivers. So after a complete uninstall and reinstall of the nForce2 drivers, I tried encoding again. With XVid VDubMod crashed but without a BSOD (at least that was a small improvement), with DivX5 it BSOD'ed again.
Disabling the 'faster read access'-function restores normal non-crashing functionality with both DivX5 and XVid.
Anyone else have problems with this VDubMod function?
--edit--
Hmmm, I see the function is only used for Matroska - which I don't use. But I assume it's still not good that VDubMod crashes with this function enabled. Or does it only work correctly when using Matroska? If so, users will need to disable it everytime they want to do a non-Matroska encoding...