Introduction
When Google Chrome keeps crashing on Windows 11 — suddenly closing, freezing mid-page, or showing a “Aw, Snap!” error — it can derail your whole day. The problem is especially frustrating because it often hits at the worst moment: during a video call, while filling out a form, or right in the middle of important research.
Chrome crashes on Windows 11 for a handful of common reasons: too many tabs eating up RAM, a conflicting extension, a corrupt browser profile, outdated graphics drivers, or a hardware acceleration glitch. The good news is that the fix is almost always free and takes less than 30 minutes.
This guide walks you through 8 proven fixes in order from quickest to most thorough.
Quick Answer
To fix Google Chrome crashing on Windows 11: open Chrome, go to Settings > Help > About Google Chrome and install any update, then turn off hardware acceleration under Settings > System. If crashes continue, clear your cache (Ctrl + Shift + Delete), disable all extensions, and run sfc /scannow in an elevated Command Prompt. One of these steps resolves most Chrome crashes.
Fix 1: Update Chrome to the Latest Version
Outdated Chrome builds can carry known crash bugs that a newer release already patched. This takes 60 seconds and should always be your first step.
- Click the three-dot menu (⋮) in Chrome’s top-right corner.
- Go to Help > About Google Chrome.
- Chrome checks for updates automatically. If one is available, click Relaunch.
- Once Chrome restarts, test whether crashes continue.
Pro tip: Chrome updates silently in the background, but you need to relaunch for them to apply. The About screen shows a colored dot next to the menu icon when a pending update is waiting for a relaunch.
Fix 2: Disable Hardware Acceleration
Hardware acceleration offloads browser rendering tasks to your GPU. When your GPU driver and Chrome version don’t agree, this setting becomes the most common hidden cause of random crashes.
- Open Chrome and go to Settings (three-dot menu).
- In the left sidebar, click System.
- Toggle off Use hardware acceleration when available.
- Click Relaunch.
Troubleshooting tip: If Chrome won’t stay open long enough to reach Settings, press Win + R, type chrome.exe --disable-gpu, and press Enter. This launches Chrome with GPU rendering disabled so you can access Settings normally.
Fix 3: Clear Chrome’s Cache and Cookies
A bloated or corrupted cache can cause Chrome to crash on specific sites — sometimes every time you load them.
- Press Ctrl + Shift + Delete inside Chrome.
- Set the time range to All time.
- Check Browsing history, Cookies and other site data, and Cached images and files.
- Click Clear data and wait for it to finish.
- Restart Chrome.
Real-world example: If Chrome crashes only on a specific site (like a banking portal or streaming service), the problem is almost always stale cached data for that site. Clearing the cache for “All time” resolves it in under a minute.
Fix 4: Disable or Remove Extensions
Every extension runs alongside every page you visit. One poorly coded or outdated extension can conflict with Chrome’s processes and trigger repeated crashes — and you’d never know which one without testing.
- Type chrome://extensions in the address bar and press Enter.
- Toggle off every extension.
- Restart Chrome and browse for a few minutes.
- If crashes stop, re-enable extensions one at a time to find the culprit.
- Remove the problem extension by clicking Remove.
Pro tip: Ad blockers, VPN extensions, and screen-recording tools are the most frequent crash offenders. Test those first before working through the rest.
Fix 5: Reset Chrome Settings
If Chrome’s internal settings have drifted — often from a bad extension or a site that changed a setting without asking — a reset restores everything to factory defaults. Your bookmarks and saved passwords are not affected.
- Go to Settings > Reset settings in Chrome’s left sidebar.
- Click Restore settings to their original defaults.
- Read the confirmation, then click Reset settings.
This clears your startup pages, default search engine, pinned tabs, and extension settings.
Fix 6: Create a New Chrome Profile
A corrupt user profile is a common cause of persistent crashes that no other fix solves. Creating a fresh profile is quick, and you can migrate your data later.
- Click your profile picture in Chrome’s top-right corner.
- Click Add (or the + icon) to create a new profile.
- Use Chrome under the new profile for a while. If it runs fine, your old profile was corrupted.
Troubleshooting tip: If Chrome won’t open at all, open File Explorer and navigate to C:UsersYourNameAppDataLocalGoogleChromeUser Data. Rename the Default folder to Default.old, then relaunch Chrome. It creates a clean profile automatically.
Fix 7: Run an SFC Scan to Repair Windows System Files
Corrupt Windows system files can destabilize apps across the board, including Chrome. The built-in System File Checker (SFC) scans for and repairs them automatically. If your PC is also freezing in other apps, this fix is especially worth doing.
- Press Win + S, type
cmd, right-click Command Prompt, and choose Run as administrator. - Type
sfc /scannowand press Enter. - Wait for the scan to finish (10–15 minutes is normal).
- Restart your PC if files were repaired.
If SFC reports errors it can’t fix, run this command next:
DISM /Online /Cleanup-Image /RestoreHealth
Then run sfc /scannow again.
Fix 8: Update Your Graphics Driver
Chrome uses your GPU for page rendering. An outdated or corrupt graphics driver — especially combined with hardware acceleration — can cause repeated crashes during heavy browsing or video playback. If your CPU or GPU is already under strain, driver issues make things worse.
- Right-click the Start button and open Device Manager.
- Expand Display adapters.
- Right-click your GPU and choose Update driver.
- Select Search automatically for drivers and follow the prompts.
- Restart your PC after the update.
Pro tip: For the freshest driver, go directly to your GPU maker’s website — nvidia.com (NVIDIA), amd.com (AMD), or intel.com (Intel) — rather than relying on Windows to find the latest version.
Common Mistakes to Avoid
- Reinstalling Chrome without fixing the profile first. A fresh install copies your profile data back over, so crashes caused by a corrupt profile return immediately. Use Fix 6 before you reinstall.
- Skipping Windows Updates. Windows updates often include stability patches that affect how browsers interact with system components. Check Settings > Windows Update and install anything pending.
- Ignoring too many open tabs. Chrome runs a separate process for each tab. On systems with 4–8 GB of RAM, 20+ tabs can trigger a crash. Enable Chrome’s Memory Saver mode to automatically suspend inactive tabs and reduce the load.
- Testing with extensions still on. Diagnosing a crash with all extensions enabled makes it nearly impossible to isolate the cause. Always disable all extensions first — it takes 30 seconds and rules out a whole category of problems.
- Not restarting after each fix. Driver updates, SFC scans, and Windows updates all require a full restart before they take effect. Skipping the restart makes the next fix look like it failed when it hasn’t been applied yet.
- Confusing a crash with a freeze. If Chrome’s window stays open but stops responding (rather than closing entirely), the cause is usually high disk usage or RAM exhaustion rather than a corrupt install. Open Task Manager (Ctrl + Shift + Esc) and check Chrome’s resource usage before diving into profile or driver fixes.
Frequently Asked Questions
Why does Chrome keep crashing every time I open it?
The most likely causes are a corrupt Chrome profile or a conflicting extension. Start with Fix 4 (disable all extensions) and Fix 6 (create a new profile). These two steps solve the majority of “crashes on startup” problems.
Does reinstalling Chrome fix crashes?
Sometimes, but not if the crash is caused by a corrupt user profile — reinstalling leaves your profile data intact. Create a new profile first (Fix 6). If that fixes it, you can migrate your bookmarks and passwords to the new profile and delete the old one.
Can too many open tabs cause Chrome to crash?
Yes. Each tab runs as its own process and consumes RAM. When Chrome runs out of available memory, it can crash or forcibly close individual tabs. Enable Memory Saver mode in Chrome Settings to automatically free up RAM from tabs you haven’t used in a while.
Is Chrome crashing a sign of malware?
It can be. Some malware injects code into browsers and causes instability. After trying the fixes above, run a full scan with Windows Defender: open Windows Security > Virus & threat protection > Quick scan.
Why does Chrome crash only when I watch videos?
Video playback is GPU-intensive. Disable hardware acceleration (Fix 2) and update your graphics driver (Fix 8) — these two fixes resolve most video-related Chrome crashes. If it’s only one platform (e.g., YouTube), also try clearing that site’s cookies and cache.
Why does Chrome crash on one specific website but not others?
Site-specific crashes usually point to corrupted cached data for that site. Clear your cache with the time range set to “All time” (Fix 3) and try again. If the site uses heavy JavaScript or video, disabling hardware acceleration (Fix 2) can also help.
How do I know which Chrome extension is causing crashes?
Disable all extensions at once (chrome://extensions), then re-enable them one at a time, restarting Chrome between each. The crash will return when you re-enable the problem extension. Ad blockers, VPN extensions, and screen-recorders are the most common culprits.
Conclusion
Chrome crashing on Windows 11 is almost always fixable without reinstalling Windows or replacing hardware. Work through the 8 fixes in order — update Chrome, disable hardware acceleration, clear your cache, and test without extensions — and you’ll solve the problem in under 30 minutes in most cases.
If all 8 fixes still haven’t solved it, test another browser (Edge or Firefox). If other browsers crash too, the issue is in Windows itself rather than Chrome — revisit the SFC/DISM commands in Fix 7 and make sure Windows is fully updated.
Found the fix that worked for you? Leave a comment below — it helps other readers skip straight to the right step.