Talk about overclocking displays at a higher refresh rate. This includes homebrew, 165Hz, QNIX, Catleap, Overlord Tempest, SEIKI displays, certain HDTVs, and other overclockable displays.
Alright I finally got this figured out. My one hiccup is that I have a password to launch windows so I have out of range before I can get windows to launch. Do I have to blind-type the password every time now? Has there been a more permanent solution found? Thanks.
Well, you can enable auto login through the Netplwiz tool provided by Windows (press Winkey+R, enter "netplwiz" and uncheck the "require username and password" checkbox. When you apply the changes, Windows will ask for the password to use for auto login.)
That way Windows will boot directly to the desktop, logged in already.
Hello, any one Know how to overclock a xl2411p v9 firm 2019 ? Tried all method but won't go over 150hz.
Ty for reply.
Ty for reply.
I've tried this, and some more things, but I can't seem to get past 150hz without the "Out of range" error. Even OorBuster and Anti-OutOfRange did not help. I am using a Xl2411p connected to a RX 580 via a DisplayPort 1.4.Chief Blur Buster wrote: ↑12 Jul 2019, 18:56Successful Universal 144Hz -> 220Hz Overclock For BenQ
For BenQ/ZOWIE 144Hz 1080P Monitors
200Hz+ Overclock Successes So Far
- XL2720 at 220Hz
- XL2720Z at 220Hz
- XL2420G at 220Hz
- XL2420T at 230Hz
- XL2536 at 200Hz
- XL2430T at 215Hz via DP
- XL2411Z at 200Hz via DVI
- XL2411Z at 210Hz via DVI using ToastyX Pixel Patcher (uncap DVI)
Record: ~260-268 Hz (and a glitched 440Hz!) on an old BenQ XL2420T, see link to photos
No S-Switch Needed!
Credit to forum member loopy750 for discovering the S-Switch 220Hz Overclock Hack for BenQ 144Hz monitors!
However, it's possible to overclock without the S-Switch! You heard about this on Blur Busters first.
And, yes, it lowers lag to less than 144Hz
Potentially Supported Models
Most 144Hz 1080p BenQ / ZOWIE monitors with DisplayPort between 2013-2019.
XL2420, XL2420T, XL2420Z, XL2420G (Classic Engine), XL2420P, XL2411P, XL2430T
-- You need 144Hz and 1080p and DisplayPort in your BenQ/Zowie
-- Easiest with NVIDIA GPU
-- This won't work with 240Hz BenQs
-- This won't work with 1440p BenQs
-- Works with DisplayPort (~220Hz) and DVI (~200Hz). Try both ports, one may overclock higher than other.
-- IMPORTANT: For old XL2720Z (V2) do NOT combine blur reduction with overclock unless you know what you're doing (strobe backlight voltage boost bug in pre-2015 firmwares). If you dare try, set Persistence / Strobe Duty to 5 or less BEFORE you overclock.. This risk doesn't apply if you are not using motion blur reduction.
The "Out Of Range" Defeat Trick
To Improve 220 Hz Colors And Sharpness
- You need two monitors to make this easy initially
- Set your BenQ/Zowie as primary.
- Download [url=https:///lib/softmccs.shtm]Entech Taiwan SoftMCCS[/url]
- Launch SoftMCCS onto 2nd monitor (the one you're not overclocking)
- Launch NVIDIA Control Panel onto 2nd monitor
- Select the 220 Hz custom mode in NVIDIA Control Panel (create it if not already created)
- Your BenQ will immediately go OUT OF RANGE
- Now in SoftMCCS (displayed on your 2nd monitor), click "OSD language - 0xCC" -> Activate
- Next, click "Display application - 0xDC" -> Activate.
- Doing both of the above will dismiss the OUT OF RANGE watchdog and your 220Hz will appear!
- For a long term fix, use an automatic utility such as /hleVqq/OorBuster (this makes SoftMCCS unnecessary) or a more recent fork such as /Chopper1337/OORbuster
You will have 6-bit color depth on the DisplayPort cable but the NVIDIA GPU will be automatically doing GPU-side temporal dithering (DRC) to convert 6-bit to 8-bit. It might not always be as good quality as the monitor DRC but much better looking than 6-bit color. The GPU DRC looks nearly as good as monitor DRC if using Movie Mode.
- In SoftMCCS, select "Movie" radio button (nothing will happen until step 3)
- Click "Display application - 0xDC" -> Activate.
- 220Hz becomes visible but sharpness will go out of whack. Slide "Sharpness" to "5"
- The picture looks much better color quality, and graident looks fully 8bit (via GPU soft-DRC)
You will have to repeat the important "OSD language" -> "0xCC" -> "Activate" in SoftMCCS steps every time you switch back into 220Hz. To prevent having to do this too many times repeatedly, make sure you have SoftMCCS running on your 2nd monitor and make sure your Desktop is 220Hz before you launch your game in 220Hz. Then Windows/Game is not doing any mode switches. Do not Alt+Enter / Alt+Tab. The single most important step is SoftMCCS window open on 2nd monitor, and ready to click "OSD language - 0xCC" -> Activate .... whenever you see an OUT OF RANGE message pop up on your monitor.
Also, another tip is to create a mode such as 1920x1079 whose only refresh rate is the overclocked Hz. That way, games automatically have to use the overclocked Hz, and also can help reduce the number of mode switches (which can cause the OUT OF RANGE issue to come back, and need resetting again).
A utility was written by hleV to reset the OUT OF RANGE every time a mode switch occurs. The utility monitors for mode switches, and automatically dismisses the OUT OF RANGE via DDC commands: ./hleVqq/OorBuster
Disclaimer: Blur Busters disclaims responsibility for any damages. Do at own risk. It works on my BenQ XL2720Z, but your mileage will vary.
Post Your Success Reports Here
Does anyone have further advice on what I could possibly try?
Any help is appreciated.
Exact same problem here.Xefaxe wrote: ↑09 Jul 2021, 10:47Greetings everyone!
I'm trying different ways to go above 150Hz for a XL2411P but in vain.
I tried the method with a second monitor and running SoftMCCS or only using OorBuster.
Also, I used NVIDIA Control Panel or CRU, and already patched with NVLDDMKM Patcher.
I'm currently using a Display Port cable.
Can anyone of you who already had a sucessfull OC with the same monitor tells me what exactly to do and maybe share me his CRU config?
Thank to all for your advices and good luck in your overclocking tests!
Did everything you have done but with the AMD equivalent, sadly to no avail.
Have you found a fix yet?