GPU Artifacts? Sort Software vs Dying VRAM Before You RMA (2026)

By LK Wood IV · 2026-07-10 · ~11 min read · St. Louis County, MO

Some retailer links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Commissions never influence what gets recommended — see our disclosure.

The screen fills with colored lines, snow, or textures stretching into garbage, and the top of every search result says the same two things: it’s dying, RMA it — or just reinstall your drivers. Both are sometimes right. But “GPU artifacting” is really a handful of very different problems wearing one ugly symptom, and if you reach for the wrong one you’ll either bin a card that a five-minute fix would have saved, or keep reinstalling drivers on a card that’s physically failing.

Two questions sort almost the entire thing before you touch a setting: does the glitch show up in a screenshot, and does it stop when you back off the clocks? Answer those and you’ve already thrown out most of the advice on the internet.

But first, the question people actually type into the search bar: what am I even looking at? Artifacts come in a handful of recognizable shapes, and the shape tells you which lane to start in — the cable, the driver, the heat, a rendering setting, or the silicon itself. Here’s the field guide.

Step 1: The 60-second test — is it even the GPU?

Artifacts you see on the monitor can be born in two completely different places: on the render side (the GPU rendered a broken frame) or on the display path (the GPU rendered a fine frame and it got corrupted on the way to the panel). One test splits them.

Take a screenshot while the artifacts are on screen — or better, record a couple of minutes with OBS Studio — then open the file on your phone or another PC. Screen capture grabs the frame before it leaves the graphics card:

A clean capture with a glitchy screen is a good result — it usually means a bad DisplayPort/HDMI cable, a flaky adapter, an over-aggressive refresh rate, or a failing monitor, none of which require a new graphics card. If the glitch is specifically lines rather than sparkles or blocks, our guide on lines on a monitor — cable, GPU, or dying panel has the one-button OSD test that isolates the display side in under a minute. (Some VRAM faults won’t always capture, so a clean shot isn’t an absolute guarantee — but a captured artifact almost always means the card.)

Then note where the artifacts appear, because that narrows it further:

• Only in one game → most likely that game’s engine or a corrupted shader cache, not your hardware.
• In every game, but the desktop is clean → driver, heat, overclock, or VRAM under load.
• At the Windows desktop, or even in the BIOS/UEFI screen → this is the serious one. Desktop-level artifacting that isn’t tied to a 3D load points hard at failing hardware.

The 2026 curveball: ghosting and afterimages that aren’t a dying card

Before you walk the hardware ladder, rule out the “artifact” that panics the most people in 2026 and almost never means a failing card: ghosting — faint trailing afterimages or smears behind moving objects, lights, and highlights. This is usually not your GPU at all. It’s a side effect of how modern games render, and it’s the single most common “is my card cooked?” false alarm on r/pcmasterrace and r/nvidia right now.

Three rendering features blend information across frames, and that blending is exactly what you see trailing:

• DLSS / FSR upscaling. The game renders at a lower resolution and reconstructs the rest; ghosting gets worse the more aggressive the preset (Performance trails more than Quality) and at lower output resolutions.
• Frame Generation. Inserted frames can smear on fast motion and around the HUD — the more frames it’s generating, the more visible.
• TAA (temporal anti-aliasing). It blends and jitters frames to smooth jagged edges, and that blend smears during fast movement. It leans on frame data, so it looks worse at 1080p than at 1440p and up.

The tell is dead simple, and it follows the same Step-1 logic: the trailing appears only in games with these features on, and vanishes the moment you switch to DLAA or native resolution, raise the DLSS preset, or turn Frame Generation off. If your game supports it, DLAA gives you NVIDIA’s anti-aliasing without the upscaling and usually kills the ghosting outright.

One lookalike is not render-side: monitor overdrive set too high also trails. The screenshot test separates them — render-side ghosting shows up in a screen recording, but overdrive ghosting does not (it happens on the panel, after the frame has already left the card), so it only appears when you point a phone camera at the screen. Drop the monitor’s overdrive / response-time setting a notch and it’s gone. Either way, none of this is a dying GPU: real VRAM or die failure looks like the lines, blocks, snow, and broken geometry in the gallery above, not soft motion trails.

Step 2: Rule out software first — it’s free

Before you spend a cent, clear the causes that cost nothing. In order:

Reset any overclock. If you’ve touched core clock, memory clock, or voltage in MSI Afterburner or your card’s software, set everything back to default (or hit the reset button). An unstable overclock is one of the most common artifact sources, and it’s invisible until you undo it. If the artifacts vanish at stock, that was your answer.

Do a clean driver reinstall with DDU. A corrupted or half-installed driver produces artifacts that look exactly like hardware failure. Download the latest driver from NVIDIA, AMD, or Intel first, then run Display Driver Uninstaller (DDU) in Windows Safe Mode to wipe the old driver completely, reboot, and install clean. This single step resolves a large share of “sudden” artifacting.

Clear the shader cache if it’s one specific game. Delete the game’s shader cache (Steam: right-click the game → Properties → Installed Files, or clear the driver’s cache in the NVIDIA/AMD control panel). A broken cache renders corrupted geometry in one title while everything else is fine.

If artifacts survive all three, the odds swing toward hardware — but there are still two free things to check before you write the card off.

Step 3: Check the temperature

Install HWiNFO and watch the GPU temperatures (and the separate memory junction / VRAM temp on cards that report it) while the artifacts appear. If the card is running hot and the glitches show up under load but vanish when it idles and cools, you’re looking at thermal-driven artifacting, not dead silicon. Not sure whether your card is actually running hot or just showing normal load temps? Check core vs hotspot first — see Is Your GPU Really Overheating?

The fixes are physical and cheap: blow the dust out of the heatsink and fans with a can of compressed air, confirm every fan actually spins (if one is dead or none spin under load, see GPU Fans Not Spinning), and improve case airflow. On an older card whose thermal paste has dried out, a thermal paste repaste (and fresh thermal pads on the VRAM/VRM) can drop temperatures 10–20 °C and stop heat-triggered artifacts entirely.

Step 4: Test the VRAM and confirm hardware

If it’s cool, at stock, freshly re-drivered, and still artifacting, it’s time to prove whether the memory or core is failing. There are two tools:

The underclock test. In MSI Afterburner, lower the memory clock by 100–300 MHz (and, if needed, the core by about 50 MHz), apply, and retest. If the artifacts stop at the reduced clock, the hardware can no longer hold its rated speed — that’s degrading VRAM or an unstable die. A modest undervolt/underclock can genuinely keep a fading card usable for months by cutting heat and electrical stress, but understand what it means: the card is on a downward path.

A stress test. Run OCCT (it has a dedicated VRAM test) or FurMark for a short session and watch closely. Stop immediately if temperatures spike fast, the screen goes black, the PC crashes, or the artifacting intensifies instead of settling — those are all signs of real instability, and there’s no benefit to cooking a failing card.

Two patterns confirm a hardware fault rather than a setting: artifacts that reproduce across multiple games, and artifacts that follow the card across different monitors and cables. When corruption shows up everywhere with no software trigger and survives a clean driver reinstall, the usual culprits are failing VRAM, a destabilizing GPU die, damaged board components (ceramic caps, memory-power circuitry), or a power-delivery fault on the card.

Step 5: The physical causes people skip

Before you accept “dead,” check the mechanical stuff that repair techs see constantly — none of it shows up in software:

• Power-connector trouble. A PCIe or 12VHPWR / 12V-2×6 connector that isn’t fully seated, or one running through thin-gauge daisy-chained PSU wiring, can overheat and feed the card dirty or insufficient power — which shows up as artifacts and instability under load. Unplug and firmly re-seat every power cable at both ends, and look (and smell) for any browning or melting on the connector. A weak or aging power supply can also mimic a dying GPU.
• Card sag and board flex. Heavy modern multi-slot cards slowly bend under their own weight, and that flex stresses the solder joints under the GPU and memory chips over years. A cheap GPU support bracket removes that stress and is worth fitting on any large card as prevention.
• Cracked solder joints (BGA). The “dying” that people describe is often a cold or cracked BGA solder joint under the die, caused by years of heat cycling — heavy load to idle, over and over. That’s what a repair specialist actually fixes.

On a laptop, the playbook shrinks. You usually can’t reseat the GPU, repaste easily, or touch the core clock, and the dGPU is soldered to the board — so your real moves are the free ones (reset any overclock utility, clean-reinstall the driver, clear the shader cache, and blow the dust out of the vents) plus one hardware check: plug in an external monitor. If the artifacts show on the external screen too, it’s the laptop’s GPU or its memory; if the external screen is clean, the built-in panel or its ribbon cable is the fault, not the graphics chip. A soldered mobile GPU that artifacts across displays after a clean driver reinstall is usually a warranty/RMA or board-repair case, not a home fix.

Step 6: When it’s the display path (clean capture)

If your Step-1 capture came back clean, the GPU is rendering fine — chase the connection instead. Swap the video cable for a known-good one (cheap cables and worn connectors are a top cause), try a different port on the card and a different input on the monitor, drop the refresh rate to a standard value in case the current mode is out of the panel’s stable range, and test a second monitor entirely. If a different screen and cable are clean, the original monitor is the fault. This is a much happier outcome than a dead card — see Monitor Keeps Going Black? for the full display-side walk-through.

When it’s genuinely dying — RMA or repair

You’ve reset the clocks, reinstalled drivers clean, ruled out heat, re-seated power, and the card still throws artifacts at the desktop across multiple monitors. At that point it’s a hardware failure, and the path depends on warranty:

• Under warranty → RMA it. That’s almost always the right call; the manufacturer replaces or repairs it and you’re not gambling on a fix.
• Out of warranty → weigh repair vs replace. A GPU repair specialist can sometimes reflow or reball the core/VRAM to fix a cracked joint, but component-level work often costs more than a mid-range card is worth. If you’re replacing, match a current graphics card to your power supply and case, and if your testing implicated the PSU, fix that too — a failing power supply will happily kill the replacement card as well.

Before you spend anything, be sure: confirm the artifacts follow the card into a second PC. A failing PSU or a bad cable can frame a perfectly good GPU, and the whole point of the tests above is to make sure you only retire a card that’s actually done.

The quick version

1. Screenshot or record the artifacts. In the capture → it’s the card (Steps 2–5). Clean capture → it’s the cable/monitor (Step 6).
2. Trails or afterimages? If it only happens with DLSS/TAA/Frame-Gen on and stops when you switch to DLAA/native or turn Frame Gen off, it’s a rendering feature, not a dying card.
3. Where does it show? One game = shader cache; every game = driver/heat/OC/VRAM; desktop or BIOS = hardware.
4. Do the free software pass: reset the overclock, clean-reinstall the driver with DDU, clear the shader cache.
5. Check heat (HWiNFO) — dust, fans, and a repaste fix thermal artifacts.
6. Confirm hardware: a −100–300 MHz memory underclock that stops the artifacts means degrading silicon; OCCT/FurMark and cross-testing on other games, monitors, and cables confirm a real fault.
7. Then, and only then, RMA (in warranty) or weigh a reflow/replacement — after proving the card is dead in a second machine.

Find out whether it’s software, the display path, or dying hardware first, and you stop reinstalling drivers on a card that never had a driver problem — and you stop throwing away cards a reset overclock would have fixed. For the driver side of this in depth, see Fix GPU Driver Crashes; if the card isn’t showing up at all rather than glitching, that’s a different branch covered in Graphics Card Not Detected.