Daz DAZStudio 4.23

[coffeeaddicted]

I have to say, this is the most unstable version i ever installed.
It collides with the windows security monitor. I assume that it moves things in a secure section, thus crashing the system.
I had so many blue screens, it's not even funny.
Is there a sure way to downgrade to a more stable version?
Not sure which version is good actually. But some version that doesn't crash windows and ends in reboot.

Thanks

p.s. i wonder how they release version without QA.

 

[Sunday95]

https://f95zone.to/threads/daz-studio-repository-daz-older-versions.109219/

I had so many blue screens, it's not even funny.

Blue screens are usually hardware failures.

I'd start diagnostics with running Windows built in memtest over night, or get an external memtest and put it on a USB stick and run that.

 

[MissFortune]

Daz can be unstable, but I've never had it cause a bluescreen on me. As mentioned, it's most likely hardware related.

This is pretty common behavior for dying RAM/system memory. Have you checked your Event Viewer? They usually aren't super helpful, but they can be a good starting point.

 

[anne O'nymous]

This is pretty common behavior for dying RAM/system memory.

RAM that can perfectly be the GPU one in the present case.

The 4.23 is the worse version Daz ever made when it come to memory management.
There's a part of the GPU RAM (apparently around 200 to 300 MB) that is never freed after a render; like if they decided to store something there too (the compiled shaders?) and simply forgot that the memory used should be freed at the end of the process. If you batch render, or pass a long time working on small scenes and rendering them, even on low quality, to have a better view of the result, you can quickly have the GPU reach part of its RAM that are usually not used.

 

[MissFortune]

RAM that can perfectly be the GPU one in the present case.

The 4.23 is the worse version Daz ever made when it come to memory management.
There's a part of the GPU RAM (apparently around 200 to 300 MB) that is never freed after a render; like if they decided to store something there too (the compiled shaders?) and simply forgot that the memory used should be freed at the end of the process. If you batch render, or pass a long time working on small scenes and rendering them, even on low quality, to have a better view of the result, you can quickly have the GPU reach part of its RAM that are usually not used.

I'm aware of the memory leak. It's not necessarily new, though. Worse? Maybe, but I've not updated to 4.23, so I can't really speak to it. Don't really plan to, either. Likely will finish this game with Daz and move to Blender.

I've run out of VRAM (and RAM) pre-4090, but never had a bluescreen. Usually just crashes, at worst. It could very well be that, but it sounds more like system memory, or maybe a boot drive issues.

 

[anne O'nymous]

I've run out of VRAM (and RAM) pre-4090, but never had a bluescreen. Usually just crashes, at worst. It could very well be that, but it sounds more like system memory, or maybe a boot drive issues.

It's not what I meant, anyway running out of GPU RAM will just make Daz Studio switch to CPU rendering. But by over filling the RAM, either GPU or system, it make RAM banks/cells that were generally ignored be used.
To simplify, see it as a bucket with an invisible crack near its top. As long as you don't fill it completely, everything is fine and you believe that your bucket is in perfect condition. But each time you fill it up to the crack, or over it, you'll get water everywhere.

 

[coffeeaddicted]

Just to inject.
DAZ is a horrible software. These issues are indeed not new but it's the only software i use that gives me from time to time a bluescreen.
Granted my system isn't new but it runs fine with everything else. Even AAA games.
I just think its lazy coding and bad QA.
And yes, every new version runs slower. Just the default.
I have still to run memcheck but i am certain it isn't my ram.
The bluescreen stated security violation. So i have to assume there is something else going on. It runs otherwise, stable.
I just think that their "new" versions aren't really tested before release them. I don't need bleeding edge software that is unstable.
But like i said, i have to still test my hardware.

The crash, most of the time, happens when loading a new scene after flushing the old one. I kind of assume there is some mem corruption going on. The blue screen itself is more or less random. Doesn't happen all the time. If i have some time, i may read the log if it captured something.