Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


AMD VISION Engine Control Center - CLR Error 8004005

  • Please log in to reply
1 reply to this topic

#1 Skyty


  • Members
  • 17 posts
  • Local time:04:21 AM

Posted 25 August 2013 - 05:01 PM

For the longest time I have been having issues with this software. Every time that I try and open it, it says:


"CLI.exe - Fatal Error


CLR error: 80004005

The Program with now terminate."


The same issue also happens with a file called MOM.exe which is also associated with AMD Vision as far as I know.


I've searched Google a few times but I haven't had much luck.


One said to re-install Microsoft .NET Framework, however that seemed to do very little.


Any suggestions?


I searched the forums, but I didn't see anything... maybe I used the wrong keywords. I'm not sure.


Any help would be greatly appreciated.


Thank you!

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,266 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:21 AM

Posted 25 August 2013 - 06:37 PM

What's the issue?


Exactly what are you trying to do?




Any video problems evident?


Cli.exe is apparently part of the CCC package...but you don't even need to use CCC to utilize ATI/AMD graphics features, IME.


The app refelcting the error...should be keyed on, IMO.  CCC would be my target and I would uninstall it, reinstall it.  Or uninstall/reinstall the whole video driver package.


I'd also try running the DirectX Troubleshooter, just for the heck of it.



Edited by hamluis, 25 August 2013 - 06:45 PM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users