Comments

D7K wrote on 9/7/2012, 10:59 AM
sounds like a system problem, overheating? Try CPUthermometer (free download). I had similar problems and my CPU grease had dried out. Out of ram or diskspace?

What's your system?
skinrade wrote on 9/7/2012, 11:26 AM
I have 615 GB available on system hard drive and another 320 with external hard drive. 3.75 GB usable RAM. Pentium dual core CPU, 64-bit system
Steve Grisetti wrote on 9/7/2012, 12:18 PM
I'd recommend you keep your photos no larger than 1000x750 pixels in size.

Down-rezzing huge photos can sometimes choke the program -- or at least make it vulnerable to choking.

Besides, using photos closer to video resolution will greatly speed up the rendering process!
skinrade wrote on 9/7/2012, 1:51 PM
I changed photo sizes to your specs, and it still froze-up at 39%...ugh...
rdandrea wrote on 9/7/2012, 2:29 PM
Is there some effect that kicks in at that point in the render?
vkmast wrote on 9/7/2012, 2:43 PM
skin,
after you've checked and ruled out the overheating, which D7K suggested,
take a look at this
https://www.custcenter.com/app/answers/detail/a_id/4168/kw/4168
Tips 1. and 2. from that have been suggested to you already, but e.g. 6. might be helpful.
Remember that only the VMStudio 11 builds since 283 (Platinum) or 37 (basic v.)
are able to address up to 4 GB of memory when running on a 64-bit version of Windows Vista or Windows 7.
Steve Grisetti wrote on 9/8/2012, 10:40 AM
Here's one other trick that sometimes works.

Do a Save As and save your project under a new name and in a new directory folder. Then try rendering.

This can keep the program from running into old, corrupt render files and gives it fresh space to do its job.