suddently, can't enable 2nd monitor

Hey guys, Since I got my computer I've been using dual monitors then all of
a sudden today when I booted up, my pc crashed during login so I had to
manually power it off and turn it on again. Well this time when I logged in
my 2nd monitor wasn't enabled. So I went to display properties to try and
extend the desktop to monitor 2 but when I click apply the icons on my
desktop flicker for a second and then the box is unchecked again and my 2nd
monitor is still dark.

The last thing I installed was FireFox 3 but that was a little while ago and
I have booted up many times since then.

I checked the event viewer and found that there was a system error
Type / Source / Category / Event
Error / ati2mtag / CRT / 45062
CRT invalid display type

0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 2c 00 00 00 06 b0 00 c0 ,....°.À
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 ........

Aparently this has been happening every day since the 24th (this last
Sunday) but even thought this error was appearing in the log, I only found
out today since today was the only time ever the 2nd monitor didn't start
up.

I tried downloading and installing the latest drivers (and catalyst control
center) from ATI but have been
unable to get my 2nd monitor up and running again.

Any ideas?

Rob wrote:
> Hey guys, Since I got my computer I've been using dual monitors then all of
> a sudden today when I booted up, my pc crashed during login so I had to
> manually power it off and turn it on again. Well this time when I logged in
> my 2nd monitor wasn't enabled. So I went to display properties to try and
> extend the desktop to monitor 2 but when I click apply the icons on my
> desktop flicker for a second and then the box is unchecked again and my 2nd
> monitor is still dark.
>
> The last thing I installed was FireFox 3 but that was a little while ago and
> I have booted up many times since then.
>
> I checked the event viewer and found that there was a system error
> Type / Source / Category / Event
> Error / ati2mtag / CRT / 45062
> CRT invalid display type
>
> 0000: 00 00 00 00 01 00 5a 00 ......Z.
> 0008: 2c 00 00 00 06 b0 00 c0 ,....°.À
> 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 ........
>
> Aparently this has been happening every day since the 24th (this last
> Sunday) but even thought this error was appearing in the log, I only found
> out today since today was the only time ever the 2nd monitor didn't start
> up.
>
> I tried downloading and installing the latest drivers (and catalyst control
> center) from ATI but have been
> unable to get my 2nd monitor up and running again.
>
> Any ideas?
>
>

I found a thread discussing this issue, here.

http://www.driverheaven.net/windows-xp-2k-radeon-display-drivers/15569...ti2mtag

This was posted July 24, 2008, last post in the thread.

"Installed the 8.7 package last night.

So far only had 1 freeze then a refresh which is better than a freeze & must
reboot. Usually have 1/2 dozen a freeze & must reboot a day.

No error message w/ 8.7

The error message I use to get was -

ati2mag - CRT invalid display type "

One person suggested it was an overheating card. Perhaps a utility
can tell you the temperature. Or maybe you can check that the fan
is working on the card, and the heatsink is free of dust or obstructions.

A second thing you can try, which isn't guaranteed to do anything,
is run Moninfo, and see if the actual info coming from the monitor
is sane. A while back, there was an instance of the EDID EEPROM inside
the monitor, getting overwritten for some reason. So for some monitors,
it is possible to corrupt the plug and play information coming from
the monitor. (BTW - This utility is now at version 2.0 and has a different
looking interface. Says it was released Aug.28, which is pretty recent.)

http://www.entechtaiwan.com/util/moninfo.shtm

In the Driverheaven thread, they leave the impression that the error message
comes about, because of an error condition that may have existed a
fraction of a second before. So it could be a side effect of an
attempt to recover the GPU from a serious error condition. Thus
the theory about overheating etc.

Perhaps you could torture the card with ATITool.

http://en.wikipedia.org/wiki/Atitool

Paul