You're staring at that sad little page with the frowning face, and it's driving you nuts. Let's cut to the chase—most of the time, this comes from a corrupted GPU cache or a bad graphics flag. Here's the fix that works in 90% of cases.
The Fix: Clear GPU Cache and Reset Flags
- Close Chrome completely. Make sure no background processes are running—check your system tray (the little icons near the clock) for Chrome, and right-click any you see, then choose Exit.
- Press
Windows + R(orCmd + Shift + Gon Mac in Finder) to open a run dialog. Type the following path and press Enter:
%LOCALAPPDATA%\Google\Chrome\User Data\Default\GPUCache
On Mac, the path is:
~/Library/Application Support/Google/Chrome/Default/GPUCache
If that folder doesn't exist, don't panic—it means your GPU cache is already gone, so skip to step 4.
- Select everything inside the GPUCache folder (Ctrl+A or Cmd+A) and hit Delete. You don't need to delete the folder itself, just its contents. After you do this, close the File Explorer window.
- Now open Chrome again. Type
chrome://flagsin the address bar and press Enter. This page is full of experimental settings—don't touch anything else here. - In the search box at the top, type "GPU". You'll see several entries. For each one, click the dropdown and select Disabled. Specifically, look for:
- GPU compositing on all pages
- Override software rendering list
- GPU rasterization
- After you've disabled those, click the blue Relaunch button at the bottom right. Chrome will close and reopen if you have "continue where you left off" enabled, or you'll open it fresh.
When Chrome comes back, try loading a page that was crashing. You should see it load normally. The 'Aw, Snap!' message shouldn't appear anymore.
Why This Works
Here's the deal. Chrome uses your GPU to render web pages faster. When the graphics driver updates or crashes, the cached data in GPUCache gets corrupted. Chrome reads that bad data and can't draw the page, so it gives up and shows you the error. Clearing the cache tells Chrome to start fresh. Disabling the GPU flags forces Chrome to use a simpler rendering path that doesn't rely on your graphics card. That avoids the problem entirely until the driver sorts itself out.
I've seen this on Windows 10 and 11 after a driver update, and on older MacBooks with Intel graphics. The fix holds until the next driver hiccup, but at least you're not stuck.
Less Common Variations
Sometimes clearing the GPU cache isn't enough. If you're still seeing 'Aw, Snap!' on every page, try these in order:
1. Clear All Cache and Cookies
Go to Chrome Settings > Privacy and security > Clear browsing data. Set time range to "All time", check both "Browsing history" and "Cached images and files", then hit Clear data. This wipes out any other corrupted cache files—not just the GPU ones.
2. Disable Hardware Acceleration
Go to Settings > System and turn off "Use hardware acceleration when available". This is the nuclear option—it stops Chrome from using your GPU for everything, not just graphics. It's a bit slower for video playback, but it's stable. After changing this, Chrome will ask you to relaunch. Do it.
3. Check for Malware
If the problem only happens on certain pages, like your bank or email, something might be injecting scripts. Run a scan with Malwarebytes—don't trust built-in Windows Defender alone. A quick scan catches most of it.
4. Create a New Chrome Profile
Your profile might be corrupt. Click your avatar in the top right, then the gear icon, then "Add". Create a new profile and try browsing there. If it works, your old profile has a problem—you can move bookmarks over with the bookmark manager, but don't copy extensions one by one; a bad extension is often the culprit.
Preventing It From Happening Again
You can't stop every crash, but you can cut them down. First, keep Chrome updated. Go to menu > Help > About Google Chrome. If there's an update, it installs automatically and you restart. Updates often include GPU cache fixes.
Second, keep your graphics drivers current. On Windows, go to Device Manager, find Display adapters, right-click your card, and select Update driver. Search automatically—Windows will pull the latest. On Mac, just install all system updates from the App Store.
Third, if you're using Chrome extensions that mess with page rendering (like ad blockers or dark mode toggles), consider limiting them. One bad extension can corrupt the GPU cache every time you load a page. Test with extensions disabled by going to chrome://extensions and toggling them off one by one.
Lastly, don't ignore repeated crashes. If you're seeing 'Aw, Snap!' more than once a week, check your event viewer for graphics driver errors. Go to Start, type Event Viewer, open it, then Windows Logs > System, and look for entries with source "Display". If you see "The driver \\Device\\Video... stopped responding and has recovered", that's your GPU driver crashing. Fix that first, and the Chrome error follows.
That's the whole process. Clear the GPU cache, disable graphics flags temporarily, and you're back in business. If it recurs, you know to look at drivers and extensions.