Home/Troubleshooting guide
Troubleshooting guide

Apex Legends crashing on AMD 26.8.1? Install 26.9.1

Apex Legends crashing on AMD 26.8.1? Confirm an RX 9000 GPU, install AMD 26.9.1 through the official path, read back the version, and retest once.

Apex Legends crashing on AMD 26.8.1? Install 26.9.1
Short answer: AMD Software: Adrenalin Edition 26.9.1 includes a fix for intermittent Apex Legends crashes on Radeon RX 9000 series graphics. If your PC has an RX 9000 card and AMD Software reports 26.8.1, protect the game and crash evidence, download 26.9.1 from AMD's official support route, install it, restart if asked, and read the installed version back. Then repeat the same limited Apex test once. If the hardware or version does not match, do not assume this driver fix applies.
Do not start by deleting game data or stripping the driver. Do not remove saves, local settings, crash files, shader data, the EA app, Steam, or the game as a first step. Do not use a repacked driver, third-party driver remover, registry cleaner, DLL download, BIOS change, firmware change, security-software workaround, or GPU tuning guide. Keep the BitLocker recovery key available before Safe Mode or deeper driver recovery, but never post or share that key.

Confirm that the PC matches AMD's fixed issue

AMD's September 3 release notes name a narrow problem: an intermittent Apex Legends game crash on Radeon RX 9000 series graphics. The fix is listed under resolved issues in Adrenalin Edition 26.9.1.

  • Game: Apex Legends is the program that crashes.
  • Graphics card: the PC uses a Radeon RX 9000 series GPU.
  • Driver: AMD Software reports Adrenalin Edition 26.8.1.
  • Failure: the game exits, freezes, or stops during a repeatable stage without clear whole-PC instability.
  • Platform: the system is a supported Windows PC, not an Apple Boot Camp or handheld gaming device path excluded by the AMD package notes.

If the GPU, driver, or platform does not match, use the broader game-crash guide. The same symptom can come from a game update, damaged files, memory, storage, overlays, tuning, heat, Windows, or another driver.

Record one repeatable crash test

Write down the exact GPU, AMD Software version, Windows version, Apex version, launcher, crash point, error text, and recent changes. Record whether the crash happens at startup, shader preparation, the lobby, match loading, or during play. Note whether other games or Windows also fail.

Choose one safe reproduction that does not risk rank, purchases, or other players. Do not keep running a crash loop. One clear before result is enough to compare after the driver update.

Protect the evidence before the update

Keep the current AMD version screen, Apex crash report, Windows Reliability Monitor entry, and the time of the failure. If a crash file or event record will be shared, save an untouched local copy before redacting it.

Logs and screenshots can expose a Windows username, device name, file path, account name, email address, IP address, token, or recovery detail. Remove private values from the shared copy. Never post passwords, two-factor codes, recovery keys, or full account screens.

Update Apex through the normal launcher

Let the EA app or Steam finish any available Apex Legends update before changing the driver. Read the game state back from the launcher rather than assuming a completed progress bar means every file is current.

Do not combine a game reinstall, cache deletion, overlay removal, settings reset, and driver change in one test. If the current game update alone fixes the same crash, record that result before continuing with any separately justified driver update.

Get AMD 26.9.1 from the official route

Use AMD's official Drivers and Support page or the supported update control in AMD Software. Match the package to the exact GPU and Windows version. AMD's 26.9.1 notes list Windows 11 version 21H2 and later or Windows 10 version 21H2 and later, depending on the product.

For a laptop or all-in-one PC, check the computer maker's support page before replacing its graphics package. AMD says its reference driver has broad compatibility, while the manufacturer may provide a package validated for that system's features. Keep the OEM installer or recovery route available.

Install the update without adding unrelated changes

Close the game and important work, keep the computer on reliable power, and run the official installer. Use the normal installation path unless the current AMD instructions or the computer maker direct otherwise. Do not disable antivirus protection because an unrelated guide suggests it.

The screen can flicker or go blank briefly while the display driver changes. Let the supported installer finish. Save the final message and restart if it asks. If the installer reports an error or Windows cannot recover the display, stop adding changes and keep that exact result.

Read the version back before retesting

Open AMD Software after the restart and confirm that the installed version is 26.9.1. A closed installer or a downloaded file is not proof that the active driver changed. Also check the Windows display-driver version if Windows or an OEM utility may have replaced the package.

Launch Apex and repeat the same limited test with the same game settings, launcher, and crash point. Do not enable new overlays, tuning, recording tools, or graphics changes between the before and after tests.

  • 26.9.1 is installed and the same test works: keep the versions and result. Do not add a cleanup or rollback step.
  • 26.9.1 is installed and the same crash remains: save the new evidence and widen the diagnosis. The driver may not be the whole cause.
  • The version did not change: check the installer result, package match, OEM path, and whether Windows replaced the driver.
  • The PC now fails outside Apex: stop the game test and move to wider graphics-driver recovery.

Use cleanup only as a recovery step

AMD Cleanup Utility is not required just because Apex crashed. AMD documents it for removing installed AMD graphics and audio driver software when normal installation or driver recovery needs a clean state. It does not remove AMD chipset drivers.

Cleanup can use Safe Mode, create a restore point, interrupt the display, and require a restart. Prepare sign-in access and the BitLocker recovery path before using it. Download the correct replacement or OEM driver first. If those recovery steps are unfamiliar, stop and get qualified help instead of experimenting on the only working display.

Keep other crash patterns separate

AMD 26.9.1 also lists a fix for an intermittent Starfield crash on some RX 9000 products. If Starfield is the affected title, use the separate Starfield and AMD 26.8.1 guide. One fixed game does not prove that every crash has the same cause.

If Apex still crashes after the exact update, compare another game and ordinary Windows use. Check whether the system restarts, loses display, reports memory or storage errors, or fails only in one Apex stage. Send the redacted before and after evidence to EA, AMD, the PC maker, or a technician instead of repeating driver removal.

Where OmniMend fits

OmniMend does not update Apex Legends, install or remove AMD drivers, change GPU tuning, delete game data, or prove the cause of a crash. On a supported Windows PC, OmniMend 2.0.5 can help organize system, storage, update, service, and log clues before or after the official vendor steps.

Download OmniMend for Windows if you want an optional diagnostic pass. Review what OmniMend can inspect, keep account and recovery details out of shared reports, and approve any supported repair action separately.

Editorial sources

Checked September 4, 2026 against AMD's current Adrenalin Edition 26.9.1 release notes, Adrenalin Edition 26.8.1 release notes, AMD Software installation guidance, and AMD Cleanup Utility guidance. AMD provides the affected GPU and game match, the 26.9.1 fix, supported package path, OEM boundary, and cleanup behavior. OmniMend added the evidence checklist, privacy limits, one-test readback, recovery stop points, and product boundaries.

Bring the problem.
Start with the evidence.

Try supported diagnostics on your own device. Eligible new users get a limited-usage 7-day trial, with no card required.

Get OmniMend