The error looks similar to the previous one so can you temporarily uninstall Dropbox and Notepad++ and see if the error re-occurs.
Surface Pro 2017, Win 10 Pro x64: Explorer crash (Windows.UI.XamlHost.dll)
![](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)
Anonymous
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]
Windows for home | Windows 10 | Performance and system failures
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.
68 answers
Sort by: Oldest
-
Anonymous
2018-01-31T03:08:23+00:00 -
Anonymous
2018-01-31T13:36:57+00:00 Can do auggy.
Can you see DropBox or Notepad++ listed in the CrashDump? I could not see them listed as a potential problem.
-
Anonymous
2018-01-31T13:57:09+00:00 Dropbox shows up :
*** ERROR: Symbol file could not be found. Defaulted to export symbols for sppc.dll -
*** WARNING: Unable to verify timestamp for DropboxExt64.19.0.dll
*** ERROR: Module load completed but symbols could not be loaded for DropboxExt64.19.0.dll
*** WARNING: Unable to verify timestamp for igd10iumd64.dll
*** ERROR: Module load completed but symbols could not be loaded for igd10iumd64.dll
GetUrlPageData2 (WinHttp) failed: 12002.
Probably caused by : Windows.UI.XamlHost.dll ( Windows_UI_XamlHost!wil::details::ReportFailure+e5)
I also suggest to uninstall Notepad++ as the NppShell_06.dll has been known to cause Explorer crashes albeit usually on a right-click.
-
Anonymous
2018-02-01T16:28:37+00:00 Thanks auggy. I am going to start with DropBox and see if that helps. Interestingly it has been stealthily installing updates (I was rather sure I had turned that off, and I almost ever use the app). I do not think that is the source of my issues (the last update was on 23 Jan and my most recent explorer crashes were on 25 Jan and 29 Jan), but definitely not going to miss it for now.
-
Anonymous
2018-02-01T21:36:40+00:00 Sigh no dice. Another explorer crash. They seem to be more frequent now too. Here is the crash dump:
https://1drv.ms/u/s!AoMjGh2ERllBaylgKp0\_uCiMPI8
Let me note again that Edge is totally frozen after this happens: cannot close it, switch tabs, etc. I have to manually close Edge via Task Manager. So either this is due to Edge (which I think is the source of all of this) or the explorer crash is at least temporarily disabling Edge
One other note:
the timestamp on the crashdump is from when the surface was in sleep mode. I had thought this happened when I exit sleep mode but this happened during sleep mode itself.