Google Chrome Aw Snap: Fixing the Recurring Crash

If Google Chrome crashes immediately on opening and shows the “Aw, Snap!” error page instead of loading normally, here’s how to work through it systematically. Troubleshooting Steps Restart Chrome completely — close every Chrome window and check Task Manager for lingering chrome.exe processes, since a stuck background process can cause this on relaunch. Disable hardware […]

Google Chrome Aw Snap Crash
If Google Chrome crashes immediately on opening and shows the “Aw, Snap!” error page instead of loading normally, here’s how to work through it systematically.

Troubleshooting Steps

  1. Restart Chrome completely — close every Chrome window and check Task Manager for lingering chrome.exe processes, since a stuck background process can cause this on relaunch.
  2. Disable hardware acceleration — go to chrome://settings/system and turn off “Use hardware acceleration when available,” then restart Chrome. GPU driver issues are a common cause of crash-on-launch.
  3. Disable extensions — launch with chrome.exe --disable-extensions or check via chrome://extensions in a working profile; a misbehaving extension can crash the browser on startup.
  4. Create a new Chrome profile — a corrupted user profile is a very common cause. Create a new profile and see if it opens cleanly; if it does, your original profile’s data is the problem.
  5. Reinstall Chrome — uninstall completely (including leftover data in %LocalAppData%\Google\Chrome, backing up bookmarks first if needed) and reinstall the latest version.

At Scale (Group Policy)

If this is hitting multiple users at once, check whether a recent Chrome auto-update or a Group Policy change (particularly around hardware acceleration or extension allow/block lists) rolled out around the same time — a policy pushed via GPO that’s incompatible with the current Chrome version is a common cause of a fleet-wide, simultaneous onset of this issue.

Still Current in 2026

All five steps above remain valid, current troubleshooting guidance — Google’s own support documentation still lists disabling extensions and a full uninstall/reinstall as standard fixes for this class of crash. Chrome’s current stable channel is version 152 (released August 2026), so if you’re troubleshooting a machine running something noticeably older, updating first is worth trying before working through the rest of this list — an out-of-date build is itself a common cause of crash-on-launch behaviour.

Resources

aw snap Registry Addition

Discover more from TechyGeeksHome

Subscribe to get the latest posts sent to your email.

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Active Directory, PowerShell, and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published over 1,500 practical guides covering real-world IT problems and solutions. When not solving IT problems,

Andrew develops free Windows utilities including Ultimate Settings Panel, which has been downloaded over 850,000 times.