At this point is there any way this could be a hardware issue? So far all the tests I've run have shown things coming back ok and working, but I'm wondering as most of the hardware is a few years old at least.
Multiple DistributedCOM errors, system freezing, etc
I've been trying for several months to solve a problem where my system would freeze up while working. Occasionally it would be while web browsing, other times playing games, but I can't find a real pattern.
When I check the event viewer after rebooting I often find errors similar to the following;
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 4/17/2018 6:26:38 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: DEEPTHOUGHT\samue
Computer: deepthought
Description:
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 DEEPTHOUGHT\samue SID (S-1-5-21-4100534078-2505195061-3857586593-1002) 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2018-04-17T22:26:38.249263700Z" />
<EventRecordID>1668</EventRecordID>
<Correlation />
<Execution ProcessID="776" ThreadID="3804" />
<Channel>System</Channel>
<Computer>deepthought</Computer>
<Security UserID="S-1-5-21-4100534078-2505195061-3857586593-1002" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>
<Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>
<Data Name="param6">DEEPTHOUGHT</Data>
<Data Name="param7">samue</Data>
<Data Name="param8">S-1-5-21-4100534078-2505195061-3857586593-1002</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
The CLSID and APPID occasionally are different than above (CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} is another example.
I've tried adjusting persmissions but still get errors. I eventually ran in to so many problems and crashes that I did a reformat and reinstall of Win10. It's ran fine for a few days but now is starting to freeze again.
I've run a memtest in the past but not overnight, just about an hour but no errors.
Any help is appreciated.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
13 answers
Sort by: Most helpful
-
Anonymous
2018-04-24T15:30:13+00:00 -
Anonymous
2018-04-23T13:14:26+00:00 I installed version 1703 clean and updated all drivers. I have Windows Update disabled in order to prevent updating past 1703 for now.
I still am getting freezes and crashes. Most recent DCOM error is as follows and led to BSOD:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 4/23/2018 9:02:05 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: deepthought
Description:
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\SYSTEM SID (S-1-5-18) 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2018-04-23T13:02:05.288836100Z" />
<EventRecordID>1407</EventRecordID>
<Correlation />
<Execution ProcessID="892" ThreadID="1404" />
<Channel>System</Channel>
<Computer>deepthought</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>
<Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
I also got fourwarnings that were similar to the following before freezing, in each case the text after "SWD\WPDBUSENUM" was different but it seemed to refer to similar issues.
In each case (crash/freeze) this happened when running a game on Steam.
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 4/23/2018 9:06:11 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: deepthought
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM{7236b002-45f6-11e8-a388-806e6f6e6963}#0000000000100000.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-04-23T13:06:11.142300200Z" />
<EventRecordID>1451</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="228" />
<Channel>System</Channel>
<Computer>deepthought</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">70</Data>
<Data Name="DriverName">SWD\WPDBUSENUM{7236b002-45f6-11e8-a388-806e6f6e6963}#0000000000100000</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WudfRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>
-
Anonymous
2018-04-19T22:55:17+00:00 Yes, it won't be officially released until the next 4 weeks.