Is overclocking more successful with a lower resolution?
Is overclocking more successful with a lower resolution?
I don't care if I have to lower my resolution to 800x600, I just want to experience that 200hz on my 144hz monitor
- Chief Blur Buster
- Site Admin
- Posts: 11670
- Joined: 05 Dec 2013, 15:44
- Location: Toronto / Hamilton, Ontario, Canada
- Contact:
Re: Is overclocking more successful with a lower resolution?
It depends.
Sometimes it can succeed. But the success rate is not necessarily higher than native resolution.
You can try all methods, to figure out how a monitor overclocks:
- Simply raising Hz
- Reduced horizontal totals too (transfer bandwidth from HBI to increasing Hz)
- Reduced vertical totals too (transfer bandwidth from VBI to increasing Hz)
- Reduced bit depth (e.g. 6bpc) too (transfer bandwidth from color depth to increasing Hz)
- Reduced resolution too (transfer bandwidth from high resolution to increasing Hz)
- Enabling/disable of instant modes or low-lag modes
- Enabling/disable of HDR modes
- Enabling/disable of VRR modes
- ToastyX CRU versus NVIDIA Control Panel versus AMD Catalyst Control Center
- GPU scaling versus monitor scaling
- Disabling of features that interfere with overclocking
- Out-of-Range defeat hacks (dismiss that firmware popup message & force monitor to try to sync)
Sometimes you need to focus on a different pre-requisite, to figure out how to trick a display into overclocking successfully.
Most of the time, lowering resolution to overclock is not usually successful on modern high-bandwidth connections such as DisplayPort 2.0 and the overhead of a scaler can produce a weak link to overclocking. You do need to use ToastyX CRU instead of NVIDIA Custom Resolution sometimes, to force native resolution from the GPU, rather than GPU scaling.
Sometimes it can succeed. But the success rate is not necessarily higher than native resolution.
You can try all methods, to figure out how a monitor overclocks:
- Simply raising Hz
- Reduced horizontal totals too (transfer bandwidth from HBI to increasing Hz)
- Reduced vertical totals too (transfer bandwidth from VBI to increasing Hz)
- Reduced bit depth (e.g. 6bpc) too (transfer bandwidth from color depth to increasing Hz)
- Reduced resolution too (transfer bandwidth from high resolution to increasing Hz)
- Enabling/disable of instant modes or low-lag modes
- Enabling/disable of HDR modes
- Enabling/disable of VRR modes
- ToastyX CRU versus NVIDIA Control Panel versus AMD Catalyst Control Center
- GPU scaling versus monitor scaling
- Disabling of features that interfere with overclocking
- Out-of-Range defeat hacks (dismiss that firmware popup message & force monitor to try to sync)
Sometimes you need to focus on a different pre-requisite, to figure out how to trick a display into overclocking successfully.
Most of the time, lowering resolution to overclock is not usually successful on modern high-bandwidth connections such as DisplayPort 2.0 and the overhead of a scaler can produce a weak link to overclocking. You do need to use ToastyX CRU instead of NVIDIA Custom Resolution sometimes, to force native resolution from the GPU, rather than GPU scaling.
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter
Forum Rules wrote: 1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
2. Please report rule violations If you see a post that violates forum rules, then report the post.
3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!