Quick answer: Close Chrome, rename the Crashpad folder in your user data directory, then restart Chrome. If that doesn't work, move on to the steps below.
That error code, STATUS_BREAKPOINT, isn't as scary as it sounds. It's a Windows exception that Chrome throws when something forces a breakpoint — basically a debugger stop — in the middle of normal operation. You'll often see it right after a Chrome update, especially on Windows 10 or 11, and sometimes when third-party antivirus software like Avast or Bitdefender decides Chrome is acting suspiciously. The crash can happen on startup, when you open a new tab, or when you're watching a video. I've seen it pop up most commonly after a Chrome auto-update that didn't quite finish cleanly.
What's actually happening under the hood? Chrome uses the Breakpad crash reporter, and the Crashpad folder stores crash dumps. If that folder gets corrupted or contains a crash dump from a previous crash, Chrome can loop — it tries to write a new dump, fails, throws the breakpoint exception, and crashes again. Also, some security software injects DLLs into Chrome processes to scan web traffic, and that injection can trigger a breakpoint exception.
Step-by-Step Fixes
1. Kill Chrome completely and delete the Crashpad folder
- Press
Ctrl + Shift + Escto open Task Manager. - Look for any process named
chrome.exe. If you see one or more, click each and hitEnd Task. Don't skip this — Chrome often runs background processes. - Press
Win + R, type%LOCALAPPDATA%\Google\Chrome\User Data\and hit Enter. This opens the Chrome user data folder in File Explorer. - Find the folder named
Crashpad. Right-click it, chooseRename, and typeCrashpad_old. Yes, just rename it. Don't delete it yet — you might want to recover something if the fix doesn't work. - Now start Chrome normally. You should see Chrome open without that error. If it doesn't crash, you're done. If it does, close Chrome again and go to step 2.
After you confirm Chrome is stable, you can delete the Crashpad_old folder to free up space. But only after a week of no crashes.
2. Reset Chrome flags that might be causing the issue
Sometimes a specific flag — like hardware acceleration or the new download UI — triggers the breakpoint. Resetting all flags is quick and safe.
- In Chrome's address bar, type
chrome://flagsand press Enter. - You'll see a long list of experimental features. At the top right, click the
Reset allbutton. - Chrome will ask you to relaunch. Click
Relaunch. - After Chrome restarts, test your browsing. If the error is gone, you can turn your preferred flags back on one by one, but don't go overboard — stick to stable flags.
3. Disable hardware acceleration
Graphics driver issues can also cause breakpoint exceptions, especially on Windows 10 with older GPU drivers. Here's how to turn off hardware acceleration:
- Click the three-dot menu in Chrome's top right corner, then choose
Settings. - Scroll down to
System(you might need to clickAdvancedfirst). - Turn off the toggle for
Use hardware acceleration when available. - Click
Relaunchwhen prompted.
After relaunch, try loading a video or a graphics-heavy site like YouTube or Google Maps. If the crash no longer happens, keep this setting off. Some users report that this alone fixed the problem for them.
4. Update your GPU drivers and Windows
Outdated graphics drivers are a common cause of Chrome crashes with various STATUS errors. Here's what to do:
- Press
Win + Ito open Windows Settings. - Go to
Windows Updateand clickCheck for updates. Install any available updates, including optional driver updates. - After Windows updates, also check for GPU driver updates. Go to
Device Manager, expandDisplay adapters, right-click your graphics card, and chooseUpdate driver. Then selectSearch automatically. If Windows finds nothing, go to your GPU manufacturer's website (NVIDIA, AMD, or Intel) and download the latest driver for your model.
Reboot your PC after updating drivers, then test Chrome.
5. Run Chrome's built-in cleanup tool
Malware or unwanted extensions can crash Chrome in weird ways. Chrome has a cleanup tool that scans for and removes problematic software.
- In Chrome, go to
chrome://settings/cleanup. - Click
Findand let it run. This may take a few minutes. - If it finds anything, click
Removeand restart Chrome.
I've seen this tool catch adware that was causing regular breakpoint errors. It's worth trying before you nuke your whole Chrome profile.
If the main fixes don't work
6. Disable antivirus integration temporarily
If you're using third-party AV like Avast, Kaspersky, or Bitdefender, try disabling the web protection or HTTPS scanning feature temporarily. Here's how to test if AV is the culprit:
- Open your AV software's settings.
- Look for anything like
Web Shield,HTTPS Scanning, orScript Protection. Turn that off. - Now try Chrome. If it doesn't crash, you've found the problem. Right now, the fix is to add Chrome to your AV's exclusion list, or permanently disable that overzealous scanning feature.
- Remember to re-enable your AV protection after testing. You don't want to leave your system exposed.
7. Create a new Chrome profile
Your current profile might be corrupted. A fresh profile often fixes persistent crashes.
- Close Chrome.
- Press
Win + R, type%LOCALAPPDATA%\Google\Chrome\User Data\and press Enter. - Find the folder named
Default. Right-click it and rename it toDefault_old. - Start Chrome. It will create a new
Defaultfolder automatically. Sign in to your Google account to sync bookmarks and passwords. If the crash is gone, you can slowly move your important files over from the old profile, but honestly, I recommend just starting fresh and re-importing your bookmarks from a backup.
8. Reinstall Chrome completely
If none of the above works, do a clean reinstall. Uninstall Chrome, but also delete the Google Chrome folder inside %LOCALAPPDATA%\Google\Chrome and the Google\Chrome folder in %APPDATA% to get rid of all leftover data. Then download the latest Chrome installer and install again. This is drastic, but it works when nothing else does.
Prevention tips
- Keep Chrome updated, but after each update, give it a moment to fully finish before you start using it. If you see the “Updates” icon in the menu, restart Chrome soon after.
- Don't run a bunch of extensions. Each one adds risk of conflicts. Stick to a few trusted ones.
- If you use third-party AV, check if it has a “game mode” or “quiet mode” that disables web scanning for certain apps — configure that for Chrome.
- Make it a habit to clear your browsing data (especially cached images and files) once a month. That keeps Chrome's temporary files from getting stale.
That's the whole deal. Try those steps in order, and you'll likely get Chrome back to stable. If you still see STATUS_BREAKPOINT after everything, it's a rare incompatibility with your specific hardware — check Chrome's community forums for your exact model.