Countless Application Error caused by SkypeHost.exe: Build 10558

Is anyone else getting this?

My Event Viewer is filled with error reports about this, even uninstalled Skype itself thinking it was that but it wasn't

Faulting application name: SkypeHost.exe, version: 10.0.0.325, time stamp: 0x5615656e
Faulting module name: SkypeHost.exe, version: 10.0.0.325, time stamp: 0x5615656e
Exception code: 0xc0000602
Fault offset: 0x001f4136
Faulting process id: 0x2d14
Faulting application start time: 0x01d10365ff054c36
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe\SkypeHost.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe\SkypeHost.exe
Report Id: 2c7e5af3-6ebd-449c-a8ba-479b9c79693c
Faulting package full name: Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe
Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1

-

System

- Provider [ Name] Application Error

- EventID 1000 [ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated [ SystemTime] 2015-10-10T14:14:37.685002400Z

EventRecordID 81199

Channel Application

Computer PRS-Win8

Security

-

EventData

SkypeHost.exe

10.0.0.325

5615656e

SkypeHost.exe

10.0.0.325

5615656e

c0000602

001f4136

2d14

01d10365ff054c36

C:\Program Files\WindowsApps\Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe\SkypeHost.exe

C:\Program Files\WindowsApps\Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe\SkypeHost.exe

2c7e5af3-6ebd-449c-a8ba-479b9c79693c

Microsoft.Messaging_1.10.7000.0_x86__8wekyb3d8bbwe

ppleae38af2e007f4358a809ac99a64a67c1

It's generating a new error report ever 1-2 seconds

I just rebooted and at first all seemed good but then after about 60 seconds once it had completed "The Software Protection service" stuff it starts up again. Every few seconds an error message the same.

So I go to the folder: C:\Program Files\WindowsApps (need to "take ownership" to be allowed in) then delete the three folders:



And immediately the error reports stop (as you'd expect), just one single new error now in event viewer "Activation of app Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1 failed with error: The system cannot find the file specified. See the Microsoft-Windows-TWinUI/Operational log for additional information."

So I'll reboot and see what happens! :)

As its a non official release, i wouldn't worry about it.

Roy

Well the main problem was that it seemed to be affecting the performance of my PC but yeah at least with it not being able to find it the errors are not happening so that'll do as the best solution for now :)

I would have gladly stayed away from all insider builds the problem was inputmapper wasn't working with Windows 10 Retail and the only way to get it working was a number of unreliable workarounds that were a real pain in the butt! :)

The same crash is still here in Win-10, 1152, (OS build 10586.71). The last build I believe (?).
Some details from windbg. Call-stack:

SkyWrap!MSNPNetworkConnector::queueEvent+0x7
SkyWrap!MSNPManager::endBackgroundMode+0x49
SkyWrap!callback::ThreadCallScheduler::ExecThreadCalls+0x200
SkyWrap!callback::manager::ExecCallbacks+0xc
SkyWrap!Backbone::Run+0x20f
SkyWrap!SplOpaqueUpperLayerThread::run+0x8c
SkyWrap!spl_v18::winrtThreadDispatch+0x49
SkyWrap!spl_v18::winrtThreadEntry+0x87
SkyWrap!spl_v18::ThreadPoolThreadEntry::Invoke+0x45
threadpoolwinrt!Windows::System::Threading::CThreadPoolWorkItem::CommonWorkCallback+0xaf
threadpoolwinrt!Windows::System::Threading::CThreadPoolWorkItem::TimeSlicedCallback+0x27
KERNEL32!BaseThreadInitThunk+0x24
ntdll!__RtlUserThreadStart+0x2f
ntdll!_RtlUserThreadStart+0x1b

And a bit from the module list + offending instruction:
ModLoad: 00320000 00347000 C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\SkypeHost.exe
ModLoad: 77530000 776ab000 C:\WINDOWS\SYSTEM32\ntdll.dll
ModLoad: 74940000 74a20000 C:\WINDOWS\SYSTEM32\KERNEL32.DLL
ModLoad: 77050000 771ce000 C:\WINDOWS\SYSTEM32\KERNELBASE.dll
ModLoad: 70cb0000 70d42000 C:\WINDOWS\system32\apphelp.dll
ModLoad: 77340000 774fd000 C:\WINDOWS\SYSTEM32\combase.dll
ModLoad: 752b0000 7536e000 C:\WINDOWS\SYSTEM32\msvcrt.dll
ModLoad: 755e0000 7568d000 C:\WINDOWS\SYSTEM32\RPCRT4.dll
ModLoad: 74260000 7427e000 C:\WINDOWS\SYSTEM32\SspiCli.dll
ModLoad: 74250000 7425a000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
ModLoad: 771d0000 77228000 C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
ModLoad: 70c30000 70c58000 C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\SkypeBackgroundTasks.dll
ModLoad: 757d0000 75814000 C:\WINDOWS\SYSTEM32\sechost.dll
ModLoad: 70b30000 70ba1000 C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\msvcp120_app.dll
ModLoad: 70bb0000 70bec000 C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\vccorlib120_app.DLL
ModLoad: 70a60000 70b2c000 C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\msvcr120_app.dll
....

bc4.186c): Access violation - code c0000005 (!!! second chance !!!)
*** WARNING: Unable to verify checksum for C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\SkyWrap.dll
eax=03dbfac0 ebx=00ab5c70 ecx=00000000 edx=00000000 esi=00000000 edi=00ae34a8
eip=61df6197 esp=03dbfaf0 ebp=03dbfaf8 iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
SkyWrap!MSNPNetworkConnector::queueEvent+0x7:
61df6197 8b7e50 mov edi,dword ptr [esi+50h] ds:002b:00000050=????????

was just looking at my reliability report monitor thing and noticed something similar.
(C:\Program Files\WindowsApps\Microsoft.Messaging_2.13.20000.0_x86__8wekyb3d8bbwe\SkypeHost.exe
and combase.dll)

that apparently started right after win10 (threshold 2) updated a bunch of stuff, including messaging+skype on 14/3

doesn't seem to have affected anything in day to day running. (i don't use skype) just bemusing that the error report is logged every 15 minutes for a week and ms hasn't pushed out a fix.

pzhndal said:

....(i don't use skype) ....
...the error report is logged every 15 minutes for a week and ms hasn't pushed out a fix.

That's the main reason I distrust all Metro apps and have un-installed most of them.

Besides, I think this article pretty much sums up the idea behind MS's shift to the Metro-style app market:
http://www.startmenu10.com/Epic-Fail...indows-10.html