59Hz

......sounds to me the idiot you talked to did not even understand the problem! Microsoft providing Bangalore quality support? - interesting!

That's off-shore outsourcing at its finest!

Like always on any Windows we have to wait for SP1..

Bad news, guys: NVIDIA knows about this 59Hz problem and they say that it is up to Microsoft to fix it.
Yes, and Microsoft says that this is a feature - not a bug.

Check out the Nvidia Release Notes for Driver Vesion 196.21

(See Windows 7 Limitations under page 17)

and Microsoft's KB2006076.

I have ATI but I unchecked in CCC - Detect whenever CCC is opened - in Display Detection Option, and the 60hz is now locked in W7 display options. Something like detection of displays in Nvidia Control Panel could possibly do the trick

GordonNT said:

Bad news, guys: NVIDIA knows about this 59Hz problem and they say that it is up to Microsoft to fix it.
Yes, and Microsoft says that this is a feature - not a bug.

Check out the Nvidia Release Notes for Driver Vesion 196.21

(See Windows 7 Limitations under page 17)

and Microsoft's KB2006076.

The bad news is that you clearly haven't read the comments on here - since everything you wrote here has been written before, and not even too many pages before the one you landed on. If you choose to contribute to a forum, at least read a few pages back from the last one so that you can get caught up and not duplicate the efforts made by others. On that note, thanks for the effort.

I've tried everything suggested here that is relevant to my hardware spec, but when I start a 3D game, I get any 2D content that shows before the game loads then when the 3D engine tries to kick in I get a black screen with the sound playing. When I check Task Manager, the game is running, it just can't be used.

Any suggestions beyond what's here?

win7 - nvidia 196.21 - evga gtx275

I think the 59hz issue happens as soon as you make any resolution change. As if the original 60hz configuration got damaged. Then the solution is just delete the 60hz original resolution. So you have to go
to a 1280x720 resolution mode and delete de 1920x1080@60hz from there, otherwise it wouldnt be posible.

Then while staying in 1280 resolution, create a fresh new 1920x1080@60hz one - 32bits color of course - in manual mode and changing - below - 60.000hz to 60.001hz. Once this resolution is created, close the nvidia control panel, change to the new resolution by the windows tap and problem will finish.

It worked perfect for me at least. But take into account that the problem will appear again as soon as you made a new resolution change.

I also think that it was affecting the performance rather much since I was playing NFSCarbon perfect at 60hz but it was lagging a lot at 59hz. So I don't think it was just a reporting mistake made by the OS.

Hey all, I found something that is maybe the reason the custom resolution works for some of you and not for others. Apologies if this has been said before, not gonna read the entire thread.

The original instructions just say to create a custom resolution and then go straight to manual timing. This failed for me when I tried to put 60.001 "Test" went grey. What I did then was change the top number from 59 to 60. After that it let me use 60.001 in manual timing:

I have the same problem, I used the tutorial on here and I'm forcing it to use 60Hz.