Hi paramount,

as you said "two loads" ... don't know if it is the same with P7 but P5 & P6 are loading lot's quicker at the second and following loads. They might have done something tricky to have some libs staying in memory for further loads not being there the first time.

You might have a look to your poser directory and especially to the temporary directory. After a crash nearly all bigger softwares are loosing some of their data in that places, which are normally been deleted with normal end. Ok, there are also software (like MS office) loosing such rubbish also with normal ending ... so to clean out temporary places from time to time is not a bad idea as such.

And have a look to the total space of the harddisk where your temporary directory is located.
Having to less there might be also a reason for crashes. Keep in mind that this is normally the drive where windows is growing it's swap file and the (all) software is placing some things on the fly. Poser for example will place there shadow maps and other temporarily used things.

This remembers me to a colleague who normally opened word, access with 3-5 db's and excel with at least 10 sheets beneath a host terminal, pdf reader and, and, and ... and then complained that normally after 2 hour's of work his pc crashed and all work was lost ... :cursing:
It was the time of Win-NT SP2 and he had read something about the multitasking features ... I don't know, I'm working with pc's since the time of intel 8086 and DOS and have had never a need for more than 2 DB's and one excel at a time ... so one can go over the top ...
After cleaning that users temp-dir I have found 16 gig more capacity ... with only a 120 gig harddrive in that puter, really not a bad result I think ... :laugh:

So if poser crashes it might be not only poser itself but windows is normally a big supporter in doing so.

But for sure a big library might be a problem. But normally only in the time starting up while reading it. But it should not be the main point for a crash.

Did you do some disk cleaning to resolve fragmentation from time to time ... this could help lot's and is also a typical reason for bad performance and/or crashing software.
Microsoft once had said NT (W2K, XP) doesn't need that opposite to DOS and Win9x ... but it's a real myth, told everytime with the beginning "once upon the time ..." ... but I have never found the princess in that saga ... only the frog ... :ohmy:

So ok, out again to kill some unused/overused vertices from the saber and belt ... glad that you love the poses. Now we are making a fine pirat's basic armament package ...