Windows clients crash after Desktop Window Manager event
|Opened on:||Thursday, January 19, 2017 - 02:41|
|Last modified:||Tuesday, July 31, 2018 - 20:39|
My Windows 10 laptop is set to keep running when I close the lid.
Normally, all is well. A few times, however, all Foldit clients have crashed when I open the lid.
A few seconds before the crash events were logged, the Windows application log had an event from Desktop Window Manager (DWM), stating "[t]he Desktop Window Manager has registered the session port". It was event ID 9027, with qualifier 16384.
I had multiple clients open, and all crashed. No debug.txt logs were generated, but all clients had a similar unhandled exception in log.txt:
1: no symbol (no line)
2: no symbol (no line)
3: no symbol (no line)
4: no symbol (no line)
5: DrvPresentBuffers +847222 bytes (no line)
6: DrvPresentBuffers +849420 bytes (no line)
7: DrvSetLayerPaletteEntries +530964 bytes (no line)
8: DrvPresentBuffers +485253 bytes (no line)
9: library_main +3707346 bytes (no line)
I've seen similar Foldit crashes when switching user ids. I think that was before I upgraded this machine to Windows 10, so I'm pretty sure if was Windows 7 professional.
It seems like there's some problem with how the Foldit client interacts with DWM. (DWM controls what appears on the screen in current versions of Windows.) Perhaps the 9027 event gives a hint as to what's happening.