Most fixes posted for server status are shotgun advice: try everything, claim credit for whatever worked.

Short answer

Nine times out of ten it is a stale cache or an overlay injecting itself. Both are two-minute checks.

  • Clear the shader cache if the symptom is stutter rather than a crash.
  • Disable every overlay, then re-enable them one at a time.
  • If a menu path does not exist for you, your build is older or newer than the one described.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Anti-cheat drivers are the one component where a plain reinstall genuinely helps. Changing several settings at once makes the cause impossible to identify afterwards.

The checks worth doing first

Treat anything stated without a version number as provisional. A status page tells you in five seconds what an hour of troubleshooting will not. Overlays from chat apps, capture tools and storefronts all hook the same rendering path. Rainbow Six Siege is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

A crash that always happens at the same moment is a content problem, not a hardware one. Logs are usually more specific than the error dialog that pointed you here. There is no hidden trick here that the game is keeping from you.

Is it you or is it them

File verification is non-destructive and repairs a surprising share of these cases. Most of the disagreement you will find online is two people describing different builds. Do the cheap check before the expensive one — that ordering alone saves most of the frustration.

  • Run once as administrator to rule out a permissions problem.
  • Verify or repair the installation through the launcher.
  • Expect one number in every guide to be out of date; the method is what matters.
  • Check the official server status before anything else.
  • Update the GPU driver, and clean-install it if this has happened before.

When a reinstall is justified

A single check up front replaces a lot of guessing later. What follows assumes you are on a current install and have not modified it. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. Where two approaches both work, the one with fewer moving parts is the one to keep.

The awkward part is rarely the step itself, it is knowing which step comes first. Everything below is framed around the current state of Rainbow Six Siege rather than a launch-week impression. The short version is near the top on purpose; the reasoning is there if you want to know why.

If it comes back

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Anything that behaves differently on console than on PC is flagged where it matters. The community wisdom on this is roughly half right, and the half that is wrong costs the most time.

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. If your result differs from what is described here, note what is different first rather than starting over. If you are coming to this after a long break, the terminology has probably moved on.

Overlays, and why they cause this

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. Screenshots age faster than text, which is why this describes rather than shows. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of.

Where people go wrong

  • Changing five things at once and then not knowing which one helped.
  • Ignoring the platform-specific note and then wondering why the steps do not line up.
  • Treating a rare edge case as the normal behaviour and planning around it.
  • Skipping the prerequisite because it looked optional in someone else's summary.

Siege FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

Is this problem on my end?

Check the status page first. If Rainbow Six Siege is up for everyone else, then yes, and the checklist above is ordered by likelihood.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

Come back to the caveats list if it does not work first time — the answer is almost always in there.