How to Fix the STATUS_BREAKPOINT Error in Chrome and Edge

The STATUS_BREAKPOINT error appears on a crashed tab in Chrome or Edge with the familiar Aw, Snap message and the error code visible in smaller text below. The page stops loading entirely, and attempting to reload often reproduces the crash immediately, particularly on sites that are video-heavy, run complex JavaScript, or use WebGL rendering.

The name sounds alarming because breakpoints are a debugging concept. In software development, a breakpoint is a deliberate pause point a developer inserts to inspect code during testing. When a browser hits a breakpoint instruction in production, outside any debugger, it means the process reached an internal state it should never reach under normal operation. The browser crashes rather than continuing from a corrupted state.

Both Chrome and Edge experience this error for the same reason: both are built on the Chromium engine and share the same renderer architecture, the same GPU process, and the same sandbox mechanisms. Every fix that works for one browser works for the other. The fixes below are ordered from the causes that account for the majority of cases to the causes that require deeper system-level investigation.

STATUS_BREAKPOINT is not a security breach and does not indicate your data was compromised. It means a browser renderer process crashed. However, if the error began immediately after installing a new extension, visiting an unfamiliar site, or noticing browser redirects or unwanted pop-ups, check for malicious extensions before applying other fixes.

What STATUS_BREAKPOINT Means at the Technical Level

At the processor level, a breakpoint is generated by the x86 INT 3 instruction, which is a single-byte opcode (0xCC) that triggers a software interrupt. Operating systems and debuggers use this to pause execution and hand control to a debugging handler. When this instruction executes inside a browser renderer process with no debugger attached, the operating system has no handler to pass it to and terminates the process.

In Chromium’s multi-process architecture, each tab runs in its own renderer process isolated from other tabs and from the browser itself. When a renderer crashes, it produces the Aw, Snap error page for that tab only. The crash is contained. Other tabs and the browser shell continue running. This architecture means STATUS_BREAKPOINT is almost always a tab-level or process-level problem rather than a system-level problem.

The renderer process can hit a breakpoint instruction for several distinct reasons. The GPU process can fail and trigger a crash in any renderer that was depending on it for hardware-accelerated rendering. A browser extension injecting code into the renderer can reach an unexpected state. Corrupted cached data fed to the renderer during page load can produce a memory access violation that terminates the process. Experimental browser flags can activate code paths that are not stable in production builds.

Fix 1: Disable or Isolate Browser Extensions

Extensions are the most common source of STATUS_BREAKPOINT crashes. They run inside the renderer process and can inject JavaScript or native code that reaches an unexpected state during page rendering. The crash often targets specific types of pages: ad blockers on pages with complex ad structures, script managers on pages with heavy JavaScript, or translator extensions on dynamically loaded content.

The fastest diagnosis is loading the same page that triggers the error in a private or incognito window, which runs without extensions by default. If the page loads without crashing in private mode but crashes in normal mode, an extension is the cause.

To isolate which extension is responsible:

1. Open Chrome Settings (three-dot menu, Settings) or Edge Settings
2. Go to Extensions (Chrome: three-dot menu, Extensions, Manage Extensions; Edge: three-dot menu, Extensions)
3. Disable all extensions using the toggle switches, then reload the page
4. If the error stops, re-enable extensions one at a time, reloading the page after each one
5. The extension that causes the crash to return is the source of the problem

Ad blockers, script injectors, VPN extensions, and browser automation tools are the most frequent offenders. If the problematic extension is one you need, check whether the developer has published an updated version, or look for an alternative extension that performs the same function.

Fix 2: Disable Hardware Acceleration and Update the GPU Driver

Hardware acceleration is the most common non-extension cause of STATUS_BREAKPOINT. When enabled, Chrome and Edge delegate rendering-intensive tasks including video playback, CSS animations, and WebGL to the GPU rather than the CPU. This improves performance on hardware that supports it well. When the GPU driver is outdated, corrupted, or has a compatibility issue with Chromium’s graphics stack, the delegation fails and the renderer process crashes.

To disable hardware acceleration in Chrome:

6. Click the three-dot menu in the top right corner and select Settings
7. In the left sidebar, click System
8. Toggle off Use graphics acceleration when available
9. Click Relaunch to restart Chrome with the setting applied

To disable hardware acceleration in Edge:

10. Click the three-dot menu and select Settings
11. Click System and performance in the left sidebar
12. Toggle off Use hardware acceleration when available
13. Click Restart to apply the change

If the STATUS_BREAKPOINT error stops after disabling hardware acceleration, the GPU driver is the underlying cause. Disabling hardware acceleration is a workaround, not the complete fix. The full resolution is updating the GPU driver and then re-enabling hardware acceleration.

To update the GPU driver on Windows:

• For NVIDIA: open NVIDIA GeForce Experience and click Check for Updates, or download the latest driver directly from nvidia.com/drivers
• For AMD: open AMD Radeon Software and navigate to Updates, or download from amd.com/en/support
• For Intel integrated graphics: open Device Manager (Win+X, Device Manager), expand Display adapters, right-click the Intel graphics device, and select Update driver, then Search automatically for drivers

After installing a GPU driver update, restart your computer fully before re-enabling hardware acceleration in the browser. A driver update does not take full effect until after a restart, and re-enabling hardware acceleration before restarting can reproduce the crash even with the new driver.

Fix 3: Clear the Browser Cache and Reset Experimental Flags

Corrupted cached data is a persistent cause of STATUS_BREAKPOINT that can survive browser restarts and updates. When the browser loads a page, it checks the cache for previously downloaded resources. If a cached file became corrupted after a browser crash, a storage error, or an interrupted download, the renderer crashes when it tries to parse the corrupted data.

To clear the cache in Chrome or Edge:

14. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) to open the Clear browsing data dialog
15. Set the time range to All time
16. Check Cached images and files and Cookies and other site data
17. Click Clear data and restart the browser

Experimental flags are a separate issue. Chrome and Edge include a flags page at chrome://flags (Chrome) or edge://flags (Edge) that exposes experimental features not enabled in the stable build. If you or a browser update enabled an experimental flag that is unstable in your configuration, it can produce consistent STATUS_BREAKPOINT crashes on specific types of pages.

To reset all experimental flags to their defaults:

18. Type chrome://flags in the Chrome address bar or edge://flags in Edge and press Enter
19. Click the Reset all button at the top of the page
20. Click Relaunch to restart the browser with all flags at default values

Resetting flags is safe. The flags page only affects experimental features. Resetting it returns the browser to its designed production configuration. If a flag you rely on was reset, you can go back to chrome://flags and re-enable it individually.

Fix 4: Update the Browser

A STATUS_BREAKPOINT crash caused by a bug in the browser itself is resolved by updating to a version that contains the fix. Chrome and Edge release updates frequently, sometimes weekly for security and stability patches. Running an outdated version means known crash bugs that have since been fixed are still present.

To update Chrome:

21. Click the three-dot menu and hover over Help
22. Click About Google Chrome
23. Chrome checks for updates automatically and installs any available update
24. Click Relaunch to apply the update

To update Edge:

25. Click the three-dot menu and hover over Help and feedback
26. Click About Microsoft Edge
27. Edge checks for updates and installs them automatically
28. Click Restart to apply

After updating, reproduce the steps that triggered the error. If the crash was caused by a specific browser bug, the update will resolve it. If the crash persists after updating, the cause is not the browser version itself but one of the other factors covered in this guide.

Fix 5: Check for Antivirus or Security Software Interference

Antivirus and endpoint security software that includes browser scanning or real-time web protection features can inject hooks into browser processes to inspect network traffic and script execution. When these hooks conflict with the browser’s own renderer sandbox, the renderer crashes and produces STATUS_BREAKPOINT. This is particularly common after a security software update that changed its injection behavior.

The test is straightforward: temporarily disable the browser-scanning or web-protection component of your antivirus, not the entire antivirus, and reproduce the error. Most security suites allow disabling real-time web scanning without disabling the full protection. In Windows Defender, you can temporarily turn off Real-time protection under Windows Security, Virus and Threat Protection, Manage settings.

If the STATUS_BREAKPOINT error stops after disabling the security software’s browser scanning feature, the fix is to add Chrome or Edge to the antivirus exclusions list:

• For Windows Defender: Windows Security, Virus and Threat Protection, Virus and Threat Protection Settings, Add or remove exclusions, add the Chrome or Edge application path
• For third-party antivirus: each product handles exclusions differently. Look for Application Exclusions, Process Exclusions, or Trusted Processes in the antivirus settings and add the browser executable

Adding a browser to antivirus exclusions reduces security scanning on that process. Only do this if you have confirmed the antivirus is causing the crash and only add the specific browser executable, not an entire folder. The antivirus continues to protect other processes and system components.

Fix 6: Run Windows System File Checker and DISM

If the STATUS_BREAKPOINT error occurs across multiple sites and multiple browsers, not just Chrome and Edge but also Firefox or other applications, the cause may be corrupted Windows system files rather than anything browser-specific. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools scan for and repair corrupted system files.

Run these commands in an elevated Command Prompt (search for cmd in the Start menu, right-click, and select Run as administrator):

The SFC scan typically takes 10 to 20 minutes. The DISM RestoreHealth command downloads replacement files from Windows Update and can take longer depending on internet speed. Both commands must complete successfully before restarting. If SFC reports it found corrupt files and could not repair all of them, run DISM first to repair the Windows image, then run SFC again.

Fix 7: Disable Conflicting Third-Party Applications via Clean Boot

Certain third-party applications run background services that interfere with browser processes in ways that produce STATUS_BREAKPOINT. Screen recording software, game overlays (GeForce Experience overlay, Discord overlay, Steam overlay), clipboard managers, and accessibility tools can all inject into browser processes or compete for graphics resources in ways that destabilize the renderer.

A Windows clean boot starts the operating system with only Microsoft services and startup programs, disabling all third-party services. If the STATUS_BREAKPOINT error stops in a clean boot environment, a background application is the cause, and you can identify it by re-enabling services in groups until the error returns.

To perform a clean boot on Windows 10 or 11:

29. Press Win+R, type msconfig, and press Enter to open System Configuration
30. On the Services tab, check Hide all Microsoft services, then click Disable all
31. On the Startup tab, click Open Task Manager. In Task Manager, disable all startup items
32. Close Task Manager, click OK in System Configuration, and restart the computer
33. After restarting, test whether the STATUS_BREAKPOINT error reproduces
34. If the error is gone, re-enable services in batches of five or ten to identify which service is responsible

Common sources of browser process interference found by clean boot testing: NVIDIA GeForce Experience overlay, Discord’s hardware-accelerated rendering, Logitech G Hub, OBS Studio background service, Malwarebytes real-time scanning (separate from antivirus), and screen reader accessibility software.

Fix 8: Check RAM Stability and Adjust Virtual Memory

Memory-related STATUS_BREAKPOINT crashes are less common than GPU and extension causes but occur regularly on systems with overclocked RAM, unstable XMP or EXPO memory profiles, or failing RAM modules. Chrome uses aggressive memory management and is more likely to expose RAM instability than less demanding applications. A crash that appears only in Chrome but not in other applications does not rule out RAM as the cause.

Two approaches address memory-related crashes. The first is increasing virtual memory allocation, which gives Chrome more address space on systems where physical RAM is under pressure:

35. Right-click This PC and select Properties
36. Click Advanced system settings, then under Performance, click Settings
37. On the Advanced tab, under Virtual memory, click Change
38. Uncheck Automatically manage paging file size for all drives
39. Select Custom size and set both Initial size and Maximum size to 1.5 times your physical RAM in megabytes. For 8GB of RAM, that is 12288 MB.
40. Click Set, then OK, and restart the computer

The second approach is testing RAM integrity. To run the Windows Memory Diagnostic:

41. Press Win+S and search for Windows Memory Diagnostic
42. Select Restart now and check for problems
43. The computer restarts and runs a full memory scan before booting back into Windows
44. After the restart, the results appear as a notification. If errors are reported, a RAM module is failing and needs replacement.

For systems with overclocked RAM or enabled XMP/EXPO profiles in the BIOS, try disabling the XMP profile and running the RAM at its base rated speed. Chromium is documented to be sensitive to marginal memory instability that other applications tolerate. A system that passes basic memory tests can still produce Chromium crashes if the memory timings are aggressive.

Fix 9: Create a Fresh Browser Profile

A corrupted browser user profile is a cause of persistent STATUS_BREAKPOINT crashes that survives cache clearing, flag resetting, and extension removal. The profile contains settings, saved passwords, browsing history, and various configuration files. If any of these becomes corrupted, the corruption persists even after clearing the cache because the cache and the profile are stored separately.

To create a new profile in Chrome:

45. Click the profile icon in the top right corner of Chrome
46. Click Add
47. Choose Continue without an account to create a local profile without syncing
48. In the new profile window, navigate to the page that was triggering the error
49. If the error does not reproduce in the new profile, the old profile contained the corruption

To create a new profile in Edge:

50. Click the profile icon in the top right corner
51. Click Add profile
52. Select Add to confirm
53. In the new profile window, test the page that was causing the crash

If a new profile resolves the error, you can use Chrome’s sync feature to transfer bookmarks, passwords, and settings from the old profile. The corruption in the old profile is typically limited to local settings files rather than synced data, so the transferred data is clean.

Fix 10: Reinstall the Browser with Full Data Removal

When all previous fixes have been applied and the error persists, a clean reinstallation removes every browser file including any corrupted binaries in the installation directory. Standard uninstallation through Windows Settings often leaves behind the user data folder and various registry entries. A full removal requires deleting these manually.

Full removal process for Chrome on Windows:

54. Uninstall Chrome via Settings, Apps, find Google Chrome, and click Uninstall
55. After uninstalling, open File Explorer and navigate to C:\Users\[your username]\AppData\Local\Google
56. Delete the Chrome folder. This removes all user data including saved passwords, bookmarks, and history. Back up anything important before this step by exporting bookmarks from within Chrome first.
57. Press Win+R, type regedit, and navigate to HKEY_CURRENT_USER\Software\Google. Delete the Chrome key if it exists.
58. Restart the computer
59. Download a fresh Chrome installer from google.com/chrome and install

Full removal process for Edge on Windows: Edge is a system component on Windows 11 and cannot be fully uninstalled through standard means. For Edge, creating a new profile (Fix 9 above) is the equivalent of a clean installation for most purposes. If Edge continues to crash after a new profile, run the Edge repair tool from Settings, Apps, find Microsoft Edge, click Modify, and select Repair.

STATUS_BREAKPOINT on Specific Sites or Page Types

Error only on video streaming sites

Video streaming sites including YouTube, Netflix, Twitch, and similar platforms use hardware-accelerated video decoding. When the GPU driver fails during video decode acceleration, the renderer crashes. Disabling hardware acceleration (Fix 2) resolves this immediately. For a more targeted approach without fully disabling hardware acceleration, go to chrome://flags, search for Hardware-accelerated video decode, and set it to Disabled. This disables GPU-accelerated video decoding specifically while leaving other hardware acceleration active.

Error on pages with heavy JavaScript or WebGL

Pages running complex three-dimensional graphics, interactive data visualizations, or heavy JavaScript frameworks can push the renderer to its memory limit. On machines with 4GB or less of RAM, this consistently produces STATUS_BREAKPOINT. The fixes are increasing virtual memory (Fix 8), enabling Chrome’s Memory Saver feature (Settings, Performance, Memory Saver), and closing background tabs before loading the problematic page. Chrome’s Task Manager (Shift+Esc) shows per-tab and per-process memory consumption to help identify which pages are consuming the most resources.

Error after a Windows Update

A Windows Update that included a GPU driver update or a security patch affecting process isolation can trigger STATUS_BREAKPOINT in previously stable browser configurations. The most direct fix is checking Device Manager for the GPU driver version installed by Windows Update and rolling it back if it coincides with the start of the crashes. In Device Manager, right-click the GPU under Display adapters, select Properties, go to the Driver tab, and click Roll Back Driver if the option is available.

Error on one specific site consistently

A STATUS_BREAKPOINT that only occurs on one specific site and not on any other site is almost always caused by content on that page rather than by the browser configuration. The page may be running malicious JavaScript, serving a corrupted file, or using a WebGL or Canvas API call that triggers a bug in a specific GPU driver version. Report the URL to the Chrome or Edge bug tracker and test in a different browser to confirm whether the crash is browser-specific or cross-browser.

Quick Fix Reference by Most Likely Cause

Frequently Asked Questions

What does STATUS_BREAKPOINT mean in Chrome or Edge?

STATUS_BREAKPOINT is a crash code that appears when a browser renderer process terminates because it hit an internal breakpoint instruction, which is a CPU-level instruction that normally only executes during software debugging. In a production browser, this means the renderer reached an unexpected state and shut down to prevent further damage. The crash is typically caused by a GPU driver conflict, a problematic browser extension, corrupted cache data, or an experimental flag activating unstable code. It is a browser process crash, not a security breach.

Why does STATUS_BREAKPOINT appear in both Chrome and Edge?

Chrome and Edge are both built on the Chromium open-source engine and share the same underlying renderer architecture, GPU process, and sandbox mechanisms. A bug or configuration issue that affects the Chromium renderer manifests identically in both browsers. If you see STATUS_BREAKPOINT in both, the cause is something that both browsers share: a GPU driver issue, a Windows system-level problem, antivirus interference, or RAM instability. Extension conflicts affect only the browser where the extension is installed.

Is STATUS_BREAKPOINT a virus or malware?

Not directly. STATUS_BREAKPOINT is a browser crash error, not a malware indicator. However, malicious extensions or JavaScript from unsafe websites can trigger browser crashes that present with this error code. If the error began after installing a new extension, visiting an unusual site, or noticing changes to your browser’s default search engine or home page, check your extensions list immediately and run a malware scan. Remove any extension you do not recognize or did not deliberately install.

How do I fix STATUS_BREAKPOINT without losing my saved passwords and bookmarks?

Most fixes in this guide do not affect saved passwords or bookmarks. Disabling hardware acceleration, clearing the cache, disabling extensions, resetting flags, updating the GPU driver, and running SFC all leave your saved data untouched. If you need to create a new browser profile (Fix 9), export your bookmarks first using Chrome’s Bookmark Manager export function, and sync your passwords to your Google account before creating the new profile. Creating a new profile does not delete the old one, so you can access it again if needed.

The error only happens on one specific website. Is the site broken?

Possibly. A STATUS_BREAKPOINT crash on a single site consistently, with no errors on any other site, suggests the specific page content is triggering the crash rather than your browser configuration. This can happen if the page runs JavaScript that hits a bug in your specific browser or GPU driver version, uses a WebGL shader that exposes a driver bug, or serves a corrupted file. Test the same page in Firefox to confirm whether the crash is Chromium-specific. If the page crashes in all browsers, the site has a content problem. If it only crashes in Chrome or Edge, report the URL to the Chromium bug tracker at crbug.com.

Can overclocking cause STATUS_BREAKPOINT?

Yes. Chromium is documented to be more sensitive to marginal memory and CPU instability than most applications. Overclocked RAM with aggressive timings, an overclocked CPU running at unstable voltages, or an enabled XMP or EXPO memory profile that is not fully stable on a specific motherboard can all produce STATUS_BREAKPOINT crashes in Chrome and Edge that do not appear in other applications. If you have overclocking enabled, revert to stock settings in your BIOS and test whether the crashes stop. Run the Windows Memory Diagnostic after reverting to confirm whether the overclock was causing memory errors.

Will reinstalling Chrome fix STATUS_BREAKPOINT?

A clean reinstallation with full data removal (Fix 10) resolves STATUS_BREAKPOINT caused by corrupted browser installation files or a corrupted user profile, but it does not fix causes outside the browser such as GPU driver issues, antivirus interference, or RAM instability. Try the other fixes first before reinstalling. If the error persists after reinstalling Chrome, the cause is outside the browser and requires one of the system-level fixes: GPU driver update, antivirus exclusion, SFC scan, or RAM testing.