Maximum PC

This log is basically full of Info error logs about amd and the weird part is over the course of a minute there are about 30 of them, for example:

0000000001: 2012-02-23 21:08:27:416 Failed to merge manifest file: C:\Program Files (x86)\ATI Technologies\ATI.ACE\MOM-InstallProxy\mom-installproxy.xml with exception: Could not find file 'C:\Program Files (x86)\ATI Technologies\ATI.ACE\MOM-InstallProxy\mom-installproxy.xml'.
Error Called by: ATI.ACE.CLI.Foundation.XManifestation::ReadManifest processID:02436 threadID:( ) domainName:(CCC.exe ) assemblyName:(CLI.Foundation.XManifest, Version=3.5.4356.39860, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------



0000000002: 2012-02-23 21:08:27:588 Exception <Cannot get CCC NET Version>: Object reference not set to an instance of an object.
Exception Called by: ATI.ACE.CLI.Component.Runtime.Runtime::.ctor processID:02436 threadID:( ) domainName:(CCC.exe ) assemblyName:(CLI.Component.Runtime, Version=3.5.4356.39827, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

It goes up to 95- I wonder if everyone with win 7 64 bit gets such errors as a norm, or have I misconfigured some thing?

0000000095: 2012-02-24 02:21:21:567 Exception <WndProc - Source handler>: Object reference not set to an instance of an object.
Exception Called by: System.Windows.Forms.Control+ControlNativeWindow::WndProc processID:02436 threadID:(HotKeyForm ) domainName:(CCC.exe ) assemblyName:(System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
************************************************************************************************************************


No wait goes to a higher number, in sequence
0000000158: 2012-02-23 06:51:07:207 Exception <WndProc - Source handler>: Object reference not

As far as I know the driver is current (12.1) for my card.
Perhaps someone has a way to fix whatever makes windows create these "errors".