59Hz

Well it would appear that there's an official "resolution" to this issue posted by Microsoft ( Screen refresh rate in Windows 7 does not apply the user selected settings on monitors & TVs (that report specific TV compatible timings) ). According to them, no action is needed to be taken as this is not a real problem. I beg to differ, and here's why: If I turn on windows and the refresh rate shows as 59hz, then what is it really switching to when I change it to 60hz? If it's already at "60hz" (59.94Hz) then why does my screen actually switch refresh rates when I change it from 59 to 60? Could it be that every time I start windows it's actually really at 59 not 59.94? I don't think this is a non-issue at all. Even with v-sync enabled, I used to have tearing but since I have implemented the quick-fix as noted in previous posts (custom resolution...60.001Hz) this tearing no longer occurs - and just to be sure I tried it at the only setting at which windows 7 seems to want to use (59Hz) and the tearing does come back. The point is - when the selection box is at its deafult (59hz) what is my actual hardware refresh rate - is it 59.00Hz or is it at 59.96Hz, or is at 60Hz? GRRRRRRRR!!!!!!

Yeah, there's definately a difference between the 59hz that windows 7 likes to revert to and true 60hz when I create a custom resolution with 60.001hz in my graphics drivers. I get tearing at 59hz and don't at 60hz.

I've sent microsoft a message using the box at the bottom of that "solution" explaining this. Everyone should do the same.

its your monitor there is nothing you can do about it ...........

Regarding 59hz Bug. - Guru3D.com Forums

archie123 said:

its your monitor there is nothing you can do about it ...........

Regarding 59hz Bug. - Guru3D.com Forums

you can,
my problem with the 59hz refresh rate was because a game pes 2010 needed to be @60hz too enable vsync in the setting..
all you have to do is download http://downloads.guru3d.com/PowerStr...nload-169.html Powerstrip trial run it go to icon in tray bar -right click icon-goto custimize moniter ,and theres an option to change the refresh rate to 60hz
and the program doesnt have to be run all the time.
once you change the refresh rate to 60hz /problem solved

i think you'll find your refresh rate is still 59.94 (or thereabouts) you have just forced your drivers to report 60hz via powerstrip , its a workaround not a fix , fraps will report 60 fps ingame as it rounds up and of course you can enable v sync which is a good thing

if the DDC is reporting 59.94 to the OS you cant have true 60hz its just not possible , you never had it in vista or XP either it was rounded up so we thought we had it.

archie123 said:

i think you'll find your refresh rate is still 59.94 (or thereabouts) you have just forced your drivers to report 60hz via powerstrip , its a workaround not a fix , fraps will report 60 fps ingame as it rounds up and of course you can enable v sync which is a good thing

if the DDC is reporting 59.94 to the OS you cant have true 60hz its just not possible , you never had it in vista or XP either it was rounded up so we thought we had it.

It's definately not, my monitor reports 59.7hz in it's osd at 59hz. When I create a custom resolution with a 60.001hz refresh rate, my monitor osd reports 60hz. At 59hz there's tearing, at 60hz there's no tearing.

It's also not down to my monitor, Windows XP and Vista were fine with setting my refresh rate to 60hz, it's only Windows 7 that has a problem with it.

I think with all the posts we're all getting a little confused hehe. So, in XP, the setting was at 60Hz with the understanding that it was really at 59.96Hz. I get that - but when I had it at 60Hz and enabled vsync in games, there was never ever any tearing whatsoever. Now, in Windows7, it's stuck at 59Hz, even though they are saying it's really at 59.96Hz (essentially at 60Hz) and yet I get tearing. Doesn't that mean that it's not really at 60Hz (or 59.96Hz)? So, apparently XP's 60Hz (59.96Hz) and Windows7's 60Hz ... 59Hz (59.96Hz) do not give the same results. This is not a monitor issue, nor a GPU driver issue, this is 100% an OS issue and it's time for Microsoft to recognize its impact on our experience. Is there any other issue on this forum with this many posts? Just curious... Cheers!

omnimodis78 said:

Well it would appear that there's an official "resolution" to this issue posted by Microsoft ( Screen refresh rate in Windows 7 does not apply the user selected settings on monitors & TVs (that report specific TV compatible timings) ). According to them, no action is needed to be taken as this is not a real problem. I beg to differ, and here's why: If I turn on windows and the refresh rate shows as 59hz, then what is it really switching to when I change it to 60hz? If it's already at "60hz" (59.94Hz) then why does my screen actually switch refresh rates when I change it from 59 to 60? Could it be that every time I start windows it's actually really at 59 not 59.94? I don't think this is a non-issue at all. Even with v-sync enabled, I used to have tearing but since I have implemented the quick-fix as noted in previous posts (custom resolution...60.001Hz) this tearing no longer occurs - and just to be sure I tried it at the only setting at which windows 7 seems to want to use (59Hz) and the tearing does come back. The point is - when the selection box is at its deafult (59hz) what is my actual hardware refresh rate - is it 59.00Hz or is it at 59.96Hz, or is at 60Hz? GRRRRRRRR!!!!!!

guys, this is a big issue. THIS IS IMPORTANT, READ THIS, SPREAD IT. Microsoft says this is a non-issue, correct? But it is an issue. People have problems with tearing, my TV won't even display at 59hz, etc.... SO USE THE OPTION MICROSOFT HAS GIVEN TO YOU.

Screen refresh rate in Windows 7 does not apply the user selected settings on monitors & TVs (that report specific TV compatible timings)

scroll down.

"Did this information solve your problem?" select no

"Was the information relevant?" select yes

"comment box" add reasons why 59hz actually IS an issue (eg: HDTVs not displaying at all due to it, tearing, etc)

and hope that the system they have in place eventually forces their software development team to look at this issue.