Here's the deal: I can render the P4 Woman all day long and no problems. The first 2 times I render Vicky with the ASIA skin kit it renders fine. The 3rd time it freezes. Not a hard-lock, I can still use other apps, Poser just stops responding and I cannot cancel the render. When I go back in, everything works fine, but when I go to render, there's a 90% chance it will lock. If I reboot the machine, the first 2 renders are fine, then it goes downhill. Question is, if Poser runs out of RAM, does it suppress the message and lock? Before upgrading fro Poser4 to 4.03 (or whatever current is) I would get out of memory errors that crashed the program, now I don't get errors, just dumped. Anyone else on here have, and solve, this problem? I'm going to upgrade my RAM, but am interested in finding out if it's not memory at all but something else I need to fix. My system: Asus A7V133 Mobo Athlon Tbird 1.33GHz 256MB CAS2 PC133 SDRAM 2XIBM GXP75 7200 RPM ATA100 Drives (20 and 30GB) Visiontek Geforce3 64MB Lotsa other crap that isn't pertainent. Anyone with a similar rig and the VICKY2 / ASIA model plz let me know if you've had the same problems. Thanks a ton!

Which OS are you running on your machine? Windows 2000 and Windows XP (not yet released) should reallocate Virtual Memory to take care of this problem for you.

what version of Detonator drivers are you using? I'm experiencing frequent lockups in W2K just minitues into using Poser 4.0.3.. something that never happened under 4.0.2. Wierd lockups. And my system is quite similar to yours.

Attached Link: http://www.microsoft.com/hcl

Under Windows 2000 or Windows XP (Beta), right click on the task bar and pull up Task Manager. Click on Performance and this will give you a performance monitor. When you run Poser, watch the performance. It should peg out at 100% occasionally. The app may appear hung while the processor is pegged. On my system I can leave it and it will come back to normal and then for no apparent reason will peg the processor again. Poser does not allocate memory and handles the way that we would expect them to. After you have accessed an object in Poser, it still retains a finger on it and that consumes resources. These are not freed until you have exited Poser. If your machine is actually crashing, try downloading a signed/logo'd video driver from www.microsoft.com/hcl. The driver may not be as feature rich as the one from the manufacturer, but is stable. Advanced users can use PERFMON to monitor CPU usage and memory use. I have not been having problems on Windows XP (RC2) but I am also not rendering very large projects.

I've been using the WHQL'd 12.41's on my Geforce3 which have performed fine in Direct3D and OpenGL apps.. since Poser is for fun and not a factor in my current project, it'll be a bit before I downgrade to the 6.50's. But I'll get around to it someday. ;) Thanks for the tips. BTW armand, what version is your Detonator driver at?