Fix Chrome's 'Aw, Snap!' STATUS_ACCESS_VIOLATION Error
Chrome's 'Aw, Snap!' with STATUS_ACCESS_VIOLATION means a tab tried to write to protected memory. Disable hardware acceleration, or update your graphics driver.
Quick answer for advanced users
Open chrome://settings/system, toggle off "Use hardware acceleration when available", then restart Chrome. If that doesn't stick, disable GPU rasterization at chrome://flags/#disable-gpu-rasterization.
Why you're seeing this
This error trips up a lot of people. I remember fielding tickets on this exact code back in my help desk days. STATUS_ACCESS_VIOLATION means Chrome's process tried to write to a memory address it didn't have permission to touch. That's typically a battle between the browser's rendering engine and your GPU driver—especially on pages loaded with heavy JavaScript, like Google Maps, Figma, or a complex dashboard with real-time charts. The trigger is almost always hardware acceleration: Chrome tries to offload rendering to your GPU, and if the driver's flaky or outdated, the memory gets stomped on.
Fix steps
- Disable hardware acceleration. Go to
chrome://settings/systemand turn off "Use hardware acceleration when available." Then click "Relaunch." This forces Chrome to render everything on the CPU, which is slower but stable. - Update your graphics driver. Check your GPU manufacturer site—NVIDIA, AMD, or Intel. On Windows, you can also use Device Manager, but I've seen Windows Update push old drivers. Go direct. Reboot after updating.
- Disable GPU rasterization. If step 1 didn't help, type
chrome://flags/#disable-gpu-rasterizationin the address bar. Set it to "Enabled" (yes, weird naming—it disables the feature). Restart Chrome. - Reset Chrome flags. Type
chrome://flagsand click "Reset all to default." Over time, flags can get misconfigured.
If the main fix fails
Repair or reinstall Chrome
On Windows, go to Settings > Apps > Chrome > Modify (or Advanced options) and run the repair. If that doesn't fix it, uninstall Chrome, delete %LOCALAPPDATA%\Google\Chrome and %APPDATA%\Google\Chrome (backup your profile first!), then reinstall.
Check for malware
Run Malwarebytes or Windows Defender offline scan. Some redirectors inject script that triggers memory errors.
Create a new Chrome profile
Go to chrome://settings/people, click "Add profile". If the new profile doesn't crash, your old profile has corrupted extensions or data.
Prevention tip
Keep Chrome updated automatically (chrome://settings/help). Also, avoid running multiple heavy JavaScript tabs simultaneously if you have a older integrated GPU. If you're a developer, use Chrome's Task Manager (Shift+Esc) to kill memory-hogging tabs before they crash.
Was this solution helpful?