Corsair Cove

Corsair Cove crashing at the first event: how to get past it

By the New Games Guide team · Last updated 2026-08-02

A crash that happens at the same scripted moment every time is the most fixable kind there is. It means a specific asset or a specific system is failing reproducibly, rather than something random about your machine — and reproducible problems have findable causes.

Work down this list in order. It is sorted by how often each fix works against how long it takes.

Fix 1 — Disable every overlay#

Overlays inject into the rendering pipeline, and a scripted event that changes render state — a cutscene, a camera transition, a UI takeover — is exactly where that injection breaks.

Turn all of these off and test before changing anything else:

• Discord overlay (globally, and for this game specifically)
• Steam overlay — game Properties → General
• NVIDIA app / GeForce Experience overlay
• AMD Adrenalin overlay and performance metrics
• Xbox Game Bar — Windows Settings → Gaming → Game Bar → off
• MSI Afterburner and RivaTuner — close both entirely; RivaTuner survives closing Afterburner's window
• Razer Synapse, Logitech G Hub, iCUE and similar peripheral suites
• OBS with game capture hooks, and any screen recorder

Fix 2 — Verify or repair the installation#

A single corrupt file gives you a crash at one fixed point — precisely your symptom.

• Steam: right-click the game → Properties → Installed Files → Verify integrity of game files.
• Game Pass / Microsoft Store: Windows Settings → Apps → Corsair Cove → Advanced options → Repair first, then Reset if repair does not help. Reset clears app data, so confirm your saves are in cloud storage before using it.

This takes minutes and is the correct first move before considering a reinstall, which takes hours and does the same job.

Fix 3 — Delete the shader cache#

A stale shader cache causes crashes shortly after launch, particularly on the first heavy scene. Delete these and relaunch; expect one stuttery session while it rebuilds.

%LOCALAPPDATA%\NVIDIA\DXCache
%LOCALAPPDATA%\NVIDIA\GLCache
%LOCALAPPDATA%\AMD\DxCache
%LOCALAPPDATA%\D3DSCache

Also clear the game's own cache folder under %LOCALAPPDATA%, leaving any SaveGames or Saves directory alone.

Fix 4 — Lower settings and change display mode#

If it runs at all, get through the event first and tune afterwards.

1. Set graphics to Low across the board.
2. Set display mode to Borderless windowed. Exclusive fullscreen mode switches are a common crash point during scripted transitions.
3. Set resolution to your monitor's native, scale at 100%.
4. Cap the framerate about 10 below your refresh rate. Uncapped menus and cutscenes can spike a GPU hard.
5. Turn off any upscaling and frame generation.

Get past the event, save, then raise settings one group at a time.

Fix 5 — Clean-install the GPU driver#

An update is not a clean install. Layered driver installs carry forward the stale profiles and caches that cause this.

• NVIDIA: installer → Custom → tick Perform a clean installation. Use DDU in Safe Mode for a stubborn case.
• AMD: AMD Cleanup Utility or DDU, then install fresh.

If the crashes began immediately after a driver update, try the previous version. A new driver against a week-old game is a well-known bad combination.

Fix 6 — Memory and page file#

Builders allocate aggressively, and the opening sequence loads a lot at once.

• Set the page file to system-managed on the drive holding the game. People who disabled it years ago are the most common victims of this crash class.
• Close browsers before launching. Several gigabytes of RAM and VRAM go back immediately.
• Disable XMP/EXPO temporarily. Memory profiles that pass normal use often fail under a game's sustained allocation pattern. If the crash stops, that was your cause.
• Watch VRAM in Task Manager during the event. Pinned at maximum means lower textures, not a new driver.

Fix 7 — Game Pass specific#

The Microsoft Store version has failure modes the Steam build does not.

1. Reset the app — Windows Settings → Apps → Advanced options → Reset. Confirm cloud saves first.
2. Confirm the Gaming Services component is healthy. Reinstall it from the Store if the game fails to launch at all.
3. Check the install drive. Store apps installed to an external or secondary drive with unusual permissions cause crashes that vanish when installed to the system drive.
4. Sign out and back into the Xbox app, and confirm Windows is signed into the same account.

Fix 8 — Skip the event as a last resort#

If nothing works and the event is genuinely unpassable:

• Check whether the opening is skippable in settings, or with a key held during the transition.
• Start a different game mode or scenario if the game offers one — that tells you whether the problem is this specific event or the game as a whole, which is valuable either way.
• Wait for a patch. A reproducible launch-week crash at a scripted moment is exactly the kind of thing fixed in the first hotfix, and it is worth reporting so it makes that list.

Reporting it usefully#

If you report the crash, include: your GPU and driver version and whether it was clean-installed, whether you are on Steam or Game Pass, whether it happens with all overlays disabled, whether a fresh save reproduces it, and the crash dump from the game's Saved\Crashes folder if one exists. That set of facts is what turns a bug report into a fix.

FAQ#

Will reinstalling fix it?#

Rarely, and it costs you hours. Verification (Fix 2) does the useful part of a reinstall in minutes, and cached configuration — the actual cause in many cases — survives a reinstall anyway. Only reinstall if verification reports errors it cannot repair.

Is it my PC or the game?#

If other demanding games run stably for an hour, it is this game or its configuration. If several games crash, look at memory profiles, temperatures and power delivery before touching game settings.

Does the Game Pass version crash more than the Steam version?#

They are usually the same build with different packaging, but the Store version adds the Gaming Services layer and a stricter install location model — both of which introduce failure modes Steam does not have. If you own it on both, testing the other one is a fast diagnostic.

Should I roll back my Windows update?#

Almost never worth it. Windows updates rarely cause single-game crashes at a fixed point, and rolling one back is disruptive. Exhaust the driver, overlay and verification fixes first.