Fix ERROR_STACK_BUFFER_OVERRUN (0x00000502) in Windows 10/11

What is ERROR_STACK_BUFFER_OVERRUN?

If you're seeing this stop code, your system just hit a block. The error means a program tried to write more data into a stack buffer than it can hold. It's like pouring a gallon of water into a cup — things spill, and Windows says enough, kill the app or restart the PC.

I've seen this on Windows 10 and 11, often when opening a specific app or during a game. One client had it every time they launched their accounting software. Another got it randomly during Chrome browsing. It's not a virus, but it can feel like one.

The good news? Most fixes are quick. Let's go through them in order, from 30 seconds to 15 minutes.

Fix 1: Quick Reboot (30 Seconds)

Yes, I know it's boring. But do it. A temporary glitch in a driver, a memory leak, or a bad page file can cause this error once. If it never comes back, you're done. Don't overthink it.

If the error reappears, move to Fix 2.

Fix 2: Update or Roll Back Graphics Drivers (5 Minutes)

In my experience, this error is most common with graphics drivers — especially NVIDIA and AMD. A driver update might have introduced a bug, or you might have an old one that's not compatible with a recent Windows update.

1. Press Win + X and open Device Manager.
2. Expand Display adapters.
3. Right-click your graphics card and select Update driver > Search automatically.
4. If that doesn't help, go to the manufacturer's site (NVIDIA, AMD, Intel) and install the latest version manually.

But wait — sometimes the newest driver is the problem. If this started after a driver update, roll back: right-click the card, go to Properties > Driver > Roll Back Driver.

I had a client last month whose print queue died because of a bad NVIDIA driver. Rollback fixed it in three minutes.

Fix 3: Run System File Checker and DISM (10 Minutes)

Corrupted system files can cause all sorts of weird crashes. The built-in tools are decent enough.

1. Open Command Prompt as administrator. Win + X > Terminal (Admin) works.
2. Type sfc /scannow and press Enter. Wait for it to finish.
3. If it finds errors but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth.
4. Reboot and test.

Note: This won't always work. SFC is hit or miss. But it's worth a try because it's free and doesn't break anything.

Fix 4: Disable Data Execution Prevention (DEP) for the Problem App (5 Minutes)

DEP is a security feature that prevents code from running in non-executable memory. Sometimes it's too strict and blocks a legit app, causing this error. I'm not a fan of disabling DEP globally — that's asking for trouble. But for a specific app, it's okay.

1. Open Command Prompt as admin.
2. Type bcdedit /set nx AlwaysOff and press Enter.
3. Reboot.

Wait, that turns off DEP for everything. Not ideal. Better to add an exception for the specific app. Since Windows doesn't have a GUI for that anymore, you'd need to use editbin from the Windows SDK. Too much hassle for most people.

Alternative: uninstall the problematic app and reinstall it. Often the installer sets a compatible flag. I've seen that fix Outlook plugins more than once.

Fix 5: Check for Memory or Hard Drive Problems (15+ Minutes)

If you're still here, we're getting serious. Bad RAM can cause stack overruns, though it's less common than you'd think.

Memory Diagnostic

1. Search for Windows Memory Diagnostic and run it.
2. Choose Restart now and check for problems.
3. Let it run. It takes a while.

If it finds errors, you need new RAM. No software fix for that.

Check the Hard Drive

Open Command Prompt as admin and run chkdsk C: /f. It might ask to schedule on reboot. Say yes, restart, and wait for it to finish. Bad sectors can corrupt files and trigger crashes.

If both come back clean, we're looking at a deeper issue.

Fix 6: Clean Boot to Isolate the Culprit (10 Minutes)

Sometimes another program or service is messing with your app. A clean boot starts Windows with the minimum drivers and programs.

1. Press Win + R, type msconfig, press Enter.
2. On the Services tab, check Hide all Microsoft services.
3. Click Disable all.
4. On the Startup tab, click Open Task Manager. Disable all startup items.
5. Reboot and try the problematic app.

If the error goes away, turn services back on one by one until it returns. That finds the culprit. I did this for a client whose antivirus was blocking their CRM software. Uninstalled AV, switched to Defender, problem gone.

When to Give Up and Reinstall Windows

Honestly, if you've done all this and the error persists, it might be a corrupt installation. Before you nuke everything, try a repair upgrade: download the Windows 11 ISO from Microsoft, run setup, and choose Keep files and apps. It reinstalls the OS without wiping your data.

If that doesn't fix it, back up your files and do a clean install. I know it's painful, but sometimes it's faster than chasing ghosts.

One last tip: check the Event Viewer. Go to Event Viewer > Windows Logs > System and look for errors that match the timestamp of the crash. It might point to a specific DLL or driver. That's saved me hours in the past.