Cat5.3 & ati2mtag Event Viewer Overload!

[oj213]

Ever since installing Catalyst 5.3, a System erros keeps coming up in Event viewer. It always comes up 30-50 entries long. It happens several times a day since the install. So far it actually hasnt affected my system that i can tell but it still worries me that something serious could come up soon. Any help?

Event Type: Information
Event Source: ati2mtag
Event Category: DVD_OV
Event ID: 62486
Date: 3/28/2005
Time: 7:39:53 PM
User: N/A
Computer: GORILLA64
Description:
Invalid parameters
Data:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 3d 00 00 00 16 f4 00 40 =....ô.@
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

[takhimi]

Same here. Even with new Cat5.4 the problems still remains. I`m using the old CP driver.

[sandermvdb]

Me to. I don't know if it had anything to do with overclocking or not. Probably not because it is in the category DVD_OV. I am trying to find out what causes it.

[celloman]

I also get some ati2mtag errors with cat 5.4 (event viewer description: Unknown video decoder type).

[spyre]

I don't get any errors like that

Have you got the WMD drivers installed for your VIVO card?

And what other graphics cards are you people using?

[oj213]

I only have the x800 Pro Vivo. It started with the Cat 5.3's because it never happened before that. I always use driver cleaner for installing new drivers. It also doesnt seem to actually do anything negative that I have noticed but I wouldnt mind having it stop.

P.S Im using the non-catalyst control center driver 5.3 with WDM driver if that makes a difference.

[sandermvdb]

I have a X800 Pro (non Vivo) and have not installed the WDM drivers. The reason we get these messages with 5.3 and further is because ATI has enabled some sort of error logging in their drivers since 5.3.

[Zonk]

i have a connect3d x800 xt-pe and get error messages in the event viewer every minute using net framework 1.1 with all updates from ms for xp. i also lose my tray icon after some time without doing anything. WDM Drivers are installed

A64 3400+ (CnQ enabled)
Asus K8V Deluxe
SB Audigy2 ZS

[atlantis78]

A similar problem happens to me ("invalid pixel format" IIRC)
But it happens only when I play a video with "mplayer" (win32)

bba 9700 pro + xp sp2 + cat 5.4 ccc

edit:

Event Type:	Warning
Event Source:	ati2mtag
Event Category:	DVD_OV 
Event ID:	62470
Date:		15/04/2005
Time:		19.27.07
User:		N/A
Computer:	MONGOLO
Description:
Invalid pixel format
Data:
0000: 00 00 00 00 01 00 5a 00   ......Z.
0008: 3d 00 00 00 06 f4 00 80   =....ô.€
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

[hoak]

Dittos I get the ati2mtag spam in the eventlog too... Anyone gotta clue what's going on?

[TilRoquette]

We get the same problem here: warning event 62470 (ati2mtag, DVD_Ov), while playing videos. Warning is always coupled with an information event 62486 (ati2mteg, DVD_OV).

radeon x300, catalyst 3.?, xp sp2, no ATI WDM installed

Regards, Til

[HungryHom3r]

I'm running a PowerColor Radeon 9800 Pro 128MB, and I've got the same issue as well with ati2mtag giving an 'invalid pixel format', but it only shows up when loading certain games (GTAIII and Vice City for example). Odd how this only started happening with the newer drivers (v5.1 and up I think it was).

[Craig0]

Anybody know what's going on here?

I have the problem when playing back video using the Overlay Mixer renderer. No problems when using VMR 7/9

[oj213]

Originally Posted by Craig0

Anybody know what's going on here?

I have the problem when playing back video using the Overlay Mixer renderer. No problems when using VMR 7/9

I continue to get them and still have no idea why. It doesnt seem to harm anything or be attached to a problem. It still irks me a bit seeing all those errors there.

[Synetech]

Oh boy. I'm getting this too. I just noticed that my events directory (I keep it on a different drive) has exploded since my last major backup. I checked the event viewer and bam! I see tens of thousands of this message.

Information - DATE - TIME - ati2mtag - DVD_OV - EVENT - USER - COMPUTER

I have been getting these since Jun.28.05.


Now I have to find a way to delete these entries from the logs since they take up a ridiculous amount of space for nothing. Also, ATI needs to figure out what the problem is and fix it.

[spyre]

Apparently that error goes away if you use alternate pixel centre I belive.

[Synetech]

Originally Posted by spyre

Apparently that error goes away if you use alternate pixel centre I belive.

Allright, I'll give it a shot.

[bjf2000]

I'm inundated with these as well using the latest drivers, though I can't determine exactly what is triggering them.

Is the Alternate pixel center change a solution [Edit: No, it isn't; it has no effect on the problem.]? Isn't there something more concrete?

[rseiler]

Still present in 5.12. Does anyone else object to a projected 90% of your System log being consumed by non-information or is it just me?

Oh, this silly, stupid pastime of mine.

[Lugzan]

Hi


I noticed the ati2mtag overload some 6 months ago I guess and left it alone 'cause it didn't seem a critical error. After I resinstalled my windoze recently and looked into event viewer the error stood already there in enormous amounts =)

But I did not install the latest catalyst after fresh installation, so it must be a driver caused error, don't you think.

After all, I think of myself as an advanced user not to go through all that is suggested at http://forum.osnn.net/showthread.php?t=68545 - there has to be an easy solution, damn it! =)

My machine :
AMD Athlon 2500+ Barton @ ~2.100 GHz
1 GB Dual DDR
Abit NF7
Radeon 9800 Pro @ XT
supported by win2k SP4 etc.


J.

[drakkar]

This is also pi$$ing me off.
Make sure you let ATI support know if you want anything done about it.

[Synetech]

Hmmm... What happened to the post I made yesterday? (stupid Rage3D's new ISP ) Well here it is again...

This problem showed up earlier this year but went away around 5.8~5.10. It came back in 5.11 although I have not had it for 7 days. Yesterday I got a few standalone instances (not 1,000 in a row) as well as another 1,000-entry-run.

It's very annoying because it does not provide any useful information and drowns out other messages that may be useful. One entry is sufficient! On my system, every time it happens it spits out exactly 136 messages all at the same time!

What's worse is that I keep the logs on a different drive and have it set to keep the maximum amount. The log files have exploded to over 20MB because of this. ATI really needs to fix this immediately. I'll be sending them feedback about it and I suggest everyone else do so as well. If you are note registered, submit it using the Catalyst Crew Feedback Form, if you are registered submit a ticket AND with the feedback form.


On a related matter, does anyone know of a way to remove specific entries from the event log? I want to get rid of all but one-per-instance of the ATI entries and keep everything else. I've looked around but could not find anything that works.

[rseiler]

Synetech, I'm in the middle of a week-long ticket with ATI over this issue (via ATI's deathly slow https site, which is run on two 486's with 56K modems in a basement in Toronto), and I'll report back here with the results. So far, the best I've gotten out of them is that Event Viewer is able to do filtering. Sigh.

I will not back down though, since they haven't a leg to stand on with this issue. It's completely meaningless (even one entry is too many), useless, dangerous in the way it obscures other real information, and can only cost them by clogging their support with people like us.

That said, until they engineer it out of the driver or at least provide a workaround (like a Registry mod), then I too encourage everyone to speak up to them about it. It's the equivalent of spam, but without any chance of increasing one's sexual potency.

As for deleting events out of Event Viewer, I wish. I looked long ago and couldn't find anything, but there must be something out there that does it. I'm sure MS discourages such tools since it makes hiding your tracks easy.

[Auric]

Does every system suffering the DVD_OV error have ATI's MMC and/or DVD app installed?

Those are not installed on mine and it does not suffer that error but rather two others from ati2mtag:

Category: CPLIB
Event ID:52236
CPLIB :: General - Invalid Parameter

Category: SDTV
Event ID: 49166
MODE: Multimedia mode not supported for the standard

It seemed a fair guess that CPLIB was related to the Control Panel but after uninstalling it the error continues.

The SDTV error is certainly due to the incorrect TVO signal defect since CAT 5.3 discussed here: http://www.rage3d.com/board/showthread.php?t=33811464

[Synetech]

Auric, I have those two error messages as well but only one copy of them at a time. They are genuine messages which are useful. The DVD_OV error is indeed a DVD overlay related message and spits out 136 each time.

Thanks for pointing to the other thread, I'm also experiencing that problem too. Stupid ATI, why to they keep breaking things that were working? As a software developer myself, I can understand that sometimes you mess existing things up when expanding but come on, I'm one person in my house, they're a many-person team of "professionals" with all kinds of checks and balances. Hmmm... Microsoft?

[rseiler]

Auric, I do not have the DVD player or MMC installed; further, I've never seen the two errors you speak of.

It's interesting that you don't get the DVD_OV one though, which should be exceedingly easy to get even if you never touch a DVD drive. I get it merely for playing AVI's with Bsplayer! Do you play many media files?

Perhaps if we figure out why you DON'T get them we can emulate what you're doing.

[Auric]

I play media files of all kinds very frequently. As said in the other thread I use Overlay Theater Mode for TVO, VMR7 windowed output from MPC with a combo of filters and decoders from those integrated with MPC and fddshow as well as Cyberlink's, plus QT & Real Alternative.

No idea why the difference in errors but clearly ATI needs to shape up.

[rseiler]

The good folks at ATI have provided me what appears to be a workaround. I'm off to try it now and suggest others give it a whirl as well:

I have done alot of digging and have found a workaround so that only the ati2mtag events are not logged.

As this issue doesn't happen in my system, I had to use the "Service Control Manager" source as my test. When I did this, I no longer had these entries in the Event Log (I had hundreds, after the modification, no more were created).

In the registry, go to the following location:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\System

You will see a "REG_MULTI_SZ" entry on the right for Sources. Double click on this and find "ati2mtag" in the list, highlight and delete only this entry. Click OK.

Repeat for these registry locations:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Eventlog\System

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System

Note: Your system may vary. For example, mine didn't have a 'ControlSet002' branch but it did have a 'ControlSet003' -- change what's appropriate for what you have. Also, while 'ati2mtag' was present in the 'ControlSet001' and 'ControlSet003' branches for me, it wasn't in 'CurrentControlSet'.

[rseiler]

Unfortunately, it appears not to work.

Initially, I made the changes and without rebooting tested for the problem (running AVI files) -- the problem was still there. So I figured the changes don't take effect until reboot. After rebooting, I casually checked the Registry, and to my horror, found that 'ati2mag' returned in both places.

It's the monster that won't go away.

So while this attempt at a solution may be onto something, and may work for other events like "Service Control Manager," it doesn't work for this one.

The best solution of all would be to figure out why some people don't have this issue in the first place.

[Synetech]

The best solution is for ATI—who has the source code and knows exactly what is happening and why it does it (or at least should)—to edit their code to remove the bug that is causing it or at least make sure that only one entry per incident is written. At least for the time being, they should explain what the heck it means so that we can try to figure out for ourselves.