AntewiseGames
Visit antewise.com
troubleshooting beginner

Destiny 2 Crashing on PC: Fixes That Actually Work

Destiny 2 crashes and BEAVER errors on PC: driver updates, overlay conflicts, FPS caps, and other fixes in order

6 min read

Advertisement

Destiny 2 crashes on PC are common, and the usual suspects are overlays and monitoring software. Work through the list in order. Most players never get past the third item.

Fix the usual offenders first

Overlays and stat monitors cause more Destiny 2 crashes than anything else. Close all of these before you relaunch:

  • Discord overlay
  • Steam and Battle.net overlays
  • GeForce Experience and Xbox Game Bar overlays
  • MSI Afterburner, RivaTuner, and similar stat tools

RivaTuner in particular is a known crash source with this game. Quit it from the system tray, not just the window.

Update your graphics driver

Crash-heavy sessions often trace back to a stale GPU driver. Do a clean install of the latest driver for your card. On a laptop with hybrid graphics, force Destiny 2 onto the discrete GPU in your graphics control panel. Running on the integrated chip causes crashes that look random.

Cap your frame rate

An uncapped frame rate destabilizes the game and cooks laptop hardware. Cap at 120 or lower, either in-game or with your driver’s frame limiter. This alone fixes a large share of BEAVER crashes.

Verify and repair the game

On Steam, use Verify Integrity of Game Files. On Battle.net, use Scan and Repair. This catches corrupted installs that survive every other fix.

Other steps that help

  • Run the game as administrator.
  • Close background apps that inject into games, like RGB software.
  • Check your temperatures. A GPU above 85 degrees will throttle and crash under load.
  • Lower settings to test stability, then raise them back one at a time.

Crash fixes that backfire on PC

  • Reinstalling Windows before closing RivaTuner.
  • Running two overlay stacks at once.
  • Ignoring laptop thermals during long sessions.

Change one thing at a time

The reason a crash fix seems to work and then stops working is that most players apply five at once. Every change resets the clock, so when the crash returns you cannot tell which one mattered. Apply one fix, play a session on the content that reliably crashed, and only then move to the next. If a fix survives a full evening, write it down — the next time the game touches its renderer you will want that list. Capping the frame rate is the change most likely to show a result within one evening. See best settings and the settings file location.

Advertisement
Advertisement

Related Destiny 2 Guides

Destiny 2 Best Settings for FPS on PC

Destiny 2's biggest FPS costs are not the settings most players lower. Here is what to change, and what to leave alone.

Destiny 2 checkpoint bot: what it is and the risks

Checkpoint bots hand you a raid save so you can skip to a boss. Here is how they work, why Bungie warns against them, and the safe in-game alternatives.

Destiny 2 Error Codes Explained: What They Mean and Fixes

The most common Destiny 2 error codes and what to do about each one, from BEAVER and CAT to network errors

Destiny 2 on GeForce Now: How to Play Without a Gaming PC

Destiny 2 runs on GeForce NOW with a linked Steam account. Free tier limits, bandwidth needs, and what to expect

Destiny 2 Inventory Manager: Tools, Safety, and Setup

Set up a Destiny 2 inventory manager safely. Compare trusted tools, fix common loading errors, and keep your account secure.

Destiny 2 isn't working: quick fixes before you reinstall

Game won't launch or keeps crashing? Run through these checks first. Most 'not working' cases have a simple cause.

Sources & References

This guide is verified against the game's own data and official communications. For patch notes, current balance, and authoritative specifics, consult the references below. Where a precise number cannot be verified, we explain the mechanic rather than invent a figure.