Ati2Mtag error into event viewer

[Keithj]

I knew my machine had the ATI video card, so I had the correct drivers in the Catalyst 8-7-mobile set.

I don't know if there's a set of Catalyst drivers for the firegl 3200.   If there isn't, then that fix won't work - but then, would you have the same problem I did, which I think is only with the ATI display? 

[mcapasso]

Yes, this problem is related to Ati display and at the moment any fix I tried work.

But I don't understand why IBM/lenovo doesn't solve the problem that affect a lot of its machines

Maurizio

[Petert44]

I ended up after many months of searching and frustration reinstalling a previous version of the driver (Version: 8.163.1.1.1-060121a File Name: 1yd167ww). I don't know if it will work for you, but it got rid of the WARNING. However, I believe it has adversely affected my boot time. Lenovo will probably, one day, come out with a fix; like they did with scandisk. What kills me is that they don't even acknowledge the problem and you have waste hours searching for a solution, which does not exist.

[MadManBam]

---

Keithj wrote:

I had the same problem with my T43. Much Googling revealed a lot of suggestions that didn't fix it.

Then I found a German-language one that suggested downloading the Catalyst (not Lenovo or ATI) drivers.

I went to Computerbase.de and downloaded the Catalyst 8-7-mobile drivers, ran the install (a very large package) and all is fixed.

They seem to be ATI drivers, but they fixed it so no complaints!

Message Edited by Keithj on 08-10-2008 08:01 PM

----------------------------------------------------------------------------

Nice find! I went to the site and downloaded 8.11 drivers posted 11/13. My laptop boots up much quicker now and I'm not seeing the multiple ati2mtag errors in event viewer.

[Nightowl70]

 I realize this is an old thread with several possible fixes already listed.

 However, I have an older Thinkpad R52 notebook and none of the listed fixes worked for me. I got constant Event Log entries for Unknown EDID Version and my boot up would literally take about 5-6 minutes+ to get to the desktop after startup.

 After much research I did finally find a fix that solved my problem, though, so I wanted to revive this old thread and list it here in case anyone else is still having this issue.

 Simple fix. Go to Start, Run, type regedit to enter the registry. Then drill down to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Atierecord

 Make both entries listed under this key a value of 0 by double-clicking on them. Then restart.

 This fix was listed on another forum site as simply a means to stop the event log entries for this Ati related error and the Invalid CRT error that is also fairly common. However, when I did it, it also completely fixed the problem, not just stopped the message.