I still have crash of dwm with the new version:

Nom de l’application défaillante dwm.exe, version : 10.0.14393.0, horodatage : 0x578999ab
Nom du module défaillant : udwm.dll, version : 10.0.14393.0, horodatage : 0x5789987f
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000033f0f
ID du processus défaillant : 0x594
Heure de début de l’application défaillante : 0x01d21018c29ce972
Chemin d’accès de l’application défaillante : C:\Windows\system32\dwm.exe
Chemin d’accès du module défaillant: C:\Windows\SYSTEM32\udwm.dll
ID de rapport : 597e02e3-bac4-41fb-bda1-23e1f27d0b99
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

still, the error message have change because windowblinds64 doesn't appear anymore in the error message.

already done a support message.

not hardware realted

not windows 10 installation related.

yop . After more digging in the problem, windowFX is only a .... how do we say that in english.... pusher? because that it calls more often the dwm windowFX makes the problem happening more often. that's why one other guy and me were thinking about windowFX but in fact both of the programs are at fault because calling the same process - libraries.

Anyway the problems always occured with nearly the same conditions. It's always due to the interaction of dwm between stardock products and games open or clicking a link to open Edge or clicking in a mail notification in the action center to open the APP mail. I suspect it's always because there is a timeout of the app that we try to open and so dwm can't apply the effects that the stardock products are requesting etc ...

something like that I think. But anyway the problem is not happening of none of my computers with none of the stardock products installed. Anyway to make the problem appear you need to make some multitasking, so open some games in window mode, some universal app etc . Not just one program etc, we are working in real world where people does multitasking all the time, not laboratory conditions where you do one action after another.

so you didn't understand at all what I've said ^^

I was saying that on multiple computers with the stardock products activated I'm experiencing dwm crashes :" the problem is NOT happening at NONE of my computers with NONE of the stardock products installed."

=Maybe I'm not speaking correctly. that's means : it s not happenning with none of the stardock programs activated on any of my computers.

and as I stated: "not windows 10 installation related."

Window FX is a pusher of the problem = more occurences of the problem

windowblind seems to be the cause of the problem because it start happening with him only installed.

And I give  a clue to look into it: TIMEOUT

So I would suggest that we discuss more about how you test your software since I'm not the only one complaining about it .

 

Does the problem happen without WindowBlinds installed but WITH WindowFX installed?

Honestly, I didn't try yet because lack of time .

WindowFX causing it makes a great deal more sense as it directly interacts with the DWM in much more complicated ways than WindowBlinds which if the DWM is crashing with say 10.0.7 would strongly point to a Microsoft end issue. 

There have been bugs in the DWM before, ModernMix could crash out the DWM if a modern app was closed within Xms of a thumbanil window being shown.  This was a Microsoft issue though not ModernMix.

Great explanation We can finally find common grounds with a good example. Ok so more a misscoded usecase in the dwm than a bad interaction of your software with the DWM. understood. But so yes, to answer to your implicit quesiton, occured a lot with 10.0.7. Occured a bit less frequent with the new beta version. So don't know why. Maybe you avoid a function of dwm in the new version I don't know but anyway I had transfered for a week now the logs to your technical support and if your logs takes the compilation of events of the event monitor, you can easily see some crash with the windowsblind64 module in cause.

What were you doing at the time when that happened?

Were you changing skin?

Also what skin are you using and where is WindowBlinds installed.  I assume you have not relocated the WindowBlinds skin directory.