Event Error 10010

In my case I think I've found the stimulus that causes the error, and I appear to have stopped it from happening...

In the Task Scheduler, once you expand Task Scheduler Library > Microsoft > Windows, scroll down and click on SkyDrive, you find two scheduled jobs, "Idle Sync Maintenance Task" and "Routine Maintenance Task".  I found that disabling both of these jobs has caused the error message to cease.

I don't think disabling these jobs will be a good solution for everyone, since there may be useful things that these jobs [are supposed to] do, but for me, since I have no interest in SkyDrive, disabling them is fine.

I hope this helps someone.

-Noel

Hi Ronnie

thanks for the quick response, I didn't have those errors in Windows 8.0 and Windows 8.1  was a clean install to a New SSD.

I have been looking for a cure for this for several weeks in that time period that's all I seen was DCOM error 10010 {1B1F472E-3221-4826-97DB-2C2324D389AE} and {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} in windows 8.1, I'm not just talking for myself  but also for the others that are having the same issue, You said the errors are meaningless for the end user and only for the software developers, I trust what your saying but intact Event Viewer is saying something is wrong, cant Microsoft get a fix for this ?  

Were the errors caused by Windows Defender ? 

Ronnie I'm not trying to be a pain or put you in a bind  I'm a 71 year old,  my father told me if you don't ask questions you wont learn !

Thanks

Hi

These Event errors about timing issues are meaningless for the computer end user.

They are only useful for the software developer when optimizing the software programs they are developing.

These timing issues are measured in Milliseconds (1 / 1,000) of a second). Most timing issues can not be detected unless you are using a developer tool to measue them.

You can safely ignore these errors.

Regards

Hi

Sometimes the way the Event Viewer works can be incomprehensible to someone looking at it for the first time.

You did mention that "There seems to be no operational problem other then the Errors showing up in the Event Viewer".

This was the reason why I mentioned that these timing errors are usually noted in Milliseconds. This time period is usually so short that the end user will not even notice any effects in the software.

The Event Viewer is designed to report these events as errors, even though the event may not create any error messages or noticeable effects in the UI.

The errors may be created when Windows Defender runs, but the exact cause would require running special developer testing tools to pinpoint the exact problem. It could be anything, such as another software program or driver that may be using a large amount of resources.

This is why I recommended that this error can be safely ignored.

I also recommend that you spend some time looking through the Event Viewer and note the errors that you find. You will probably be surprised to find thousands of these errors in a typical system.

Regards

Hey Ronnie,

No disrespect intended, but your answer is insufficient.  People should NOT be advised to just ignore errors!

There are those of us who would prefer our event logs to be clear of all errors, which would indicate the system is running entirely properly.  It has been possible to accomplish this in the past!

There's some evidence that the error message "

The server {

BF6C1E47-86EC-4194-9CE5-13C15DCB2001

} did not register with DCOM within the required timeout." is related to SkyDrive (specifically, "Automatic Maintenance task to enable SkyDrive file sync to make progress while in Connected Standby")

On the system on which I see this message I don't use nor want SkyDrive support.  It is set up with a local account.  The above message implies some part of the SkyDrive software is still trying to run.

What do I have to disable to stop these events from happening once a day?

-Noel