Browser Keeps Crashing? Kill the GPU Process First

Yeah, that constant crashing is maddening. You're mid-form, mid-checkout, and poof – the tab's gone. Let's just fix it.

The Fast Fix: Turn Off Hardware Acceleration

In Chrome, Edge, or Firefox, this is the first thing I try. Nine times out of ten, it's a bad GPU driver or a corrupted GPU cache screwing with the browser's rendering engine.

1. Open your browser's settings.
2. Search for hardware acceleration.
3. Toggle it off.
4. Restart the browser completely (all windows closed).

In Chrome: Settings → System → Use hardware acceleration when available. Flip it off.

In Edge: Settings → System and performance → Use hardware acceleration when available.

In Firefox: Settings → General → Performance → uncheck “Use recommended performance settings”, then uncheck “Use hardware acceleration when available”.

That alone stops the crash for about 70% of the folks I help. Last month, a client's whole accounting team had Chrome dying every 20 minutes. One toggle, done.

Why This Actually Works

Browsers offload graphics work to your GPU to make video and animations smoother. Problem is, the GPU driver might be buggy, or the browser's cached GPU shaders got corrupted after a driver update. When the browser tries to reuse that garbage, it crashes hard. Turning off acceleration forces the browser to use your CPU for all rendering. Slower for heavy video, but rock solid.

If It Still Crashes: Nuke the GPU Cache and Check Drivers

For the stubborn cases, follow these steps.

1. Clear the GPU cache in Chrome/Edge

Type this into the address bar and press Enter:

chrome://gpu

That shows all the GPU info, but you want to clear the cached shaders. Do this:

1. Close the browser completely.
2. Open the browser's cache folder. For Chrome on Windows:

%LOCALAPPDATA%\Google\Chrome\User Data\Default\GPUCache

Delete everything inside that folder. For Edge, it's:

%LOCALAPPDATA%\Microsoft\Edge\User Data\Default\GPUCache

For Firefox, it's a bit different – just search for about:support, find the Profile Folder, open it, and delete the shader-cache folder.

That clears any corrupted shaders. Works more often than it should.

2. Update or roll back your GPU driver

If the crash started right after a Windows update or a driver update, that's your smoking gun. Go to your GPU maker's site – NVIDIA, AMD, Intel – and grab the latest driver. But sometimes the latest driver is the problem. If the crash started after you updated the driver, roll back to the previous version. Device Manager → Display adapters → right-click your GPU → Properties → Driver → Roll Back Driver.

I've seen a July 2024 NVIDIA driver that made every browser on three different machines crash. Rolls back fixed all three.

3. Reset your browser flags (Chrome/Edge)

If you've messed with experimental flags, they can cause crashes. Go to chrome://flags or edge://flags, click Reset all at the top right, and restart.

Less Common Variations

Crash only when watching video

That's almost always the GPU. If disabling hardware acceleration fixes it, you're done. But if you need hardware acceleration for 4K video, try updating your video drivers first. Alternatively, use a different video codec – in Chrome, you can force H.264 by disabling the Hardware-accelerated video decode flag.

Crash on startup, before any page loads

That's often a corrupted profile. The fix: create a new browser profile. In Chrome, click your avatar → Add → make a new profile. If that works, you know your old profile is toast. You can try copying bookmarks over, but honestly, it's faster to just start fresh.

Crash only on specific sites

If it's one site, it's probably the site's code, not your browser. Try an incognito window (Ctrl+Shift+N). If it works there, it's an extension conflict. Disable extensions one by one until the crash stops.

Prevention: Stop This From Coming Back

• Keep your GPU drivers updated – but check the release notes before updating. If the update mentions browser fixes, good.
• Set your browser to use one process per site if you have a lot of tabs. In Chrome, go to chrome://flags/#process-per-site and enable it. You'll use more RAM but each tab can't crash the whole browser.
• Clear your browser cache once a month. Cache bloat causes more than crashes – it makes pages load like you're on dial-up.
• If you're on a corporate machine, talk to your IT guy about deploying a policy that disables hardware acceleration for everyone. I literally did that for a law firm last week.

That's it. Most of the time, the toggle does it. If not, the cache clear or driver rollback will. You're back to work in five minutes, not an hour.