Am still getting this with the new version, only not quite as bad.
I did notice that not being logged-in improved the situation a little, but I really don't think this has any true connection, but is just an anecdotal/hopeful response by me.
I wonder if this could still be down to either of the following -
1. In the "Good Old, Bad Old Days", sometimes too much memory (RAM) could cause crashes due to poor memory management - this PC has 64GB.
How about you guys? Lots of memory in your S3D-crashing machines?
2. The crashes seem to happen whenever something is written to the Registry (Windoze) - I'm wondering if something is intercepting the Registry writes, such as Ccleaner, or SpyBot S&D, AV, etc.
Have just removed the first two, and going to see how that goes.
My AV is KasperskyTS, and although I had already stopped KTS messing with the S3D folders that have been scattered all over my PC, it is possible that KTS is still upsetting S3D with its grip on the Registry.
If removing the first two items actually improve things, I'll let you know.