Error: DistributedCOM Event ID: 10010, E10F6C3A-F1AE-4ADC-AA9D-2FE6552566

On 9-27-2011, Cat 11.10 Preview has finally fixed the Dcom error at shutdown.
On 9-28-2011, Cat 11.9 WHQL Release Notes indicates that the Dcom Errors are fixed.

​

Is anyone getting this error after install cat 11.4? I'm reading a few reports of this and wanted to know if anyone else noticed this? You can check this by opening up event viewer and looking at Administrative Events.

Update:
Problem is reproduced after a reboot or shutdown. Error appears to only show up during shutdown process. Using a driver earlier then 11.4 March 22/23 preview solves the problem. Cat 11.4 March 7 preview and Cat 11.3 don't exhibit that error. Disabling atiesrxx.exe (AMD External Events Utility) may stop the error from happening when shutting down. However, may cause other problems that effect 2D/3D clocks of your video card (or causes another event viewer error).

• 11.4 (Early) Preview - March 7th [8.84.3-110226a-114256E] *No DCOM error*
• 11.3 WHQL [8.831.2-110308a-115928C] *No DCOM error*
• 11.4 Preview - March 23rd (posted on March 29th) [8.84.2-110321a-115519E] *DCOM error*
• 11.4 WHQL [8.841-110405a-116954C] *DCOM error*
• 11.4 Hotfix -April 27th [8.84.9-110427a-118103E] *DCOM error*
• Cat Beta 8.85 released May 5, 2011 (8.85-110419a-116502C) *DCOM error
• 11.4c new hotfix dated May 4, 2011...waiting for release
• 11.5 released May 9, 2010 *DCOM error*
• 11.5a Hotfix released May 9, 2010 *DCOM error*
• 11.5b Hotfix released May 25, 2010 *DCOM error*
• Cat Beta 8.86 released June 3, 2011 *DCom error*
• 11.6 WHQL June 15, 2011 *DCOM error*
• 11.7 Early Build June 29, 2011 *DCOM error*
• 11.7 WHQL July 27, 2011 *DCOM error*
• 11.8 Preview July 27, 2011 *DCOM error*
• 11.8 WHQL, August 17, 2011 *DCOM error per GPUCoder
• 11.10 Preview September 26-27, 2011 *DCOM Fixed, Finally*
• 11.9 WHQL September 28, 2011 The release notes indicate that this drivers fixes the Dcom issues.

Thanks to k1net1cs for checking some of the drivers.

Edit:
A temporary solution is to go to services and select AMD External Event Utility stop the service and set it from automatic to manual. Then reboot the PC (not just to see if the Dcom error comes up or not but to start windows with the service disabled). Once done you should be able to play games and the 2D and 3D clocks should work as normal. CCC should also work as normal. Just keep in mind that you had the service disabled if you run into any problems when you install different drivers. This is by no means a fix nor is it a solution but a temporary change until AMD fixes the problem.


Edit #2:
After some searching around I found a few threads discussing the issue:
http://www.rage3d.com/board/showthread.php?t=33976892
http://social.technet.microsoft.com...l/thread/10e6ca24-8fe4-4b7f-82e7-154f0957935d
http://forums.amd.com/game/messageview.cfm?catid=279&threadid=150420
http://forums.guru3d.com/showpost.php?p=3967469&postcount=48
http://www.computerbase.de/forum/showthread.php?t=891838
http://forum.radeon.ru/viewtopic.php?p=750925
http://forums.amd.com/game/messageview.cfm?catid=354&threadid=119657
http://www.rage3d.com/board/showthread.php?t=33977542



New Update:
You can use atiesrxx.exe and atieclxx.exe files from Cat 11.4 Preview March 7 in place of the current build version (Cat 11.7 for example) to prevent the dcom error. However, this may cause other problems.
-Start it to decompress the files. Once you see the welcome screen exit. You are not doing an full install.
-Navigate to C:\AMD\AMD_Catalyst_11.4_Preview_Win7_March7\Packages\Drivers\Display\W7_INF or W76A_INF\B114386\. I think W7_INF is for 32bit but I'm not sure.
-Copy atiesrxx.ex_ and atieclxx.ex_
-Create a Temp Folder on your hard drive, example C:\temp
-Type CMD at Start's search box and start it with Admin rights
-Navigate to that folder, example: cd\temp
-Type: expand atiesrxx.ex_ atiesrxx.exe
-Type: expand atieclxx.ex_ atieclxx.exe
-Open Services and Disable AMD External Events Utility then stop the process
-Navigate to windows\System32\ and place atiesrxx and atieclxx in another folder (don't delete)
-Replace them with the same files from Cat 11.4 Preview from the Temp folder.
-Set AMD External Events Utility from Disabled to Automatic. Then start the service
-Reboot.
Once you do the dcom errors should stop. However, there maybe stability issues or other problems using the older atiesrxx and atieclxx. I don't know how stable those older files are on current Cat releases. If you experience issues just disable and stop the AMD External Event Utility and replace the files found in system32 with the originals. Then set the AMD External Events Utility to automatic and start. You do this at your own risk.

Edit Update:
If you use this method and want to uninstall your current cat drivers for a different version just switch the old files with the original ones 1st before uninstalling.

Edit Update:
After using this for a week or so I've experienced no ill effects in games, streaming, etc. Caution is still advised though.

Update:
After using this method for over a month I've not seen any ill effects. Gaming, watching videos, recoding movies, etc have all worked without issue.

New Update:
Cat 11.10 Preview has finally fixed the Dcom errors (at shutdown) that has been an issue for the past few months. If you are reading this post you no longer need to use the old Cat 11.4 Preview's atiesrxx and atieclxx files.

One More Update
OP updated to reflect the release of Cat 11.19 released 9-28-2011. The release notes reflect that the Dcom issue is fixed.

 

I have stopped it, by disabling the service: AMD External Events Utility.

 

That would be the atiesrxx.exe file?

Anyone else seeing this in the event viewer?

 

I have it.

 

Thanks for responding. Anyone else checked this yet?

 

http://technet.microsoft.com/en-us/library/dd337766(WS.10).aspx

Basically, AMD f*cks up something somewhere on 11.4 WHQL, and with a big possibility ever since the 'last' 11.4 Preview from April 15th; checked Event Viewer and the 'oldest' record of that error with the same server was April 16th.
If I have to come to a conclusion, I'm willing to bet it's what 'fixed' the 99% GPU bug, especially if the error is generated by the 'AMD External Events Utility' service.

Maybe someone on the driver team disabled a check from that monitoring service that was deemed the cause of the 99% GPU bug, but in turn generating those DCOM errors.
You might say it's a hackfix rather than a hotfix.

Whatever works, I guess.

 

Could you try something. Take note of the time you reboot and check the event log again to see if the Dcom error shows up at exactly the time you reboot?

 

Done that three times already, before I posted that reply.

 

Sorry, I'm not understanding you. Does that mean it's happening or not?

 

It means it's happening, as in I've checked it three times before I posted my 'findings'.
Also two times with that service disabled, with the same conclusion as Luke7's.

 

I've asked because all I wanted to know is if the problem surfaces most during a shutdown (when you reboot) or if it's happening sometime while at desktop.

 

Definitely at shutdown.
Probably caused by the service not terminating correctly?

Now I'm trying to figure out whether the error happens with all 11.4 ever since March 7th EP.
This one I'm trying on is my desktop, which I've only had access to from April 9th because I was out of town before that date, so I haven't had the chance to test earlier 11.4 EPs on this system.


[edit]
It's confirmed; the error occurred at shutdown.
I manually stopped the service and restarted; nothing at Event Viewer.

Gonna check the 1st 11.4 EP and 11.3 WHQL.

Temporary (personal) conclusion :
The error might not have detrimental effect(s) on a system, since it occurs only at shutdown a.k.a. negligible.
[/edit]

 

I will check again when I get back on that particular PC. I noticed earlier when I was on it that there were two that "may" have occured at the time of shutdown. I will have to check later to make sure though. I will also check to see if it happens after game play i.e. down clocks.

 

I have same problem as OP too, I don't know if I should disable service AMD External Events Utility or not.

Hope AMD will fix it next patch.:nerd:

 

Can you all collectively tweet CatalystCreator about this:
http://twitter.com/#!/catalystcreator

 

How about you tweet him to check this thread instead?
It's better than having to retweet him everything every time anyone finds something.

Anyway, just checked 11.4 EP March 7th; no DCOM error at shutdown.
Because of this I'm going to check the 11.4 EP (posted March 29th, but dated March 23rd; official AMD release) before the 'leaked' (April 5th) 11.4 WHQL.

 

I'm not sure if one tweet will get him to even look but whatever will see.

 

Well, maybe just suggest everyone to tweet him about this thread instead of the whole shebang, unless that was actually your intent from the start and I read it wrongly. =b

Anyway, 11.4 EP March 23 produced the DCOM error.
Keep in mind that that one has a packaging version of 8.84.2-110321a-115519E, while March 7th had 8.84.3-110226a-114256E, for whatever weird reason(s).
And IIRC, 11.3 WHQL had a different packaging version altogether; gotta check on 'em in a moment.

 

Alright, first of all, sorry for the double post.
This is simply because it's too much to add to just simply edit an existing one.

Anyway, here's what I've found so far.

• 11.4 (Early) Preview - March 7th [8.84.3-110226a-114256E] *No DCOM error*
• 11.3 WHQL [8.831.2-110308a-115928C] *No DCOM error*
• 11.4 Preview - March 23rd (posted on March 29th) [8.84.2-110321a-115519E] *DCOM error*
• 11.4 WHQL [8.841-110405a-116954C] *DCOM error*

It's sorted based on release date, not packaging date nor packaging version.
11.3 WHQL and 11.4 Preview (March 23rd) were released concurrently, btw.

And here's my 'standard operational procedure' for testing each drivers.

1. Express uninstall currently installed Catalyst.
2. Reboot to Safe Mode.
3. Uninstall 'Standard VGA Graphics Adapter' from Device Manager.
4. Run TwL's Genetix Cleaner 4.85.
5. Run Driver Sweeper 2.9.0.
6. Refresh Device Manager, let it install 'Standard VGA Graphics Adapter' again.
7. Reboot.
8. Install Catalyst, then reboot as prompted.
9. After a post-installation reboot, do a manual reboot.
10. Check Event Viewer.

The cleaning process might be overkill, but I'm not one to say that doing less than that provides an ideal/clean 'testing ground' for every Catalyst installation.
Besides, I'm not the one having BSODs like some people here have from 11.4 WHQL. =b

 

Thanks for the write up! And yeah, it was my intent to imply that everyone a write a short explanation and a reference to this thread when tweeting him.

So folks, if you are reading this thread and have that problem it's best that you speak up now.