ATI driver question...

[Cr00zng]

The video card in this system is ATI Radeon HD 5570 and the driver version is 8.8.21. It works just fine; however, the driver is spamming the event log with informational messages like these:



At this forum, this is how these logs explained, quote:

DVD_OV stands for DVD Overlay. OPM stands for Output Protection Mecanism. HFS stands for Hardware Function Scan. This log/error is the cards DVD screen overlay failing it's High-bandwidth Digital Content Protection (HDCP) check over DVI/HDMI.

Disabling AMD External Events Utility service does not get rid of these multiple events per second; however, the link suggested registry fix did.

And again, in my other system with the Asus P7P55 motherboard, with ATI Radeon HD 5850 video card, drive version 8.801.0, there are no event ID 62464 informational messages. I am not certain that the driver version would make that much difference.

The major difference between the two system is the OS. The machine with these event ID messages is Windows 7 64-bit with SP1, while the other is the same without the SP1. I vaguely can recall some discussion about SP1 adding High-bandwidth Digital Content Protection (HDCP), which can contribute to some of the issues I've experienced with this new PC. If the HDCP had been added, is there a way to remove it from the system? Well, short of starting fresh and don't add SP1.
Thanks in advance....

 

[dsperber]

Fascinating!

Just looked at my own system, which is Win7 x64 SP1 and has an HD4670 running with Catalyst 11.3 (and an old 4x3 19" IBM P92 CRT monitor connected using VGA), and it's producing the same nonsense in Event Viewer.

I looked at the other forum discussion on this same subject, and it would appear that the suggested Registry fix is apparently the only real way to stop this:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Atierecord]
"eRecordEnable"=dword:00000000

To me (who doesn't know anything about this logging for general use and other situations, much less why AMD is doing this) it does seem that disabling logging universally for ATI (which is what I think this change does) seems a bit extreme. Would seem to be forcing the loss of information for other situations that might be useful.

But I may just be overreacting here. Personally I have NEVER even looked into this particular set of Event Viewer information for anything... and doubt that I ever will again! And it does seem to be only for ATIeRecord... so I'm sure it's fine.

Anyway, it does seem wrong what is happening right now, and the other forum members seem to be pretty knowledgeable. So I will apply that fix on BOTH of my systems (including my other system, also Win7 x64 SP1 with an HD4850 in it and also Catalyst 11.3, with two-monitors 24" 16x9 LCD and 21" 4x3 CRT on extended desktop, both connected with DVI) and what I'm guessing is ALSO logging like crazy).

 

[spinifex]

Though i don't have any ATI graphics cards, reading the OP's post made me quite curious.
After spending time reading nigh everything posted about the problem, I could not find a fix.
All there appears to be, are the 4 registry fixes, which must really be annoying.

Sorry i can't be of more help.

 

[dsperber]

All there appears to be, are the 4 registry fixes

Only the one fix, to "current control set", seems to be needed to get the job done.

I only made that one fix and the logging disappeared.

 

[Mike Connor]

You might find this of interest;

Delete all event logs at once in Windows 7 - CNET Windows 7 Forums

The best solution is buried in the comments somewhere, you don't need a huge batch file;

At a command prompt, type ( Or paste!);

for /f %x in ('wevtutil el') do wevtutil cl "%x"

The only way I have found to clear all the logs at once without saving.

Curious is that the AMDinformational stuff still keeps going even if you try to disable it;







I didn't know about the registry tweak, I will try it and see what happens. I do wish the system would not generate so much rubbish, or at least give you the chance to clean it properly. I can't remember the last time I even bothered looking at these logs for any sensible reason. They may be useful to an extent in a corporate environment, but on the usual standalone PC they are about as much use as a chocolate fireguard.

Regards....Mike Connor

 

[Mike Connor]

PS. Was looking around and found this here on the forums;

http://www.sevenforums.com/tutorials/25480-event-viewer-one-click-clear.html

Works perfectly.

Regards....Mike Connor

 

[Cr00zng]

I've looked at the logs for two reasons....

The ATI logs are recorded on the "C" drive, which in my case an SSD drive; at least until they were they've been moved to a platter based drive. Having the ATI driver writing these useless, same non-descriptive six entries per seconds is spamming. Not to mention its impact on performance in general and the life of the SSD drive.

The other is the HDCP component that the log entry refers to. Why are these logs showing up on Windows 7 Professional SP1, but not on the system without the SP1? I understand that the High Definition Content Protection is a "must" nowadays; however, it should not negatively impact system performance. Nor should it continuously keep verifying that the content protection is operational for the DVD, much less logging it all the time.

 

[Mike Connor]

I've looked at the logs for two reasons....

The ATI logs are recorded on the "C" drive, which in my case an SSD drive; at least until they were they've been moved to a platter based drive. Having the ATI driver writing these useless, same non-descriptive six entries per seconds is spamming. Not to mention its impact on performance in general and the life of the SSD drive.

The other is the HDCP component that the log entry refers to. Why are these logs showing up on Windows 7 Professional SP1, but not on the system without the SP1? I understand that the High Definition Content Protection is a "must" nowadays; however, it should not negatively impact system performance. Nor should it continuously keep verifying that the content protection is operational for the DVD, much less logging it all the time.

Indeed, the reasons for some of these things are dubious at best, but in a lot of cases there is absolutely nothing one can do about them. ( Except have a really good moan now and then! ).

Regards....Mike Connor

 

[dsperber]

Turns out modifying only the "CurrentControlSet" registry entry was NOT sufficient to stop this stuff.

Searching on the AMD Forum, it seems you really do need to modify ALL of those ControlSet versions of ATIerecord (not minding if you don't have all of them, like ControlSet003).

Furthermore, there are additional entries for ATIerecord that need to be set to 0, so you need to do a "find" and "find next" repeatedly, and set each one you find to 0.

=========================================

For Windows 7 Click Start then type regedit
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atierecord]


Right click on eRecordEnable and modify the value to 0 for all of these, don't worry if you don't have the same amount of keys.

After looking more there's more ATIeRecord entries than these, so you might want to use the search function, Edit at the top of regedit, then Find - type in atierecord (dont forget the e in the middle of ati and record). Then hit F3 to "Find Next" and keep doing that until you find every atierecord key and set it the value to 0.

===================================

This seems to have finally turned off the event logging for me.

 

[Cr00zng]

We can agree to disagree about the nature of the reasons...

The fact is that the High Definition Content Protection negatively impacts the performance of the system and in extreme case, it can results crashing some of the systems.

The problem is that the there isn't much information available for the HDCP, both MS and AMD are tight lipped about this service and as such, people look for hardware and/or software failure for systems that have issues. They may spend countless hours for testing the memory, reinstalling their system, running torture test, etc., just to learn that HDCP is the cause of the issue.

I guess that's how MPAA and others prefer to "control" computers; as little information as possible...

 

[Mike Connor]

This seems to have finally turned off the event logging for me.

Thanks, will have a good work through that.

Regards....Mike Connor

 

[Mike Connor]

We can agree to disagree about the nature of the reasons...


I guess that's how MPAA and others prefer to "control" computers; as little information as possible...

Indeed, it's much the same as hiding recording devices on sound cards etc.

They are banking on the vast majority of people not being able to use them. This of course makes things very much more difficult for legitimate users, and doesn't stop the pirates anyway.

The entertainment industry as a whole has tried to ignore and suppress these things, and they have been buried under an avalanche as a result. They are still attempting to fight rearguard actions all over the place. Terrified as they are of losing yet more revenue.

They would have been better advised to find ways and means of distributing their material sensibly on the web.

Just how it is...........

You know what will happen if anybody ever discovers the secret of eternal youth? ( Or even a reasonable facsimile thereof ). The insurance companies will fight them to the death!

Regards....Mike Connor

 

[Cr00zng]

Well, a little grunt doesn't hurt every once in awhile and please don't get me started on the insurance companies

The issue with the log had been resolved when this thread was started; I was hoping that someone has some insight into the inner working of the HDCP with ATI/MS drivers. It seems that this forum may not be the appropriate one to look into this.

On the bright side....

There's this registry key as well, related to AMD/ATI:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag]

That's probably where some of the events that generate these logs is controlled. The sort of funny entry is:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag\MosquitoNoiseRemoval_NA]

It's currently set to "0"; do you think if I set it to "1", then I won't hear the mosquitoes this summer?

 

[Phone Man]

Well, a little grunt doesn't hurt every once in awhile and please don't get me started on the insurance companies

The issue with the log had been resolved when this thread was started; I was hoping that someone has some insight into the inner working of the HDCP with ATI/MS drivers. It seems that this forum may not be the appropriate one to look into this.

On the bright side....

There's this registry key as well, related to AMD/ATI:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag]

That's probably where some of the events that generate these logs is controlled. The sort of funny entry is:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag\MosquitoNoiseRemoval_NA]

It's currently set to "0"; do you think if I set it to "1", then I won't hear the mosquitoes this summer?

You won't here them coming but it won't stop them from biting.

Jim

 

[Cr00zng]

You won't here them coming but it won't stop them from biting.

Jim

See, I knew this was crapware; why would you need a feature that does more harm than good?

 

[Phone Man]

Turns out modifying only the "CurrentControlSet" registry entry was NOT sufficient to stop this stuff.

Searching on the AMD Forum, it seems you really do need to modify ALL of those ControlSet versions of ATIerecord (not minding if you don't have all of them, like ControlSet003).

Furthermore, there are additional entries for ATIerecord that need to be set to 0, so you need to do a "find" and "find next" repeatedly, and set each one you find to 0.

=========================================

For Windows 7 Click Start then type regedit
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atierecord]


Right click on eRecordEnable and modify the value to 0 for all of these, don't worry if you don't have the same amount of keys.

After looking more there's more ATIeRecord entries than these, so you might want to use the search function, Edit at the top of regedit, then Find - type in atierecord (dont forget the e in the middle of ati and record). Then hit F3 to "Find Next" and keep doing that until you find every atierecord key and set it the value to 0.

===================================

This seems to have finally turned off the event logging for me.

I changed just the Current Control Set but had to restart for the log to stop.

Jim