59Hz

[loquacious]

Does not change it for Windows 7 X64 .. i get the option for 60hz but after applying it it jumps straight back to 59hz :huh:

 

[Skumin]

And did you download the graphics card drivers?I chose 185.85 for nVidia and for Vista 64bit and everything works well.Try to reinstall your monitor drivers.You should then see the name of your monitor at the"Screen resolution/advanced".So there is not written Plug'n'Play but the proper name of the monitor.

 

[mushroomboy]

And did you download the graphics card drivers?I chose 185.85 for nVidia and for Vista 64bit and everything works well.Try to reinstall your monitor drivers.You should then see the name of your monitor at the"Screen resolution/advanced".So there is not written Plug'n'Play but the proper name of the monitor.

That's not the latest drivers, the latest are 191.07

[edit] Ops it's 195.62

 

[Skumin]

Well,maybe I didn't get the latest ones nut they worked well.I think the monitor drives are problematic.You should install them for Vista 64bit as I said.My monitor has now 60Hz,I don!t if it works for everyone but for me does...

 

[falkenjeff]

I'm sick today so I don't have time to read that entire post, but I meant code is dynamic as in once you release a (good) piece of software, you maintain it and change it to fix any bugs that appear. It doesn't stay broken.

I'm gonna get back to laying around doing nothing for the day. If anyone cares, I am still using DirectRefresh to fix this issue.

I only keep coming back here because I'm too lazy to unsubscribe to this topic, and my inbox keeps getting spammed lol.

 

[mushroomboy]

I'm sick today so I don't have time to read that entire post, but I meant code is dynamic as in once you release a (good) piece of software, you maintain it and change it to fix any bugs that appear. It doesn't stay broken.

I'm gonna get back to laying around doing nothing for the day. If anyone cares, I am still using DirectRefresh to fix this issue.

I only keep coming back here because I'm too lazy to unsubscribe to this topic, and my inbox keeps getting spammed lol.

Ahh sorry, I did the same thing in an earlier part of the thread. already gave you props I think for fixing my mistake? I don't remember lolz but yeah sorry I jump on people easy but it's not because I like to it's because I like the right info out. =P Oh and if I get jumped and am wrong I'll admit it... SHHHH don't say that though.

 

[Ex_Brit]

I recently updated my nVidia295 drivers to 195.62 and the 59hz issue returned, but only in my spare Windows 7 boot...the main one stayed at 60hz, very weird.
I had to do the fix that jimmyt1988 posted here: http://www.sevenforums.com/graphic-cards/1792-59hz-23.html#post316486 to get it to work.
This is most definitely a Windows 7 quirk and whilst it may seem trivial to some it's important in certain games and HD.
By contrast my Vista OS has never had this problem and neither did the XP I had before that.

 

[JackNaylorPE]

I had 59 originally too on prmary monitor...went away when i added 2nd smaller monitor, now both say 60Hz. Agree with others that this looks like a display of umber thing not a real indication of improper frequency.

 

[mushroomboy]

I had 59 originally too on prmary monitor...went away when i added 2nd smaller monitor, now both say 60Hz. Agree with others that this looks like a display of umber thing not a real indication of improper frequency.

If a second monitor fixed the problem, it might also be a problem with the nvidia cards. =S As 2 monitors draw different than one monitor, maybe ground out has problems, who knows. Or maybe the profiles are different, but I don't see why some people use the same drivers, the same setup, just different monitors and get different results then say it's all software. That's just not how troubleshooting goes. Usually it's not all that complicated and is a lot more obvious than people want to think. Like 1G hard drives stuttering.... People don't understand that when we started building computers and file systems we didn't anticipate 1G space to be used as a whole for an OS. But either way, I'm saying if the code works for x scenario than I will work for any other scenario. Software is all math, and the math doesn't lie. So if you have only one changing variable and you get different results when that changes.... What does that show you? It's like programming html... EVERY browser interperts stuff slightly different, making universal web pages is a ****ing bitch. You have to code and test in 3 different browsers... Is the code wrong? No, because by different standards it's correct. That's just it though, universal 59.95 hz isn't a definite, hardware is known to fluctuate. So what if MS decided to change how things are being reported, they wanted to do a whole new re-write when they started vista. That means we might see more stuff like this in the future. With everything becomming more and more accurate I'm not suprised we see 59Hz being reported, hell I never knew they had options for offset hz back in the day until one day my linux reported 73hz and I was all WTF WTF WTF. I learned what was up and dealt with it.

 

[gohan2091]

Hi,

I also suffer this 59Hz bug. It has not happened on XP and Vista, just with Windows 7 so it must be software based as I am using the exact same hardware 2 weeks ago with Vista and did not have a problem. I admit, I have not read the whole thread though so may be missing some words of wisdom.

Basically I get tearing in Pro Evolution Soccer 2010 and I cannot enable v-sync (it is greyed out). When I change to 60hz, it just goes back to 59hz. I tried PowerStrip and can successfully force 60hz (even though when I do this, PowerStrip suddenly says 16hz....) but when I reboot, it goes back to 59hz again. Is there a way I can tell PowerStrip to keep it at 60hz even after a reboot?

I use an ATI Radeon HD 4890.

 

[omnimodis78]

I am getting so sick of this issue. I have to add my weekly complaint about it lol. I really can't understand why you (gohan2091) wouldn't be able to enable vsync though. I haven't had any such issues. although even with vsync enabled, I get tearing. In most games, you can specify the refresh rate in the game - mine usually is set to 59Hz by default, so I get tearing with vsync enabled regardless if I leave it on 59Hz or 60Hz. I have replayed games (CoD Modern Warfare) that I remember specifically never to have given me any tearing issues under XP, but now it does. So clearly there's an issue. I will keep repeating myself until this gets fixed: there's a problem somewhere and I don't buy Microsoft's explanation about the number rounding - if it was just that I wouldn't care, but I get tearing with vsync enabled and refresh rates set (in game) to both 59Hz and 60Hz. And to this day nobody has explained to me what refresh rate is my system set to. What happens if I really want my monitor to run at 59Hz, if the setting "59Hz" is actually 60Hz, then how do you get real 59Hz? Just asking. I don't buy this rounding nonsense. Don't be shy people, keep posting here and grow this thread so that it becomes substantial. I am a gamer and I use my PC for watching movies. For me tearing is a real issue which shouldn't be an issue with an OS which is marketed on its visual and multimedia experience premise. Clearly video tearing was a non-issue in XP, and Vista, and it's an issue in Windows7 and yet Microsoft is blaming our hardware? BULL ****!!!

 

[scatology]

I'm agree with you omnimodis78.

I have the same problem. I have a Acer x223w and SLi of gtx 280. My monitor is not a good monitor but I don't have this problem in vista and xp...

I come back on vista... shame on me.

 

[Mark]

Well for me 59Htz has not been a problem at all and I have been able to enable V-Sync in every game that I play and have never noticed any tearing with it enabled and all my games play smoothly at 60fps.

 

[Deanos]

Best solution!!!!

Hi guys...

Been a while since anybody has posted here, wonder if you all found your own solutions????

OK, so I had to format and re-install my Win 7 due to a NASTY virus that ate everything up!!!! I didn't have the time to sit and manually remove the thing so I chose the quick way out!

After doing all the updates, installing everything I need and updating that, I remembered about this 59Hz thing...
So, I thought I would try a few things that never worked in the past from here...

This actually worked first time around...

http://www.sevenforums.com/tutorials/33641-screen-refresh-rate-custom-nvidia-brand.html

- 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

But what I did realize now is possibly where myself and some other may have gone wrong....

Nope, doesn't work for me!

Tells me that 60,001 is out of range!

Can only set between 58,000 and 60,000?!?!?

As I mentioned in this post, it would not accept the 60,001, although it did this time.
The solution I found for that was to set it to 60,000 first, click accept, but this still gives the refresh at 59Hz...
Then I tried again, and by some miracle, it opened and accepted 60,001!
Infact, I can even go right up to 64Hz now, but it gives some problems...

So, I hope this can help a few of you out...

Cheers all and have a FANTASTIC Christmas and New Year!!!!!

 

[Deanos]

I also just found this.....

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

OH, and there is a new nVidia driver out! Go get it!!!!

 

[DHAmoKK]

Hi,

I'm now using the 195.62 driver. First it still didn't work, but now the trick with the 60,001Hz DOES work My monitor now shows 60Hz (in 1920x1200) and I'll tell you another thing: I now can play Games with fixed resolution without problems!
For example 'A Vampyre Story': My monitor is now getting the real resolution of '1024x768' and I can use the internal upscaling functions. I really don't know, if it's only the new driver doing this or a mix of the driver and the 60,001Hz setting.

Since I'm still using the Win7 RC, I'm curious, if it still works with the final release, I buyed it a few days ago and I'm awaiting the parcel tomorrow, installing it on x-mas though.

 

[omnimodis78]

If you read the nvidia driver 195.62 release notes, there's a section in there with the heading "Windows 7 Limitations" - which, would you look at that, addresses this issue ( http://us.download.nvidia.com/Windows/195.62/195.62_WinVista_Win7_Desktop_Release_Notes.pdf ). So apparently nVidia is clear about the fact that this is not their problem and obviously it's something they are not going to fix (rightly so if it's not their doing). The 60.001 workaround works and tearing is gone (yet another proof that Microsoft's rounding explanation is BS (as they stated, 59Hz is really 59.96Hz which is effectively 60Hz...and yet some of us are getting tearing we haven't seen before). Here's what I want Microsoft to answer (let me put it in point form):
1. If I choose 60Hz but it keeps chaning back to 59Hz, then what actual refresh rate am I using?
2. If I choose 60Hz but then it changes to 59Hz and then I decide I really do want 59Hz, how do I now select 59Hz if it's already in that mode (but supposedly it's really at 60Hz)?

 

[chrysalis]

I got curious and checked my monitor, it reports as 60khz but nvidia panel says 59khz. So far I noticed no issues in games but however if games are showing problems such as tearing then I back all you guys up, microsoft should revert the behaviour back to rounding up as to maintain compatability.

 

[gohan2091]

What about us ATI users? Anything in the control panel for us?

 

[Evildemon]

hey gohan the solution i found to resolve the problem was to make the connection using a hdmi cable instead of a dvi (with a adapter on the graphic card dvi-hdmi)... it solved for me : D
My graphic card is a sapphire 4890...
now i can normally set 60hz : D
See if it solves to you too ^^