#JimmyJohn

1. virtual memory: system defaults to 16M minimum and 150% of your Ram size as maximum. The first setting guarantees than the pagefile exists and does not have to be created at the moment you run out of ram (this handling / waiting time can make apps fall over). The second ensures that there is enough pagefile available when going into sleeping mode / hybernation (all ram is dumped into the pagefile then).

But... in some cases 150% is not enough,
And... if your disk is too fragmented, there might be a problem growing the file, as the pagefile should be an unfragmented one. So: regularly defragmenting might be of help. Although maybe Win7 might have tackled that, not sure.

2. yeah, I realized later that I was messing up the specs of Sheedee and yours. Sorry for that, 64-bit should rock with 8Gb ram.

Note that the renderer is multi-threaded, and each thread takes a bucket at a time, and considers all geometry within that part of the scene. This is why larger buckets take more memory per thread to render. And since all buckets have a bit of an overlap, this might reduce the overall overhead and gives you a (up to 5%) speed increase. So when smaller buckets reduce the problem, there is certainly some memory issue going on.

But since Poser on 64-bit should ot present any software problem, I begin to wonder whether there might be a hardware / driver issue. With the CPU, the Ram modules, the motherboard or the combi.

So perhaps a hardware techy or a windows techy could have a look. Have a clever nephew in the family? You might need hardware tests and Windows error logs. This goes beyond what I can do in a Poser forum. Sorry.

- - - - - 

Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.

visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though