Com surrogate stopped working

Scottyboy99 · 25 Dec 2017

Not having any issues with the pc but in reliability history I am seeing occasional ‘com surrogate has stopped working’ messages. It’s very sporadic. Sometimes many many days with nothing listed but then yesterday I saw it shortly after starting machine and then again today. I tried today restarting again immediately in the aftermath to see if it listed a second time but it didn’t so it seems very sporadic. Tried googling but there isn’t anything concise. Wondered if any one had any ideas or similar experiences ?

cheers
Wayne

bro67 · 26 Dec 2017

Something that is using it is causing it to stop. Many processes use a Com Surrogate.

Scottyboy99 · 26 Dec 2017

Ok thanks. I’ll try and ignore it seeing as it’s relatively rare and doesn’t seem to have any effect - I guess troubleshooting it will be like looking for a needle in a haystack!

Layback Bear · 26 Dec 2017

This is probable more than you wanted to know but it is a good read.
From MSDN blog.

What does the COM Surrogate do and why does it always stop working? The Old New Thing

Jack

Scottyboy99 · 26 Dec 2017

I looked a little closer and my issue is exactly the same as in this thread. The faulting module is mso20win32client.dll

Mystery COM Surrogate crashes

looks like office 365 is the cause. Obviously mine is always updated (they are pretty regular) but I guess the last update might have introduced this. Hopefully a new update will come out soon and maybe stop these. For what it’s worth I notice no system functionality issues before and after these entries and office appears to be working absolutely fine. So it’s a mystery

Scottyboy99 · 26 Dec 2017

Layback Bear said:

This is probable more than you wanted to know but it is a good read.

What does the COM Surrogate do and why does it always stop working? The Old New Thing

Jack

Thank you, I was just posting as this came through. I’ll have a read through on this

bro67 · 26 Dec 2017

I really would not worry about it, since it is nothing more than a scratch pad operation to keep the main process from crashing. It is to take the load off of what was already poorly written and band-aided by Microsoft. Unless Microsoft was to rewrite completely from Scratch, for all of the windows items they have kept around since Windows 95 days. Things are not going to change. 365 was another rushed out to market front end that sales did not want to wait on all of the code to be finished.