Why Does My Chromebook Keep Crashing? Causes and Fixes

Your Chromebook freezes mid-scroll, the screen blanks for a second, then it reboots on its own — and whatever you were doing is gone. If “why does my Chromebook keep crashing” is the question that brought you here, the answer is usually simpler than it feels in the moment: too many tabs competing for memory, a misbehaving extension, a stuck ChromeOS update, or, less often, failing hardware.

This guide walks through what to try first, how to tell a software problem from a hardware one, and when a hard reset, Powerwash, or full Recovery actually makes sense. It also covers the part people forget: Powerwash and Recovery erase your Chromebook’s local Downloads folder — exactly where backup files tend to sit. We’ll cover how to keep your tabs and files safe before you reset anything.

Why Does My Chromebook Keep Crashing?

Most repeat crashes come from memory pressure, a misbehaving extension, a stuck ChromeOS update, or (less commonly) a hardware fault. Chromebooks ship with modest RAM by design, so a browser window full of tabs, a video call, and a couple of Android apps running at once is often enough to push things over the edge. When that happens, the whole system can stall, a single tab can crash with an “Aw, Snap!” page, or the Chromebook can reboot itself without warning.

Before you chase a single cause, match the symptom to the likely reason. The table below is a starting point — work through it top to bottom, since the fixes get more drastic, and more disruptive, as you go.

If your Chromebook keeps crashing and restarting rather than just freezing, the cause list barely changes — memory pressure, a bad extension, a stuck update, or hardware wear are still the top suspects. A one-off freeze after weeks of smooth use is usually nothing more than too many tabs and an overdue restart. A pattern (crashing at the same point every day, or right after waking from sleep) points somewhere more specific, like an extension conflict or a battery on its way out. If your Chromebook keeps rebooting during a specific task, like video calls or streaming, that’s worth noting too, since it usually points to CPU or memory load rather than a random fault. For a Chromebook that only ever freezes without fully crashing, our companion guide on why your Chromebook keeps freezing covers that narrower case in more depth.

What’s the First Thing to Try When a Chromebook Crashes?

Turn the Chromebook off, then back on. That’s the first troubleshooting step Google’s own support recommends for a stuck or crashing device, and it’s the fastest way to fix a Chromebook that keeps crashing without erasing a single file.

If the Chromebook comes back clean and stays stable, you’re done — no need to dig further. If the exact same tab or app crashes again within a few minutes, the problem is specific to that tab or app rather than the whole system, and the next section covers how to deal with it directly instead of restarting on repeat. It’s worth building the habit of a full shut-down rather than just closing the lid every so often, since sleep alone doesn’t clear the same kind of memory buildup that a real restart does.

How Do You Fix a Frozen Tab or App on a Chromebook?

Press Shift + Esc to open Chrome’s Task Manager, then close whichever tab or app is stuck. It’s faster than restarting the whole Chromebook and leaves every other open tab untouched. Whether your Chromebook keeps freezing and crashing on one page or the whole system locks up, Task Manager is the tool built for exactly this.

If it’s just one page that’s frozen rather than the whole browser, try a hard refresh first: Ctrl + Shift + R forces the page to reload from scratch, ignoring anything cached that might be causing the hang. That alone solves a surprising number of “stuck” tabs, especially on pages that auto-refresh data or stream video. Ending a process through Task Manager is also gentler than force-quitting the whole browser, since it only removes the one offending tab from memory rather than reloading everything you had open.

Could a Bad Extension Be Crashing Your Chromebook?

Yes — a single extension can crash tabs, drain memory in the background, or freeze the whole Chromebook, and it’s one of the most overlooked causes because the crash rarely looks like it’s coming from the extension itself.

Open the Chrome menu, go to More tools, then Extensions, and look at what you’ve added recently. If a crash started around the same time you installed something new, that’s your first suspect. Turn it off, not just close the tab, and see whether the problem comes back over the next day of normal use.

If you’re not sure which one is guilty, disable everything except what you truly need, then re-enable them one at a time over a few days. It’s slower, but it’s the only reliable way to isolate an extension that only causes trouble under specific conditions, like during a video call or when a certain site is open. Extensions that inject content into every page you visit, such as ad blockers or note-taking tools, are worth suspecting first, since they run constantly rather than only on the sites they’re built for.

Is It a Hardware Problem? Using Chromebook Diagnostics

Open the built-in Diagnostics app — type “Diagnostics” into the launcher, or go to Settings, then About ChromeOS, then Diagnostics — and it tests your battery, CPU, memory, and connectivity in a few minutes. That’s the fastest way to rule hardware in or out before you spend time on software fixes that won’t help. Diagnostics needs ChromeOS 90 or later, which almost every Chromebook still receiving updates will have.

A battery with a high cycle count or a CPU pegged near its limit for no obvious reason both point toward hardware wear rather than a software fix. If Diagnostics comes back clean across the board, you can rule out hardware and focus on ChromeOS itself, extensions, or your update status instead — which is where most crashes come from.

Run Diagnostics right after a crash if you can, since some issues, like a spike in CPU or memory use, only show up while the problem is happening. Running it a day later, once everything’s calmed down, might miss the pattern entirely and send you looking in the wrong place.

Does Updating ChromeOS Fix Crashes?

Often, yes. An outdated ChromeOS version is one of the easier causes to miss, because updates mostly happen in the background and it’s easy to keep clicking “restart later” for weeks. To check, select the time in the bottom right, open Settings, then About ChromeOS, and choose Check for updates. Updates download automatically once you’re online (a blue notification means it’s recommended, orange means required) and you apply it by selecting Restart.

If updating doesn’t help, or your Chromebook hasn’t offered one in a while, check how much longer it’s eligible for updates. Every Chromebook has an Auto Update Expiration policy, and Google guarantees automatic updates for up to ten years from the device’s original release. You can see your own device’s cutoff at Settings, then About ChromeOS, then Additional details, then Update schedule. Past that date, ChromeOS itself stops changing, and any new crash won’t get a fix — worth knowing before you spend hours troubleshooting a machine that’s simply aged out. Our guide on updating a Chromebook covers what changes, and what doesn’t, with each update.

Past the update cutoff. If your Chromebook is past its Update schedule date, Google no longer provides technical support or new fixes for it. Persistent crashes on an aged-out device are more likely hardware wear than something an update could patch.

When Should You Try a Hard Reset?

Only after restarting, closing the stuck tab, checking extensions, and running Diagnostics haven’t fixed it. Google is explicit that a hard reset is a last resort for a Chromebook that’s stuck, not something to reach for first. It’s a more forceful version of a restart, meant for a system that won’t respond to a normal shutdown.

To do it, hold Refresh and tap Power, then release Refresh once the Chromebook starts back up. On a tablet or detachable, hold Back + Refresh + Power for at least ten seconds instead.

A hard reset doesn’t erase any data (it’s closer to pulling the plug than to a factory reset) but it can interrupt whatever was mid-write at the time, so it’s not something to do routinely. If a hard reset becomes something you need weekly, that’s a sign of a deeper issue, and it’s worth running Diagnostics again or considering the Powerwash and Recovery options covered next, rather than repeatedly forcing a restart.

What’s the Difference Between Restart, Hard Reset, Powerwash, and Recovery?

They escalate in what they erase: a restart erases nothing, a hard reset erases nothing but forces a restart, Powerwash wipes local data back to factory settings, and Recovery erases the entire drive and reinstalls ChromeOS. Which one you need depends on whether the Chromebook is simply stuck, misbehaving, or won’t boot at all — Google’s guide to restart, Powerwash, and Recovery lays out the same order.

Your Google Account data isn’t stored on the device itself, so it survives a Powerwash regardless — your bookmarks, Chrome sync data, and Drive files come back once you sign in again. What doesn’t survive is anything local: the Downloads folder, installed Android apps, and any settings you’d customized. Recovery is more destructive still, since it wipes the whole drive rather than just resetting it to factory state, and it’s meant for a Chromebook whose operating system is broken, not just slow or crash-prone. On school or work devices, admins can also disable Powerwash entirely, in which case you’d contact IT rather than trying to force it yourself.

How Do You Powerwash a Chromebook Without Losing Your Tabs?

Back up anything local before you start. Powerwash erases your Downloads folder along with every installed app and setting, and that folder is exactly where a lot of backup files, including BelayTab’s own scheduled export, end up sitting by default.

1. Back up first. Turn on BelayTab Sync, or move your BelayTab export file out of Downloads and into Google Drive.
2. Go to the sign-in screen. Sign out, or restart and wait for the sign-in prompt.
3. Trigger Powerwash. Hold Ctrl + Alt + Shift + R, then select Restart.
4. Confirm. Choose Powerwash, then Continue, and sign back in once it’s done.

Your Google Account and anything already saved in Drive come back automatically once you sign back in — bookmarks, Chrome sync, extensions tied to your account. What doesn’t come back on its own is anything BelayTab was keeping locally in that scheduled export file, since Powerwash treats it like any other file in Downloads. That’s the gap BelayTab Sync closes: it keeps a copy of your sessions in the cloud, outside the Chromebook’s local storage, so a Powerwash, or handing the device off to IT, can’t take your open tabs with it.

If you’d rather not pay for Sync, at minimum export your sessions and drag that file into Google Drive manually before you Powerwash — see how to export your sessions and how to set up automatic export backups. For general tab shortcuts and recovery basics on a Chromebook beyond just crash situations, our Chromebook tabs guide covers the everyday version.

What Should You Do Before Recovery Mode Wipes the Drive?

Recovery is more destructive than Powerwash (it erases the entire drive, not just local user data) so back up everything you care about first, not just your tabs. Chromebook crash recovery gets more serious as you move down this list, which is why backing up before Powerwash or Recovery matters so much more than before a simple restart.

You’d use the Chromebook Recovery Utility, a Chrome extension from the Chrome Web Store, to build a USB recovery drive, then boot into recovery mode by holding Esc + Refresh, pressing Power, and releasing it. On some models it’s Esc + Maximize + Power instead. Because Recovery wipes the whole drive, anything not backed up elsewhere is gone for good, including files that would have survived a Powerwash.

Recovery should be rare. If you find yourself reaching for it more than once, that’s usually a sign of failing storage rather than a one-off software glitch, and Diagnostics is worth running again once the Chromebook is back up. For the full breakdown of what each reset option does and doesn’t touch, see our Chromebook reset options guide and what the Recovery Utility erases.