*I think your looking at the wrong item, I read in a forum (here at Renderosity) that it's not your memory that Poser uses to render images, but your "CPU".

*It's the CPU that does all the number-crunching, but, provided that the CPU has the basic minimum required processing-power, the CPU isn't going to stall a render.   You may grow old waiting for a render to complete, if the CPU is lacking in muscle, but it IS probably memory (or, to be more precise, lack of it, or the application's inability to exploit it) that is the killer, when a render fails.   For a Firefly render, I have long followed the procedure that pjz99 described above.   It doesn't always work, but it certainly helps.