When you sent in the report to tech support, did they ask you for a sample scene that shows the problem? Granted, that doesn't always let the engineers know what exactly went wrong, but it's a start anyway.
Usually the best thing to do when you get corrupted scenes and you want to provide 'em to Smith Micro is to take the simplest one you can get, open it up (screwy or not) and use the CollectSceneInventory script (in Scripts>Utility) to save the whole thing and all its parts into a new folder- then you zip that up, send it in and the techies can open it even if they don't have the same stuff in their Runtimes that you used to build the scene.
And if it is Poser's fault, that's probably the best first step to getting it fixed.

As a FYI, just in case anyone's Windows copy of Poser should crash, it would be most helpful if possible to collect some information about the state of the app, by following these steps:

1. If a crash occurs and WER offers to send a report, choose 'Send Error Report' or 'Check online for a solution and close the program' (if you are not presented with this dialog you likely won't be able to exercise the following steps)
2. Go to 'Control Panel' > 'Problem Reports and Solutions' (or quicker Start > "problem" > Enter, actual program is %SystemRoot%system32wercon.exe)
3. Click the 'View Problem History' link
4. Find the entry for the most recent crash for Poser (Debut, Pro) and double-click it
5. Click 'View a temporary copy of these files' under 'Files that help describe this problem' on the problem report page (this option might or might not be available; WER is apparently not always able to capture the files we're looking for)
6. Create an archive of those files and send it in to Tech Support
7. You may choose to delete the archive from the temp directory once the report is uploaded (NB- the directory from which you created the archive will be automatically removed upon closing 'Problem Reports and Solutions', so don't close out until you're done collecting the data)

Mac users should always have the option to generate a report, which can be copy/pasted into a new text document and sent along in the same way. 

It'd be wonderful if Poser just didn't crash of course- that's the goal- but if it does, that'll help the engineering crew figure out where things went amiss, and would be much appreciated.

That certainly makes a difference! Unfortunately since Pro 2010 is out now I wouldn't expect any further Pro updates beyond 7.0.4.220. As ratscloset points out there may be a setting that would help. If you do contact Tech Support they'll probably want to see your Poser.ini file to see what settings it's using.

Interesting- I took a look at this on a Win7 x64 AMD system with a Radeon HD3870 and the latest 10.10 drivers and didn't see a problem (Poser Pro 2010 11916, the SR1 version.) Was there anything specific in the scene that you were working on that might cause this problem, or does it happen with even really simple scenes (like the default?)

Sorry this one slipped through until SR1; my cats have both been fixed thus can't reproduce.

... and be sure that at least one of your lights has Ambient Occlusion active, of course!

Yeah, the ReadMe says (if I recall correctly) that SR2 rolls in all the changes from SR1 as well as the new stuff, so SR1 is redundant- mind, I'd keep a copy around if you have one, Just In Case. In my experience you don't even have to restart the computer after SR2- not that it's a bad idea to restart, though! Jay's procedure looks right to me.

Yep, PMDs are new to Poser 6 and earlier versions can't read 'em. You can turn off external binary morph targets in the General Preferences and save the figure back into your library to create a CR2 containing all the morphs, that Poser 5 can use (I had to do that to get a version of Terai Yuki that Poser 5 could handle.) -- BG63

Aside from running the SR2 plugin- which should get Poser to ignore DivX, according to e-frontier people I've talked to- you can open the root-level Library folder, open the QuickTime folder that's in there, and move the DivX 5.component file from the QuickTime folder to anywhere else. That fixed it for me, and it's consistent with ef's FAQs. -- BG63

(from Francemi) The only fix I was hoping and waiting for is the one that would make transparent or semi-transparent objects show up in the document window when I select Texture Shade but it is not there. I still have to use Cartoon with outline. ;o( ***** Francemi, have you tried opening the Render Settings and, in the Preview tab, selecting the "Limit To" radio button and entering a very low value, like 10% or less? That should make all the transparent objects show up in Texture Shaded preview mode. Not strictly speaking an update or bug-fix, just a scantily-documented feature... --BG63

Does this happen in scenes with fewer lights? Could be that (for some reason) Poser 6 can't handle as many infinite lights in a scene as Poser 5 could- a workaround to get a globally illuminated look would be to use a single diffuse image-based light and one or two shadow-casting lights, rather than nine or ten infinite lights.

Yes, just to clarify- although you do need your Poser 5 serial number to purchase a Poser 6 upgrade, you'll need your new Poser 6 serial number to download updaters from either e frontier or Content Paradise- and you will also need to have registered your copy of Poser 6 with e frontier in order to download the SR1 updater. The e frontier site will ask you to enter your (registered) Poser 6 serial number to verify ownership before it lets you download the updater. Hope this helps! -- e frontier Technical Support