Starfield crashing after AMD 26.8.1? Install 26.9.1

Start with the four-part gate

AMD's bulletin is specific. It does not say that every Starfield crash is a 26.8.1 problem, and it does not expand the confirmed scope to every Radeon GPU.

• Game: the problem happens in Starfield.
• GPU: the PC uses a Radeon RX 9000 series graphics product.
• Driver: AMD Software reports Adrenalin Edition 26.8.1.
• Timing: the crash is new or materially changed after that driver arrived.

If any part is false or unknown, pause the incident-specific update. Use the broader game-crash guide to classify the failure instead. A mod conflict, damaged save, unstable overclock, heat problem, missing runtime, or unrelated game update needs different evidence.

Record the current state before changing the driver

Open AMD Software and record the graphics product and software version. Also write down the Windows version, where Starfield was installed, whether the game reaches the menu, where it crashes, which save or new-game path you tested, and whether other games or Windows are affected.

Save screenshots of the version page and the crash timing, but remove usernames and account details before sharing them. If the whole screen goes black, Windows loses the display adapter, or the PC fails outside Starfield, move to the broken-driver recovery guide. That is wider than AMD's Starfield-only bulletin.

Protect saves and the test condition

Make sure your local and cloud save state has finished synchronizing before a driver update or restart. Do not delete a save because it crashes under 26.8.1. The same save-load attempt is useful evidence after the update.

If you use mods, record the exact mod state without changing it yet. Changing the driver, game files, mods, overlays, and saves at the same time makes the result hard to interpret. One controlled change gives you a cleaner answer.

Get 26.9.1 from AMD, not a mirror

Use AMD's official Radeon RX 9000 driver route and match the exact product and Windows version. Read the 26.9.1 release page before downloading. A desktop Radeon package is not automatically the correct package for a laptop or all-in-one.

• Desktop card: confirm the exact RX 9000 model and supported Windows version on AMD's page.
• Laptop or all-in-one: check the PC manufacturer's driver package and support notes. AMD says some OEM-specific features are supported by the manufacturer's customized driver.
• Handheld, Boot Camp, Linux, or another platform: do not use this Windows desktop incident as a shortcut. AMD's 26.9.1 package notes exclude handheld gaming devices and Apple Boot Camp platforms from this package.

Download the correct 26.9.1 package before starting the update. That avoids searching for a driver while the display is in a reduced-function state.

Keep cleanup as a recovery step

Start with AMD's normal 26.9.1 installation path. If the installer fails or the installed version does not change, AMD's Cleanup Utility is a documented recovery option. The utility removes AMD graphics and audio driver software, not AMD chipset drivers. AMD recommends running it in Safe Mode for the best result, creates an AMD Cleanup Utility Restore Point, and requires a restart when cleanup finishes.

AMD also warns that the display can flicker or go blank during cleanup. Read the full official instructions and recovery notes before starting. Do not launch cleanup while Windows Update is installing, the PC is unstable, storage is reporting errors, or you do not have reliable power and a recovery path.

If the computer does not recover as AMD describes, stop stacking changes. Use AMD's documented restore-point path or move to supported Windows recovery with the evidence you saved.

Install, read back, and repeat one test

Install the official 26.9.1 package that matches the hardware. Restart if the installer requires it. Then open AMD Software and read the installed version back. Do not assume the update worked because the installer closed normally.

Launch Starfield and repeat the same limited test you recorded earlier: the same route to the menu, the same save-load attempt, or the same new-game checkpoint. Stop if the system becomes unstable outside the game.

• 26.9.1 is installed and the same load works: the result matches AMD's fixed-issue note. Preserve the before-and-after record.
• 26.9.1 is installed and the same crash remains: the result weakens the driver-incident explanation. Return to general game-crash diagnosis instead of repeating cleanup.
• The installed version is not 26.9.1: do not call the update successful. Check the product package, OEM path, installer result, and whether Windows replaced the driver.
• Windows or other games now fail: stop the Starfield test and treat this as wider driver recovery.

What the update does not prove

A successful 26.9.1 test does not prove that every 26.8.1 installation is defective. It also does not repair a corrupt save, remove a bad mod, fix unstable hardware, or explain an unrelated crash on a different GPU family. It shows that the controlled version change affected your exact reproduction.

Keep checking AMD's current release notes before making another driver change. Only AMD's live release information should set the supported path—not an old forum comment or an unofficial package.

Where OmniMend fits

OmniMend does not install, remove, or roll back graphics drivers, and it cannot guarantee that Starfield will launch. It can help you keep the Windows, GPU, driver, event, and repeat-test evidence organized so you can tell an exact driver incident from a broader game or PC problem.

Download OmniMend for supported Windows diagnosis if you want an optional evidence pass before or after the vendor-directed update. Review what OmniMend can inspect, and keep saves, account details, and private logs out of anything you share publicly.