PC Freezing for short periods -> DistributedCOM Error?

I am having fairly frequent PC freezes (I'm on 1803). It will freeze everything for maybe 15 seconds.

I checked my event viewer, and found this:



The details say this:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The searches I've done on this bring up symptoms different from mine, so not sure I should follow them.

Anyone have any suggestions?

I am no expert on Windows events, but Event 10016 is not worth bothering too much about. However, I see that you have both WHEA-logger Event error 17 and Kernel Processor Power event error 37 which may be the most likely culprits. If you Google for those events, you may be able to track down and mitigate their effects on your System. For example, and this may or may not apply to you, if you are overclocking your system, you can try and bring down the overclock to a lower level until you don't get any freezes. As I said, search for these two events and see if anything applies to your hardware setup.

Thanks for the input.

I don't overclock...but I will check out your suggestions.

Unlikley to be the common 10016 'errors' - just ignore them.

I would do a sfc / scannow scan and run chkdsk. Also check your main drivers are up date - GPU, sound, ethernet/wifi, mainbord drivers etc.

Hi,
The only way it might matter is 10 will still send these error reports to the home nest constantly.

I have yet to resolve the problem. I've been checking the event log right after a freeze, and am not finding any errors showing up tha are at the same time. So I'm going to start watching warnings.

Here's one that I wonder about.

Check your Reliability History for red flags and if any,then view the Tech details for a possible culprit.Temporary freezes are often a graphic card problem and are caused by timeout delays,TDR.
If the freeze re-occurs,use win +ctrl+shift+b keys to reset the graphics drivers,which might help,or not.

One pcie device reporting error. U must reseat it, or rma it if it broken.
Whea is hardware error ( except from one case haswell cpu with microcode 23)

I am beginning to think Chrome is causing the problem. I have never had it freeze when using Edge. Of course it could be conincidental, but I've been using Edge a lot more, and no freezes.


Only thing is, I find no current mentions of Chrome freezing in a Google search.

I hate to move away from Chrome, but may have to. At least until I find it is freezing when Chrome is not loaded.