Windows 10: System Shutdown after DCOM errors.

I have been experiencing some random system shutdowns. This is a fairly new system with about a year. I keep it always on 24/7 and it is heavily used, frequently reaching 100% on CPU and GPU intensive tasks. I frequently monitor system temps to check if everything is within admissible boundaries. The random system shutdowns have been a on-off problem. I have ran all possible system stress tests to check for memory, cpu or disk errors and they all have turned out ok. Every time the system shutdowns the only thing that event viewer reports is DCOM errors. I found others reporting this but no solution. The event viewer logs are here. Thanks.!


Best,

:)

 

DCOM error 10016 on shutdown

I had been getting the DCOM error 10016 on shutdown immediately followed by 4 SCM 7031 errors for quite some time until the MS August 10 updates were installed. I am still getting the SCM 7031 errors but the DCOM 10016 errors have stopped. Has anyone
else had this experience? I am running Win 10 Version 1511 on a desktop.

 

DCOM error 10016 on shutdown

Is this procedure supposed to resolve the DCOM 10016 errors or the Service Control Manager 7031 errors? The recent MS updates have apparently solved the DCOM 10016 errors I was getting for "Runtime Broker." Now they only happen for Cortana.

It is actually the SCM 7031 errors that I would like to eliminate now.

 

DCom persistent error


Remote proxy factory 32 class writes a Dcom Event Viewer error when EDGE, with multi-tabs, is closed...saying that it doesn't have activation permission for NJNxxx\My Account. It has.

In this HOME version, there are two registry entries for the RPF32 class. In each, Desktop-NJNxxx\Users; Desktop-NJNxxx\My Account; Desktop-NJNxxx\Administrators and SYSTEM have full control.

The same entries appear in DComcfg, along with Local Service, which has been given local launch permission for both RPF32class entries.

So, the permissions procedure has been followed, yet the error persists. Why?

(This box has HOME Win10. Another, with PRO, uses default Dcom settings and doesn't reference 'Desktop-NJNxxx. ' It instead lists the user name, and it never throws the Dcom error. That's likely not relevant - just a naming convention difference.)