Fast answer
Separate a crash-to-desktop from an endless Logging In screen first. For a true crash, apply only the official branch for your store: Steam/Xbox account services, Xbox blocked-contact checks, or general PC crash checks.
Do this first
Save-safe order
- Confirm the game closes or shows an error; a screen that stays open is the loop branch.
- Update the game, OS, and GPU driver, then restart once.
- Use Obsidian's Steam-login or general crash article for the matching store.
- On Xbox/Xbox PC, review the tracker condition involving blocked contacts.
- Capture exact error text before escalating.
01
Pick the correct branch
Store and account layers differ. Steam may still touch Xbox services for identity, while Xbox console and Xbox PC have different local repair surfaces.
- Steam: official Steam-login and Gaming Services path
- Xbox app PC: account services and file verification
- Xbox console: tracker condition and account list
- Any PC build: specs, drivers, file integrity, mods, overlays, thermals
02
Protect the save
Do not delete the save directory, clear cloud data, or replace a world to test a login problem. Record the store, version, error, and whether the crash occurs before or after the title screen.
Evidence ledger
Sources checked
OfficialGame Is Crashing at LoginOfficial tracker entry for the login-crash family.
↗Official supportCrashing on Steam LoginOfficial Steam-specific repair path.
↗Official supportGrounded 2 Is CrashingOfficial general PC crash checklist.
↗Official sources establish shipped features, issue status, and support steps. Cross-check and community sources are labeled and never treated as universal fixes.


