This started happening on two machines with Windows RTM (neither are insider builds) a couple of weeks ago for both my and my wife's accounts.
Here's the event log:
Faulting application name: HxTsr.exe, version: 16.0.6208.4200, time stamp: 0x55ef64bd
Faulting module name: hxcomm.dll, version: 16.0.6208.4200, time stamp: 0x55ef6548
Exception code: 0x80000003
Fault offset: 0x00000000003ea929
Faulting process id: 0xd2c
Faulting application start time: 0x01d0f0fa741173af
Faulting application path: C:\Program
Files\WindowsApps\microsoft.windowscommunicationsapps_17.6208.42001.0_x64__8wekyb3d8bbwe\HxTsr.exe
Faulting module path: C:\Program
Files\WindowsApps\microsoft.windowscommunicationsapps_17.6208.42001.0_x64__8wekyb3d8bbwe\hxcomm.dll
Report Id: 8d684bb4-c24a-45d0-b1a7-cdf76d7ad646
Faulting package full name: microsoft.windowscommunicationsapps_17.6208.42001.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
Here's the callstack from a crashdump captured with procdump:
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x37a321
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x176fff
HxComm!Hx::UnregisterHxCommETWProviders+0xbdb38
HxComm!Hx::UnregisterHxCommETWProviders+0xbd67d
HxComm!Hx::UnregisterHxCommETWProviders+0xb9b10
HxComm!Hx::UnregisterHxCommETWProviders+0xb9f1a
HxComm!Hx::UnregisterHxCommETWProviders+0x7cb06
HxComm!Hx::UnregisterHxCommETWProviders+0x31a47
HxComm!Hx::UnregisterHxCommETWProviders+0x3637d
HxComm!Hx::UnregisterHxCommETWProviders+0x35460
HxComm!Hx::UnregisterHxCommETWProviders+0x23d0c
HxComm!Hx::UnregisterHxCommETWProviders+0x21772
HxComm!Hx::UnregisterHxCommETWProviders+0x34089
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x27e384
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x225d53
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x270155
HxComm!Hx::RegisterHxCommETWProviders+0x166db
HxComm!Hx::RegisterHxCommETWProviders+0x133c
HxComm!Hx::GenerateReplyHeaderFromOriginPart+0x34f90e
mso20imm+0x2318e
mso20imm+0x2b4f2
threadpoolwinrt!Windows::System::Threading::CThreadPoolWorkItem::CommonWorkCallback+0xbd
threadpoolwinrt!Windows::System::Threading::CThreadPoolWorkItem::BatchedCallback+0x47
ntdll!TppWorkpExecuteCallback+0x35a
ntdll!TppWorkerThread+0x6da
kernel32!BaseThreadInitThunk+0x22
ntdll!RtlUserThreadStart+0x34
FOLLOWUP_IP:
HxComm!Hx::GenerateReplyHeaderFromOriginPart+37a321
00007ffb`d50fa929 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: hxcomm!Hx::GenerateReplyHeaderFromOriginPart+37a321
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HxComm
IMAGE_NAME: HxComm.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 55ef6548
STACK_COMMAND: ~15s; .ecxr ; kb
FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_HxComm.dll!Hx::GenerateReplyHeaderFromOriginPart
BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_hxcomm!Hx::GenerateReplyHeaderFromOriginPart+37a321
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_hxcomm.dll!hx::generatereplyheaderfromoriginpart
FAILURE_ID_HASH: {6afd4f33-dd22-7c02-6080-91e529c4b8ab}
I already tried uninstalling and reinstalling the communication apps with:
Remove-AppxPackage microsoft.windowscommunicationsapps
Going into the Outlook sync settings and disabling the Email sync option prevents the apps from crashing, but of course that defeats the purpose of the mail app.
On one of the machines I even did a hard reset of Windows to no avail.
I'm at my wit's end on this one. Any advice would be greatly appreciated.