DWM reset on 24H2 multi-monitor when switching windows

[RibShark]

On my multi-monitor setup on 24H2 I am having an issue where occasionally switching between windows from one monitor to another is causing a DWM reset (seems to happen more when the window on the first monitor is in fullscreen).

[ALTaleX531]

Can't reproduce, please provide your memory dump file.

[RibShark]

No memory dump files are created. When it happens, both screens go black for a short period before returning with Aero Basic titlebars, then after a second or so go back to the normal titlebars. When OpenGlass is uninstalled this never occurs.
Event viewer shows a Dwminit warning with the message "The Desktop Window Manager process has exited. (Process exit code: 0xc0000409, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 3060 Ti)".

[Exyzos]

Same thing happened to me, and i do have a dump file. How do I send you the dump, it's too large to send here

[Exyzos]

Nevermind, analysis of the dmp file with WinDBG using the analyze -v command yielded this
dwmcrash.txt

[ALTaleX531]

The result of this analysis is not useful because it does not show any stack frames from OpenGlass.

[Exyzos]

So the DMP file is too large to upload here, how should I send it?

[ALTaleX531]

Google Drive would be a good choice.

[Exyzos]

https://drive.google.com/file/d/1wiqAOQoJKMxspaebegJEbdKxXYugqElS/view?usp=drive_link

[Exyzos]

Google Drive would be a good choice.

The link is shared with you now, I approved your request

[ALTaleX531]

It looks like 24H2 breaks a lot of things and there is a lot of code that needs to be refactored. Since this problem can't be reproduced in a VM, it could be quite tricky.

[Skyyblaze]

It looks like 24H2 breaks a lot of things and there is a lot of code that needs to be refactored. Since this problem can't be reproduced in a VM, it could be quite tricky.

@ALTaleX531 I wouldn't mind help testing various builds if that helps you fixing the bug, I'm running 24H2 on a real machine.

[gonzalologorg]

I have been having this issue since updating to 24H2, I knew it was this but seen nobody mentioned it, if there's anything I can provide I can help

But definitely no user with 24h2 and multimonitor should ever use this, usually when I alt tab, sometimes it will work, but damn...The moment it doesn't it's an 8 seconds facepalm until the screen reboots and everything goes back to normal

But damn, i need my windows to look fine, it's a 50% being unusuable and 50% being too good for what windows 11 is

[frandj99]

Hi there,

I just took a look at this GitHub issue, and I'm definitely experiencing the same problem. I use three screens (two 4K and one 1440p), and my DWM resets about once a day. 😅 I guess I might be the most extreme case!

It usually happens when I'm around the taskbar area with the mouse, but I can't be sure that's the only trigger. The screen freezes completely for a few seconds, then everything goes black. When it comes back, there are weird glitches, and the windows have the AeroLite theme for a few seconds until something happens to make them re-render correctly.

I'm also using StartAllBack and ExplorerBlurMica. Maybe these could be factors, so it might be worth checking if @RibShark and @Exyzos have these installed as well.

Where should the memory dump file be located? I don't see anything in the OpenGlass folder or in C:\

Thanks in advance for this amazing project!

[frandj99]

I just got a crash and I can see only the error on Windows's Event Viewer
Oh BTW I'm an nvidia user me too, and I see I had other errors related to NVIDIA Display Container, next to this one with dwm
No clue if this can help

Faulting application name: dwm.exe, version: 10.0.26100.2454, time stamp: 0x102c19e2
Faulting module name: ucrtbase.dll, version: 10.0.26100.1882, time stamp: 0x52db7a2d
Exception code: 0xc0000409
Fault offset: 0x00000000000a502e
Faulting process id: 0xB3C
Faulting application start time: 0x1DB51FA088252FB
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: d316ca56-9484-49c0-a825-5dc49fe9e99f
Faulting package full name:
Faulting package-relative application ID:

Log Name: Application
Source: Application Error
Date: 19/dic/2024 15:19:14
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: Window Manager\DWM-1
Computer: Fra-ROG
Description:
Faulting application name: dwm.exe, version: 10.0.26100.2454, time stamp: 0x102c19e2
Faulting module name: ucrtbase.dll, version: 10.0.26100.1882, time stamp: 0x52db7a2d
Exception code: 0xc0000409
Fault offset: 0x00000000000a502e
Faulting process id: 0xB3C
Faulting application start time: 0x1DB51FA088252FB
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: d316ca56-9484-49c0-a825-5dc49fe9e99f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

21143


Application
Fra-ROG



dwm.exe
10.0.26100.2454
102c19e2
ucrtbase.dll
10.0.26100.1882
52db7a2d
c0000409
00000000000a502e
0xb3c
0x1db51fa088252fb
C:\WINDOWS\system32\dwm.exe
C:\WINDOWS\System32\ucrtbase.dll
d316ca56-9484-49c0-a825-5dc49fe9e99f