Log in

View Full Version : cannot allocate memory for dll


h3170ra
9th September 2013, 08:43
recently I just reinstall my windows xp sp3
since my editing program which is edius crashed every time I want to use it.
but right now virtualdub crashes everytime I want to encode and there's an error dialogue always pop ups,
cannot allocate memory for dll.
anybody ever experience this?
fyi, I want to encode avi with canopus dv codec.
before I reinstall windows xp sp3, my virtualdub was fine.

thanks in advance.

StainlessS
9th September 2013, 17:17
Might be worth checking how much mem is showing (right click My Computer/Properties OR CTRL-SHIFT-ESC == Task Manager-Performance tab,Physical Memory)
Perhaps you had the m/c open and knocked a ram module.

h3170ra
10th September 2013, 11:58
no, my mem is 2GB. nothing wrong with my mem.
is there any suggestions?
thanks anyway.

raffriff42
10th September 2013, 14:13
http://www.virtualdub.org/contact.html Crashes. VirtualDub asks you to send crash logs to me, particularly if the crash is within VirtualDub itself. Note that VirtualDub will attempt to detect at crash time whether the crash may have been caused by a third-party driver. Please attempt to diagnose these yourself first as there is little I can do when a third-party driver is involved.Can you post a crash log? I think it'll be in your V-dub install folder.

h3170ra
10th September 2013, 14:39
no, my virtualdub doesn't ask me to send the crash report
and I couldn't find the crash log in my virtualdub folder.

Groucho2004
10th September 2013, 15:23
recently I just reinstall my windows xp sp3
since my editing program which is edius crashed every time I want to use it.
but right now virtualdub crashes everytime I want to encode and there's an error dialogue always pop ups,
cannot allocate memory for dll.
anybody ever experience this?
fyi, I want to encode avi with canopus dv codec.
before I reinstall windows xp sp3, my virtualdub was fine.

thanks in advance.
If you want help you need to be a bit more verbose. Why did Edius crash? Which DLL can't VDub allocate memory for? What's the full error message? What source are you trying to encode?

h3170ra
10th September 2013, 16:34
my edius pro 6 & virtualdub used to work then one day, my edius pro 6 stopped working.
the splash screen did show up but everytime I want to open a project or create a new one, nothing is showed up.
after reinstall the edius pro 6, the problem still exist.
I decided to reinstall the windows. fyi my OS is win XP SP3 then I install the edius pro 6.
It's even worse. after the splash screen, edius pro 6 is crashed with an error dialog box. I forgot what it is said.

since I couldn't use edius pro 6, I installed edius pro 4 and it run smoothly.
but now my vdub become very very slow. only got 3 fps when I encode from canopus dv codec avi into canopus dv codec avi.
eventually my vdub will crash with an error dialog box saying "cannot allocate memory for dll"
after I closed that dialog box, another error dialog box popped up saying "video compression error: an unknown error occured (may be corrupt data). (error code -100)"

oh ya, btw when I reinstall the OS, the program files from the old OS still exist, is it that causing the problem?
hope my explanation this time is better.

Groucho2004
10th September 2013, 16:48
oh ya, btw when I reinstall the OS, the program files from the old OS still exist, is it that causing the problem?
Could be. You should always install the OS on a clean partition.

DonQ
13th September 2013, 17:34
I would check hardware - old motherboard (with tired capacitors), some corrupted sectors on HDD, lose cabling, a slightly faulty ram chip, CPU/chipset overheating etc can cause strange faults.
memtest86+ and some utility with SMART capability (eg speedfan, that measures temperatures too) are your friends.
About motherboard - you can find leaking or bulged capacitories by visual inspection; usually such components cause problems on cold start, but may cause another problems too.

Sure clean windows install would isolate software errors, but there is no point to install new system on broken hardware.