NVIDIA Pixel Clock Patcher
|
03-23-2014, 08:24 AM
Post: #281
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(03-22-2014 03:34 PM)apav Wrote: Oops I should've mentioned that I tried that, and nothing changed except that the nvidia icon disappeared from my tray.If you use CRU, you must either disable the extension block and remove GeForce Experience (and Samsung Magician if you have that), or you must enable the extension block and import blank-extension.dat. If that's not working, then you need to patch the driver. Those are the only reasons the resolutions wouldn't be available. |
|||
04-06-2014, 07:33 AM
Post: #282
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Hi Toasty.
I tried the 1.25 and 1.24 patcher with 331.40 and everything works fine but any other recent driver and i still get the freeze that i showed you is the Deus ex video that i uploaded. I get this with every game. There is a new nvidia driver coming tomorrow the 337.50. Hopefully this new driver and your fixes will work better than the previous otherwise its back to 331.40. Something has changed as everything was working fine for t he last 16 months but in the last 2 months im getting this freezing when running at 100hz as i explained earlier. |
|||
04-07-2014, 11:38 AM
Post: #283
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Hey toasty will the latest patcher work with the new 337 driver? thanks
|
|||
04-07-2014, 03:12 PM
Post: #284
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
The 1.25 patcher does not find the SLI/HDMI value on the 337.50 driver.
|
|||
04-07-2014, 08:36 PM
Post: #285
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Hey guys,. Will I need to patch and download driver in order to overclock my qnix 1440p monitor? I have SLI 780 Ti classifleds. I download the CRU already and made a 96hz profile.
|
|||
04-07-2014, 09:25 PM
Post: #286
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(04-07-2014 08:36 PM)cusco Wrote: Hey guys,. Will I need to patch and download driver in order to overclock my qnix 1440p monitor? I have SLI 780 Ti classifleds. I download the CRU already and made a 96hz profile.Does it work with CRU without patching the driver? If not, you need the regular patch. The full patch shouldn't be needed for the GTX 780 Ti cards. |
|||
04-07-2014, 09:28 PM
Post: #287
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(04-07-2014 11:38 AM)cubadoo23 Wrote: Hey toasty will the latest patcher work with the new 337 driver? thanks (04-07-2014 03:12 PM)PFS Wrote: The 1.25 patcher does not find the SLI/HDMI value on the 337.50 driver.The SL-DVI/HDMI limit is not needed for overclocking 1440p monitors, and the SLI limits still work with 64-bit. I have updated the patcher to fix the SL-DVI/HDMI limit for 64-bit and the SLI limits for 32-bit. |
|||
04-07-2014, 09:44 PM
Post: #288
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(04-07-2014 09:25 PM)ToastyX Wrote:(04-07-2014 08:36 PM)cusco Wrote: Hey guys,. Will I need to patch and download driver in order to overclock my qnix 1440p monitor? I have SLI 780 Ti classifleds. I download the CRU already and made a 96hz profile.Does it work with CRU without patching the driver? If not, you need the regular patch. The full patch shouldn't be needed for the GTX 780 Ti cards. How can I tell if it worked? Lol sorry for being a noob. I also went into the NVIDIA and did a custom profile in there also. And about the moniter driver should I download it and install it? |
|||
04-07-2014, 09:50 PM
Post: #289
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(04-07-2014 09:44 PM)cusco Wrote: How can I tell if it worked? Lol sorry for being a noob. I also went into the NVIDIA and did a custom profile in there also. And about the moniter driver should I download it and install it?If it worked, you should be able to set the refresh rate. If you're using CRU, don't add the custom resolution using the NVIDIA control panel. Either use CRU, or use the NVIDIA control panel, not both. You only need the monitor driver if you're using the NVIDIA control panel. |
|||
04-07-2014, 09:53 PM
Post: #290
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(04-06-2014 07:33 AM)PFS Wrote: Hi Toasty. You still haven't clarified exactly when the problem happens. The SLI limit is supposed to be 400 MHz, but you said the problem was happening below that. If that's the case, then you're having a different problem that nobody else has reported. If you were hitting the SLI limit, the problem should only happen if the pixel clock is greater than 400 MHz. If you're having the problem below that, then I need to know the exact the pixel clock where the problem starts happening to figure out if this is a limit that could be patched. So far you've given me different answers, which makes this hard to figure this out. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 52 Guest(s)