F5F Stay Refreshed Hardware Desktop Troubleshoot the Event Viewer error by checking logs and ensuring system updates are applied.

Troubleshoot the Event Viewer error by checking logs and ensuring system updates are applied.

Troubleshoot the Event Viewer error by checking logs and ensuring system updates are applied.

C
CaptianTimo
Member
Find
159
09-25-2023, 10:20 PM
#1
Looking into these issues, can anyone assist in identifying the underlying cause? These problems don't appear to impact the system directly but might be leading to unexpected behavior and delays. I'm currently focused only on errors, having fixed most of them. The critical ones involve forced shutdowns, which aren't major concerns yet. They seem linked to power-off events. Common sources include the ones listed below, shown in screenshots: Kernel-EventTracing IDs 2 & 28, DeviceSetupMAnager Event 131, DistributedCOM Event 10010. Attach more images if needed. Event 2 involves several items happening at different speeds—like NT Kernel Logger not starting, Cloud Files Diagnostic Event Listener, PerfDiag Logger, and a specific dc3a3596-71e1... failure. Event 28 shows two errors with the provider ID 77811378-e885-4ac2-a580-bc86e4f1bc93, plus another error code 0xC0000005 and 0xC0000001. Event 131 appears to be multiple codes for a metadata staging failure, and it mentions a server registration issue with DCOM. Someone with expertise would help clarify these.
Reply
Reply
C
CaptianTimo
09-25-2023, 10:20 PM #1

Looking into these issues, can anyone assist in identifying the underlying cause? These problems don't appear to impact the system directly but might be leading to unexpected behavior and delays. I'm currently focused only on errors, having fixed most of them. The critical ones involve forced shutdowns, which aren't major concerns yet. They seem linked to power-off events. Common sources include the ones listed below, shown in screenshots: Kernel-EventTracing IDs 2 & 28, DeviceSetupMAnager Event 131, DistributedCOM Event 10010. Attach more images if needed. Event 2 involves several items happening at different speeds—like NT Kernel Logger not starting, Cloud Files Diagnostic Event Listener, PerfDiag Logger, and a specific dc3a3596-71e1... failure. Event 28 shows two errors with the provider ID 77811378-e885-4ac2-a580-bc86e4f1bc93, plus another error code 0xC0000005 and 0xC0000001. Event 131 appears to be multiple codes for a metadata staging failure, and it mentions a server registration issue with DCOM. Someone with expertise would help clarify these.

Reply
Reply