NVIDIA Pixel Clock Patcher
|
11-09-2015, 11:20 PM
(Last edited: 11-12-2015, 02:32 AM by sephr)
Post: #471
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Edit: Nvm, ignore this post.
Neither 1.3.4 or 1.3.3 seems to work with the new 358.91 driver. When I click apply after selecting 1440p 120hz, it does nothing and just re-selects 60hz. (On Yamakasi Catleap 2B + GTX 680) When attempting to re-create the custom resolution it says my display doesn't support it. I've been doing 120hz fine with the previous drivers. I also get this error when putting any value other than 60hz (so even 59 and 61hz are not working). |
|||
11-10-2015, 08:34 PM
Post: #472
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
I tried 358.87 and 358.91, but the problem doesn't seem to be affecting the old Fermi card that I have. The problem might only affect newer cards. Regardless, this is not a patch issue because you shouldn't need the patch to add 61 Hz, and if you're using the NVIDIA control panel, you should be able to add 2560x1440 @ 96 Hz without the patch. If it's not letting you add any custom resolutions at all, then that's a driver issue that you should bug NVIDIA about. The patcher is working for the limits that it's designed to patch.
Is it also rejecting resolutions lower than 165 MHz pixel clock like 2560x1440 @ 40 Hz? |
|||
11-12-2015, 02:30 AM
(Last edited: 11-12-2015, 09:19 AM by sephr)
Post: #473
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Sorry Toasty, that problem was transient or user error on my part. I did a clean reinstall of the driver for a third time and now it works (rocking 1440p 120hz again). I don't think I did anything different, so I have absolutely no idea what was causing the issue. ¯\_(ツ)_/¯
|
|||
11-20-2015, 10:12 AM
(Last edited: 11-20-2015, 10:21 AM by DJLeeZ)
Post: #474
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Hey guys I'm having the exact same issue as sephr. However it's not correcting itself for me like it did for him. Ive reinstalled 6 times now and it hasn't changed anything. I have to keep going back to 358.50 as its the only one that lets me oc. Has anyone else got this? GTX 980 using a Qnix 2710
|
|||
11-21-2015, 06:39 AM
Post: #475
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
My 2710 oc'd to 116mhz before hitting flicker. Ive loved every minute of it
|
|||
11-21-2015, 07:56 AM
Post: #476
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher | |||
11-23-2015, 06:38 PM
Post: #477
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher | |||
11-23-2015, 06:48 PM
Post: #478
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(11-20-2015 10:12 AM)DJLeeZ Wrote: Hey guys I'm having the exact same issue as sephr. However it's not correcting itself for me like it did for him. Ive reinstalled 6 times now and it hasn't changed anything. I have to keep going back to 358.50 as its the only one that lets me oc. Has anyone else got this? GTX 980 using a Qnix 2710Latest drivers are just plain broken. I don't know why it only affects some people. |
|||
12-01-2015, 12:55 AM
(Last edited: 12-01-2015, 08:54 PM by sephr)
Post: #479
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
It has to do with multiple monitors for me.
I can OC only when I have just my Yamakasi enabled, but if any of my side monitors (2x 1080p 60hz) are enabled in Windows, I can no longer OC my Yamakasi to 1440p 120hz. I've been disabling my side monitors whenever I play games so I can OC, and then re-enable them when I'm finished. Hope this helps the rest of you. @ToastyX: Could you poke around and investigate Nvidia's latest drivers to see why having multiple monitors enabled could be causing this? I get that you may not be able to patch that yourself, but just a little insight as to why it's happening would be very useful. |
|||
01-04-2016, 09:50 PM
Post: #480
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
seems like it doesn't work with 361.43 nvidia driver
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 5 Guest(s)