Blur Busters Forums

Hi guys I'm hoping someone can give me some advice here. I've had my Swift for a few months now and the only problem I have started post 344.80 drivers (start of the r346 branch). The problem is I get a full screen "Blinking" effect when the monitor is at 144Hz with G-Sync ON and the 143.5FPS is reached or stressed on the monitor, Its as if a black frame is getting thrown up every few seconds. This happens in all games and benchmarks but only when the 143.5 FPS limit is reached and only with G-Sync ON.
I have tried different cables (no difference) and even rolled back to 344.80 and before to double check where the problem doesn't show. I have also noticed that the blinking effect doesn't happen in Single GPU or when 60Hz or 120Hz is selected. I play allot of BF4 and using the games own FPS limiter @ 135FPS works and stops it but for some reason Rivatuner's doesn't.
Is this just a case of a conflict with Tri SLI and G-Sync when the driver is men't to regulate the frame barrier but fails?

Thanks in advance

Tried :
Rotating cards
Windows 10
Stock clocks and default BIOS settings
Three different 1.2 Display Port cables of various short lengths
All drivers after 344.80 including Quadro and Mobile

What game is having the problem? Have you tried lowering the cap down a little?

Hi lexlazootin, thanks for getting back to me. It happens in all games and benchmarks, basically the worst time for it happening is on a games menu screen or a lower res benchmark where the frame rate can be very high and would normally push past the 143.5 FPS limit but G-Sync holds it back. I did try Rivatuner and DxTory to cap the frame rate lower but it still happens, if I use a games internal caper like BF4's it doesn't happen, there must be a difference between internal and external limiters. I'd have RMA'd the monitor by now but Single GPU works perfect and the drivers before and including 344.80 are fine.
I've reported this to Nvidia twice now and also tried to get help on the Asus ROG site but no one got back to me.

Thanks

I did try Rivatuner and DxTory to cap the frame rate lower but it still happens

I want to recreate the issue too see if it happens to me too but I haven't played any games that have this issue, that's why I want to know what you are playing.

I did try Rivatuner and DxTory to cap the frame rate lower but it still happens

How low do you go on the capping?

lexlazootin wrote:

I did try Rivatuner and DxTory to cap the frame rate lower but it still happens

I want to recreate the issue too see if it happens to me too but I haven't played any games that have this issue, that's why I want to know what you are playing.

I did try Rivatuner and DxTory to cap the frame rate lower but it still happens

How low do you go on the capping?

At first I tried with Rivatuner capping to 143FPS, still got the blinking then I went down to 135FPS but it still gave me the issue. I find it strange that a games internal limiter (BF4) stops the blinking but an external limiter doesn't. The best way for me to reproduce the issue is to run 3DMark or a game like CS-GO where the frame rate would be far over the 143.5FPS limit for G-Sync and watch how the driver (I hope it is) struggles to regulate this and throws up a random black frame every few seconds.
Like I said single GPU works no problem and the last working driver that didn't do this was 344.80. I can only think its my Tri setup conflicting with the G-Sync limit of the monitor, but I was just needing someone to verify this if possible or advice to help it.
Thanks for the replies though lexlazootin, much appreciated.

CS:GO has a internal fps limiter as well as most source games. Open up console and type "fps_max 130".

I know it's not a fix but in the nvidia control panel you might be able to disable your gpus when running games that have this issue until they fix it.

lexlazootin wrote:CS:GO has a internal fps limiter as well as most source games. Open up console and type "fps_max 130".

I know it's not a fix but in the nvidia control panel you might be able to disable your gpus when running games that have this issue until they fix it.

Ah, thanks for the tip. Looks like I'll just have to wait and see if the drivers get sorted out or roll back to 344.80 or even just set at 120Hz. A shame to have a monitor which I do personally think is very good but expensive and get problems from the drivers side of things.
Thanks

I got this same issue in Postal 2 and Halo: Spartan Assault with the 350.12 drivers but it didn't happen in any of the other games I tried. Rolling back to the previous driver fixed it so it appears to be a driver issue.