My last three computers were AMD and an ATI Radeon video card, two MBs were
ASUS and one MB was Gigabyte.

The event log has an ACE category and there are always errors in it.
Everything seems to work correctly 99.99999% of the time but has anyone ever
figured out why ATI video cards generate so many errors?

Searching the INET does not reveal anything useful.

Thanks.

--g

Hello,

Been there, done that. Latest everything including the latest CCC which
reveals the correct version for my card.

An INET search revealed the following:

Reinstall windows
power supply
old or wrong video drivers
Windows (and its associated products like dot net, etc.) are not updated
Overclocking
Overheating
Hardware on card failing (which the people RMA'd, got a new one, same
issues)

The answers were, none of it helped. Some had more severe problems like
BSODs. My situation is not like that but my event log has loads of ACE
errors.

Curious if anyone has ever been able to fix that. Also, if anyone has a
consistently empty ACE log, what MB, video card, and OS are they using?

Thanks.

--g

"geoff" <(E-Mail Removed)> wrote in message
news:hfXUl.45863$(E-Mail Removed)...
> The answers were, none of it helped. Some had more severe problems like
> BSODs. My situation is not like that but my event log has loads of ACE
> errors.
>
> Curious if anyone has ever been able to fix that. Also, if anyone has a
> consistently empty ACE log, what MB, video card, and OS are they using?
>
> Thanks.
>
> --g
>
>

You mean the ACEEventLog? I have lots of stuff in it but they're just
Information events, not errors. Probably just routine logging. It might have
something to do with the .NET framework that CCC is built on. If you
actually have "Error" events, that would be concerning but if it doesn't
affect your operation of the card, you can probably ignore it. If they are
in fact errors, what kind of messages do the events contain?

My system started out as an Abit nForce 2 board and MSI Radeon 9800 Pro
running Windows 2000. I later upgraded it to an MSI 790FX board with an MSI
Radeon 4670 running XP.

Hello,

Yes, the ACEEventLog. My entries are all listed as information as well but
here is the text from one of them:

=======================================
0000000012: 2009-06-01 16:07:07:546 Exception: Cannot access a disposed
object.--Object name: 'DashboardForm'.

Exception Called by:
ATI.ACE.CLI.Component.Runtime.Shared.Private.BaseRuntime::myEndInvoke
processID:02244 threadID ) domainNameccc.exe )
assemblyNameCLI.Component.Runtime.Shared.Private, Version=2.0.3403.16840,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
========================================

.. . . that certainly seems like an error to me. Most of the 'information'
entries are like that, some kind of exception being thrown.

--g

On Jun 1, 4:29 pm, "geoff" <nos...@nospam.com> wrote:
> My last three computers were AMD and an ATI Radeon video card, two MBs were
> ASUS and one MB was Gigabyte.
>
> The event log has an ACE category and there are always errors in it.
> Everything seems to work correctly 99.99999% of the time but has anyone ever
> figured out why ATI video cards generate so many errors?
>
> Searching the INET does not reveal anything useful.
>
> Thanks.
>
> --g

Running various PCI Radeon 8500 and 9xxx series some vendor's selling
this week on Fatwallet for $5, the latter. Mine are OEM Sapphires,
tho. Ran fine then, and switched to a universal driver set from OMEGA
when I adapted to desktop HDTVs for the native resolution. Still run
fine. Canadian, but seems eventually AMD picked them up not that long
ago.

"geoff" <(E-Mail Removed)> wrote in message
news:8%2Vl.44538$(E-Mail Removed)...
> Hello,
>
> Yes, the ACEEventLog. My entries are all listed as information as well
> but
> here is the text from one of them:
>
> =======================================
> 0000000012: 2009-06-01 16:07:07:546 Exception: Cannot access a disposed
> object.--Object name: 'DashboardForm'.
>
> Exception Called by:
> ATI.ACE.CLI.Component.Runtime.Shared.Private.BaseRuntime::myEndInvoke
> processID:02244 threadID ) domainNameccc.exe )
> assemblyNameCLI.Component.Runtime.Shared.Private,
> Version=2.0.3403.16840,
> Culture=neutral, PublicKeyToken=90ba9c70f846762e)
> ========================================
>
> . . . that certainly seems like an error to me. Most of the 'information'
> entries are like that, some kind of exception being thrown.
>
> --g

That's the sort of message I get also. Exceptions aren't necessarily errors
though. They could simply be debug logging, or benign alerts. If your video
card works as expected, you probably don't need to pay any attention to
this.

On Tue, 02 Jun 2009 01:44:30 -0400, geoff wrote:


0000000012: 2009-06-01 16:07:07:546 Exception: Cannot access a disposed
object.--Object name: 'DashboardForm'.


That exception was thrown from .NET and it has nothing to do with the
video card driver.

The exception itself happened because some code in something called
'CCC.exe' (I guess it is a control panel type form) attempted to access
an object which had already been disposed of from memory. That kind of
exception probably occurred when shutting the machine down.

Anyway, it has nothing to do with hardware, video drivers, overheating
etc. Pure and simple it is just bad programming of the CCC.exe utility
(which you don't need to use anyway).