ati2mtag gives blue screens

[MoP]

I have installed the latest Omega drivers, and keep getting this BSOD with
the following data:

Event Type: Error
Event Source: ati2mtag
Event Category: DAL
Event ID: 43015
Description:
I2c return failed

I had similar experiences with previous driver versions as well. Any idea
what could be causing this?

 

[Henry Bemis]

I never figured it out. I tried Omega and Catalyst from the ATI site.

I had to remove the version that caused it, wipe all ATI stuff off my system,
then go backwards one version number at a time until I hit one that was semi
stable and didn't crash to the BSOD. It took over 6 hours and five steps ONE
BSOD AT A TIME. Wasted my day off and turned my hair grey(er). Even now the TV
function sucks so bad it's useless.

I can't understand why ATI can't get thier collective sh*t together and give us
a decent driver package that can identify the card in use and install the
correct files and drivers needed to function properly. Nothing in my system has
changed EXCEPT the drivers and files from the website. Everybody keeps telling
me it's operator error, I'm doing something wrong. If that's true why the H*LL
did it work fine before the Catalyst Crap Center hit the scene? I suspect
something is being left behind by the ATI's cleaner and DC3, but what I don't
know what. I've tried a complete reinstall with the original CD that came with
it and that no longer operates as described. The ATI CD that is supposed to
validate the DVD functionality is no longer accepted during the install. I moved
to the ATI AIW at retail expense due to the sales hoopla about how great it is.
I personally think they screw up the drivers/files so you will be coerced into a
newer version of thier card.

Hey ATI, it didn't work.....I'm moving on.

 

[First of One]

No conclusive answer, but I've seen "I2C" mentioned in two places:

1. According to http://en.wikipedia.org/wiki/HD15 the I2C protocol is used
for communication between the monitor and video card. Thus, reinstall your
monitor driver or INF file and see if it makes a difference.

2. When I install the regular version of ATi Tray Tools on top of stock ATi
drivers, there is an option for "old style I2C access". Find that option in
ATi Tray Tools and toggle whatever the current setting is.

3. Uncheck "VPU recover" in ATi Tray Tools.

Do you get the same problem with non-Omega drivers?

 

[MoP]

No conclusive answer, but I've seen "I2C" mentioned in two places:

1. According to http://en.wikipedia.org/wiki/HD15 the I2C protocol is
used for communication between the monitor and video card. Thus,
reinstall your monitor driver or INF file and see if it makes a
difference.

2. When I install the regular version of ATi Tray Tools on top of
stock ATi drivers, there is an option for "old style I2C access". Find
that option in ATi Tray Tools and toggle whatever the current setting
is.

3. Uncheck "VPU recover" in ATi Tray Tools.

Do you get the same problem with non-Omega drivers?

I haven't tried the non-Omega drivers for ages, as they used to give me
lots of headaches.

I have installed the LG LCD flat panel drivers, but still the same
situation. I googled for this problem, and noticed lots of people had the
same with the 7.1 drivers (and the latest Omega ones that are based on
7.1), so I switched to an older Omega version.

The result is the same, with the difference that I don't get a detailed
report on Event Viewer.

I tried to uncheck the alternative DVI function at no avail.

Now I unchecked the VPU recover and see what happens. If the problem still
persists, I think I will switch to nvidia.

 

[MoP]

I haven't tried the non-Omega drivers for ages, as they used to give
me lots of headaches.

I have installed the LG LCD flat panel drivers, but still the same
situation. I googled for this problem, and noticed lots of people had
the same with the 7.1 drivers (and the latest Omega ones that are
based on 7.1), so I switched to an older Omega version.

The result is the same, with the difference that I don't get a
detailed report on Event Viewer.

I tried to uncheck the alternative DVI function at no avail.

Now I unchecked the VPU recover and see what happens. If the problem
still persists, I think I will switch to nvidia.

Looks like the problem insists, and is mainly caused by using overlay
applications like the tv tuner or videos.

I think I will change to some nvidia card, I have this 9200 for >3 years
and got tired of driver problems.

 

[Henry Bemis]

Let us know how you make out. I'm going to try a Hauppage. Which Nvidia has TV?

 

[MoP]

Looks like the problem insists, and is mainly caused by using overlay
applications like the tv tuner or videos.

I think I will change to some nvidia card, I have this 9200 for >3 years
and got tired of driver problems.

While searching for a replacement (which I will buy next week), a thought
occured to me. Maybe all the problems that are being reported about driver
problems are actually caused by faulty graphics card memory chips or
overclocked (by the manufacturer) components?