There's nothing quite like the feeling of your game freezing mid-round — your team mid-execute, your drone parked perfectly, and then… desktop. Rainbow Six Siege crashes on PC for a long list of reasons, from outdated drivers to overheating hardware to the game itself having a bad day. The good news: most crashes have a fix, and you can find it with a methodical approach instead of random guesswork.
This guide walks you through diagnosing the real cause of your crashes and fixing it, in the order that actually makes sense. No registry hacks, no sketchy third-party "optimizer" tools, no risky advice — just the standard, safe fixes that solve the vast majority of Siege crashes on PC.
What "Crashing" Actually Means (and Why It Matters)
Not all crashes are the same, and the type of crash is your first diagnostic clue. Pay attention to what happens when Siege goes down:
Crash to desktop (CTD) with no error. The game just closes. This is the most common type and usually points to a driver issue, an overlay conflict, or corrupted game files.
Crash with an error dialog. If Siege (or Ubisoft Connect) shows an error code or message, write it down or screenshot it. Error codes are the single most useful piece of information for diagnosis — they narrow the cause dramatically.
Freeze, then crash. The game locks up for a few seconds before closing. This often suggests the GPU is struggling — overheating, unstable drivers, or an unstable overclock.
Blue screen (BSOD). If your whole PC blue-screens, the problem is deeper than Siege. This usually means hardware instability, a bad driver at the system level, or failing RAM. Take this seriously and work through the hardware section below.
Crash at launch. The game never gets past the splash screen or menu. This is almost always a software conflict — overlays, antivirus, corrupted files, or a driver issue — rather than hardware.
Crash only in matches. If menus are fine but the game dies mid-round, especially in heavy firefights, suspect thermals, power delivery, or GPU instability. The game working fine until it's under load is the classic signature of a heat or power problem.
Keep a simple crash log for a few days: when it crashed (menu vs match), what you were doing, and whether anything changed recently (new driver, new Windows update, new software installed). Patterns will jump out.
Step 1: Rule Out the Game Itself First
Before you tear your PC apart, check whether the problem is on your end at all. Siege has bad patches and bad server days like every live game.
Check the game's status. If crashes started suddenly today and nothing changed on your PC, check Ubisoft's status page or community channels for reports of widespread issues. If everyone is crashing, no amount of driver reinstalling will help — wait for a hotfix.
Did it start after a patch? If crashes began right after a Siege update or a Windows update, that's your prime suspect. Game patches occasionally ship with bugs that get hotfixed within days. Windows updates can also break things — check if a driver or system update landed at the same time.
Try a different mode. If crashes happen in ranked but not in quick play or custom games, note that. It won't always be meaningful, but server-side issues sometimes affect specific queues.
If the timing doesn't point at a patch or server issue, move on — the problem is local, and the next steps will find it.
Step 2: Update Your GPU Drivers (Properly)
Outdated or corrupted GPU drivers are the single most common cause of game crashes on PC. This step fixes more crashes than everything else combined.
Do a clean driver install. Don't just update over the top — use the "clean install" option in the NVIDIA installer (custom installation → check "perform clean installation") or the "factory reset" option in AMD's Adrenalin installer. This removes stale driver profiles that can conflict with the game.
Don't use Windows Update for GPU drivers. Windows Update often installs older, generic driver versions. Download drivers directly from NVIDIA or AMD.
Match the driver to the game. Occasionally a brand-new driver release has a bug with a specific game. If crashes started right after a driver update, rolling back to the previous driver version is a legitimate troubleshooting step — it's not admitting defeat, it's data.
Update your other drivers too. Chipset drivers (from your motherboard manufacturer's site) matter for system stability. Audio drivers occasionally cause crashes in games with heavy audio processing. These are quick checks worth doing.
Restart your PC after driver changes. Test Siege for a session or two before moving on — give each fix a chance to prove itself.
Step 3: Verify and Repair Game Files
Corrupted game files are a quiet, common cause of crashes — especially CTDs with no error. A single bad asset can kill the game whenever it's loaded.
Verify through Ubisoft Connect. Go to your games library, find Rainbow Six Siege, and use the verify/repair option. This scans the installation and replaces corrupted or missing files. It's safe and doesn't delete your settings.
Verify through Steam if that's where you own the game: right-click Siege → Properties → Installed Files → "Verify integrity of game files."
Reinstall as a last resort, not a first step. A full reinstall takes a long time and rarely fixes what verification doesn't. Save it for after you've exhausted the other software causes.
Step 4: Disable Overlays and Background Software
Overlays are software that draws on top of your game — and they inject code into the game's process, which makes them a classic crash source. Siege is particularly sensitive to some of them.
Disable these one at a time and test:
- Discord overlay — the most common offender. Turn it off in Discord → Settings → Game Overlay. You can keep Discord voice running; just kill the overlay.
- Steam overlay — disable per-game in Steam (right-click Siege → Properties → uncheck "Enable Steam Overlay while in-game").
- Ubisoft Connect overlay — try disabling it temporarily.
- GeForce Experience / AMD Adrenalin overlay — fine for most people, but the instant-replay buffer can cause issues. Turn off ShadowPlay/ReLive recording while troubleshooting.
- RGB software — iCUE, Synapse, Armoury Crate and similar suites run background services that occasionally conflict with games. Close them completely (not just minimized) for a test session.
- Screen recorders and capture tools — OBS, recording software, even some screenshot tools inject into the game process.
Antivirus and firewalls deserve a mention too. Overzealous antivirus can interfere with game files or block the game's anti-cheat from working, which can cause crashes or launch failures. Add Siege and Ubisoft Connect to your antivirus exclusions rather than disabling protection. Never recommend disabling antivirus permanently — exclusions are the safe approach.
If disabling everything fixes it, re-enable programs one at a time to find the culprit. Tedious, but definitive.
Step 5: Check Temperatures and Thermals
If your game crashes mainly in matches — especially in heavy firefights — but menus are stable, heat is a prime suspect. Modern GPUs and CPUs throttle when hot, and severe overheating causes exactly the freeze-then-crash pattern.
Monitor under load. Use a hardware monitor (your GPU software usually includes one, or use a reputable free tool) and watch CPU and GPU temperatures while playing. Sustained temperatures above roughly 85–90°C on either component are a red flag.
Common thermal fixes:
- Clean your PC. Dust-clogged fans and filters are the number one cause of gradual thermal degradation. If your PC "used to run fine" and now crashes, dust is the first thing to check. Power off, open the case, and clean filters and fans.
- Check fan curves. Make sure your GPU and case fans actually ramp up under load. A fan stuck at low speed will cook your components quietly.
- Improve airflow. Cables blocking intake, a case shoved against a wall, or a PC sitting on carpet can all strangle airflow.
- Revisit your overclock. If you overclock your GPU or CPU, an unstable overclock is a classic crash cause — especially the freeze-then-crash type. Reset to stock speeds and test. If crashes stop, your overclock was the problem, not the game.
Don't ignore the PSU. An underpowered or aging power supply can cause crashes under load that look exactly like GPU problems. If your system crashes only when the GPU is working hard and thermals are fine, the PSU is worth suspecting — particularly if it's old or was borderline for your components from the start.
Step 6: Test Your RAM
Failing RAM causes the most confusing crashes in computing: random CTDs, different errors each time, crashes in some games but not others. If your crashes are inconsistent — different error messages, different timings, no pattern — RAM deserves a look.
Run Windows Memory Diagnostic. It's built into Windows: search for "Windows Memory Diagnostic," restart, and let it test. It's not the most thorough tool, but it's free and easy.
For a deeper test, MemTest86 (booted from a USB drive) is the gold standard. Run it overnight if you suspect RAM — it takes hours but it's definitive.
Quick practical test: if you have multiple RAM sticks, try running with one at a time. If crashes stop with a particular stick removed, you've found your bad module. This is faster than it sounds and surprisingly effective.
Step 7: Check Windows Itself
Sometimes the operating system is the problem, not the game or the hardware.
Run System File Checker. Open Command Prompt as administrator and run `sfc /scannow`. This scans Windows system files for corruption and repairs them. It's safe, built-in, and occasionally fixes exactly this kind of problem.
Check for Windows updates — both ways. A missing update can leave known bugs unfixed; a brand-new update can introduce new ones. If crashes started right after a Windows update, check community reports — and know that rolling back a problematic Windows update is a supported troubleshooting step.
Check your storage. Siege installed on a failing drive can crash when it tries to load corrupted assets. If you hear clicking from a mechanical drive, or your SSD is very old, check the drive's health with your manufacturer's tool or a SMART reader.
Virtual memory / page file. If you're running with very little RAM (8GB or less), Windows paging heavily during gameplay can cause stutter and occasional crashes. This ties back to the honest hardware guidance in our how to improve FPS in Rainbow Six Siege guide — 16GB is the comfortable standard for modern gaming.
When It's the Game's Bug, Not Your PC
Here's the honest part: sometimes you've done everything right and the game is just broken. Siege is a complex live-service game, and patches do ship with crash bugs.
Signs it's on Ubisoft's side:
- Crashes started immediately after a game patch, across many players
- The crash happens at the exact same point every time (a specific menu, a specific operator select, a specific map load)
- Community forums and social media are full of identical reports
- Nothing on your PC changed
What to do about it: report it through the proper channels with your error details, and wait for a hotfix. In the meantime, check whether the community has found a workaround — sometimes there is one (avoiding a specific operator, a specific setting, a specific map). These workarounds are worth trying but treat them as temporary.
Don't chase your tail. If the evidence points at a game bug, stop reinstalling drivers and repasting your GPU. The most common troubleshooting mistake is continuing to "fix" your PC for a problem that isn't yours.
Preventing Crashes Going Forward
Once you're stable, a little maintenance keeps you that way:
- Update GPU drivers on a sensible schedule. You don't need every single release — but don't fall a year behind either. Update when a new driver mentions Siege or when you're troubleshooting.
- Keep your PC clean. A quick dust check every few months prevents the slow thermal decline that causes "it used to work fine" crashes.
- Don't stack overlays. Pick the ones you actually use and disable the rest. Every overlay is another injection point.
- Be cautious with new software. If crashes start after installing something new — especially anything that hooks into games (recording tools, FPS counters, mods for other games) — that's your suspect.
- Keep Windows reasonably updated, but don't install major feature updates on day one if you're mid-ranked-grind. Let others find the bugs first.
FAQ
Why does Rainbow Six Siege keep crashing on the loading screen?
Launch crashes are almost always software conflicts: overlays, antivirus interference, or corrupted files. Work through Steps 2–4 above in order — clean GPU driver install, verify game files, disable overlays. If it crashes at the exact same loading point every time after a patch, check community reports for a known game bug.
Is crashing caused by my PC not being good enough?
Usually not directly. A weak PC causes low FPS, not crashes — the game will run badly rather than close. Crashes point to instability (drivers, heat, bad RAM, software conflicts), not low specs. The exception is running out of RAM entirely, which can crash games.
Can overlays really crash my game?
Yes — this is one of the most common and most overlooked causes. Overlays inject code into the game's process, and Siege's anti-cheat is sensitive to unexpected injections. The Discord overlay is the most frequent offender. Disabling overlays is free, safe, and takes two minutes, which is why it's early in the diagnosis order.
Should I reinstall Windows to fix game crashes?
Almost never as a first resort. A Windows reinstall is the nuclear option — it takes hours and usually isn't necessary. Work through the methodical steps in this guide first. If you've genuinely exhausted every software and hardware cause and the system itself shows signs of deep corruption, then it's worth considering — but that's rare.
Why does Siege crash only in ranked and not in quick play?
If this pattern is consistent, it's worth noting — but be careful about confirmation bias. Ranked matches are longer and more intense, so heat-related crashes are more likely to appear there simply because the GPU works harder for longer. True queue-specific crashes are usually server-side and affect many players at once.
The game crashes with no error message. Where do I even start?
Start with Step 2: clean GPU driver install. Silent CTDs are most often driver or overlay issues. Then verify game files (Step 3) and disable overlays (Step 4). If those don't fix it, the crash log pattern — when it happens, menu vs match — will point you toward thermals or hardware.
The Bottom Line
Fixing Siege crashes is a diagnosis problem, not a guessing problem. Start by ruling out game-side issues, then work the local causes in order of likelihood: clean GPU driver install, verified game files, overlays disabled, thermals checked, RAM tested, Windows repaired. Most crashes die somewhere in the first four steps.
The two mistakes to avoid: changing five things at once (you'll never know what fixed it, and you can't undo what you don't understand), and continuing to "fix" your PC when the evidence says it's a game bug. Methodical beats frantic every time.
Once your game is stable, make sure it's also running well — our best R6 PC settings guide covers the competitive configuration, and how to improve FPS in Rainbow Six Siege will help you squeeze out the frames your hardware can actually deliver. If responsiveness rather than stability is your issue, read our guide on reducing input lag in R6.