Getting STATUS_STACK_BUFFER_OVERRUN in Chrome on Windows 11? Check out a quick fix!

If you are experiencing STATUS_STACK_BUFFER_OVERRUN in Chrome on your Windows device, an easy fix is available.

Google Chrome is one of the most popular browsers in the world because it is fast, simple, and works across all devices. But sometimes, even Chrome can run into strange issues after an update. One such problem many users started seeing recently is the STATUS_STACK_BUFFER_OVERRUN error. This error causes Chrome to close suddenly, especially while watching YouTube Shorts or scrolling through video content.

This issue is not caused by your PC, antivirus, or malware. It appears to be a Chrome-side bug, and hundreds of users reported the same problem on the same day.

What Users Tried Before Finding the Real Fix

Many users attempted common troubleshooting steps, but none of these solved the issue:

• Clearing browser cache and history
• Running system cleanup commands
• Full antivirus scan (no threats found)
• Updating graphics drivers
• Trying Incognito Mode (still crashed)
• Changing Chrome compatibility mode settings

None of these worked because the issue is linked to Google Chrome’s graphics backend after a recent update.

Working Fixes for STATUS_STACK_BUFFER_OVERRUN in Chrome

Change Chrome’s ANGLE Graphics Backend (Recommended Fix)

This is the most reliable fix reported by multiple users. Steps below:

1. Open Chrome.
2. In the address bar, type: chrome://flags
3. Search for: Choose ANGLE graphics backend
4. Change it from Default to D3D11.
5. Restart Chrome.

Users confirmed that this completely stopped the crashes.

Some users also noted that Chrome may sometimes fall back to D3D9, which triggers the error again. Setting it manually to D3D11 prevents that.

2. Launch Chrome With This Flag

If the above doesn’t work:

1. Right‑click your Chrome shortcut → Properties
2. In the Target field, add this at the end:

Code

--use-angle=d3d11

3. Click Apply → OK
4. Restart Chrome

Users confirmed this also works reliably for STATUS_STACK_BUFFER_OVERRUN in Chrome.

Temporary Workaround: Rename chrome.exe

This is the weirdest but surprisingly effective workaround. The steps for that are below:

1. Go to the Chrome installation folder
2. Rename chrome.exe to chrome1.exe
3. Launch Chrome using the renamed file.

These steps can help you fix with STATUS_STACK_BUFFER_OVERRUN in Chrome.