What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start with Bungie’s service status and your platform’s update queue, not with router changes or a reinstall. Maintenance or a missing patch can look like a local crash or disconnect. If services are online and the game is current, classify the exact code and its pattern: one isolated disconnect usually needs a relaunch, the same code repeatedly points to one installation or network fault, and several different codes often indicate unstable connectivity.
This guide follows that order for Destiny 2 on console and PC. It covers CAT and SHEEP update errors, post-update crashes, Steam and Epic Games Store repair steps, Wi-Fi diagnostics, advanced network settings, known hardware-specific issues, and the details to collect before escalating.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Destiny 2 - PlayStation 4 Standard Edition | $6.01 | Buy on Amazon |
| 2 |
|
Destiny - Standard Edition - PlayStation 4 | $15.60 | Buy on Amazon |
| 3 |
|
Destiny 2 - Standard Edition | $10.00 | Buy on Amazon |
| 4 |
|
Destiny 2: Forsaken - Legendary Collection - PlayStation 4 | $8.52 | Buy on Amazon |
Use this 60-second triage first
| What you see | Most useful first action |
|---|---|
| Destiny is unavailable or maintenance is announced | Wait for service restoration and monitor Bungie’s Destiny Server and Update Status page. |
| CAT appears | Exit Destiny 2, install the available update, then restart the launcher or console. |
| SHEEP appears in a fireteam | Have every player close Destiny 2 and install the same latest update. |
| The game crashes without a code | Check known issues, confirm the update completed, restart the platform, and then repair files or clear cache. |
| One disconnect with a recognizable code | Close and relaunch Destiny 2 once. |
| The same Destiny code returns repeatedly | Restart the game and platform, clear the platform cache, test a wired connection, and follow the article for that exact code. |
| Different Destiny codes keep appearing | Treat the pattern as a network-stability problem: power-cycle network hardware, reduce competing traffic, and test Ethernet. |
These are diagnostic priorities, not guarantees. A cable test can reveal a Wi-Fi problem but cannot repair a Bungie outage or a damaged game installation.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →1. Check Bungie’s service status and the update queue
Rule out maintenance or an outage
Bungie warns that Destiny may be offline during scheduled maintenance. Open the Destiny Server and Update Status page before changing local settings. If maintenance or an incident is active, wait, watch Bungie’s official support updates, and retry after service is restored. Local reinstalls and router changes cannot bring a game service back online.
#1 Best Overall
- From the makers of the acclaimed hit game Destiny, comes the much-anticipated sequel
- An action shooter that takes you on an epic journey across the solar system
- Humanity’s last safe city has fallen to an overwhelming invasion force, led by Ghaul, the imposing commander of the brutal Red Legion
- To defeat the Red Legion and confront Ghaul, you must reunite humanity’s scattered heroes, stand together, and fight back to reclaim our home
For broader symptoms, Bungie’s Destiny 2 Server Issues guidance covers post-maintenance connection failures, cache clearing, power cycling network equipment, and additional network checks.
Install a missing patch
CAT means a newer Destiny 2 update is available. Exit the game completely and let the platform download and install the current version before launching again. Restart the console or PC launcher and manually check for updates if the patch does not appear.
On Steam, Bungie’s Error Code: CAT instructions include restarting Steam. If CAT remains, verify the game’s file integrity and clear Steam’s download cache, then restart Steam and check the update again.
Recommended Free Tools
On Epic Games Store, restart the Epic launcher. If the update still will not apply, verify the installed files and clear the launcher’s webcache before trying again. Do not launch an older build while other fireteam members are on the current one.
Synchronize a fireteam
SHEEP generally means a fireteam member is running an older version. Bungie’s status guidance says every player should close Destiny 2 and install the latest update. Reopen the game only after each platform reports that the update has finished.
What changed in 2026
Bungie’s Monument of Triumph and Update 9.7.0 Support Guide dates Update 9.7.0 to June 9, 2026. Bungie says planned live-service content updates have ended, but it may still ship a health-and-stability hotfix. Therefore, “no planned content updates” does not mean Destiny 2 can never receive another patch; continue checking for hotfixes when troubleshooting an update-related failure.
Rank #2
- Online only and requires a PlayStation Plus membership.
- An incredible story set within a newly-imagined, always-connected universe filled with action and adventure.
- Create your character, forge your legend by defeating powerful foes, and earn unique and customizable weapons, gear, and vehicles.
- Unprecedented variety of FPS gameplay that redefines the genre and breaks traditional conventions of story, cooperative and competitive multiplayer modes.
2. Identify the code and its pattern
Destiny codes versus platform codes
Destiny’s own disconnect messages commonly use names such as WEASEL, MARIONBERRY, and BANJO. PlayStation, Xbox, Steam, and Epic can also display platform-specific codes. Use Bungie’s Error Codes: Disconnected From Destiny page for a Destiny code; use the relevant platform’s support service for a platform code. The distinction matters because a launcher error may need a file or account fix while a Destiny code may reflect the connection between your setup and Bungie’s services.
Free tools Windows power users keep installed
One-click scans. No signup required.
Read the frequency, not only the label
| Pattern | What it suggests | Next move |
|---|---|---|
| One isolated disconnect | A transient event is possible. | Close and relaunch Destiny 2 once. |
| The identical Destiny code repeats | One root cause is more likely, such as installation data corruption or a persistent network fault. | Restart the game and platform, clear cache, test Ethernet, and follow the exact-code article. |
| Several different Destiny codes recur | Bungie says varying codes often reflect instability in the network setup, including Wi-Fi or upstream traffic. | Power-cycle the modem/router, stop competing traffic, test wired networking, and investigate packet loss or stability with the ISP. |
| A code appears only in a fireteam | Version mismatch or a member’s connection may be involved. | For SHEEP, have all players update; otherwise compare each player’s exact code and platform. |
Write down the complete code, when it appears (launch, matchmaking, activity loading, or mid-game), how often it occurs, and whether all players are affected. That pattern is more useful than a generic “Destiny keeps disconnecting” description.
3. Follow a safe troubleshooting order
- Finish the update. Confirm the launcher or console shows the current Destiny 2 version. Restart it and check again if the update was queued but not applied.
- Restart Destiny 2. Close it rather than leaving it suspended, then launch a fresh session. This is the proportionate response to a single disconnect.
- Restart the platform. Reboot the console or PC so a stuck launcher, shader process, or network session is discarded.
- Clear the platform’s cache. On Steam, restart Steam and, if CAT or installation behavior persists, clear the download cache. On Epic Games Store, restart the launcher and clear its webcache when needed. Use the launcher’s own documented process; do not delete arbitrary Destiny folders.
- Repair game files. Verify file integrity in Steam or verify files in Epic Games Store when the update will not complete, files are reported missing, or crashes began immediately after patching.
- Test the connection. Pause downloads, streaming, cloud backups, and other heavy traffic. If possible, connect the platform directly to the router with Ethernet for one or more sessions.
- Power-cycle network hardware. Shut down the modem and router, wait for them to finish powering off, start them again, and wait for the connection lights and internet service to return before launching Destiny.
- Escalate conditionally. If the same failure remains, use the exact-code article, platform support, Bungie’s help forum, or your ISP, depending on what the evidence points to.
This sequence avoids making advanced router changes before establishing whether the service is down, the patch is missing, or Wi-Fi is the variable.
4. Fix crashes that began after an update
Confirm whether the crash is update-related
Note whether Destiny 2 crashes at launch, during a particular activity, when entering a crowded area, or after a repeatable action. Check that the update completed, restart the platform, and verify files before changing graphics settings. A crash with no error code is not automatically a network problem, and a generic cache clear is not a universal fix.
Check Bungie’s current known-issues list
Bungie’s Destiny 2 Known Issues and Vital Information page lists issues that can be hardware- or platform-specific. The Monument of Triumph section is marked “Last Updated: July 7, 2026,” so check the page for changes rather than assuming an old workaround still applies.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsIntel 12th-generation Iris integrated graphics laptops
Bungie specifically lists crashes under high demand on laptops using Intel 12th-generation Iris integrated graphics. Its Windows 10 mitigation is to select the laptop’s discrete GPU and set Destiny 2 to High Performance in Windows Graphics Settings. This is a targeted workaround:
Rank #3
- Brand New in box. The product ships with all relevant accessories
- Open Windows Settings.
- Go to System > Display > Graphics.
- Add or select the Destiny 2 executable.
- Choose Options, select the discrete GPU or High Performance, and save.
- Restart Destiny 2 and check whether the high-demand crash still reproduces.
Do not apply this Intel-specific setting as a universal crash cure. It does not address a missing update, corrupted files, a Bungie outage, or a separate graphics driver problem.
Steam performance drops and hitches
The known-issues page also says Bungie was investigating Steam frame hitches and performance drops present since Update 9.7.0.2. If the symptom is stutter or a sudden frame-rate decline rather than a full crash, record that version context and check the page for status. Avoid presenting a performance investigation as proof that every Steam crash has the same cause.
When file verification is appropriate
- Use verification after an interrupted download, a launcher-reported file error, or a crash that began directly after patching.
- Restart the launcher after verification so pending downloads can finish.
- If verification repeatedly finds the same files, capture the result and escalate; repeated replacement can indicate a disk, permissions, or launcher problem rather than a Destiny server issue.
5. Stabilize connection and disconnect problems
Start with Ethernet as a diagnostic test
“For the best Destiny experience, Bungie strongly recommends a wired internet connection as WiFi connections may lead to signal strength and stability issues.”
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
That statement appears in Bungie’s Network Troubleshooting Guide. Connect the console or PC directly to the router with an Ethernet cable and repeat the activity that normally disconnects. A low-cost Cat 6 cable is sufficient for a basic test; no particular brand is required. If the wired session is stable while Wi-Fi fails in the same place and time, investigate wireless signal, interference, or router placement. If both fail, the cause may be upstream congestion, packet loss, the platform, the game installation, or Bungie’s service.
Reduce competing traffic
Pause large downloads, game updates on other devices, cloud synchronization, video uploads, and high-bitrate streaming while testing. Bungie notes that upstream traffic and unstable Wi-Fi can produce varying disconnect codes. Ask other users to avoid saturating the connection during one controlled test session so you can compare results.
Power-cycle, then measure
Power-cycle the modem and router before changing settings. After they reconnect, test Destiny 2 and record whether the code, timing, or frequency changes. If the problem persists, use Bungie’s latency and packet-loss guidance and ask the ISP whether it sees packet loss, line instability, or upstream congestion. A speed-test headline number alone does not prove that a game connection is healthy; consistency during the activity is the relevant observation.
Rank #4
- Available 9.3.18. Playable 9.4.18 at 10AM PDT
- Destiny 2
- Expansion I: Curse of Osiris
- Expansion II: Warmind
- Destiny 2: Forsaken
Advanced router options are conditional
Bungie’s server-issues guidance discusses UPnP, NAT status, port forwarding, and changing DNS as later possibilities. Consider them only after service status, updates, restarts, cache, wired testing, and power cycling have been checked. Record the original router settings before changing them, change one setting at a time, and undo a change that worsens matchmaking or disconnects. Port forwarding is not a guaranteed fix and should not be the opening step for an unexplained crash.
6. Platform and launcher decision table
| Platform or launcher | Update and repair sequence | When to escalate |
|---|---|---|
| PlayStation | Restart the console, manually check for the Destiny 2 update, then follow the exact Destiny code article. For a platform code, use PlayStation support. | The platform displays its own error, the update will not install, or other games show the same failure. |
| Xbox | Restart the console, check the Destiny 2 update, and distinguish an Xbox system code from a Destiny code. | Xbox reports a platform or account service issue, or multiple games fail. |
| Steam | Restart Steam; for CAT or update trouble, verify integrity and clear Steam’s download cache, then restart and retry. | Verification loops, Steam reports disk or permission errors, or only Steam shows the failure. |
| Epic Games Store | Restart Epic Games Store; verify files and clear its webcache if the patch is missing or files appear damaged. | The Epic launcher cannot update or reports a launcher-specific code. |
Platform support is the correct destination for a console, Steam, or Epic error that is not a Destiny code. Bungie’s code article is the right reference when the message names a Destiny error such as WEASEL, MARIONBERRY, or BANJO.
7. Know when a reinstall is—and is not—reasonable
A reinstall is a later recovery option, not the first response to a maintenance window, CAT, or a single disconnect. Try the current update, restart, cache clearing, and file verification first. Reinstalling cannot fix Bungie downtime, Wi-Fi interference, ISP packet loss, or a platform outage, and it consumes time and bandwidth.
Consider reinstalling only when the launcher cannot repair files, verification repeatedly fails, the installation is clearly incomplete, or platform support directs you to do so. Keep your exact error record and note whether a clean installation changes the symptom; that comparison helps separate installation corruption from network instability.
8. Escalate with evidence that can be acted on
If the ordered checks do not resolve the problem, report a compact timeline rather than a generic crash description. Include:
- Exact Destiny or platform error code, including capitalization.
- Platform and launcher (console, Steam, or Epic Games Store).
- Destiny 2 version or update involved, such as 9.7.0 or 9.7.0.2.
- Date and approximate UTC/local time of each failure.
- Activity and location where it occurred, plus whether it happened at launch or mid-session.
- Whether the event was one disconnect, the same code repeatedly, or several different codes.
- Results of restart, cache clearing, file verification, wired testing, and modem/router power cycling.
- Whether other devices or games lost connectivity at the same time.
Use the relevant platform’s support service for platform errors. For Destiny codes, consult Bungie’s Error Codes: Disconnected From Destiny page and Bungie’s server-issues guidance; Bungie directs players with unresolved recurring problems to its help channels. If the evidence points to packet loss or line instability, give the same timestamps and pattern to the ISP.
Quick Recap
Final decision guide
- Maintenance or outage: wait and monitor Bungie status.
- CAT or SHEEP: close Destiny 2 and synchronize the latest update for every player.
- Single disconnect: relaunch once.
- Repeated identical code: investigate installation data and the local connection.
- Changing codes: prioritize wired testing, competing-traffic reduction, power cycling, and packet-loss investigation.
- Crash on a listed hardware configuration: apply only the matching known-issue workaround and keep checking Bungie’s current list.
- Platform-specific message: use that platform’s support path.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
