I guess people should stop caring what errors happen in Event Viewer.

Redbatman said:

With the DCOM errors and some other ones that happen just cause, it seems one can drive themselves crazy trying to "fix them"

Today I found out that if I sign out of my computer and sign back in I will get 20 or so of kernel-eventtracing event id 2 0xc0000035. However it seems to only happen once per boot and if I do it again I don't get them again. Needless to say I don't have any other people on my system so I don't need to this unless my system icons decided to go away so sign out to bring them back. Funny enough this started with April Update.

But yes It seems that I have reached the point that its just unnecessary to try to make Windows 10 perfect for me since Microsoft decides to do what they want with it. I mostly use my Windows 10 PC for games anyways.

Anyone else feel this way?

Event Viewer is a tool to be used when the need arises. If your PC isn't broken resist the urge to delve into Event Viewer unless you need another hobby. Just my 2 cents.

Some events matter and must be attended to (or worked around). Others are basically "noise" as in the Bible phrase "full of sound and fury, signifying nothing." I understand why some folks here on the forums and elsewhere feel compelled to clean such things up, but for me it's a matter of trading off time and effort against the reward or value obtained. The DCOM errors (and many others) require a fair amount of time and effort for little or no reward. That's why I don't mess with them myself. Good on you for coming to a similar conclusion!
--Ed--

Redbatman said:

I just find it baffling how each new windows overhaul update can bring about new errors like the one I talked about with event ID kernel tracing.

Just my opinion but Given the vast number of lines of code comprising Windows and the near infinite number of hardware configurations it runs on together with the many ways users try to break their systems, it is a miracle there are as few issues as their are. And remember we only see the problems here, there are a huge number of users who have few if any major issues.

For errors only two things count, what you see in reliability history:


And what you see when running perfmon /report

Everything else is probably just a time out, or something that got interrupted by a change in power status(on to sleep, hibernate, soft shutdown(shutdown with fast startup turned on), shutdown, or restart

I agree - so much superfluousness detracts from the intended use.. eg :

Code:

Provider "Environment" is Started. 

Details: 
    ProviderName=Environment
    NewProviderState=Started

    SequenceNumber=5

    HostName=Windows PowerShell ISE Host
    HostVersion=5.1.17134.48
    HostId=ef534b42-b44a-4c9b-97e4-e5e2c4163a32
    HostApplication=C:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell_ISE.exe
    EngineVersion=
    RunspaceId=
    PipelineId=
    CommandName=
    CommandType=
    ScriptName=
    CommandPath=
    CommandLine=

Who cares? it's like dism and cbs logs... full of useless doo-doo.