I sort of remember people having this problem and it was caused by using the external renderer with firewall enabled?  If you're using the external renderer, try the internal, and possibly temporarily disable your firewall if it's on, at least just to diagnose it.

Sorry but unclear to me,, external renderer? FF? I've never used that term and the interface looks the same as P6 to me. Tried with fwall off to no avail.

Look in the General Preferences.  You'll find a choice for 'external renderer'.
This is a separate little EXE (FFRENDER.EXE) which can render on its
own, leaving Poser's code open for other activities.   Poser sends a
file to this EXE, containing basically the same info that the PZ3 has ...
and firewalls sometimes see this file-sending as a "virus-like"
activity.   If you uncheck 'external renderer', you'll return to the earlier
all-in-Poser rendering.

With some firewalls, just turning the firewall off isn't enough; you
actually have to uninstall.

The Separate Process box is the one.  But it's already unchecked,
so that's not your problem anyway.

The MS error feels more to me like a memory problem than
a firewall problem ...

One thing that seems to pop up often is
video driver cards disliking Poser 7.  You might look in your
computer's System to find the name and specs of your video
card, and then check online to see if there's an updated driver
available.

Also, have you looked at the actual data given in the MS error?
It's hopelessly cryptic, but there will be one major number that
looks something like

0xC0000000000015

and you can look up those numbers to see what the problem is.

I'll do that but, it was just installed new and updated 2 weeks ago. Thanks to both for the help. Just installation quirks, I hope.

Do you still have the problem?  If so can you post a screenshot of your render settings?

Those are pretty tame render settings, although I don't see why it should blow up at the END of a render - however if you already have errors with your runtime it certainly does make sense to fix those first, hopefully that will fix your render problem.

PS: if you have a mutli core processor, you ought to go back to Preferences and set Number of Threads higher (no reason not to set it to 4).

Thanks. Several similar "end of render" crashes with P7 in the threads here... Just not the right fixes.

P7 can get totally hung up when searching for an OBJ.  It works best
with the "search depth" preference set to Shallow, but can still get
locked, and can get confused between folder names and file names
in some situations

If you're rendering after an OBJ was missing, that's a likely candidate
for the remainder of the problem.

3/7/08

This may be a memory problem. I get MS error messages when I try to render V 4.2 with morphs installed (texture, hair, simple cloths, simple scene). As pointed out by mapps, V 4.2 with morphs is a true memory/resource hog. Any scene that pushes the limits with Poser 7 can produce errors and shut downs.

If the /3GB memory switch (in the boot.ini file of your root directory) will work on your computer (XP) then you may be able to render larger scenes. This switch may not work on some older computers, with smoe video cards, or some versions of XP. There is a similar switch for Vista 32 bit computers. A google search will turn up more than enough information on this subject.

LMK

Have a look in Control panel > administration tool > Events > application  and system .

I am not 100% sure of those names but if you look at the menus it should get you there .

Make a not of any errors logged at the time of the failure.

Check your page file(virtual memory) is set higher than the default , or just set to system managed .

C:DOCUME~1somepoorsuckerLOCALS~1TempWER3dd6.dir00Poser.exe.mdmp C:DOCUME~1somepoorersuckerstillLOCALS~1TempWER3dd6.dir00appcompat.txt szModVer:0.0.0.0 offset:0000000 szModName:hungapp ...the usual suspects. I did up my virtual memory to the recommended level. Thanks. Forgot to do that.