I do not know who started the last thread on this, but it was nice to see that I was not the only one that experienced the crashes. I only have 128MB in my PC, but I have a very large swap file. Poser was using 74.7 MB at the time it crashed. It also pegs the CPU (100% CPU load on a P3 500). Total memory use (according to Norton SI) was at 169MB. Some one mentioned that Poser uses its own swap file for storage. The partition that Poser is on has 2GB free. This seems like a bug to me. If it is a memory problem, then program should inform the user, not take up all of the CPU cycles. Instead of sending CL support an email, if you have experienced problems with Poser crashing during rendering, please post a reply with your info. I volunteer to send them all in an email to CL support.

The patch to 4.0.3 may fix your problem, the following text is from Curious Labs patch page: "This will update the Windows and Mac version of MetaCreations' Poser 4.0 to Curious Labs' Poser 4.0.3. This updater includes several fixes and including a fix that enables Poser to run on systems where the total memory (RAM + Virtual Memory) exceeds 2 Gigabytes" . Your problem may be that you are exceeding 2GB total memory, hence the crashing. Hope this may help.

I'm running with the patch -- 4.0.3.126.

If you have set your own preferences for initial Poser startup, set the UI to use "Factory State". You can use the "dots" to quickly move to your preferred UI arrangement from the initial "Factory State" at start up. For some inexplicable reason, I find that this has "cured" most of my Poser render crashes, especially when the file/model is a large (memory requirements)one. Might work for you too! ;-D

Thanks! I'll try that.