The following are dumb suggestions, but I literally just got done answer a very similar post in the DS forum, so...

...has anything changed recently (if you have Windows 10, you might not know if it has or not, so check your Windows Update history This is because by default, Windows 10 will sneak in and patch stuff without you knowing it, unless you go way out of your way to tell it otherwise.

Oh, and Microsoft really has a hate-on for nVidia, so it will blow away any nVidia-built drivers and replace that driver with a Microsoft version, which tends to break stuff... hard. Blame it on a WHQL spat between nVidia and MSFT.

...and now, for the copypasta bit:

Note - this is true for any CG application... DS, Poser, 3DS Max, Lightwave, Modo...

(sneck for brevity - go to the DS Forum and look for the missing bit.)

Some things to help prevent crashing:

1. (prolly too late now for this one, but next time y'all go shopping) - don't cheap-out on the hardware - doubly so for anything with a GPU on it. Generic braded stuff and "House Brand" stuff might have a nice, fat price difference, but you only save money at the expense of time (time spent troubleshooting, time spent reloading stuff after it crashes, time buying replacement parts after that cheap part dies prematurely because it wasn't built to handle the abuse that CG application usage will always put on it... Stuff like that.)

2. If you have any drivers or other low-level stuff in your OS that is way outside of typical use, it'll sometimes gonna get in the way. For instance, I have a driver on my Windows-based laptop that allows me to read and write to disks formatted with Apple HFS/+ (so I can read all my old Mac disks.) This would be one of my first suspects if DS started acting wonky right after I installed the thing (especially if I had the installation or my DS/Poser libraries sitting on that external oddball-formatted disk.)

3. Only use approved drivers for the stuff DS relies on. For example, only the latest stable official nVidia driver for the GPU (if the laptop/desktop-supplied driver doesn't quite work). Only vendor-built drivers for everything else (doubly so if you're doing this on a laptop.)

4. Could be a resource issue. Now if you have 32GB of RAM, an SSD disk, and a late-model i7/Ryzen processor? It's probably not a resource issue, unless you have lots of other resource-hungry stuff going on at the same time.