This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi:
I have periodic explorer crashes on my Surface Pro 2017, Win Pro x64 (it is fully updated). The crash seems to occur periodically after a Hello Windows log-in (this occurs after the computer was sleeping rather than on a fresh boot). It seems to involve Windows.UI.XamlHost.dll based on the below.
When I look in the Event viewer I see errors like this:
Event ID 1000
Faulting application name: explorer.exe, version: 10.0.16299.125, time stamp: 0xfeba44fb
Faulting module name: Windows.UI.XamlHost.dll, version: 10.0.16299.15, time stamp: 0x00f27b8f
Exception code: 0xc0000409
Fault offset: 0x0000000000001db1
Faulting process id: 0x1880
Faulting application start time: 0x01d38282e4131af4
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Windows\System32\Windows.UI.XamlHost.dll
Report Id: 6e835576-b35e-4d24-b6ce-331b05fa2c55
Faulting package full name:
Faulting package-relative application ID:
If I click on Start > type "view all" then click on "View all problem reports Control panel" the "Windows Explorer" "Stopped working" errors and then double click on one I would get something like this:
Source
Windows Explorer
Summary
Stopped working
Date
11/26/2017 10:53 AM
Status
Report sent
Description
Faulting Application Path: C:\Windows\explorer.exe
Problem signature
Problem Event Name: BEX64
Application Name: Explorer.EXE
Application Version: 10.0.16299.15
Application Timestamp: 66e02565
Fault Module Name: Windows.UI.XamlHost.dll
Fault Module Version: 10.0.16299.15
Fault Module Timestamp: 00f27b8f
Exception Offset: 0000000000001db1
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.16299.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 2eb9
Additional Information 2: 2eb9591f0e04c7cfea277e3f34d3348f
Additional Information 3: 9333
Additional Information 4: 9333781589f3ec46cd357f0fda06eea0
Extra information about the problem
Bucket ID: 15f01e3e317a50b7b6bb92d1b9fc4f7c (116455065336)
I am at a loss to understand what the problem is here. I am glad to disable Hello Windows if this would end the problem. Thanks in advance for any help on this!
[Moved from: Windows / Windows 10 / Windows Hello, lock screen & sign-in]
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We appreciate your response. Yes, you can perform a fresh start, and if the same issue persists, proceed to perform a clean installation of your Windows 10. In fresh start, you can keep your files and settings while reinstalling Windows. However, the clean installation of Windows will wipe out all of your files and settings.
Don't hesitate to reach out to us if further assistance is needed.
I read through this whole thread. I have the same symptom, but a different hardware profile.
Win10 Enterprise 10.0.16299.371
HP EliteBook 840 G3
Intel HD Graphics 520 v22.20.16.4771 (I soon plan to try 23.20.16.5018 - the latest officially supported from HP)
Synaptics Fingerprint reader - Driver version v4.5.341.0
I do not have Dropbox or 7-Zip installed on my computer, but I do find that, same as this reporter, every so often, when I unlock my computer using my fingerprint with Hello, Explorer crashes with the same kind or error and Edge becomes unresponsive.
I think my commonality is the Intel graphics drivers. So this could be a bug in Windows or a (more likely) bug in the Intel Graphics drivers.
I have been experiencing this issue for several months now and decided to look to see if anyone else has reported this issue, so this isn't a new issue, but it has become annoying. I have a secondary monitor attached to my computer which is a 4K HDMI connected display via DisplayPort. I find that I am more likely to experience an explorer.exe crash if I try to use Hello before or during the time in which my secondary monitor is waking up from sleep when my computer is locked. (My displays go to sleep after a minute or so when my computer is locked.)
Hi Racebo:
OP here. Sorry for the delay in response.
This is indeed very very frustrating. After about six month this problem seems to have died down. No clue if this was a Windows or Surface patch (I manually got them: see my posts earlier).
I also disabled Hello Windows and use Hibernate rather than Standby.
Sorry I cannot be more specific about diagnosing the problem it has truly been a rough road on my end. Oh and yes now I have some dead pixels :(
I will try to check in here if you need further advice.
