Forum Discussion
Windows 10 Workstation Errors
I'm working on a small on-premise Windows network. One Windows 2019 server (DSDC), one Windows 2007 Server (DC), five Windows 10 Pc's. All servers and workstation have Windows updates installed. None of the devices have been hit with viruses.
One of the Windows 10 Pro PCs just started rebooting intermittently. I checked the power supply but couldn't detect any issues. The event viewer systems log does not have any power-related events.
The event viewer/system log shows the errors below have been occurring every day for months. Today, I ran the following processes but didn't find any errors:
SFC /Scannow
Chkdsk /f
DISM /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
Cleared temp files
Installed Samsung Magician to check for SSD health
Checked Battery Backup
Checked the case. It wasn't too dusty
Verified all four case fans were running
This same process has been performed before but the errors still occur.
Does anyone have a suggestion on how to resolve the issue?
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 3/18/2024 3:30:20 PM
Event ID: 10036
Task Category: None
Level: Error
Keywords: Classic
User: @@@@@\SBSMonAcct
Computer: FrontDeskII.@@@@@.com
Description:
The server-side authentication level policy does not allow the user @@@@@\SBSMonAcct SID (S-1-5-21-199190291-2147114010-2302728672-2653) from address 172.16.20.54 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
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">10036</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2024-03-18T20:30:20.5741820Z" />
<EventRecordID>211950</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="17696" />
<Channel>System</Channel>
<Computer>FrontDeskII.@@@@@.com</Computer>
<Security UserID="S-1-5-21-199190291-2147114010-2302728672-2653" />
</System>
<EventData>
<Data Name="Domain Name">@@@@@</Data>
<Data Name="User Name">SBSMonAcct</Data>
<Data Name="SID">S-1-5-21-199190291-2147114010-2302728672-2653</Data>
<Data Name="Client IP Address">172.16.20.54</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 3/18/2024 3:30:20 PM
Event ID: 10036
Task Category: None
Level: Error
Keywords: Classic
User: @@@@@\SBSMonAcct
Computer: FrontDeskII.@@@@@.com
Description:
The server-side authentication level policy does not allow the user @@@@@\SBSMonAcct SID (S-1-5-21-199190291-2147114010-2302728672-2653) from address 172.16.20.54 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
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">10036</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2024-03-18T20:30:20.4960495Z" />
<EventRecordID>211949</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="17696" />
<Channel>System</Channel>
<Computer>FrontDeskII.@@@@@.com</Computer>
<Security UserID="S-1-5-21-199190291-2147114010-2302728672-2653" />
</System>
<EventData>
<Data Name="Domain Name">@@@@@</Data>
<Data Name="User Name">SBSMonAcct</Data>
<Data Name="SID">S-1-5-21-199190291-2147114010-2302728672-2653</Data>
<Data Name="Client IP Address">172.16.20.54</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 3/18/2024 3:30:20 PM
Event ID: 10036
Task Category: None
Level: Error
Keywords: Classic
User: @@@@@\SBSMonAcct
Computer: FrontDeskII.@@@@@.com
Description:
The server-side authentication level policy does not allow the user @@@@@\SBSMonAcct SID (S-1-5-21-199190291-2147114010-2302728672-2653) from address 172.16.20.54 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
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">10036</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2024-03-18T20:30:20.4179427Z" />
<EventRecordID>211948</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="17696" />
<Channel>System</Channel>
<Computer>FrontDeskII.@@@@@.com</Computer>
<Security UserID="S-1-5-21-199190291-2147114010-2302728672-2653" />
</System>
<EventData>
<Data Name="Domain Name">@@@@@</Data>
<Data Name="User Name">SBSMonAcct</Data>
<Data Name="SID">S-1-5-21-199190291-2147114010-2302728672-2653</Data>
<Data Name="Client IP Address">172.16.20.54</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 3/18/2024 3:30:20 PM
Event ID: 10036
Task Category: None
Level: Error
Keywords: Classic
User: @@@@@\SBSMonAcct
Computer: FrontDeskII.@@@@@.com
Description:
The server-side authentication level policy does not allow the user @@@@@\SBSMonAcct SID (S-1-5-21-199190291-2147114010-2302728672-2653) from address 172.16.20.54 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
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">10036</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2024-03-18T20:30:20.3710529Z" />
<EventRecordID>211947</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="9736" />
<Channel>System</Channel>
<Computer>FrontDeskII.@@@@@.com</Computer>
<Security UserID="S-1-5-21-199190291-2147114010-2302728672-2653" />
</System>
<EventData>
<Data Name="Domain Name">@@@@@</Data>
<Data Name="User Name">SBSMonAcct</Data>
<Data Name="SID">S-1-5-21-199190291-2147114010-2302728672-2653</Data>
<Data Name="Client IP Address">172.16.20.54</Data>
</EventData>
</Event>
- 1. Update Device Drivers: Ensure that all device drivers on the Windows 10 Pro PC are up-to-date. Outdated or incompatible drivers can cause system instability and unexpected reboots. You can manually update drivers through Device Manager or use third-party driver update software.
2. Check for Hardware Issues: Although you've checked the power supply and fans, it's worth performing a thorough hardware inspection. Check for any signs of physical damage or loose connections inside the PC, including RAM modules, expansion cards, and cables.
3. Monitor System Temperature: Use software tools to monitor the temperature of critical components such as the CPU and GPU. Overheating can lead to system instability and spontaneous reboots. Ensure that the cooling system is functioning properly and consider cleaning any dust buildup from heat sinks and fans. - EricStarker
Community Manager
Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Windows 10 space - please post Windows 10 questions here in the future.
