Some monitor-generic background information as I’m getting annoying blankings occasionally on many ASUS and ViewSonic panels too so it’s an industry wide problem too;
One mitigation I’ve done on multiple vendor monitors is using ToastyX CRU to raise the minimum refresh rate from 48Hz to approximately 55Hz (for 144Hz VRR) or 65Hz (for 240Hz VRR). This solves a lot of blanking problems.
LFC penalty is negligible on 240Hz VRR monitors, and sometimes LFC has superior quality to non-LFC when the VRR range is unusually wide (e.g. 30Hz-360Hz).
In these events, a generous bump-up of the LFC threshold is needed to improve quality (color quality, overdrive quality, inversion-artifact quality, flicker, etc). Stutters from LFC is negligible as the LFC stutterwidth is based on max Hz.
The halftime of a 240Hz refresh cycle (2ms halftime, the stutter penalty) is lost in the motion blur of 33ms frametimes (30fps). Thus, LFC stutter penalty is negligible for ginormous VRR ranged monitors, and it’s better to raise the minimum VRR Hz.
I should add that the ToastyX trick usually works more reliably on AMD cards on FreeSync panels, than with NVIDIA cards on G-SYNC panels (ignores ToastyX EDID override). However, this is sometimes confusing when it comes to FreeSync on NVIDIA cards.
The industry standard 48 Hz can be adjusted to a different threshold in the EDID (either in native hardware, or via a Windows registry EDID override created by ToastyX CRU app), preferably between common framerates. A 65Hz threshold forces 24fps material to LFC 3x per refresh cycle, and 72Hz overdrive/inversion is usually superior.
Raising the FreeSync min Hz to “65” also forces 60fps material to automatically LFC at 120Hz, which can be superior for 60fps material because 120fps on most FreeSync panels have better VRR overdrive. Now, that being said, for proper LFC function you want max Hz to be at least 2.5x min Hz, so the threshold should be rated to 55 for 144Hz panels, instead of 65, when creating a custom EDID override for VRR ranges.
But it is the firmware responsibility to do its best to minimize this issue, such as adding hidden low-Hz support (e.g. panel able to function at lower VRR Hz even suboptimally without blanking, in an “emergency” if LFC is accidentally not enabled).
Panels with dynamic overdrive (G-SYNC native) can work better to even lower Hz without LFC than panels with fixed overdrive during VRR. This is another consideration on deciding the proper min-Hz threshold, because at a certain panel-specific crossover point, LFC becomes superior to native Hz.
Many other VRR Panels can go down to approx 30-35 Hz instead of 48Hz, even though VRR range is 48Hz+. This gives a safety margin if LFC accidentally does not activate in graphics drivers during frametimes longer than 48fps.