Rainbow Six Siege runs on Ubisoft’s AnvilNext engine and ships two separate executables, RainbowSix.exe for DirectX 11 and RainbowSix_Vulkan.exe for Vulkan, which is the first thing to understand about its crashes: many of them are specific to one renderer and vanish on the other. When Siege crashes it either disappears silently to desktop, shows the Ubisoft Crash Reporter, or returns you to the menu with an error code such as 3-0x0001000B or 0-0x00100608, which are connection or service errors rather than crashes and should not be treated as one. A crash during the BattlEye splash is the anti-cheat; a crash at the operator select screen after a season update is nearly always the shader cache or a driver profile; a crash mid-round on an old system is often memory. Siege also layers Ubisoft Connect between you and the game even when you buy it on Steam, and a damaged Connect cache can produce startup failures that look like game crashes. The fixes below are ordered by how often they solve the problem in 2026 and how little they change.
- Likely Causes
- Fix 1: Switch between DirectX 11 and Vulkan
- Fix 2: Clear the shader cache
- Fix 3: Verify game files
- Fix 4: Disable overlays
- Fix 5: Reinstall BattlEye
- Fix 6: Reset GameSettings.ini
- Fix 7: Clear the Ubisoft Connect cache
- Fix 8: Clean-install the GPU driver
- Fix 9: Return memory and CPU to stock
- If Nothing Works
- FAQ
Quick answer: Our top pick in 2026 is the Renderer-specific instability (DX11 vs. Vulkan) — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Renderer-specific instability (DX11 vs. Vulkan) | Crash stops when launching the other executable | Easy |
| Stale shader cache after a season patch | Crash at operator select or first round after an update | Easy |
| Corrupted game files | Ubisoft Connect or Steam verification replaces files | Easy |
| Overlays injecting into the game | Stable with Discord, Afterburner, Ubisoft Connect and Steam overlays off | Easy |
| Damaged BattlEye service | Crash during the BattlEye splash or “Client not responding” kick | Easy |
| Corrupted GameSettings.ini | Crash before the main menu; fresh file resolves it | Easy |
| Outdated GPU driver | Event Viewer shows a display driver reset at crash time | Moderate |
| Unstable RAM or CPU overclock | Crashes in other games too; stock is stable | Moderate |
Fix 1: Switch between DirectX 11 and Vulkan
How to check
When you press Play in Ubisoft Connect or Steam, the launcher asks which version to run. Note which one you use. If the crash shows the Ubisoft Crash Reporter with no obvious pattern, try the other renderer for several matches.
What to do
Choose the other option at the launch prompt. Vulkan often gives better frame pacing and lower CPU overhead on modern hardware, while DirectX 11 is sometimes more stable on older drivers and integrated graphics. If the prompt does not appear, you can launch RainbowSix.exe or RainbowSix_Vulkan.exe directly from the install folder; the game still routes through Ubisoft Connect.
How to undo it
Select the previous renderer at the next launch.
Fix 2: Clear the shader cache
How to check
If the crash began right after a season or mid-season update and hits at operator select or the first time you load a map, the cached shaders were invalidated.
What to do
Close the game and its launcher. Steam users delete Steam\steamapps\shadercache\359550. Everyone should clear %LOCALAPPDATA%\NVIDIA\DXCache and %LOCALAPPDATA%\NVIDIA\GLCache on NVIDIA systems, or %LOCALAPPDATA%\AMD\DxCache and %LOCALAPPDATA%\AMD\VkCache on AMD. Relaunch; expect a longer first load.
How to undo it
Nothing to revert.
Fix 3: Verify game files
How to check
Crashes on specific maps or when a specific operator’s gadget deploys often point at a damaged asset file.
What to do
In Ubisoft Connect, open the game page, click the three dots next to Play, choose Properties, then Verify files. Steam users right-click the game, Properties, Installed Files, Verify integrity. Let the process finish and launch again.
How to undo it
Not applicable.
Fix 4: Disable overlays
How to check
Siege has a long history of conflicts with overlays. Discord, RivaTuner Statistics Server, the NVIDIA App overlay, Xbox Game Bar and Ubisoft Connect’s own in-game overlay all inject into the process. Steam users effectively have two launcher overlays active.
What to do
In Ubisoft Connect, Settings, General, uncheck “Enable in-game overlay for supported games.” In Steam, disable the overlay for Siege in its Properties. Turn off the Discord overlay, close RivaTuner, and disable Game Bar. Test several matches, then re-enable one at a time.
How to undo it
Reverse each toggle.
Fix 5: Reinstall BattlEye
How to check
A crash during the BattlEye launcher window, a “Failed to install BattlEye Service” message, or an in-match kick citing BattlEye means the anti-cheat is at fault.
What to do
Close the launcher. In the game folder, open BattlEye and run Uninstall_BattlEye.bat as administrator, then Install_BattlEye.bat. Add the game folder to your antivirus exclusions. Launch through the launcher so the service starts correctly.
How to undo it
Not applicable; reinstalling restores the default state.
Fix 6: Reset GameSettings.ini
How to check
Siege stores settings in %USERPROFILE%\Documents\My Games\Rainbow Six - Siege\<Ubisoft account ID>\GameSettings.ini. A resolution the monitor no longer supports, an upscaler mode your driver rejects, or a stale value from a previous season can crash before the menu appears.
What to do
Close the game. Rename GameSettings.ini to GameSettings.ini.bak. Launch, let the game regenerate defaults, then rebuild your settings in Options. Sensitivity and keybinds are stored here too, so keep the backup for reference.
How to undo it
Delete the regenerated file and restore the backup.
Fix 7: Clear the Ubisoft Connect cache
How to check
If the game fails immediately at launch, before the BattlEye window, or Ubisoft Connect shows ownership or service errors, the launcher’s local cache may be damaged.
What to do
Close Ubisoft Connect. Delete the contents of %LOCALAPPDATA%\Ubisoft Game Launcher\cache. Restart Ubisoft Connect, sign in, and launch the game. If the launcher itself is misbehaving, reinstalling Ubisoft Connect does not remove installed games.
How to undo it
Not applicable; the cache is rebuilt on sign-in.
Fix 8: Clean-install the GPU driver
How to check
Open Event Viewer, Windows Logs, System, and look for a warning from nvlddmkm or amdkmdag at the crash time.
What to do
Install the current driver from NVIDIA, AMD or Intel with the clean installation option, reboot, and repeat Fix 2 because a driver change invalidates shaders. If the newest driver introduced the crash, install the previous release.
How to undo it
Roll back through Device Manager or install the older package.
Fix 9: Return memory and CPU to stock
How to check
Siege runs at very high frame rates and exercises memory heavily. If you use XMP/EXPO or a manual overclock and also see occasional crashes elsewhere, instability is plausible.
What to do
Disable XMP/EXPO and manual overclocks in BIOS. Test several matches. Reintroduce gradually with a small DRAM voltage increase if needed.
How to undo it
Reload your saved BIOS profile.
If Nothing Works
Submit the Ubisoft Crash Reporter when it appears; it attaches a dump that Ubisoft Support can read. Collect the Application error from Event Viewer, which names the faulting module. Test a fresh Windows user account and a session with no third-party software running. Try the other storefront’s launcher path if you own the game on both. If the crash arrived with a season update and many players report it, check Ubisoft’s known issues page; season-launch crashes are frequently fixed by the first patch, and waiting is a legitimate resolution.
FAQ
Is Vulkan or DirectX 11 more stable in Siege?
It depends on your driver and hardware. Vulkan generally performs better on modern GPUs; DirectX 11 is the fallback when Vulkan misbehaves. Test both.
Are error codes like 3-0x0001000B crashes?
No. Those are connection or service errors, and the fix is network-side: check Ubisoft’s service status, use a wired connection and disable VPNs.
Why does Siege crash only after a season update?
Shader caches and driver profiles are invalidated by new content. Clearing the cache and updating the driver usually resolves it within a match or two.
Do I need Ubisoft Connect if I bought Siege on Steam?
Yes. It runs in the background regardless, and its cache and overlay can both cause launch problems, which is why they appear in this guide.
Ready to decide? Our #1 pick for 2026 is the Renderer-specific instability (DX11 vs. Vulkan).
Live price & availability on Amazon.
