Another crash (and short extract that I could generate at the bottom of this post):
https://1drv.ms/u/s!AoMjGh2ERllBcVpsHyzkDy4jlQo
(1) Do the exception codes tell us anything?
(2) Edge
Let me mention again that Edge Browser is completely unresponsive after this happens and must be closed via the Task Manager. So whether this is the cause or the effect, there is something which is interacting with the Edge Browser associated with this crash.
At this point I have a very updated Surface with very little in the way of apps on it. I am rather amazed at how bad this device is.
FAULTING_IP:
Windows_UI_XamlHost!wil::details::ReportFailure+e5
00007ffa`c8781db1 cd29 int 29h
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ffac8781db1 (Windows_UI_XamlHost!wil::details::ReportFailure+0x00000000000000e5)
ExceptionCode: c0000409 (Stack buffer overflow)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000007
PROCESS_NAME: explorer.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: 0000000000004fb8
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 00007ffac8781e09 to 00007ffac8781db1
STACK_TEXT:
000000005ee4e090 00007ffac8781e09 : 0000ae488f91a2ab 0000000000000000 0000000000000000 00007ffac8789fd8 : Windows_UI_XamlHost!wil::details::ReportFailure+0xe5
000000005ee4f5d0 00007ffac8798d59 : 000000002496ef40 000000002bb47230 0000003700000011 000000002b7eb610 : Windows_UI_XamlHost!wil::details::ReportFailure_Hr+0x39
000000005ee4f630 00007ffac87928fb : 0000000000000000 000000002bb47590 000000002bcd31c0 000000000000c000 : Windows_UI_XamlHost!wil::details::in1diag3::_FailFast_Hr+0x29
000000005ee4f680 00007ffac879946c : 000000002b7ea960 0000000000000000 0000000000000000 0000000000000000 : Windows_UI_XamlHost!Microsoft::WRL::SimpleActivationFactory::ActivateInstance+0x34b
000000005ee4f6b0 00007ffad5a1d544 : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 : Windows_UI_XamlHost!ASTAThreadHost::s_ASTAThreadHostStartThreadProc+0x6c
000000005ee4f6e0 00007ffad5ad1fe4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : SHCore!_WrapperThreadProc+0xc4
000000005ee4f7c0 00007ffad633efc1 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
000000005ee4f7f0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21
FOLLOWUP_IP:
Windows_UI_XamlHost!wil::details::ReportFailure+e5
00007ffa`c8781db1 cd29 int 29h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Windows_UI_XamlHost!wil::details::ReportFailure+e5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Windows_UI_XamlHost
IMAGE_NAME: Windows.UI.XamlHost.dll
DEBUG_FLR_IMAGE_TIMESTAMP: f27b8f
STACK_COMMAND: ~275s ; kb
FAILURE_BUCKET_ID: STACK_BUFFER_OVERRUN_SEHOP_c0000409_Windows.UI.XamlHost.dll!wil::details::ReportFailure
BUCKET_ID: X64_APPLICATION_FAULT_STACK_BUFFER_OVERRUN_MISSING_GSFRAME_SEHOP_MISSING_GSFRAME_Windows_UI_XamlHost!wil::details::ReportFailure+e5
WATSON_STAGEONE_URL: http://watson.microsoft.com/00001db1.htm?Retriage=1
Followup: MachineOwner