I also meant to say if you override the refresh rates on your monitor to one
that it will not support you have a good chance of ruining your monitor.
Excerpt from ATI interview:
In XP and 2K, we don't have access to monitor INF information in our driver
component that manages display capability. We have never used this monitor
information for any purpose. We rely on EDID data or user override
information to determine monitor capability. Even though the OS may use the
monitor information to expose high refresh rate based on monitor INF
content, the driver always restricts the actual refresh rate going to the
monitor based on EDID or the user override. In essence, the user may be able
to select from OS controlled monitor page (in advanced property pages) a
high refresh rate but internally driver will restrict the refresh rate going
to the monitor based on EDID information or user override information. If
user set the override information incorrectly then incompatible signals
would be sent to the monitor.
In 9x, we can access monitor INF information but due to issues with how OS
maps the INF to a monitor, we had disabled reading the monitor INF via
registry. Unless someone deliberately changes the registry setting for this
in 9x, they would not run into any monitor INF related issues.
They do rely on the EDID information which is contained in the registry.
The operating system does rely on the .inf file to relay the correct
information about the monitors display properties and the default monitor
may not, as stated before, have this. We had this problem with a 21" NEC
and the ATI 9700 Pro. As soon as we installed the monitor drivers
downloaded from NEC, we no longer had a refresh issue. The monitor install,
not just an .inf put in the windows directory, but an actual install put the
info in our registry. The same with our ViewSonic monitor.
http://www.ati.com/support/infobase/3653.html
Your DDC or Display Identification Standard is being incorrectly read.