2080 super crashing is usually driver, heat, power, or unstable clocks, and you can narrow it fast with a clean install, temp checks, and stock settings.
When an RTX 2080 Super starts crashing, it rarely fails in a neat way. You might get a black screen that comes back, a crash to desktop, a “driver stopped responding” message, or a full reboot. The upside is that most failures come from a short list of causes, so you can test them in a clean order instead of swapping parts at random.
This guide sticks to checks you can do with free tools and built-in Windows settings. You’ll start with low-risk changes, then move to deeper diagnostics, and finish with a clear next step.
2080 Super Crashing In Games After Driver Updates
If crashes started right after a driver update, treat the driver stack as suspect first. A standard reinstall can leave old profiles and caches behind, so the same crash loop keeps coming back. A clean baseline gives you a known starting point.
Start With A Clean Driver Baseline
- Note your current driver version — Open Nvidia App or GeForce Experience and write down the version.
- Download two drivers — Grab the newest Game Ready driver and one older version you trust.
- Do a clean installation — In the installer, choose Custom and tick “Perform a clean installation.”
- Test one repeat scene — Use the same in-game area for 15–20 minutes so results compare cleanly.
If the newest driver crashes and the older one doesn’t, stay on the stable version for now and pause auto-updates until the next release. If both crash the same way, keep going.
Cut Out Common Driver Conflicts
- Turn off overlays — Disable Nvidia, Steam, Discord, and capture overlays, then retest.
- Remove GPU tuning apps — Disable MSI Afterburner, EVGA Precision, and similar tools during testing.
- Reset 3D settings — In Nvidia Control Panel, restore defaults for global settings and the game profile.
If you want a deeper reset than the installer provides, a driver wipe tool in Safe Mode can help. Disconnect from the internet, boot Safe Mode, remove the Nvidia driver, reboot, then install the driver you already downloaded. This prevents Windows from racing in with its own driver mid-install. Use this only when a normal clean install still leaves glitches.
- Download the installer first — Save it locally so you can install while offline.
- Stop Windows auto driver pulls — Stay offline until the Nvidia install is finished.
- Reboot — A second reboot after install can clear stubborn service states.
Quick Triage Using Symptoms And Windows Logs
Before changing ten things, pin down what “crashing” means on your system. A freeze with audio still playing points one way. A reboot points another. A desktop that returns after a black screen often matches Windows’ timeout recovery behavior (TDR). Windows TDR overview
| What You See | Likely Direction | Fast Check |
|---|---|---|
| Black screen, then desktop returns | Driver reset (TDR) | Check Reliability Monitor for LiveKernelEvent entries |
| Full reboot under load | Power drop or protection trip | Inspect PCIe cables and remove daisy-chain wiring |
| Crash to desktop with DXGI error | Driver, overlay, or unstable clocks | Stock clocks, clean driver, overlays off |
| Artifacts or flicker | VRAM instability or heat | Lower memory clock and watch temps |
Use Reliability Monitor Before Event Viewer
Search for “reliability” in the Start menu, open View reliability history, then click the red X entries that line up with your crashes. If you see repeated hardware error entries like LiveKernelEvent 141 or 117 around display failures, you’re likely dealing with a driver hang or a GPU timeout. LiveKernelEvent examples
Record The Crash Pattern In One Note
- Write the trigger — A specific game, a loading screen, or a spike like alt-tab.
- Write the outcome — Desktop reset, black screen, reboot, or crash to desktop.
- Write the time to fail — Instant, five minutes, or only after an hour of heat soak.
- Write one repeat test — One scene you can rerun to validate each change.
Thermals And Airflow Checks That Catch Silent Instability
Heat is a quiet troublemaker because your 2080 Super can look “fine” on the main GPU temperature while hotspots and memory run much hotter. A system that was stable for years can also start trapping dust in fins, or a fan can slow down just enough to push it over the edge during a heavy scene.
Measure More Than One Temperature
- Log temps under load — Use HWiNFO or GPU-Z to log GPU temp and hotspot.
- Watch for heat soak — Crashes after 20–40 minutes often match rising case temps.
- Check fan behavior — Confirm fans ramp smoothly and don’t stall at low RPM.
Pay attention to how far hotspot runs above core temp. A wide gap can hint at dried paste, uneven mounting pressure, or a cooler that’s not making good contact. If your fans are loud but hotspot keeps climbing, the card may be moving heat poorly, not just lacking airflow. A careful repaste can fix that, but only do it if you’re comfortable opening the card and replacing pads exactly as they were.
Do A Simple Cooling Reset
- Clean the card and filters — Blow dust out of the GPU heatsink and case filters, then retest.
- Improve intake — Make sure front fans pull cool air in and cables aren’t blocking the GPU path.
- Test with the case open — Run one session with a side panel off to see if stability changes.
If stability improves with a cooler case, you’re chasing heat. Better airflow, a careful repaste, or a mild undervolt can bring temps down without changing how the card feels in games.
Power Delivery And Cabling Mistakes That Cause Sudden Resets
A hard reboot under load often comes from power delivery. The 2080 Super can pull fast bursts of current, and a borderline PSU or poor cabling can trigger protection circuits. This shows up more when a single PCIe cable is daisy-chained to two GPU power sockets.
Check The Basics First
- Use separate PCIe cables — Run two dedicated PCIe leads from the PSU to the GPU when possible.
- Reseat power and PCIe — Reseat the GPU in the slot and reseat both ends of each PCIe power cable.
- Avoid adapters — Remove splitters and low-quality adapters during testing.
- Try a known-good PSU — If your PSU is older, borrow a solid unit for a session to rule out power issues.
Rule Out A Loose Display Chain
- Swap the display cable — Try another DisplayPort or HDMI cable and a different port on the GPU.
- Bypass intermediate gear — Remove KVMs, adapters, and capture devices between the GPU and monitor.
Stability Tests That Isolate Overclock, Undervolt, And VRAM Issues
Even if you never overclocked, factory boost behavior and memory profiles can expose instability during GPU-heavy scenes. The goal is to force the whole system into a calm state, then add performance settings back only after it proves stable.
Return Everything To Stock
- Reset GPU tuning — Set core and memory back to default and remove custom fan profiles.
- Return CPU settings to default — Remove manual CPU overclocks for a test run.
- Back off RAM profiles — Try one session with XMP/EXPO off to see if the crash changes.
- Lower GPU power limit a bit — Drop power limit 5–10% for a test; if crashes stop, power or heat is involved.
Run Two Short Stress Tests And Watch For Clues
Pick tests you can repeat and stop quickly if things go sideways. You’re not trying to “win” a benchmark. You’re trying to see what breaks first.
- Run a GPU-only load — A graphics stress test isolates the card and driver from game-specific quirks.
- Run a mixed load — A combined CPU+GPU test can reveal a PSU that only fails when the whole system pulls power.
- Watch clock drops — Sudden drops right before a crash can point to heat, power limits, or unstable tuning.
Try A Mild Undervolt
An undervolt can stabilize a card that’s right on the edge, because it reduces peak power spikes and heat. Keep changes small and validate with the same repeat test.
- Set a gentle curve — Target a slightly lower voltage at your usual boost clock.
- Retest longer — Run 20 minutes, then 60 minutes, watching temps and behavior.
Spot VRAM Instability
- Lower memory clock — Drop VRAM by 250–500 MHz for one session and watch for fewer artifacts or crashes.
- Run a VRAM test — Use a test that can report memory errors during load.
Windows And Game Settings That Stop Repeated Driver Resets
When Windows thinks the GPU stopped responding, it can reset the driver to recover the desktop. That’s TDR. Microsoft documents TDR-related registry values and their defaults, which helps explain why a heavy spike can trip a reset. TDR registry notes
Changing TDR values can hide a deeper issue, so treat it as a last step after you’ve done drivers, temps, and power. Many systems stop resetting once clocks are stock, airflow is clean, and cabling is solid.
Reduce Load Spikes First
- Cap frame rate — Use an in-game limiter or Nvidia Control Panel to cap FPS near monitor refresh.
- Lower heavy settings — Drop ray tracing, shadows, and volumetrics before touching texture quality.
- Turn off hardware acceleration — Disable it in browsers and chat apps during gaming.
Only If Needed, Adjust TDR Delay Carefully
- Create a restore point — Make a system restore point before registry edits.
- Change one value — Add TdrDelay and test, then add TdrDdiDelay only if needed.
- Keep changes modest — Small increases can help long shader tasks; huge values can mask a failing card.
When It’s Time To Suspect The Card Or Another Part
If 2080 super crashing still happens with stock clocks, clean drivers, cooler temps, and known-good cabling, you may be facing a component fault. The fastest proof comes from changing one variable at a time.
Cross-Check With Two Simple Swaps
- Test the GPU in another PC — If the same crash pattern follows the card, the card is the likely cause.
- Test another GPU in your PC — If a different card runs clean, your system is probably fine.
- Swap the PSU for a session — A known-good PSU can rule out transient power issues.
What To Collect Before An RMA Or Repair Quote
- Save a Reliability Monitor screenshot — Capture the crash entries and any LiveKernelEvent codes.
- List driver versions tested — Note which versions crashed and which stayed stable.
- Record temps from one failing run — A short log helps show the pattern.
After you collect that set, you can stop guessing. You’ll know which change moved the needle and which didn’t, and you’ll have clean evidence to share for warranty.
