GPU Driver Upscaling NIS / RSR Not Working? Fullscreen Mode, Resolution & Double-Upscaling Diagnosis Guide

Key Takeaway
Driver-level upscaling differs from DLSS or FSR built into a game. NVIDIA Image Scaling and AMD Radeon Super Resolution work only on a supported card and driver, in the right fullscreen mode, with the game rendering below the monitor's native resolution. The switch being on is not proof; check the NIS indicator, or compare FPS before and after for RSR.
The Opposite Claim: The Driver Can Add Upscaling, But Not DLSS
A companion guide on this site explains that a driver cannot add DLSS to a game that does not support it. That statement is correct, and it is also the starting point for this guide — because the driver can add something else. NVIDIA Image Scaling (NIS) and AMD Radeon Super Resolution (RSR) are driver-level upscalers, and they are not DLSS or FSR. They were designed precisely for the thousands of games that have no built-in upscaling option, and they do not need the game to support them. Confusing the two kinds of upscaling leads to the wrong diagnosis: a reader who applies the DLSS rules to NIS or RSR will conclude that the feature cannot work at all, or will look for the switch inside the game where it does not exist.
The core claim of this guide is simple: turning NIS or RSR on does not mean it is running. Driver-level upscaling works only when three conditions are met at the same time — a supported card and driver, the right fullscreen mode, and a game rendering below the monitor's native resolution. If any one of those conditions is missing, the upscaler stays quietly inactive, with no error message. The game runs normally, the switch shows as on, and nothing changes. That silence is not a fault in the card. It is the feature waiting for conditions that have not been met.
This guide covers Windows 10 and Windows 11 desktop computers, NVIDIA Image Scaling on GeForce graphics cards and AMD Radeon Super Resolution on Radeon graphics cards, in games that are running normally. It deals with the symptom "enabled but no change" — no change in frame rate and no change in the picture — and with the related symptom "the option does not appear or cannot be enabled." Picture quality problems such as blurriness, ghosting, or flicker belong to a different guide, as do crashes that happen when a graphics feature is switched on.
What NIS and RSR Are: Driver-Level Spatial Upscaling
NVIDIA describes Image Scaling as a driver-based spatial upscaler and sharpener for GeForce GPUs, for all games. AMD describes Radeon Super Resolution as an in-driver upscaler powered by FidelityFX Super Resolution technology, designed to improve performance in thousands of games that lack integrated upscaling technology. Both descriptions point to the same mechanism: the driver takes a picture the game has already drawn at a lower resolution and enlarges it to fill the monitor, applying sharpening as part of the process.
That mechanism is different from DLSS and FSR built into a game in three ways, and the three ways need to be kept separate.
| Difference | Built-in DLSS / FSR in a game | Driver-level NIS / RSR |
|---|---|---|
| Who does the upscaling | The game engine itself, using the game's own data such as motion vectors and depth | The driver, looking only at a single finished flat picture |
| Does the game need to support it | Yes — the game must have a built-in DLSS or FSR option | No — the driver layer applies to games with no built-in upscaling |
| Quality ceiling | Higher, because temporal reconstruction uses data from several frames | Lower, because spatial upscaling uses only one frame, on a principle similar to FSR 1.0 |
The counter-intuitive point follows from that table. It is true that a driver cannot add DLSS to a game that does not support it, because DLSS needs the game's own data and the game's own code. But a driver can add NIS or RSR to that same game, because NIS and RSR do not need the game's data or code — they only need the finished picture. A reader who treats all upscaling as one thing will either expect NIS to behave like DLSS, or will dismiss NIS as impossible because DLSS is impossible in that game. Both conclusions are wrong, because the two are different technologies with different requirements.
The lower quality ceiling is also part of the honest description. Because NIS and RSR work from a single frame, they cannot reconstruct detail the way a temporal method can. They are a way to gain frame rate in a game that has no better option, not a replacement for built-in DLSS or FSR where that option exists. That distinction matters again later in this guide, when a game that already has built-in FSR is discussed.
The Five Layers of Suspicion
Once the feature is identified as NIS or RSR, the fault can be placed in one of five layers. Each layer has its own decisive test, and the order matters: the layers are arranged from eligibility and switch position, through display mode and resolution, to conflicts with other features. The processor bottleneck and frame-rate cap checks come last, because they only matter once it has been shown that the upscaler is actually running.
| Layer | What it covers | Decisive test |
|---|---|---|
| 1. Support layer | The card model or driver version does not support NIS or RSR at all, so the option never appears | NIS: a GeForce card with driver branch R495 or above. RSR: a Radeon RX 5000 series card or above with a full Adrenalin installation (see the version note below). If the system does not qualify, the option not appearing is normal, not a fault. |
| 2. Switch layer | The switch is in a different place for each brand, and there are global and per-game layers | NIS: NVIDIA Control Panel, Manage 3D Settings, Image Scaling, global or per-program. RSR: AMD Software, Gaming, Graphics, Radeon Super Resolution, global or per-game. Changing the wrong layer is the same as changing nothing. |
| 3. Mode layer | The game's display mode is wrong, so the upscaler never starts | NIS requires exclusive fullscreen — not borderless windowed, not fake fullscreen. RSR: the current AMD guidance allows exclusive fullscreen or borderless fullscreen, while older documents mentioned exclusive fullscreen only (see the version note below). If exclusive does not work, try borderless fullscreen. |
| 4. Resolution layer | The game is still rendering at the monitor's native resolution, so there is nothing to enlarge | Choose a game resolution below the monitor's native resolution. AMD states plainly that RSR will remain inactive until the game's resolution falls below the monitor's native resolution. At native resolution, NIS only sharpens; it does not upscale. |
| 5. Double-upscaling and conflict layer | Built-in upscaling, dynamic resolution, or another driver feature is running at the same time and cancels or conflicts with NIS or RSR | Turn off the game's built-in FSR or DLSS, turn off dynamic resolution, and check for mutually exclusive driver features such as integer scaling, SLI, or Surround. Change only one thing at a time. |
A sixth consideration sits outside the five layers but belongs in every diagnosis: where the bottleneck actually is. If the processor is the limiting factor, lowering the rendering resolution will not make the processor faster, and the frame rate will not move even when the upscaler is working correctly. A frame-rate cap or vertical sync can also absorb the gain, so that the upscaler is running and the frame rate stays exactly where the cap holds it. Those two checks belong after the indicator or the numeric comparison has shown whether the upscaler is running at all. Checking them first answers the wrong question.
The NIS Indicator: Green and Blue Mean Different Things
NVIDIA provides an overlay indicator for NIS, shown at the top left of the screen with the letters "NIS." Its colour is the single most important verification tool in this guide, and it must be read as a diagnostic result, not treated as decoration. The indicator should be enabled in the Image Scaling settings before testing, so that it is visible when the game is running.
- Green: NIS is doing upscaling and sharpening. The upscaler is genuinely running.
- Blue: NIS is doing sharpening only, with no upscaling. This usually means the game is still rendering at its native resolution, so there is nothing to enlarge.
- No indicator at all: NIS has not started. The fault is in the switch layer, the mode layer, or the support layer.
The colour turns a vague feeling — "it does not seem to be doing anything" — into a reading that points at a layer. Green with a frame rate that does not move points at the bottleneck or a frame-rate cap in the fifth layer. Blue points at the resolution layer: the game resolution must be lowered below the native resolution. No indicator at all points back to the switch, the mode, or the eligibility check. Do not judge NIS by feeling. Look at the indicator first, and let its colour decide which layer to investigate.
One further point about the indicator: at the monitor's native resolution, sharpening still happens, and the indicator shows blue. That is the designed behaviour, not a fault. A reader who expects green at native resolution will conclude that NIS is broken, when it is in fact doing exactly what it is supposed to do at that resolution — sharpening a picture that has nothing to enlarge.
The RSR Check: No Indicator, So Use Numbers
AMD provides no NIS-style indicator for RSR. There is no green or blue marker to look for, and no such marker should be invented or described. A guide that tells a reader to look for an RSR indicator would be sending them to search for something that does not exist, and would waste the whole diagnosis. The two brands have different verification methods, and they must be kept separate.
RSR has to be verified by numeric comparison. Use the same game, the same scene, and the same quality settings, and measure twice: once with RSR off, and once with RSR on. Record the frame rate and the graphics processor usage each time, and also record whether the game's rendering resolution has genuinely dropped below the monitor's native resolution. If the frame rate and the usage move together with the resolution drop, RSR is running. If nothing moves and the resolution has not dropped, the fault is in the earlier layers. If the resolution has dropped but the frame rate has not moved, the bottleneck or a cap is the more likely explanation.
The comparison only works if the conditions are held constant. A different scene, a different quality setting, or a different part of the game between the two measurements makes the numbers incomparable. Pick one repeatable scene, stand in the same place, use the same settings, and measure both states there. A single measurement with RSR on, with nothing to compare it against, proves nothing on its own.
Two Version Differences That Must Be Recorded Honestly
Two conflicts come from AMD's own documents, and this guide records them as they stand rather than choosing one side and presenting it as absolute. A reader who is given only one number and finds a different number in the official documentation will lose trust in the whole guide, so the difference itself is part of the information.
First, the minimum driver version for RSR. AMD's feature page gives Adrenalin 22.3.1 or above. AMD's settings FAQ, updated on 2025-06-25, gives Adrenalin 22.7.1 or above with a full installation. The two official pages do not agree. This guide uses the newer FAQ figure of 22.7.1 as the reference, and the reader should check the documentation that matches the version actually installed, rather than treating either number as an absolute threshold that applies to every version.
Second, the fullscreen mode for RSR. Older AMD documents mentioned exclusive fullscreen only. The 2025 FAQ states that exclusive fullscreen or borderless fullscreen both work, and notes that in borderless mode RSR automatically lowers the desktop resolution. This guide follows the newer FAQ wording, with one practical addition: if RSR still does not start in exclusive fullscreen, try borderless fullscreen. Neither "borderless always works" nor "borderless never works" should be stated as a rule, because the official wording itself has changed over time.
The same honesty applies to the NIS side. NVIDIA's official guidance states that NIS requires exclusive fullscreen, not borderless windowed mode and not fake fullscreen. For a game with no fullscreen mode at all, the desktop resolution can be set to the same value as the game resolution as an alternative. That alternative belongs to NIS specifically and should not be transferred to RSR as if the two features shared the same rules.
The Resolution Step: The Fork That Decides the Diagnosis
The most important single step in this guide is to set the game to exclusive fullscreen and choose a resolution below the monitor's native resolution. For example, on a 4K monitor, choose 2880×1620 in the game, and NIS will enlarge the picture back to 3840×2160. On a 1440p monitor, choose a lower step such as 1920×1080. The exact step matters less than the direction: the rendering resolution must be below native, or there is nothing for the upscaler to enlarge.
This step is a fork. If the indicator turns green, or the numeric comparison moves, after this step, the upscaler is running and the earlier layers were the problem. If nothing changes after this step, the fault is in the switch, the mode, or the eligibility layer, and those need to be re-checked rather than the resolution being lowered further and further. Lowering the resolution again and again without a result does not help; it only makes the picture worse while the real cause stays untouched.
Two related mistakes belong here. First, choosing a lower resolution in the Windows desktop settings is not the same as choosing a lower resolution inside the game. The game's rendering resolution is what the upscaler sees, and that is the number that must be below native. Second, a resolution that is only slightly below native, such as one step down in a list that is itself scaled, may not be what it appears to be. Check the number the game is actually using, not the number that was intended.
Double Upscaling: Built-In FSR Plus Driver RSR
A game that already has built-in FSR should use FSR, not RSR on top of it. AMD's own guidance is that a game with built-in FSR should use FSR, because the result is better than RSR. Running both at the same time does not add the two effects together. It upscales a picture that has already been upscaled, and the result is a softer picture with no extra benefit. The same principle applies in the other direction: a game with built-in DLSS should not also have NIS layered on top of it in the hope of a further gain.
The practical rule is simple. If the game has a built-in upscaler, use that one and leave the driver-level one off. If the game has no built-in upscaler, the driver-level one is the tool for that game. That is the whole purpose of NIS and RSR: they exist for the games that have nothing built in. Using them where a built-in option already exists is using the weaker tool on top of the stronger one.
Dynamic resolution belongs in the same layer. Dynamic resolution changes the rendering resolution during play to hold a target frame rate, and it can pull the resolution back up towards native just as the driver upscaler is trying to work from a lower one. The two fight each other: the dynamic system raises the resolution, the upscaler has less to enlarge, and the net effect disappears. Turn dynamic resolution off while testing NIS or RSR, and only consider turning it back on once the upscaler has been shown to work on its own.
NIS also has a list of unsupported situations in NVIDIA's own documentation: SLI mode, Surround multi-monitor clone mode, tiled displays, Direct Display, virtual reality, and integer scaling mode. Those are boundaries, not the main subject, and they are listed here so that a reader whose setup matches one of them can recognise it rather than diagnosing the upscaler itself. AMD likewise notes that some features inside Adrenalin are mutually exclusive with RSR and cannot be enabled at the same time. The list of such features changes between versions, so this guide does not present a fixed list as if it were complete.
The Seven Steps, In Order
The sequence below is the diagnostic method of this guide. The order is deliberate: eligibility and switch position first, then mode and resolution, then verification, then conflicts, and only then the bottleneck and the cap.
- Describe the fault precisely. Which upscaler — NIS or RSR? Is the symptom "enabled but nothing changes" or "the option does not appear or cannot be enabled"? Which game? Write down the current game resolution, the display mode, and the driver version.
- Check eligibility. For NIS, a GeForce card with driver branch R495 or above. For RSR, a Radeon RX 5000 series card or above with a full Adrenalin installation, using the newer FAQ reference of 22.7.1 while noting that an older feature page gives 22.3.1. If the system does not qualify, the option not appearing is normal, not a fault.
- Check the switch position. Go to the correct location for the brand, and confirm whether the global setting or a per-game setting was changed. A global setting and a per-game setting are different layers, and the per-game setting takes priority for that game. NIS users should confirm that Image Scaling is on and that the indicator is enabled. RSR users should confirm that RSR is on.
- Switch to exclusive fullscreen and choose a lower resolution. For NIS this mode is required. For RSR, try exclusive fullscreen first, and borderless only if exclusive does not work. Choose a game resolution below the monitor's native resolution. This is the most important fork in the whole guide.
- Verify with the indicator or with numbers. For NIS, look at the top-left indicator: green means upscaling and sharpening are running, blue means sharpening only, and no indicator means the fault is in the earlier layers. For RSR, measure frame rate and graphics processor usage before and after in the same scene with the same settings, and confirm the rendering resolution has genuinely dropped.
- Turn off double upscaling. Turn off the game's built-in FSR or DLSS, turn off dynamic resolution, and check for mutually exclusive driver features. Change only one thing at a time and test after each change.
- Rule out the bottleneck and the cap, then know when to stop. Check whether graphics processor usage sits at 95–99% or clearly below that level: a low usage figure with a flat frame rate points at a processor bottleneck, where lowering the resolution cannot help. Check the game's built-in frame-rate cap, the driver cap, and vertical sync, which can hold the frame rate exactly where it is even when the upscaler is running. If all seven steps have been completed and the upscaler still does not work, or if the problem is accompanied by a driver crash, a black screen, or coloured artefacts on screen, stop and bring the machine in with a full record.
That record should include the upscaler involved, the game, the game resolution and display mode, the driver version, the NIS indicator colour or the before-and-after frame-rate figures for RSR, and the exact wording of any error message.
Diagnostic Logic: Reading the Symptom
| Symptom | Most likely cause | Next step |
|---|---|---|
| The NIS or RSR option does not appear at all | The card or driver version does not qualify, or the installation is not a full installation | Check the card model and driver version against the support layer, and confirm a full Adrenalin installation for RSR |
| NIS or RSR is on but nothing changes, and the NIS indicator is blue | The game is still rendering at native resolution, so there is nothing to enlarge | Lower the game resolution below the monitor's native resolution and look at the indicator again |
| NIS is on but no indicator appears at all | The switch, the display mode, or the eligibility layer has failed | Re-check the switch position and the indicator setting, then switch the game to exclusive fullscreen |
| RSR is on but the frame rate and usage do not move | The rendering resolution has not dropped, a second upscaler is running, or the bottleneck is elsewhere | Confirm the actual rendering resolution, turn off built-in FSR and dynamic resolution, then check graphics processor usage |
| NIS or RSR is on and the indicator is green, or the numbers move, but the frame rate stays flat | A frame-rate cap or vertical sync is holding the frame rate, or the processor is the bottleneck | Check the in-game cap, the driver cap, and vertical sync; check whether graphics processor usage is clearly below 95% |
| The option appears for one game but not for another | Upscaling is judged game by game, and an individual game may not start it | Confirm the per-game setting for that game, and do not assume that working in one game guarantees working in another |
| NIS or RSR works in one mode but not in another | The display mode is the cause | Use the working mode, and record which mode works for that game rather than assuming one mode fits all games |
Edge Cases That Are Not This Problem
A picture that turns blurry, shows ghosting, or flickers after upscaling is enabled. That is a picture quality problem, and it belongs to the guide on upscaling picture quality. This guide deals with "enabled but no change," not with a change that looks wrong.
A crash when ray tracing, DLSS, or frame generation is switched on, which goes away when it is switched off. That is a feature-switch crash, and it belongs to the guide on crashes tied to a feature being enabled. This guide deals with a feature that does nothing, not a feature that crashes the machine.
A frame rate that drops after HDR is switched on. That is the cost of HDR, and it belongs to the guide on HDR performance. It should not be diagnosed as an upscaling failure.
A laptop with switchable graphics. NVIDIA's own guidance states that the display must be driven by the NVIDIA graphics processor for NIS to work, and a laptop in hybrid or Optimus mode must first be switched to discrete graphics mode. For RSR, a laptop should use the driver provided by the laptop maker. If the upscaler works on a desktop with the same software but not on a laptop, the question of which graphics processor is driving the display belongs in the investigation.
A game that simply does not start the upscaler. RSR compatibility is not universal. Most games that support a fullscreen mode can use it, but an individual game may be an exception. This guide does not promise that every game will work, and a single game that refuses to start the upscaler should not be treated as proof that the feature is broken everywhere.
Unofficial upscaling tools, downloaded DLSS files, and registry edits for developer diagnostics. None of those belong in this guide. Do not download or replace DLSS files from the internet, do not use an unofficial upscaling tool, and do not edit the registry to enable a developer diagnostic display. Those are not troubleshooting steps.
Six Common Mistakes
- Treating NIS or RSR as the same thing as DLSS or FSR. Driver-level spatial upscaling and built-in temporal upscaling are different technologies. NIS and RSR do not need the game to support them; DLSS and FSR do.
- Treating the switch being on as proof that the feature is running. The switch is only the first step. The fullscreen mode and the rendering resolution must also be right, and the NIS indicator is blue precisely in the case where the switch is on but no upscaling is happening.
- Expecting a frame-rate gain at the native resolution. At native resolution there is nothing to enlarge. NIS will only sharpen, and RSR will stay inactive. The resolution must be below native before either feature can do its work.
- Assuming a lower resolution step always raises the frame rate. If the processor is the bottleneck, lowering the resolution will not make the processor faster. The frame rate stays where the processor holds it, even when the upscaler is working.
- Running built-in FSR and driver RSR together and expecting the effects to add up. AMD's guidance is to use built-in FSR where a game has it, because the result is better than RSR. Running both does not stack the gains; it only makes the picture softer.
- Treating an upscaling feature as a fix for every performance problem. A processor bottleneck cannot be fixed by lowering the rendering resolution, and no single percentage figure describes the gain across different games, resolutions, and cards. Any claim of a fixed percentage gain, without the game, the resolution, and the card it was measured on, should not be used as an expectation.
When to Stop and Bring the Machine In
Stop when all seven steps have been completed and the upscaler still does not work, or sooner if the problem is accompanied by a driver crash, a black screen, or coloured artefacts on screen, because those signs have left this guide and belong to a hardware inspection.
Bring the machine in with a complete record: the upscaler involved, the game, the game resolution and display mode, the driver version, the NIS indicator colour or the before-and-after frame-rate figures for RSR, and any error messages in their exact wording. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
Frequently Asked Questions
How are NIS / RSR different from DLSS / FSR, and why can driver-level upscaling work in games with no built-in support?
Built-in DLSS and FSR are done by the game engine itself, using the game's own data such as motion vectors and depth, so the game must support them. NIS and RSR are done by the driver, looking only at a single finished picture the game has already drawn, so they do not need the game to support them. That is why a driver cannot add DLSS to an unsupported game but can add NIS or RSR to the same game: they are different technologies, and the driver-level ones were designed for the thousands of games with no built-in upscaling.
How do I confirm my graphics card and driver version support NIS / RSR?
For NIS, check that the card is a GeForce card and the driver branch is R495 or above. For RSR, check that the card is a Radeon RX 5000 series card or above and that Adrenalin is a full installation. On the driver version, note that two official AMD pages give different minimum figures: the feature page gives 22.3.1, while the settings FAQ updated on 2025-06-25 gives 22.7.1. Use the newer FAQ figure of 22.7.1 as the reference and check the documentation matching the version actually installed. If the system does not qualify, the option not appearing is normal, not a fault.
Where is the NIS / RSR switch, and what is the difference between the global setting and a per-game setting?
For NIS, the switch is in the NVIDIA Control Panel under Manage 3D Settings, Image Scaling, where it can be set globally or for an individual program. For RSR, it is in AMD Software under Gaming, Graphics, Radeon Super Resolution, where it can be set globally or for an individual game. The global setting is the default for all games; the per-game or per-program setting overrides the global one for that game only. Changing the wrong layer is the same as changing nothing, so confirm which layer was actually changed.
Why is there no change in FPS or picture at all after enabling NIS / RSR?
Because turning the switch on is only the first condition. The game must also be in the right fullscreen mode, and its rendering resolution must be below the monitor's native resolution, or there is nothing for the upscaler to enlarge. At native resolution NIS only sharpens, shown by a blue indicator, and RSR stays inactive. Check the display mode and the game resolution first, then verify with the NIS indicator or with a before-and-after frame-rate comparison for RSR, rather than assuming the feature is broken.
Does a game have to run in exclusive fullscreen for NIS / RSR to work, or does borderless windowed mode work too?
For NIS, exclusive fullscreen is required — not borderless windowed mode and not fake fullscreen. For a game with no fullscreen mode, the desktop resolution can be set to the same value as the game resolution as an alternative. For RSR, the newer AMD FAQ states that exclusive fullscreen or borderless fullscreen both work, while older documents mentioned exclusive fullscreen only. Follow the newer wording, but if RSR still does not start in exclusive fullscreen, try borderless fullscreen. Do not state either mode as a universal rule for RSR, because the official wording has changed over time.
How do I use the NIS indicator (green / blue) to confirm upscaling is actually active, and how do I verify RSR?
Enable the NIS indicator in the Image Scaling settings, then look at the top left of the screen while the game is running. Green means NIS is doing upscaling and sharpening, so the feature is genuinely running. Blue means NIS is doing sharpening only, with no upscaling, which usually means the game is still at its native resolution. No indicator at all means NIS has not started, and the fault is in the switch, the mode, or the eligibility layer. RSR has no such indicator — do not look for one. Verify RSR by measuring frame rate and graphics processor usage before and after in the same scene with the same settings, and confirming the rendering resolution has genuinely dropped below native.
If a game already has FSR / DLSS enabled, should I also enable RSR / NIS?
No. If a game has built-in FSR, use FSR and leave RSR off; AMD's own guidance is that built-in FSR gives a better result than RSR. If a game has built-in DLSS, use DLSS and leave NIS off. Running a built-in upscaler and a driver-level upscaler together does not add the two effects; it upscales a picture that has already been upscaled and makes it softer. NIS and RSR exist for games with no built-in option, and that is where they should be used.
Can dynamic resolution cancel out the effect of NIS / RSR?
Yes. Dynamic resolution changes the rendering resolution during play to hold a target frame rate, and it can pull the resolution back up towards native just as the driver upscaler is trying to work from a lower one. The two fight each other, and the net effect disappears. Turn dynamic resolution off while testing NIS or RSR, and only consider turning it back on once the upscaler has been shown to work on its own with a fixed resolution below native.
FPS still does not move after enabling NIS / RSR — does that mean upscaling is not working?
Not necessarily. First check whether it is actually running: a green NIS indicator, or a before-and-after comparison that moves, shows that it is. If it is running and the frame rate still does not move, the cause is usually a frame-rate cap or vertical sync holding the frame rate where it is, or a processor bottleneck. Check the in-game cap, the driver cap, and vertical sync, and check whether graphics processor usage is clearly below 95% while the frame rate stays flat. A low usage figure with a flat frame rate points at the processor, where lowering the resolution cannot help.
In which situations should I not use NIS / RSR?
Do not use them where a game already has a built-in upscaler — use the built-in one instead. Do not use them at the monitor's native resolution, where there is nothing to enlarge. Do not use them where the processor is the bottleneck, because lowering the rendering resolution will not make the processor faster. Do not use them in the unsupported situations NVIDIA lists for NIS, such as SLI mode, Surround clone mode, tiled displays, Direct Display, virtual reality, or integer scaling mode, or together with a driver feature that AMD lists as mutually exclusive with RSR. And do not use them as a substitute for a hardware inspection when the problem is accompanied by a driver crash, a black screen, or coloured artefacts.