• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows 7 x64 RTM 59Hz issue

powerstrip worked great, now 60HZ working fine

yagi how I can know my maximum pixel clock, I have rivatuner but can't find it
 
Go to the Graphic subsystem diagnostic report, and check Monitor EDID details. You should get something like that:

gsdr.png
 
How can you possibly force a higher refresh rate than the monitor supports?

:confused:

its not forcing a higher maximum, its forcing a higher minimum :)
 
What does increasing the pixel clock do? This looks interesting for me.
 
What does increasing the pixel clock do? This looks interesting for me.

Increasing the pixel clock subsequently raises the refresh and scan rate of your LCD.....I found out my pixel clock runs at 165 Mhz but was only running at 146 Mhz.....I've increased it to 152 and have seen a smoothing of my videos and desktop icons.....no gaming as of yet....but I'm sure it'll do just fine.....still wish I could get mine up to or around the 165 Mhz range...but I'm getting flickering beyond 152 Mhz.....thanks for enlighting the crowd here yaji. :toast: :rockout:

Hope it helps. ;)
 
the program reads my timmings incorrectly, max reported in riva tuner 170Mhz, with powerstrip it says 35Mhz, I tried 36Mhz and screen went black
 
not sure if anybody has seen this but i found that rivatuner offers the best way of fixing this issue in windows 7. The issue was solved quite easily by setting a custom rule in the rivatuner software under low level refresh rate to create an option to run the system at a set refresh rate independent of the windows drivers and edid. i then added it to the launcher and set it up to run on windows boot so that it always changes. The number i chose was modest so only 61 but seems high enough to force the pc to choose 60 in both the nvidia control panel and the windows advanced display settings all in windows 7 x64. this was tested on my asus g71 with a gtx 260 and 17.2" 1440x900 lcd, and my desktop with a westinghouse 22" lcd 1680x1050 and a gtx 285.

just thought you'd all like to know as it's got the least complicated steps out of all the things i've tried and has worked flawlessly, and needs little to no skill to figure out. If a guide is needed i'll gladly put one up, please let me know via pm if you need individual help or as here for a guide to be created. thanx all
 
Found A Fix, Found A Fix For Nvidia

HI ALL,

THIS IS A FIX FOR NVIDIA CARDS. AND IT DEFINETLY WORKS ALL THE TIME.

After frustrating countless hours, I found a fix that works like a charmmmm.

- Go to Nvidia Control Panel
- Go to Add resolution
- Create Custom Resolution
- Click on Timing
- Click on Manual
- Set refresh rate to 60.001 Hz
- Press Apply, and Have funnnn
 
Last edited:
Is there anything easy for ATI ppl? My problem isn't any flickering or minor like that, I get Mode not Supported on my Samsung 32" FHD LCD TV and it forced me to go back to xp. I was previously on nvidia and figured the custom resolution settings on my own but the "upgraded" to ati because of the price drops. Ati doesn't have any custom timing settings available so I was kinda screwed and had to revert to XP.

The problem is the same as OP, if I choose 60hz from any menu, windows's own monitor properties or ati ccc it always reverts back to 59hz. I can get it to work by plugging in a second lcd display that reports the correct edid to windows and lets me choose 60hz, and then dualview the TV and I can actually see the picture but then if I disconnect the other monitor it activates 59hz again.

The TV has just VGA and HDMI inputs so I'm connected on VGA. The HDMI connection sucked, after a hour of tweaking TV's settings I got a picture that didn't make my eyes bleed but still major problems. See http://wizeon.net/hdmi/ for pictures. If anyone has some solutions I'd be happy to hear.

edit: Just actually read the post above. Can you like promise me the beta drivers will fix the problem I described? I'm not sure if it's the edid corruption or windows rounding down the number or what, all I can say that I'm using Samsung 32" FHD TV with vga - vga lead and I have 4870 2GB Vapor-X gpu.
 
Is there anything easy for ATI ppl? My problem isn't any flickering or minor like that, I get Mode not Supported on my Samsung 32" FHD LCD TV and it forced me to go back to xp. I was previously on nvidia and figured the custom resolution settings on my own but the "upgraded" to ati because of the price drops. Ati doesn't have any custom timing settings available so I was kinda screwed and had to revert to XP.

The problem is the same as OP, if I choose 60hz from any menu, windows's own monitor properties or ati ccc it always reverts back to 59hz. I can get it to work by plugging in a second lcd display that reports the correct edid to windows and lets me choose 60hz, and then dualview the TV and I can actually see the picture but then if I disconnect the other monitor it activates 59hz again.

The TV has just VGA and HDMI inputs so I'm connected on VGA. The HDMI connection sucked, after a hour of tweaking TV's settings I got a picture that didn't make my eyes bleed but still major problems. See http://wizeon.net/hdmi/ for pictures. If anyone has some solutions I'd be happy to hear.

edit: Just actually read the post above. Can you like promise me the beta drivers will fix the problem I described? I'm not sure if it's the edid corruption or windows rounding down the number or what, all I can say that I'm using Samsung 32" FHD TV with vga - vga lead and I have 4870 2GB Vapor-X gpu.


they *may* fix it - it seems like windows still shows 59Hz, but it sends a 60Hz signal.

since my screen gets an image on both 59 and 60Hz, i cant say for sure if it will work for you
 
they *may* fix it - it seems like windows still shows 59Hz, but it sends a 60Hz signal.

since my screen gets an image on both 59 and 60Hz, i cant say for sure if it will work for you

Then I think I'll wait for a "official" solution. Microsoft doesn't seem to admit this bug even exists. I would have to delete this XP installation to even try the drivers and if they didn't fix it...well too much hassle for me just to gamble if they fixed it.
 
Can you force a resolution as well?

Obviously it wouldn't be a real resolution but I'd see more game area and desktop space etc.
 
Just reporting in that the new drivers did NOT fix the problem for me. I'm still definately getting 59hz signal. Powerstrip remains the only way to see the picture and it fails when gaming so the only option is to live with xp (or vista, haven't tried it) or change back to nvidia which sounds best but can't because of budget reasons..
 
Problem Solved (1920 x 1080 using ATI VGA output) Win 7

I have an HIS ATI Radeo 4670 512MB PCIe Adapter and am running Windows 7 Ultimate Edition 64 Bit Version 7600.

Here is what I did to fix it. After trying at least 20 different drivers from ATI's site, I finally ended up going to HIS site.

http://www.hisdigital.com/un/download.shtml

I downloaded the driver with this description:

..................................................................................................
ATI Catalyst: (ref. no: 0812)
Platform: Windows Vista (32bit/64bit)
VISTA Driver Verison: Vista_8.523-080808a-068036C-ATI with WHQL Note: Users must have Microsoft's .NET Version 1.1 Framework prior to installing the ATI driver/Catalyst Control Centre(CCC) components

..................................................................................................

The file name is:

Vista_8.523-080808a-068036C-ATI.zip

This is the Vista driver for an ATI 4670 512 mb PCIe adapter.

Uncompress the file.

1. Boot into Safe Mode.

2. Execute the following from a command prompt to turn on the Windows Installer Service:

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Network\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver

3. Execute the following from a command prompt to isable Driver Signing:

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

4. Open the Device Manager.

5. Left Click and expand "Display adapters".

6. Right Click on the Display Adapter. Example: (ATI Radeon HD 4670)

7. Left Click Update Driver Software.

8. Left Click "Browse my computer for driver software"

9. Left Click "Let me pick from a list of device drivers on my computer".

10. When the window with the prompt "Select the device driver you want to install for this hardware." comes up, uncheck "Show compatible hardware".

11. Left Click "Have Disk".

12. Browse to the directory: "C:\Drivers\ATI\Support\Vista_8.523-080808a-068036C-ATI\Packages\Drivers\Display\LH6A_INF" and click on the inf file "CH_68036.inf"

(That's where I put the uncompressed driver files.)

13. Select your adapter (if necessary).

14. Follow prompts and reboot.

You should now be able to select 1920 x 1080 using your VGA cable.
 
I have an HIS ATI Radeo 4670 512MB PCIe Adapter and am running Windows 7 Ultimate Edition 64 Bit Version 7600.

Here is what I did to fix it. After trying at least 20 different drivers from ATI's site, I finally ended up going to HIS site.

http://www.hisdigital.com/un/download.shtml

I downloaded the driver with this description:

..................................................................................................
ATI Catalyst: (ref. no: 0812)
Platform: Windows Vista (32bit/64bit)
VISTA Driver Verison: Vista_8.523-080808a-068036C-ATI with WHQL Note: Users must have Microsoft's .NET Version 1.1 Framework prior to installing the ATI driver/Catalyst Control Centre(CCC) components

..................................................................................................

The file name is:

Vista_8.523-080808a-068036C-ATI.zip

This is the Vista driver for an ATI 4670 512 mb PCIe adapter.

Uncompress the file.

1. Boot into Safe Mode.

2. Execute the following from a command prompt to turn on the Windows Installer Service:

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Network\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver

3. Execute the following from a command prompt to isable Driver Signing:

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

4. Open the Device Manager.

5. Left Click and expand "Display adapters".

6. Right Click on the Display Adapter. Example: (ATI Radeon HD 4670)

7. Left Click Update Driver Software.

8. Left Click "Browse my computer for driver software"

9. Left Click "Let me pick from a list of device drivers on my computer".

10. When the window with the prompt "Select the device driver you want to install for this hardware." comes up, uncheck "Show compatible hardware".

11. Left Click "Have Disk".

12. Browse to the directory: "C:\Drivers\ATI\Support\Vista_8.523-080808a-068036C-ATI\Packages\Drivers\Display\LH6A_INF" and click on the inf file "CH_68036.inf"

(That's where I put the uncompressed driver files.)

13. Select your adapter (if necessary).

14. Follow prompts and reboot.

You should now be able to select 1920 x 1080 using your VGA cable.

But, the problem here isn't that you can't select the resolution, but that the refresh rate is incorrect. At least that's my problem
 
same problem here, world of warcraft in window mode will tear like crazy when panning, cause its set at 60hz vsync ingame , but windows is running at 59hz , even though its set at 60hz in CCC. External third party system tools confirm its running at 59hz or whatever, its not 60hz in any casE.

Im running the latest ATI beta drivers.

Also.... why is this suddenly an issue in win 7, didnt win xp run at real 60hz all those years? i cant see the benefit of the 59hz refreshrate
 
And with a LCD the refresh rate is uber important.........not.
 
And with a LCD the refresh rate is uber important.........not.

It is. You can actually ruin displays with wrong refresh rates if they don't have any safety measures. And if I send 59hz signal to my TV I don't see the picture (safety measure), so there is a difference between 59hz and 60hz with my TV. Like day and night.
 
And with a LCD the refresh rate is uber important.........not.

try running your screen at a refresh rate it doesnt support and you'll realise "oh yeah... kinda important"
 
Only when you have too high of a refresh rate (Then it just downscales the image to somethign the display chip can handle for pixel fill). LCD it just continues to show the same image until either the data is refreshed or the signal is lost. The backlight runs at a set rate, and isn't changed, just the crystal refresh time is different, and that is only set at a "refresh rate" as we have as of yet to come up with a acceptable industry standard for allowing full digital control over a LCD panel and colorchange, and thus allowing faster response time. So your 59Hz theory is baseless, doesn't change how many FPS you get other than if Vsync is locked, and even then the picture is smooth unless you drop out of sync or experience tearing.

Really it will only matter if you have a monitor/TV that is dumb enough not to accept basic inputs. Or a CRT, and if so, I'm sorry for you.
It is. You can actually ruin displays with wrong refresh rates if they don't have any safety measures. And if I send 59hz signal to my TV I don't see the picture (safety measure), so there is a difference between 59hz and 60hz with my TV. Like day and night.


Again, only applies to CRT for damaging them, and apparently your TV. Which may or may not be junk. And may or may not be a LCD.
 
Only when you have too high of a refresh rate (Then it just downscales the image to somethign the display chip can handle for pixel fill). LCD it just continues to show the same image until either the data is refreshed or the signal is lost. The backlight runs at a set rate, and isn't changed, just the crystal refresh time is different, and that is only set at a "refresh rate" as we have as of yet to come up with a acceptable industry standard for allowing full digital control over a LCD panel and colorchange, and thus allowing faster response time. So your 59Hz theory is baseless, doesn't change how many FPS you get other than if Vsync is locked, and even then the picture is smooth unless you drop out of sync or experience tearing.

Really it will only matter if you have a monitor/TV that is dumb enough not to accept basic inputs. Or a CRT, and if so, I'm sorry for you.



Again, only applies to CRT for damaging them, and apparently your TV. Which may or may not be junk. And may or may not be a LCD.


You're wrong. running at too low a refresh rate causes flickering for a lot of people.
When you run DX10 games, it sees Interlaced refresh rates (60Hz interlaced) as higher than 59Hz progressive, so in every game you cant choose a refresh rate you get screwed over.

If there was no side effect, no one would CARE...
 
People only care as they look and think they are being screwed by that 1Hz. There is more fluctuation in the power grid that causes the signal to become out of sync that this will cause.


LCD doesn't have a refresh rate....again, they just use a common rate to expect the signal and keepthe current image alive for longer than that, and the backlight is driven by a seperate crystal. GO read up on LCD overdrive, they have plenty of articles about the refresh rate of a LCD.
 
People only care as they look and think they are being screwed by that 1Hz. There is more fluctuation in the power grid that causes the signal to become out of sync that this will cause.


LCD doesn't have a refresh rate....again, they just use a common rate to expect the signal and keepthe current image alive for longer than that, and the backlight is driven by a seperate crystal. GO read up on LCD overdrive, they have plenty of articles about the refresh rate of a LCD.

you're making assumptions based on logic.

we're all going by fact and evidence - we're having issues due to this, so we're complaining.

You're sitting back and saying "well in theory... it doesnt matter"

(and please stop with the "LCD dont have refresh rate" - you've obviously misunderstood the basics, cause uhm... they do? 60Hz, typically. some do 100Hz and 120Hz as well)
 
Back
Top