Fix the STATUS_STACK_BUFFER_OVERRUN “Aw, Snap!” Error in Google Chrome

The STATUS_STACK_BUFFER_OVERRUN error is a browser crash that triggers Chrome’s “Aw, Snap!” page. This error code indicates that Chrome encountered a serious memory handling problem—specifically, a buffer overflow where data spilled over its allocated memory stack, causing Windows to force-terminate the process for safety.

This issue is caused by hardware acceleration conflicts, outdated graphics drivers, corrupted site data, or third-party extensions. Follow these structured troubleshooting steps to resolve the crash.

Step 1: Open the Page in Incognito Mode

Before modifying system files, rule out extensions or localized tracking cookies.

1. Open Chrome, click the three vertical dots in the top-right corner, and select New Incognito Window (or press Ctrl + Shift + N).
2. Navigate to the website that triggered the crash.

If the page loads without the error, an extension or your browser cache is corrupting memory. Skip directly to Step 2 and Step 3. If it still crashes, proceed to Step 4.

Step 2: Clear Cookies and Cache for the Specific Site

If a corrupted data packet on a specific webpage causes the stack overrun, clearing that site’s local data will fix it.

1. In Chrome, click the three dots > Settings > Privacy and security.
2. Click Third-party cookies and select See all site data and permissions.
3. Use the search bar at the top right to search for the domain name causing the issue (e.g., youtube.com or facebook.com).
4. Click the Trash icon next to the site name and confirm by clicking Delete.

Step 3: Disable Defective Extensions

Third-party extensions, particularly ad-blockers or scripts that inject code into web elements, can frequently mismanage stack memory.

1. Type chrome://extensions/ into the address bar and press Enter.
2. Toggle Off all active extensions.
3. Reload the problematic tab.
4. If the error disappears, toggle your extensions back on one by one to isolate the culprit.

Step 4: Toggle Hardware Acceleration or Adjust ANGLE Backend

GPU driver mismatches are a frequent root cause of stack memory faults when rendering complex assets or video streams.

Option A: Disable Hardware Acceleration

1. Go to Chrome Settings > System.
2. Locate Use graphics acceleration when available and switch the toggle to Off.
3. Click Relaunch.

Option B: Change the ANGLE Graphics Backend

If you want to keep hardware acceleration active but change how Chrome interfaces with your GPU:

1. Type chrome://flags/#use-angle into the address bar and press Enter.
2. Change the drop-down menu next to Choose ANGLE graphics backend from Default to D3D11 or OpenGL.
3. Click the Relaunch button at the bottom of the screen.

Step 5: Check Shortcut Compatibility Settings

Sometimes Windows runs the Chrome application launcher in an unnecessary compatibility layer, forcing memory execution restrictions.

1. Right-click your Google Chrome desktop shortcut and select Properties.
2. Switch to the Compatibility tab.
3. Ensure that the box labeled Run this program in compatibility mode for: is completely unchecked.
4. Click Apply, then click OK.

Step 6: Reset Chrome to Original Defaults

If the underlying configuration files are corrupted, resetting the application backend restores fresh system paths without deleting your saved passwords or bookmarks.

1. Go to Chrome Settings > Reset settings.
2. Click Restore settings to their original defaults.
3. Click the blue Reset settings button to confirm.

If one of these options resolved the issue for you, drop a note in the comments form below. That’ll help others and me.