Originally Posted by sniggleface
You need your drivers patched to hit certain refresh rates regardless of method, since the patch removes the pixel clock limit. You should not need to use test mode at all anymore with the latest driver patcher v1.2. Here's what should work for you (if you don't want to go with the Catleap method):
- Uninstall your drivers and disable test mode, reboot
- Reinstall your drivers (may as well do the latest beta 326.80) and patch using the latest patcher, reboot
- Run CRU and add your custom resolution, uncheck "include extension block", reboot
If your new refresh rate doesn't show up in the standard list, then I'm not really sure what could be going wrong at that point.
I'm running 326.80 @ 120hz with no problem, doesn't seem any different than other driver versions.
This is pretty much what I did, except I didn't uninstall my old drivers first, I just installed over the new ones. And you never mentioned re-enabling test mode, do I need it enabled?
So, something is definitely not right here. I add 120hz, I restart, and as soon as I get to the desktop, I hear the driver uninstalled sound. Go to advanced settings, and I only see 59 and 60hz. If I restart again, then I can see 120hz.
If I add 147hz (just wanted to test if I can go that high in the CRU, because I can if I make a 147hz resolution in Nvidia), I restart. Remember I still am at 120hz. As soon as I get to the desktop I hear the driver uninstalled sound, and my screen flashes, sending me back to 60hz. Then in a few seconds again, it flashes, going back up to 120hz.
I can understand drivers crashing if I enabled 147hz and I couldn't hand it, but I know I can handle 147hz in Nvidia control panel. On top of that, I didn't even enable 147hz, nor do I see it in the dropdown menu of all my resolutions in Windows.
I'm going to forget about adding 147hz and see what happens after I enable 120hz and restart twice.
Edit: Just restarted again. Same sound and screen flashing twice, and then the driver installed sound. 147hz appears in my list of resolutions. When I enable it, I get a pretty decent amount of scan lines (compared to the 147hz I created in Nvidia control panel being completely stable).
I'm going to delete 147hz from the CRU and see what happens. Not sure why I have to restart twice for my resolutions to appear, and what's the deal with the accompanying screen flashes and install/uninstall sounds.
Edit again: Odd... I made 120hz, 110hz, and 96hz custom resolutions. Restarted 4 times now. They appear in the dropdown menu, but now every time my computer turns on and reaches to the desktop the screen flashes twice and I hear the uninstall sound!!
I just enabled test mode thinking it was because I had it disabled, but that's not it....
It was fine before... what did I do? :X
Edit edit: Tried something else. Hope this gives us more info. I deleted the display in the CRU, restarted and created my new resolutions. Restarted again, and still get the 2 screen flashes, but when I look next to the name of my display, there's a * after it but not "(active)." If I go into device manager, there's the error sign next to my "Generic PnP Monitor," stating "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)" There's only one display listing in the drop down menu in the CRU, I don't have another one. I deleted them all and created this one.
Meanwhile, I can still change between resolutions in the Nvidia control panel (the resolutions show up there but not in the advanced monitor settings tab). I remember reading though that some games won't use Nvidia custom resolution settings, and the screen flashes are annoying, so I really want to fix the CRU.
This is just too weird.Edited by apav - 8/21/13 at 4:23pm