dwm.exe crashes occasionally

However i do share your frustration when one user is calling a mod unsafe based on the sample size of one while doing activities which seem to be known to cause problems. I should also note that i have checked my logs more carefully and i did find a few instances of DWM entering a crash-reboot loop. While i DO NOT claim mod as the culprit (i have no logs archived prior to a few days of mod being installed thus there is no way to check prior DWM behavior, also i just think that my computer running out of RAM is the culprit), explanation by ephemeralViolette also makes sense. I don't think handle method (be in windhawk or CCT doing it) is "the danger", but whatever faults it have cam be brought up by whatever problematic crap user is doing.

My honest opinion is: don't do real work on your hobby setup.

I certainly didn't call it unsafe.

And the only thing I'm doing wrong is to use mods and other stuff necessary to make Windows 11 look normal with the classic theme.

But that's what everybody does here so I'm not sure what you're trying to say.

On top of that, I always try to make sure to use as few mods as possible with a lot of exclusions, in order to be as safe as you can be with mods that alter a lot (because that's just the nature of these mods).

I thought and still think that it's worth mentioning that there might be a problem with the handle mod (I can't say this for sure though, I'll just have to see what happens in the next couple of days).

Certainly NOT to blame anyone but in the hope that whatever causes the problems might get fixed.

It's no secret.

It's just that no one asked me before...

So these are the mods I use (PLUS DWM unextend frames and client edge for open/save dialogs, which didn't fit on the screenshot)

The Classic taskbar fixer mod can't be the culprit, since I've used it for quite some time.

The DWM unextend frame mod also shouldn't cause any problems because it's basically disabled except for a few processes 

(mmc.exe
notepad.exe
thunderbird.exe
dccw.exe
cttune.exe
waterfox.exe
mspaint.exe
Default Programs Editor.exe
explorer.exe
winpaletter.exe)

All mods have dwm.exe and critical system processes excluded.

P.S. I use Windhawk version 1.4.1

So these are the loaded mods:

For my part, I don't really have a choice of work on the machine on hobby setup is installed.  And I've never had a serious problem related to it (for what is really critical, I am testing on a virtual machine). The most serious problems are sudden blue screens, the origin of which is unclear to me, but which started when I purchased the machine (so it is probably a problem with certain drivers).

But I know you're not as lucky as I am with Windows. I have become accustomed to making actions that scare most people seem trivial to me. Whereas on Linux, I encounter problems (notably installing applications) that very few people complain about.

Pretty sure, yes.

Because the error message says that dwm.exe has crashed.

But let me clarify something nonetheless (not only for you but for everybody to understand the problem better):

At first, I thought that dwm.exe behaves differently on Windows 11 and that it will therefore throw me out of Windows whenever dwm.exe crashes (that's basically what I wrote in the first post in this thread). But I was wrong about that because dwm.exe crashes frequently (with the handle method several times a day) and then tries to restart several times but these problems usually go unnoticed, since nothing bad happens.

Only rarely will it happen that dwm.exe crashes and that the user will be thrown out of Windows because of that.

But it's bad enough when it happens.

And there are signs that the handle method seems to be responsible for that because every time I turned it on I got to see dozens of dwm.exe crashes and restarts in the event log (even though usually nothing bad happens).

Of course, other mods could be responsible for that too but as far as I can tell by now that doesn't seem to be the case.