(02-10-2019 11:38 PM)hupfer Wrote: [ -> ]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
75 Hz at what resolution? What monitor is this? Are you using DVI or HDMI?
(02-11-2019 01:34 PM)ToastyX Wrote: [ -> ] (02-10-2019 11:38 PM)hupfer Wrote: [ -> ]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
75 Hz at what resolution? What monitor is this? Are you using DVI or HDMI?
1920x1080
DVI
AOC 2269W
Sorry for delay
I've managed to get it stable at 74hz, but I still find weird that it can't do 75hz anymore.
(02-13-2019 05:46 AM)hupfer Wrote: [ -> ]I've managed to get it stable at 74hz, but I still find weird that it can't do 75hz anymore.
Are you using the same timing parameters as before? If 74 Hz works and the pixel clock is greater than 165 MHz, then the patch is working.
Hey man, so I just switched from a Gtx 1060 to a Rtx 2060 and somehow, my 74hz overclock just doesn't work anymore. I'm using the exact same driver and versions of CRU/NVPatcher. CRU displays my max pixel clock as 150MHz, anything I can do? Maybe go back to an older driver?
EDIT: I've just gone back to 417.71 (both the first driver for the 2060 and the the last driver specified by NVPatcher 1.4.4 to 100% work) and it still doesn't work, any clues on why it might be? Maybe a compatibility issue specific with the Rtx 2060? Is there any workaround to this that I can do by myself or something?
(02-18-2019 09:28 PM)gran172 Wrote: [ -> ]Hey man, so I just switched from a Gtx 1060 to a Rtx 2060 and somehow, my 74hz overclock just doesn't work anymore. I'm using the exact same driver and versions of CRU/NVPatcher. CRU displays my max pixel clock as 150MHz, anything I can do? Maybe go back to an older driver?
EDIT: I've just gone back to 417.71 (both the first driver for the 2060 and the the last driver specified by NVPatcher 1.4.4 to 100% work) and it still doesn't work, any clues on why it might be? Maybe a compatibility issue specific with the Rtx 2060? Is there any workaround to this that I can do by myself or something?
So the same driver version worked with the GTX 1060 but not the 2060? When you say it doesn't work anymore, what happens when you try 74 Hz?
(02-19-2019 02:52 AM)ToastyX Wrote: [ -> ] (02-18-2019 09:28 PM)gran172 Wrote: [ -> ]Hey man, so I just switched from a Gtx 1060 to a Rtx 2060 and somehow, my 74hz overclock just doesn't work anymore. I'm using the exact same driver and versions of CRU/NVPatcher. CRU displays my max pixel clock as 150MHz, anything I can do? Maybe go back to an older driver?
EDIT: I've just gone back to 417.71 (both the first driver for the 2060 and the the last driver specified by NVPatcher 1.4.4 to 100% work) and it still doesn't work, any clues on why it might be? Maybe a compatibility issue specific with the Rtx 2060? Is there any workaround to this that I can do by myself or something?
So the same driver version worked with the GTX 1060 but not the 2060? When you say it doesn't work anymore, what happens when you try 74 Hz?
Yup, exactly, 418.91 worked flawlessly on my 1060, it doesn't on my 2060. Not sure what else it could be, to be honest, already tried the first and last driver from the 2060 and none of those work.
Screen goes black and says no signal, probably because I'm exceeding the 150MHz pixel clock limited stated by CRU (The pixel clock limit should be much higher after applying the patch, right?).
Also, thanks for taking your time to reply, I bought the 2060 to enjoy 74hz gaming without sacrifices on all games, so you replying to my issue is grealy appreciated man, not playing on 74hz when I bought a card for that is suffering haha.
Please do let me know if there's anything I can do, I'd love to get this problem out of the way as quickly as possible to enjoy my new GPU.
Ok so I tried "LCD Reduced" with 74hz and it does work now (not sure this is a fix, last time I tried LCD reduced I noticed some artifacts in my display), any idea of what's going on? I've never needed to use LCD Reduced to get my usual 74hz overclock.
(02-19-2019 02:57 AM)gran172 Wrote: [ -> ]Screen goes black and says no signal, probably because I'm exceeding the 150MHz pixel clock limited stated by CRU (The pixel clock limit should be much higher after applying the patch, right?).
The limit is 165 MHz pixel clock, but it should send a dual-link signal beyond that, which the monitor probably can't handle without the patch. "LCD reduced" keeps the pixel clock from going above 165 MHz at 74 Hz. It sounds like there might be another limit that only affects RTX cards. Does your RTX 2060 have a DVI port or are you using an adapter?
No sir, no DVI port on my 2060, it's connected via HDMI and using a converter to DVI-D into my monitor. Is this fixable, btw?
(02-19-2019 05:48 PM)gran172 Wrote: [ -> ]No sir, no DVI port on my 2060, it's connected via HDMI and using a converter to DVI-D into my monitor. Is this fixable, btw?
I don't know because I don't have an RTX-series card. Try repatching with this:
https://www.monitortests.com/nvlddmkm-patcher-test.zip