Hi,

since the last Poser 13 update, I have a very annoying issue. Poser often crashes mid render.

But it smells like a memory corruption.

This is what exactly happens:

- I load simple scene, 1 figure, 1 area light

- render (CPU Fast preset) --> ok

- render (CPU Fast preset) --> ok

- render (CPU Fast preset) --> ok

- render (CPU Fast preset) --> crash

So rendering the same scene without making any modification renders fine for a few times and then it crashes.

It's not with a specific scene but with seemingly every scene file I tried (used Dawn figure, La Femme)

I also notice that large files are being produced in my Poser/Crashdumps dir (~ 4Gb files with .dmp extension)

I saw on Google that there is something call WinDbg to read .dmp files. I installed it and opened one of the .dmp files with it.

But this is far too techincal for me.

The tool showed:

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(33bc.4728): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for Poser.exe
Poser!PyInit_poser+0x8d28f6:
00000001`411ec826 85a4e964130000  test    dword ptr [rcx+rbp*8+1364h],esp ds:00000006`d6847d9a=????????

Any idea what this might be?

Otherwise I'll open a support case

I'd open a support case so Tim and co can look it over.  You may be required to do a collection and zip it up and send it to them.  See below how to go about doing that... You will want the "collectSceneInventory" script.......... 

When you submit your case you should have an area to upload (drag and drop I think) your zip file to upload to their servers.  

Thanks, I did not know about that collectSceneInventory. I'm going to open a support case

actually, there's an easier way. Under files>export save for sharing collects everything and zips it for you.

This may not be relevant but where is your content stored that you are trying to access on your drive?  

But it smells like a memory corruption.

If you would like to launch a good, thorough and reliable memory test, let me suggest you MemTest86+. I suggest that you download an USB version and launch the test outside any operating system.