● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows laptop on a desk showing a Chrome Aw Snap STATUS_ACCESS_VIOLATION error page in a dimly lit home office
Fix It Yourself · Troubleshooting

STATUS_ACCESS_VIOLATION Chrome Fix: Stop the Crashes for Good

Published 17 October 202614 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Chrome throws a lot of error codes, but STATUS_ACCESS_VIOLATION Chrome fix searches are some of the most common ones we see at Vivid Repairs. And no wonder. The error is vague, the crash page tells you almost nothing useful, and the cause could be any one of five or six completely different things. This guide cuts through that. We'll work from the most likely causes first, so you're not wasting half an hour on advanced fixes when the answer is a single toggle in Chrome Settings.

What Actually Causes STATUS_ACCESS_VIOLATION in Chrome?

The error itself means one thing: a Chrome process tried to read from or write to a block of memory it wasn't allowed to touch, and Windows shut it down before it could do any damage. That's the OS doing its job. The question is what pushed Chrome into that restricted memory in the first place.

The most common culprit, by a wide margin, is Chrome's GPU process. Chrome uses hardware acceleration to offload rendering work to your graphics card, and it does this through a layer called ANGLE. If your GPU drivers are outdated, buggy, or just not playing nicely with Chrome's current version, the GPU process can end up trying to access graphics memory it can't reach. Result: STATUS_ACCESS_VIOLATION, page crashes, Aw Snap. This is especially common after a Windows update that ships with new driver components, or after Chrome itself updates and changes how it talks to the GPU stack.

The second big cause is third-party software, usually antivirus or endpoint security tools, injecting DLLs into Chrome's renderer process. These tools do it for legitimate reasons (scanning web content in real time, blocking malicious scripts), but the injected code runs inside Chrome's process space. If that code tries to access memory Chrome has marked off-limits, you get an access violation. It's not necessarily that the antivirus is broken. It's that Chrome's security model and the antivirus's injection approach don't agree with each other. Microsoft's documentation on access violations explains the underlying mechanism well if you want the technical background.

Beyond those two, a corrupted Chrome profile is a surprisingly frequent cause. Chrome stores your settings, extensions, cached data, and session state in a profile folder under AppData. If any of those files get corrupted (after a power cut, a bad Chrome update, or just gradual file system wear), Chrome can behave unpredictably. A bad extension can do the same thing, especially ones that hook into page rendering or modify JavaScript execution. And at the hardware level, faulty RAM can cause random access violations across any application, not just Chrome. If you're seeing crashes in other programs too, RAM is worth investigating early.

Finally, there's system-level file corruption on Windows itself. If core Windows DLLs or driver files are damaged, Chrome's processes can fail in ways that look like Chrome bugs but aren't. The STATUS_BREAKPOINT Chrome variant you sometimes see is related but slightly different. It usually points to a debugger attachment or a specific code integrity check failing, rather than a raw memory access problem. The fixes overlap heavily though, so this guide covers both.

Quick routeStart here

STATUS_ACCESS_VIOLATION Chrome Fix: Quick Solutions

Start here. These take five minutes and fix the problem more often than you'd expect.

1

Restart Chrome and Test in Incognito Easy

  1. Close Chrome completely
    Don't just close the tab. Right-click the Chrome icon in the system tray and choose Exit, or go to the three-dot menu and select Exit. Make sure no Chrome processes are running in Task Manager.
  2. Relaunch and open Incognito
    Press Ctrl + Shift + N to open an Incognito window. Navigate to the same page that was crashing.
  3. Check the result
    If the page loads fine in Incognito, the cause is almost certainly an extension or cached data in your regular profile. Move straight to the extension and cache steps below. If it crashes in Incognito too, the problem is deeper.
No crash in Incognito? Extensions or cache are your target. Keep reading.
2

Disable Hardware Acceleration Easy

  1. Open Chrome Settings
    Click the three-dot menu, then Settings. In the search bar at the top, type hardware acceleration.
  2. Turn it off
    You'll see 'Use hardware acceleration when available'. Toggle it off. Chrome will prompt you to relaunch.
  3. Relaunch and test
    Click the Relaunch button. Visit the page that was crashing. This forces Chrome into software-only rendering, bypassing the GPU entirely. Pages may render slightly slower on older machines, but the crashes should stop.
If this fixes it, your GPU drivers are the underlying issue. Update them (covered below) and you may be able to turn hardware acceleration back on afterwards.
3

Disable Extensions and Clear Cache Easy

  1. Go to chrome://extensions/
    Type that directly into the address bar. Toggle every extension off using the blue sliders.
  2. Clear browsing data
    Press Ctrl + Shift + Delete. Set the time range to All time. Tick Cached images and files and Cookies and other site data. Click Clear data.
  3. Restart Chrome and test
    If the crashes are gone, re-enable extensions one at a time, restarting Chrome between each one, until the crash comes back. That last extension you enabled is your culprit. Remove it.
Ad blockers, VPN extensions, and script managers are the most common offenders in our experience. Anything that modifies page content aggressively is a candidate.
4

Update Chrome Easy

  1. Check for updates
    Click the three-dot menu, then Help, then About Google Chrome. Chrome will check for updates automatically and install them if available.
  2. Relaunch when prompted
    Click Relaunch to apply the update. Google patches known crash bugs regularly, and running an outdated version is an easy problem to fix.
Chrome is now on the latest version. If the crash was a known bug, it's likely fixed.
Intermediate routeKeep going if needed

Intermediate STATUS_ACCESS_VIOLATION Chrome Fixes

Still crashing? These steps go a bit deeper into Chrome's graphics stack, your profile, and any software that might be interfering with Chrome's processes. Budget 15 to 30 minutes for this section.

5

Change the ANGLE Graphics Backend Medium

  1. Open the ANGLE flag
    Type chrome://flags/#use-angle into the address bar and press Enter.
  2. Change the backend
    You'll see a dropdown labelled 'Choose ANGLE graphics backend'. It's set to Default by default. Change it to D3D11 first. If that doesn't help after a relaunch, try D3D9. D3D9 is older but more stable on some driver configurations.
  3. Relaunch and test
    Chrome will prompt you to relaunch. Do it, then visit the page that was crashing. ANGLE is the translation layer between Chrome's rendering engine and your GPU. Switching backends changes how Chrome talks to your graphics hardware, and on many systems this alone stops the access violations.
If you've been experimenting with other flags, visit chrome://flags/ and click 'Reset all to default' first. A misconfigured flag can cause crashes that look identical to driver problems.
6

Create a New Chrome Profile Easy

  1. Add a new profile
    Click your profile icon (top right of Chrome, next to the address bar). Select Add. Set it up without signing in if you want a clean test.
  2. Test the new profile
    Open the same pages that were crashing. Don't install any extensions yet. If Chrome runs fine on the new profile, your old profile is corrupted.
  3. Decide what to do
    You can either keep using the new profile and migrate your bookmarks manually, or try the clean reinstall in the advanced section which wipes the corrupted profile data entirely.
Crashes only on the old profile? Corrupted profile confirmed. The clean reinstall below is your next step.
7

Temporarily Disable Antivirus Web Protection Medium

  1. Open your security software
    Find your antivirus or endpoint security tool in the system tray. Look for options like Real-time protection, Web Shield, Browser Protection, or Exploit Protection. Turn it off temporarily.
  2. Restart Chrome and test
    Relaunch Chrome and visit the crashing page. If the error stops, the security software's DLL injection is the cause.
  3. Re-enable protection immediately after testing
    Don't leave it off. If disabling the AV fixes the crash, check the software's settings for a 'Chrome compatibility mode' or a way to exclude Chrome from browser injection. Some tools have this. If not, contact the vendor or consider switching to software that doesn't use aggressive process injection.
Only disable real-time protection briefly for testing. Don't browse normally with it off. Re-enable it as soon as you've confirmed whether it's the cause.
8

Update GPU Drivers Medium

  1. Identify your GPU
    Press Win + X and open Device Manager. Expand Display adapters to see your GPU model.
  2. Download drivers directly from the manufacturer
    For NVIDIA, go to nvidia.com/drivers. For AMD, use the AMD Driver and Support page. For Intel integrated graphics, use the Intel Driver and Support Assistant. Don't rely on Windows Update for GPU drivers. It often lags behind by months.
  3. Install and restart
    Run the installer, choose the standard (not custom) install unless you know what you're doing, and restart Windows when prompted. This one often needs a second reboot before it sticks, so restart twice if the crash persists after the first.
  4. Re-enable hardware acceleration in Chrome
    If you disabled it earlier, go back to Settings and turn it back on. Test whether the crash returns. Updated drivers often fix the underlying conflict.
9

Rename chrome.exe to Bypass Injection Hooks Medium

  1. Close Chrome completely
    Make sure no Chrome processes are running. Check Task Manager if you're not sure.
  2. Navigate to Chrome's install folder
    Go to C:\Program Files\Google\Chrome\Application. You'll see chrome.exe in there.
  3. Rename the executable
    Right-click chrome.exe and rename it to something like chrometest.exe. Some security software hooks into processes by name, so renaming it prevents those hooks from firing.
  4. Launch the renamed file
    Double-click chrometest.exe to launch Chrome. Test the crashing page. If it works, the security software injection was the cause. You'll need to address that properly (see the antivirus step above) rather than running renamed Chrome permanently.
This is a diagnostic step, not a permanent fix. It tells you whether injection is the cause. Address the root cause in your security software settings afterwards.
Advanced routeChange one thing at a time

Advanced STATUS_ACCESS_VIOLATION Chrome Fixes

These are the steps for when everything above has failed. They involve command-line tools, shortcut modifications, and Windows system repair. None of them are dangerous if you follow the steps carefully, but they take more time and require a bit more confidence with Windows.

10

Disable RendererCodeIntegrity via Shortcut Flag Advanced

  1. Find your Chrome shortcut
    Right-click the Chrome shortcut on your desktop (or in the Start menu) and choose Properties.
  2. Edit the Target field
    Go to the Shortcut tab. In the Target field, you'll see something like "C:\Program Files\Google\Chrome\Application\chrome.exe". Click at the very end of that text (after the closing quote) and add a space followed by --disable-features=RendererCodeIntegrity.
  3. Apply and launch via this shortcut
    Click Apply, then OK. Launch Chrome using this specific shortcut. RendererCodeIntegrity is Chrome's protection against unsigned code running in the renderer process. When third-party software injects unsigned DLLs, this check triggers an access violation. Disabling it is a workaround, not a cure, but it confirms injection is the cause and keeps Chrome usable while you sort the underlying software conflict.
  4. Verify
    If crashes stop, the cause is confirmed as third-party code injection. Address it by configuring or replacing the offending security software rather than leaving this flag on permanently.
This flag reduces Chrome's security posture. Use it as a diagnostic tool and remove it once you've identified and fixed the injecting software.
11

Run DISM and System File Checker Advanced

  1. Open Command Prompt as administrator
    Press Win + S, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Run DISM first
    Type the following and press Enter: DISM /Online /Cleanup-Image /RestoreHealth. This repairs the Windows component store. It can take 10 to 20 minutes and needs an internet connection to download replacement files from Microsoft.
  3. Run SFC after DISM completes
    Type sfc /scannow and press Enter. SFC uses the repaired component store to fix any corrupted system files. Let it finish fully.
  4. Restart Windows
    Restart after both tools complete. Then retest Chrome. System file corruption can cause Chrome process crashes that look identical to driver or extension problems. Google's own Chrome crash troubleshooting page recommends checking for system-level issues when Chrome crashes persist after browser-level fixes.
DISM and SFC complete with no errors reported? Your Windows installation is clean. If errors were found and repaired, restart and test Chrome again.
12

Clean Reinstall Chrome Medium

  1. Uninstall Chrome
    Go to Settings, Apps, find Google Chrome, and uninstall it. This removes the application but leaves your profile data.
  2. Delete the leftover profile folder
    Press Win + R, type %localappdata%\Google\Chrome and press Enter. Delete the entire Chrome folder. This is the step most people miss. Without deleting this, a reinstall just loads the same corrupted profile data.
  3. Download a fresh installer
    Go to google.com/chrome from another browser (Edge works fine) and download the latest installer.
  4. Install and test
    Run the installer. Don't sign in or restore any extensions immediately. Test Chrome clean first. If it's stable, sign in and restore extensions one at a time to make sure none of them reintroduce the problem.
If you're also seeing this kind of crash in Edge, the same steps apply. Edge is Chromium-based, so hardware acceleration, extension conflicts, and driver issues affect it identically. For broader browser stability problems, our Chrome keeps crashing guide covers additional scenarios worth checking.
13

Run Windows Memory Diagnostic Medium

  1. Launch the tool
    Press Win + R, type mdsched.exe, and press Enter. Choose 'Restart now and check for problems'.
  2. Wait for the scan
    Windows will restart and run a memory test before loading Windows. It takes 5 to 15 minutes depending on how much RAM you have. Don't interrupt it.
  3. Check the results
    After Windows restarts, the results appear in a notification. You can also check Event Viewer under Windows Logs, System, and look for MemoryDiagnostics-Results entries. If errors are found, the RAM is faulty and needs replacing. HowToGeek's guide to Windows Memory Diagnostic explains how to read the results in detail.
Faulty RAM causes access violations across multiple applications. If you're seeing crashes in other software besides Chrome, run this test before spending more time on Chrome-specific fixes. For hardware-level problems like this, also check our RAM troubleshooting guide for next steps.
14

Perform a Clean Boot to Isolate Conflicting Software Advanced

  1. Open msconfig
    Press Win + R, type msconfig, and press Enter. Go to the Services tab.
  2. Hide Microsoft services and disable the rest
    Tick 'Hide all Microsoft services', then click 'Disable all'. Go to the Startup tab and click 'Open Task Manager'. Disable every startup item there too.
  3. Restart and test
    Restart Windows. Only Microsoft services will be running. Test Chrome. If it's stable, re-enable your disabled services in batches of five or six, restarting each time, until the crash returns. The last batch you enabled contains the conflicting software.
  4. Identify and address the conflict
    Once you've narrowed it down to a specific service or startup item, you can update, configure, or remove that software. Background tools like VPN clients, system optimisers, and older driver utilities are common culprits here.

Preventing STATUS_ACCESS_VIOLATION in Chrome

Most of these crashes are preventable with a bit of routine maintenance. Here's what actually matters, in order of importance.

Keep Chrome and your GPU drivers updated. Chrome updates frequently and many of those updates fix known crash bugs. GPU driver updates fix compatibility issues with Chrome's rendering backend. Don't wait for Windows Update to push driver updates. Check the NVIDIA, AMD, or Intel support pages directly every couple of months.

Be selective with extensions. Every extension you install runs code inside Chrome's processes. Stick to extensions from the Chrome Web Store, check the permissions they request (anything asking for access to all sites is worth scrutinising), and remove ones you no longer use. A lean extension list means fewer potential conflicts.

Don't leave experimental flags enabled. Chrome's chrome://flags/ page is for testing features, not permanent configuration. If you've been experimenting, reset everything to default. A misconfigured flag can cause crashes that are genuinely difficult to diagnose because they look exactly like driver or hardware problems.

Choose security software that doesn't aggressively inject into browser processes. Some antivirus products handle web protection by injecting DLLs into every browser process. Others use a network-level proxy approach that doesn't touch the browser internals at all. The latter causes far fewer compatibility issues. If your current AV is repeatedly conflicting with Chrome, it's a legitimate reason to reconsider it.

Run Windows Memory Diagnostic once a year, or any time you see unexplained crashes across multiple applications. Faulty RAM degrades gradually and the symptoms can be subtle for a long time before they become obvious. Catching it early is much less painful than diagnosing it after months of random crashes. And if you're ever unsure whether a Chrome crash is browser-level or system-level, check our guide to random Windows crashes for a broader diagnostic approach.

STATUS_ACCESS_VIOLATION Chrome Fix: Summary

The STATUS_ACCESS_VIOLATION Chrome fix almost always comes down to one of a handful of causes: GPU driver conflicts with Chrome's ANGLE rendering backend, third-party software injecting code into Chrome's processes, a corrupted profile or bad extension, or faulty RAM. Work through the quick fixes first (hardware acceleration off, extensions disabled, cache cleared), then move to the ANGLE backend flag and the RendererCodeIntegrity shortcut tweak if those don't sort it. For persistent cases, a clean reinstall with the AppData folder deleted, DISM and SFC for system file repair, and Windows Memory Diagnostic for hardware ruling cover the remaining scenarios. The STATUS_ACCESS_VIOLATION Chrome fix is rarely one step, but it's almost always solvable without reinstalling Windows.

Frequently Asked Questions

It means a Chrome process tried to read or execute memory it wasn't allowed to touch, so Windows shut it down. The most common causes are GPU driver conflicts, security software injecting code into Chrome, a corrupted profile, or unstable RAM.

Yes, quite often. When Chrome's GPU process tries to access graphics memory it can't reach, you get an access violation. Turning off hardware acceleration in Settings forces Chrome to use software rendering and bypasses the problem entirely.

Some antivirus and security tools hook into Chrome specifically by watching for a process named chrome.exe. Rename it to something like chrometest.exe and those hooks don't fire, so the injected DLL that was causing the violation never loads.

Absolutely. Security suites inject DLLs into browser processes for web protection features, and those injected libraries can trigger renderer memory violations. Try disabling real-time or web shield protection temporarily and see if the crashes stop.

Press Win + R, type mdsched.exe, and choose to restart and check for problems. If Memory Diagnostic finds errors, that's your answer. Faulty RAM tends to cause access violations across multiple apps, not just Chrome, so look for crashes elsewhere too.