(10-21-2018 12:28 AM)Blackdragonbird Wrote: [ -> ] (10-21-2018 12:15 AM)apav Wrote: [ -> ] (10-20-2018 11:02 PM)Blackdragonbird Wrote: [ -> ]Having the same issue. Was in the 385.69 driver and tried to install Quadro 416.30. If I try to use the full patcher it says the driver is not compatible. Using the single patcher it says that the DLL was patched and signed, but after setting my new refresh rate in CRU and restarting the system my screen is still at 60hz, and there's no option to choose the overclocked refresh.
Hope you find what is the issue. If I can help in any way, say it and I send any information needed.
My system is: Win10 Pro x64 1709, EVGA GTX970, X-Star DP2710.
Try creating a custom resolution in the Nvidia Control Panel and see if it works. It did for me, even though it's not working with any of the resolutions I create in CRU. This leads me to believe that the Pixel Clock Patcher is fine with the new driver, but CRU isn't.
Custom resolution works in desktop, but some games don't see/use the overclocked/custom refresh rate, and stay at 60hz. It's why I use CRU.
Agreed. Just was making sure you could do this on the desktop as well. Clearly it's not on our end and ToastyX took a look at the patcher before and said it was fine, so I'm guessing the issue lies with the CRU.
(10-21-2018 05:45 AM)apav Wrote: [ -> ]Agreed. Just was making sure you could do this on the desktop as well. Clearly it's not on our end and ToastyX took a look at the patcher before and said it was fine, so I'm guessing the issue lies with the CRU.
It's not a CRU issue. I'm not saying the patcher doesn't need to be updated. I'm saying the patcher is still finding the same values that it always has, so this has to be a new change somewhere in the driver, but I don't have a new enough NVIDIA card to test the newest drivers. I will see about getting a newer video card, but there's no guarantee I will find a way around this.
No problem. Take your time.
I finally got a new enough NVIDIA card to test the latest drivers. The good news is the new limit is patchable. It turned out to be 340 MHz like I suspected. I've updated the patcher to find the new limit. I'm calling it the TMDS limit.
https://www.monitortests.com/nvlddmkm-patcher-1.4.4.zip
Thanks! Can put off buying a display port gaming monitor a bit longer.
Thank you very much for the update.
(12-01-2018 06:10 PM)ToastyX Wrote: [ -> ]I finally got a new enough NVIDIA card to test the latest drivers. The good news is the new limit is patchable. It turned out to be 340 MHz like I suspected. I've updated the patcher to find the new limit. I'm calling it the TMDS limit.
https://www.monitortests.com/nvlddmkm-patcher-1.4.4.zip
Wonderful! Thank you so much!
(12-01-2018 09:44 PM)bigwest Wrote: [ -> ]Thanks! Can put off buying a display port gaming monitor a bit longer.
You are in the same boat as me!
Sorry if this is a newbie question, but if I'm on a laptop with integrated graphics as the primary card, but also have discrete graphics, would this patch help me? If it changes anything I'm also using an external monitor.
(01-13-2019 01:36 AM)ArduinoBen Wrote: [ -> ]Sorry if this is a newbie question, but if I'm on a laptop with integrated graphics as the primary card, but also have discrete graphics, would this patch help me? If it changes anything I'm also using an external monitor.
No, the integrated GPU handles the resolutions.
I don't know why but mine isn't working like it was supposed to. I always update my GPU and than redo the pixel patch thing and use the res (75hz) previously set up but today was different. I updated my gpu and did the pixel patch and didn't work. I've downloaded the version 1.4.4 and redid the steps and started working after reseting my displays on CDU but still doesn't work with 75hz like it used to and with 74hz I get weird colors and little dots on the screen.
I'm on patch 418.81