Fix Chrome 'Aw, Snap!' on Windows 11: GPU Cache Corruption

1. Clear the GPU Cache (Most Common Fix)

What's actually happening here is that Chrome stores shader and rendering data in a dedicated GPU cache folder. On Windows 11, especially after a driver update or a sudden power loss, that cache can get corrupted. Once it's corrupt, Chrome's GPU process fails to initialize and every tab that tries to render hits 'Aw, Snap!'.

The fix is simple: delete that cache folder. Chrome will rebuild it from scratch.

1. Close Chrome completely. Use Ctrl+Shift+Esc to open Task Manager and make sure no chrome.exe processes are still running.
2. Press Win+R, type %localappdata%\Google\Chrome\User Data\Default\GPUCache, and hit Enter. If that path doesn't exist, try %localappdata%\Google\Chrome\User Data\ShaderCache.
3. Select everything inside the folder and delete it. You might need to confirm with UAC if Windows thinks you're doing something risky.
4. Restart Chrome and load the page that was crashing.

The reason this works is because the GPU cache is exactly that—a cache. It's not essential data. Chrome recreates it on the next launch. If the corruption was the culprit, the error disappears immediately.

I've seen this fix work on Windows 11 22H2 and 23H2, and it's the first thing I try because it takes ten seconds and has zero side effects.

2. Disable Hardware Acceleration

If clearing the cache didn't help, the problem might not be the cache itself but the GPU process stalling. Windows 11's default graphics settings can push Chrome to use your discrete GPU when it shouldn't—say, when you're on a laptop with hybrid graphics (Intel + NVIDIA or AMD).

Chrome's hardware acceleration hands off rendering tasks to the GPU, which is great for performance but terrible when the GPU driver is buggy. The result: the GPU process crashes, and you see 'Aw, Snap!' with an error code like 0x887A0006 (DXGI_ERROR_DEVICE_REMOVED).

Turning off hardware acceleration forces Chrome to render with your CPU. It's slower for video and heavy animations, but it's stable.

1. Open Chrome and type chrome://settings/system in the address bar.
2. Turn off the toggle for Use hardware acceleration when available.
3. Click Relaunch when the prompt appears.

Now test the page that was crashing. If it loads fine, the issue is clearly tied to GPU acceleration. You can leave it off, or you can try updating your GPU driver to bring acceleration back.

One note: disabling hardware acceleration will also disable your ability to play 4K YouTube videos smoothly. So if you're a media-heavy user, treat this as a temporary fix and jump to the driver update below.

3. Update Your GPU Driver

This isn't just a 'try this too' step. On Windows 11, a stale or broken GPU driver is the root cause of about half of all Chrome GPU crashes. Why? Because Chrome's GPU process is tightly coupled to DirectX 12 and WDDM (Windows Display Driver Model). If your driver doesn't support the required WDDM version or has a known bug, the GPU process will crash under load.

A specific scenario: you've got an NVIDIA GeForce driver from six months ago, and Windows 11 installed a cumulative update that changed how the graphics stack works. Suddenly Chrome's GPU process crashes on every third tab. This is exactly the situation where a driver update resolves things.

Here's how to do it properly:

1. Press Win+X and select Device Manager.
2. Expand Display adapters, right-click your GPU (e.g., 'NVIDIA GeForce RTX 3060' or 'Intel UHD Graphics 630'), and select Update driver.
3. Choose Search automatically for drivers. Windows will check Windows Update and any manufacturer-provided drivers.
4. If Windows says you're up to date but you know there's a newer driver, go to the manufacturer's website (NVIDIA, AMD, Intel) and download the latest directly. Don't use third-party updater tools—they cause more problems than they solve.

After the update, reboot your PC. If you previously disabled hardware acceleration, re-enable it in Chrome and test again.

What's actually happening here is that the new driver fixes the WDDM interaction that was causing the crash. It's not a Chrome bug—it's a driver bug that Chrome exposes. Updating the driver is the permanent fix.

Quick-Reference Summary

Try them in that order. Most people stop at step one and never look back.