New
#1
Dwm.exe and others crashing on wake - kills pc - please help!
Hi guys, I've encountered a new issue (itself a variation on an old one I thought was gone) on Windows 10 Creators edition and could use some ideas.
In short, sometimes, very occasionally, when I wake the PC up from sleep, everything gets going except the monitor. It stays in sleep and I am forced into a restart to get it going again. It's a kind of black screen without the screen actually being on.
After some huffing and puffing I seem to have isolated the culprit to either dwm.exe, lockapp.exe or logonui.exe - they all crash when this happens (via event viewer), suggesting the normal signal to monitor simply isn't happening or is being blocked because lock screen and visual apps have broken down.
I Googled it and it is a known issue, so at least it's not just me, but is there any fix or remedy?
I disabled PLL overclock in the BIOS (no idea why), I disabled auto source selection in my monitor, and I've changed the DP2 port my monitor plugs into on my 1080Ti. All of these are stabs in the dark. I have also seen an actual black screen caused by Comodo, but it was able to recover without a restart, and I am also aware Nvidia drivers can cause this.
The following are the crash logs for each app:
Faulting application name: LockApp.exe, version: 10.0.15063.0, time stamp: 0x58ccbce3
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.15063.540, time stamp: 0xd330c8c8
Exception code: 0xc000027b
Fault offset: 0x0000000000592aa3
Faulting process ID: 0x46f0
Faulting application start time: 0x01d329a023ce68f0
Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report ID: 69c9aa56-f515-4dc6-8f85-3880ae6d091c
Faulting package full name: Microsoft.LockApp_10.0.15063.0_neutral__cw5n1h2txyewyFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: dwmcore.dll, version: 10.0.15063.483, time stamp: 0x460f87da
Exception code: 0xc00001ad
Fault offset: 0x00000000000d467e
Faulting process ID: 0x4c4
Faulting application start time: 0x01d32657026c5424
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\dwmcore.dll
Report ID: 62b57f7c-4aaa-48c4-89ba-15d4304bec4f
Faulting package full name:
Faulting package-relative application ID:Hoping someone can impart words of wisdom. The annoying thing is this happens 'now and then' - meaning you can go a week on a new 'attempt' after adjusting something, think the issue is gone, it then happens and you've wasted another week trying to fix it. Can take months to resolve because of this. So could use some useful guidance!Faulting application name: LockApp.exe, version: 10.0.15063.0, time stamp: 0x58ccbce3
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.15063.540, time stamp: 0xd330c8c8
Exception code: 0xc000027b
Fault offset: 0x0000000000592aa3
Faulting process ID: 0x46f0
Faulting application start time: 0x01d329a023ce68f0
Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report ID: 69c9aa56-f515-4dc6-8f85-3880ae6d091c
Faulting package full name: Microsoft.LockApp_10.0.15063.0_neutral__cw5n1h2txyewy
Cheers.