I recently replaced my ATI Rage video card with a PowerColor/ATI 9250 card. Now, when I boot up, I get the brief message: “Frequency Over Range”, and I’m not sure why. The monitor resolution is set to 800x600, with a refresh rate of 75Hz (no such message with the Rage card). I researched this a bit, and from what I could tell, the video card is sending a signal that the monitor doesn’t like, but the PC boots up OK and everything seems to work fine. I’ve changed the monitor refresh rate several times to different settings but I still get the “Frequency Over Range” message. I also got the message when I installed an ATI 7500 card I borrowed from a friend before buying the 9250. Anyone have a similar situation, and how do I “fix” it? I hope I’m not doing any damage to the monitor.
+ Reply to Thread
Results 1 to 8 of 8
-
-
This is caused when the default refresh frequency of the card is greater than the monitor can handle. Once Windows starts to boot, the card is set to the frequency that you (or the inf file for your monitor) have told it to run at. I assume you are using an LCD monitor as the effect on a CRT was usually a couple of flashes and flickers before everything settled down. It shouldn't cause any damage though, the monitor is simply telling you why it is unable to display a picture.
-
It is the monitor complaining.
CRT and LCD monitors complain about different issues. Which do you have? -
My guess is that the OP had a CRT, but replaced it with an LCD. Since 75 is common for CRTs, but may not be the native rate (there's usually only ONE) for LCD, that's what is going on. Now, why alternate settings (resolution only?) didn't fix that, I don't know.
Scott -
Sorry, I forgot to mention it is a CRT monitor, and it had no problems/message with the old Rage card @ 800x600 res and 75Hz refresh rate. In fact, the monitor supports up to 100Hz, but I've been using 75Hz (and 800x600 res) for years.
Update: I just tried resetting the refresh rates to the lowest available (56Hz) and the highest (100Hz), but still get the "FOR" message at bootup. -
Ok, NOW my guess is just that--similar to Richard_G said--the new card support/defaults to a much higher initial frequency. When the card finds out the CRT can't accept that refresh rate (at some point during the boot process), it does this Step-down approach till it gets to a refresh rate that both can agree on, and then it's possible/likely that at a later point during the boot process, the Windows drivers kick in and tell the card exactly what it's supposed to be set at--regardless of the earlier "agreed upon" setting.
If this is actually what is happening, then the message isn't really a "bug" or even something bad, just a temporary "pre-coordination" awareness, which you can basically ignore. Shouldn't hurt anything (knock wood)...
Scott -
Try other resolutions to see if it makes a difference.
640x480
1024x768
1280x1024 -
I tried the other 3 resolutions as suggested, but no luck -- got the "FOR" message on each one.
I checked, but couldn't find any adjustment option for the video card initial frequency. I'll just have to keep my fingers crossed that what Cornucopia said is what is going on, and that it isn't hurting the monitor.
Thanks
Similar Threads
-
frequency separator required
By virendra in forum AudioReplies: 13Last Post: 21st Aug 2011, 22:17 -
Need to capture in 60hz frequency
By Teryolilio in forum Capturing and VCRReplies: 18Last Post: 21st May 2010, 10:58 -
frequency response graph
By siluet in forum AudioReplies: 13Last Post: 10th Feb 2010, 13:11 -
Frequency response correction
By siluet in forum AudioReplies: 6Last Post: 29th Jan 2010, 14:44 -
Is noise frequency cancelling possible this way?
By Shoyriazu in forum AudioReplies: 3Last Post: 31st Jan 2008, 06:13