Surface Pro 2017, Win 10 Pro x64: Explorer crash (Windows.UI.XamlHost.dll)

Anonymous
2018-01-04T03:56:25+00:00

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.

0 comments

68 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-07T07:04:23+00:00

    I have exactly the same issue. Build 16299.192 on newest Surface Pro.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-08T05:20:13+00:00

    I already tried the SFC.

    The troubleshooting only turned on sleep for battery (which I have turned off since that crashes my Surface).

    I need a specific suggestion. This is not very helpful.

    PS Sorry Gerben that you have been having the same problems. This Surface has been exceptionally disappointing. I would not expect this level of instability from such a pricey machine (and one that Microsoft makes)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-08T15:01:49+00:00

    Another explorer crash exactly like the previous ones.

    Not sure if it is related but the Edge browser stopped a few hours before (though this did not happen most times I had an explorer crash):

    via 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

    Microsoft Edge Content Process

    Summary

    Stopped working

    Date

    ‎1/‎7/‎2018 10:42 PM

    Status

    Report sent

    Description

    Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

    Problem signature

    Problem Event Name: MoBEX

    Package Full Name: Microsoft.MicrosoftEdge_41.16299.15.0_neutral__8wekyb3d8bbwe

    Application Name: praid:ContentProcess

    Application Version: 11.0.16299.15

    Application Timestamp: 59cda7cd

    Fault Module Name: EdgeContent.dll

    Fault Module Version: 11.0.16299.125

    Fault Module Timestamp: e5feec40

    Exception Offset: 0000000000082243

    Exception Code: c0000409

    Exception Data: 0000000000000007

    OS Version: 10.0.16299.2.0.0.256.48

    Locale ID: 1033

    Additional Information 1: fbbb

    Additional Information 2: fbbbeb9e75b9a392bd0b19d9abee419b

    Additional Information 3: f820

    Additional Information 4: f820b8601cb36d2a94461cc926cdff30

    Extra information about the problem

    Bucket ID: 8be98c36d855319a41b11e30cbf1228a (1274833364451402378)

    I imagine this will never get resolved. Trying to figure out which is worse: Windows 10 or my Surface Pro 2017. Tough choice.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-08T15:40:33+00:00

    Also from analysis of Edge minidump (MicrosoftEdgeCP.exe.mini.****.dmp):

    FAULTING_IP:

    EdgeContent!wil::details::ReportFailure+3d597

    00007ffa`e4722243 cd29            int     29h

    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)

    ExceptionAddress: 00007ffae4722243 (EdgeContent!wil::details::ReportFailure+0x000000000003d597)

       ExceptionCode: c0000409 (Stack buffer overflow)

      ExceptionFlags: 00000001

    NumberParameters: 1

       Parameter[0]: 0000000000000007

    PROCESS_NAME:  MicrosoftEdgeCP.exe

    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application.  This  overrun could potentially allow a malicious user to gain control of this application.

    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application.  This  overrun could potentially allow a malicious user to gain control of this application.

    EXCEPTION_PARAMETER1:  0000000000000007

    NTGLOBALFLAG:  0

    APPLICATION_VERIFIER_FLAGS:  0

    FAULTING_THREAD:  0000000000004cc4

    BUGCHECK_STR:  APPLICATION_FAULT_STACK_BUFFER_OVERRUN_MISSING_GSFRAME_SEHOP

    PRIMARY_PROBLEM_CLASS:  STACK_BUFFER_OVERRUN_SEHOP

    DEFAULT_BUCKET_ID:  STACK_BUFFER_OVERRUN_SEHOP

    LAST_CONTROL_TRANSFER:  from 00007ffae46e4ca4 to 00007ffae4722243

    STACK_TEXT: 

    000000f051efe8b0 00007ffae46e4ca4 : 0000000000000000 00007ffae46a7270 0000000000000000 0000000000000000 : EdgeContent!wil::details::ReportFailure+0x3d597

    000000f051effdf0 00007ffae4702509 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : EdgeContent!wil::details::ReportFailure_Hr+0x44

    000000f051effe50 00007ffae472319e : 0000022a13c2be20 0000000000000000 0000000000000000 0000000000000000 : EdgeContent!wil::details::in1diag3::FailFast_Hr+0x29

    000000f051effea0 00007ffb061e1fe4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : EdgeContent!`anonymous namespace'::MemoryLimitWatchdogThreadProc+0x3b43e

    000000f051efff30 00007ffb08d6ef91 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14

    000000f051efff60 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

    FOLLOWUP_IP:

    EdgeContent!wil::details::ReportFailure+3d597

    00007ffa`e4722243 cd29            int     29h

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  EdgeContent!wil::details::ReportFailure+3d597

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: EdgeContent

    IMAGE_NAME:  EdgeContent.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    STACK_COMMAND:  ~4s ; kb

    FAILURE_BUCKET_ID:  STACK_BUFFER_OVERRUN_SEHOP_c0000409_EdgeContent.dll!wil::details::ReportFailure

    BUCKET_ID:  X64_APPLICATION_FAULT_STACK_BUFFER_OVERRUN_MISSING_GSFRAME_SEHOP_MISSING_GSFRAME_EdgeContent!wil::details::ReportFailure+3d597

    WATSON_STAGEONE_URL:  http://watson.microsoft.com/00082243.htm?Retriage=1

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-08T20:01:54+00:00

    Based on the analysis that you've provided, the cause of the crash is different. To isolate if this is caused by a corrupted user profile, it is better to create a new user account and check if the crash occurs. Click this link on how to create a local user or administrator account in Windows 10.

    Keep us in the loop with the result.

    Was this answer helpful?

    0 comments