Tag: freezing

Chrome Memory Usage: How to Cut Chrome’s RAM with Built-In Settings

Chrome memory usage climbing past 2 GB? Turn on Memory Saver, audit extensions, and use Chrome’s own Task Manager to reclaim RAM in minutes — no extra apps needed.

Open Chrome with a dozen tabs and it is not unusual to watch it swallow 2 GB or more in Windows Task Manager. Chrome memory usage is one of the most common performance complaints I hear from both Windows and Mac users, and it is not a bug. Chrome runs each tab as a separate process, which protects your session when one tab crashes but also means RAM accumulates fast as your tab count grows. The good news: the biggest savings come from settings Chrome already ships with, not from any third-party tool.

Every fix below uses Chrome’s own built-in performance features plus a few targeted toggles. No extensions, no registry edits. On my own machine, after I enabled Memory Saver and disabled four forgotten extensions, Chrome dropped from 2.1 GB to roughly 1.2 GB on a 13-tab session, with no noticeable slowdown when tabs reloaded.

Quick Answer

Enable Chrome’s Memory Saver under Settings, then Performance, then Memory Saver. This freezes inactive tabs automatically and is the single biggest lever. Then open Chrome’s built-in Task Manager with Shift+Esc to spot any one tab consuming outsized memory. Most users see a 30 to 50 percent drop within a few minutes.

Start with Memory Saver, then let the built-in Task Manager point you at the one heavy tab worth closing.

How do I turn on Chrome’s Memory Saver?

Memory Saver is Chrome’s official answer to RAM overload. It puts inactive tabs to sleep so they stay visible in the tab bar but stop consuming memory until you click them. This is the first thing I switch on after any fresh install.

Steps

  1. Click the three-dot menu (top right) and choose Settings.
  2. Select Performance in the left sidebar.
  3. Toggle Memory Saver to on.
  4. Click Add under “Always keep these sites active” to exclude sites you switch to constantly, like email or a project dashboard.

Pro tip: Type chrome://settings/performance in the address bar to jump straight to this setting.

Memory Saver alone usually does most of the work, so turn it on before touching anything else.

Which Chrome tab is eating the most RAM?

Before adjusting anything else, identify the culprit. Chrome has its own Task Manager that shows per-tab memory, detail that Windows Task Manager hides by grouping everything into one “Chrome.exe” entry. When I checked mine, a single news tab with autoplay video was using more than a third of Chrome’s total footprint.

Steps

  1. Press Shift+Esc (Windows) or open the three-dot menu, then More tools, then Task Manager (Mac).
  2. Click the Memory Footprint column header to sort from highest to lowest.
  3. Any tab or extension above 300 MB is a candidate for closing. Select it and press End Process to free that memory immediately.

News sites with autoplay video, web-based design tools, and tabs left open overnight are the most common offenders. Closing one heavy tab often frees more RAM than any setting change.

Sorting by Memory Footprint turns a vague “Chrome is slow” into one specific tab you can close right now.

Should I disable extensions to save memory?

Often, yes. Extensions run as background processes with their own memory footprints, and a forgotten one can quietly claim 100 to 200 MB on its own. When I last audited mine, two extensions I had not opened in months were costing more RAM than three active tabs combined. If you want to vet what each one is actually doing, my guide to what private browsing actually hides covers how much browsers track even with add-ons in place.

Steps

  1. In Chrome’s Task Manager (Shift+Esc), look for entries prefixed with “Extension:” and note their memory use.
  2. Type chrome://extensions in the address bar.
  3. Toggle off any extension you have not actively used in the past month.
  4. For extensions you need only occasionally, disable them by default and enable them on demand.

A two-minute extension audit is the highest-value cleanup most people never do.

Does hardware acceleration help or hurt Chrome’s memory?

It depends on your hardware. Hardware acceleration hands page rendering to your GPU, which is faster on modern machines. On older systems or with outdated GPU drivers, it can actually increase Chrome’s memory use and cause visual glitches, which is the one case where I turn it off.

Steps

  1. Go to Settings, then System (or type chrome://settings/system in the address bar).
  2. Toggle Use graphics acceleration when available off.
  3. Click Relaunch to restart Chrome with the change applied.

Troubleshooting tip: If Chrome feels slower afterward, re-enable hardware acceleration and update your GPU driver through Device Manager instead. On any PC built after 2018, acceleration almost always helps, so this toggle mainly matters when RAM spikes on graphics-heavy pages.

Leave hardware acceleration on unless you are on older hardware with stale drivers.

How do tab groups keep Chrome’s memory under control?

Tab Groups let you bundle related tabs so you can collapse or close an entire cluster in one click instead of hunting tabs down one at a time. I group research sessions this way and close the whole group when I am done, which reclaims all that memory at once.

Steps

  1. Right-click any tab and select Add tab to new group.
  2. Name the group (for example, “Research” or “Shopping”) and choose a colour.
  3. When that task is done, right-click the group name and select Close group to free all its memory at once.

Here is how the main levers compare so you can pick where to start.

Method Memory Saved Effort Required Best For
Memory Saver (built-in) High (30 to 50%) One-time toggle Everyone
Close unused tabs High Ongoing habit Heavy tab users
Tab Groups, then close group Medium to High Light daily habit Researchers, multitaskers
Disable heavy extensions Medium One-time audit Extension-heavy users
Disable hardware acceleration Low to Medium One-time toggle Older PCs, outdated GPU drivers

Tab Groups turn good intentions into a one-click habit you will actually keep.

Does clearing the cache reduce Chrome’s memory use?

Indirectly. A large cache does not consume active RAM directly, but an oversized profile can slow Chrome’s startup and inflate its working memory footprint over long sessions. I clear mine every few weeks, and if pages are also rendering oddly, my walkthrough on clearing browser cache and cookies covers every major browser.

Steps

  1. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) to open the Clear browsing data panel.
  2. Set the time range to All time.
  3. Check Cached images and files. Leave Passwords and Autofill unchecked to stay signed in to sites.
  4. Click Clear data.

Clearing the cache is maintenance, not a memory fix, so do it for startup speed rather than instant RAM relief.

What are the most common Chrome memory mistakes?

  • Leaving Memory Saver off and blaming Chrome. It is disabled by default on many installs. Confirm it is actually on before assuming you need more physical RAM.
  • Installing a “RAM booster” extension. Adding an extension to save memory adds another background process. Chrome’s built-in Memory Saver does the same job without the overhead.
  • Ignoring the extension list entirely. Extensions accumulate. A two-minute review of chrome://extensions once a month often uncovers several you no longer use.
  • Disabling hardware acceleration on a modern machine. On hardware built after 2018 with current drivers, acceleration usually reduces memory load. Do not disable it without testing first.
  • Assuming Chrome is the only culprit. If total system RAM is above 90 percent, other background apps are contributing. Check Windows Task Manager (Ctrl+Shift+Esc) for the full picture, and if Chrome itself keeps falling over, see my fixes for Chrome crashing on Windows or Mac.

Most RAM complaints trace back to one of these five habits rather than a hardware shortfall.

Frequently Asked Questions

Why does Chrome use more RAM than other browsers?
Chrome’s per-tab process model isolates each tab for stability and security, so a crashed tab cannot bring down your whole session. In practice, Firefox and Edge now use similar architectures, so the gap has narrowed a lot since this reputation first formed.

Will Memory Saver slow down my browsing?
Only on re-activation, and only briefly. A frozen tab reloads when you click it, which takes one to two seconds, while actively used tabs are never frozen. On my setup I whitelisted my email and calendar so they always stay instant.

How much RAM does Chrome need to run well?
For five to ten tabs with a couple of extensions, Chrome runs comfortably on a system with 8 GB of total RAM. When I started keeping 20-plus tabs open for research, 16 GB made the difference between smooth scrolling and constant stutter.

Does clearing the cache free up RAM?
Not directly, because cache lives on disk rather than in RAM. That said, a bloated cache slowed my Chrome startup noticeably until I cleared it, since it inflates the working memory footprint over long sessions.

Can I see per-tab RAM use without a third-party tool?
Yes. Chrome’s built-in Task Manager (Shift+Esc on Windows) shows per-tab and per-extension memory in real time. I rely on it instead of Windows Task Manager, which lumps all Chrome processes into one line.

Is it safe to use End Process in Chrome’s Task Manager?
Yes. It closes that specific tab or extension, the same as clicking the X on a tab. The one time it caught me out, I lost a half-typed form, so confirm you do not need anything in the tab before ending it.

Conclusion

Turning on Memory Saver and running a quick extension audit took me from “Chrome is eating all my RAM” to noticeably smoother browsing in under five minutes. If a sluggish browser is your real problem, my guide to making Microsoft Edge faster applies many of the same ideas. Google also maintains an official overview of Chrome’s performance features worth bookmarking. Try Memory Saver today and check your numbers in Shift+Esc.

iOS Update Won’t Install on iPhone? A Calm, Ranked Walkthrough

iOS update won’t install on your iPhone? A calm, ranked walkthrough — Wi-Fi, storage, restart, Finder, and a fresh download — gets you current with zero data loss.

An iOS update that won’t install on your iPhone usually leaves you staring at a frozen spinner, a “Software Update Failed” alert, or a timer stuck on “Estimating time remaining” for an hour. I’ve hit all three on my own iPhone, and every time the cause turned out to be small: weak Wi-Fi, tight storage, or a half-downloaded file that quietly corrupted itself. Almost every failed iOS update is fixable at home in under an hour, without erasing a single photo.

Below I walk through the same ranked steps I use, starting with the most common culprit. The first three resolve it for most people in under 10 minutes; the last two cover stubborn cases where the over-the-air method keeps failing.

Quick Answer

Confirm your iPhone is on Wi-Fi (not cellular), has at least 1.5 GB of free storage, and is plugged into power. If the update still fails, go to Settings > General > iPhone Storage, delete the failed update file, then return to Settings > General > Software Update and download a fresh copy.

Is your Wi-Fi connection actually stable?

iOS updates won’t download over cellular by default, and a weak or unstable Wi-Fi signal can silently corrupt a download partway through. The first time my update kept failing, I was sitting in a coffee shop on a captive-portal network that never fully authenticated.

  1. Open Settings > Wi-Fi. Make sure you’re on your home network — not a captive portal (hotel, coffee shop) that requires a browser login to activate.
  2. Move closer to your router if signal is weak, or restart the router by unplugging it for 30 seconds.
  3. Go to Settings > General > Software Update and tap Download and Install.

Pro tip: turn Airplane Mode on for 10 seconds, then off again. This forces your iPhone to reconnect to Wi-Fi cleanly before the download restarts.

A clean, authenticated Wi-Fi connection fixes more stuck updates than any other single step.

Do you have enough free storage?

iOS needs roughly 1.5–2 GB of scratch space to unpack and install an update, even when the download file itself is smaller. With less free space than that, the install fails without a clear error message.

  1. Go to Settings > General > iPhone Storage and check your available space.
  2. Offload unused apps: tap any app > Offload App. This removes the binary but keeps your data and documents.
  3. Clear Safari cache: Settings > Safari > Clear History and Website Data.

If storage is persistently tight, my guide on freeing up iPhone storage fast shows how to recover gigabytes without touching your photo library. And if you already have 3–4 GB free but iOS still complains about space, a partially downloaded update file is likely hogging hidden room — skip ahead to the stuck-file fix below.

Give iOS at least 1.5 GB of breathing room or the installer stalls with no useful error.

Have you tried a full power-off restart?

A background process inside the Settings app can stall and silently block the update from progressing. A clean power-off restart clears it in about 90 seconds, and it has rescued my update more often than I’d expect for something this simple.

  1. Force-quit Settings: on Face ID models, swipe up from the bottom edge and hold briefly, then flick the Settings card upward. On older Touch ID models, double-press Home and swipe away Settings.
  2. Power off fully: hold Side + Volume Down until the slider appears, then slide to power off. Wait 30 seconds.
  3. Restart, then go to Settings > General > Software Update and try again.

A full power cycle clears the stalled background process that blocks every retry.

Should you update through Finder or iTunes instead?

When repeated over-the-air attempts fail, connecting to a computer sidesteps iCloud sync conflicts and unreliable Wi-Fi. Apple recommends this path for persistent OTA failures, and it takes less than an hour. Here’s how the methods compare so you pick the right one.

Method Best for Erases data? Approx. time
OTA (Settings app) Normal updates on a stable connection No 20–45 min
Finder / iTunes – Update Repeated OTA failures No 30–60 min
Finder / iTunes – Restore Boot loop or won’t start Yes 60–90 min
Recovery Mode Won’t turn on at all Yes 60–90 min
  1. Connect your iPhone to a Mac (Finder) or Windows PC (iTunes) with a trusted USB cable.
  2. Open Finder or iTunes and click your iPhone in the left sidebar.
  3. Click Check for Update, then click Update — not Restore. Your apps and data stay intact.
  4. Follow the on-screen prompts. The phone restarts automatically once complete.

If Finder or iTunes doesn’t recognize your device, my guide on fixing AirDrop failures on iPhone covers the same USB-trust and network settings that affect how your Mac detects the phone.

A wired Finder or iTunes update bypasses the flaky Wi-Fi and iCloud conflicts that derail OTA installs.

Is a stuck update file blocking every download?

A partially downloaded iOS update can corrupt quietly and cause every new attempt to stall at the exact same percentage. Deleting it forces a clean fetch from Apple’s servers — this is the step that finally cleared an “Update Requested” loop on my own phone.

  1. Go to Settings > General > iPhone Storage.
  2. Scroll the app list and tap the iOS update entry (listed by version number, e.g., “iOS 18.x Update”).
  3. Tap Delete Update and confirm.
  4. Return to Settings > General > Software Update and tap Download and Install for a fresh copy.

This is the fix Apple’s official iOS update guide recommends first for “Update Requested” loops that keep recycling on their own.

Deleting the corrupted installer is the single most reliable cure for a download stuck at the same percentage.

Common Mistakes to Avoid

  • Starting an update on cellular. iOS blocks OTA downloads over mobile data by default. Connect to Wi-Fi before tapping Download.
  • Updating with low battery. iOS pauses installation when battery is below roughly 50% to prevent a dead battery from corrupting the system mid-install. Plug in first.
  • Ignoring a frozen “Estimating time remaining” screen. It can hang indefinitely on a slow connection. Cancel the download, move to a faster network, and restart.
  • Tapping Restore instead of Update in Finder/iTunes. Restore erases all your data. Always click Update unless you deliberately intend to start from scratch.
  • Retrying without restarting first. A stalled background process blocks every attempt. Do a full power-off restart before each new try.

Frequently Asked Questions

Why does my iPhone say “Software Update Failed”?

The update file was corrupted or your connection dropped mid-download. Delete the file under Settings > General > iPhone Storage and re-download on stable Wi-Fi. When I saw this alert, deleting the half-finished file and reconnecting to my home network cleared it on the next attempt.

Can I update iOS without Wi-Fi?

Yes, on iOS 16 and later — go to Settings > Cellular and enable “Software Updates” under Cellular Data options. Apple still recommends Wi-Fi for large updates, and the one time I tried over cellular, a brief signal drop corrupted the partial download and I had to start over.

How much free storage do I need to install an iOS update?

Plan for at least 1.5–2 GB of free space, even if the update file is smaller. On a 64 GB iPhone I keep around, freeing two extra gigabytes by offloading unused apps was enough to get a stuck install to finally complete.

What do I do if my iPhone gets stuck on the Apple logo after updating?

Hold Side + Volume Down (Face ID models) or Side + Home (older models) until the screen goes black and the phone restarts. If the logo returns, connect to Finder or iTunes and use Recovery Mode — that recovered a relative’s iPhone for me after a logo loop.

Does updating iOS delete my photos and apps?

No. Standard iOS updates preserve all your apps, photos, and settings. Only a full Restore through Finder/iTunes or a factory reset erases content, which is why I always confirm I’m clicking Update, not Restore.

Is it safe to install a major iOS update right away?

Generally yes, though I wait a few days on my main phone for major releases. If a big update ships with widespread early bugs, Apple typically issues a patch within one to two weeks, so a quick check of tech forums first is a reasonable precaution.

Conclusion

iOS update failures almost always trace back to a weak Wi-Fi signal, low storage, or a corrupted download file. Work through these fixes in order and you’ll be running the latest iOS in under an hour — no Apple Store required. If a charging problem interrupts your update midway, my guide on fixing iPhone charging problems covers every cable and port scenario. Share this page with anyone stuck on an outdated iOS version.

Slow Android Phone: How to Make It Fast Again in Minutes

A slow Android phone usually isn’t dying hardware. I share the exact restart, cache, and storage steps I use to bring lagging phones back to speed fast.

A slow Android phone makes everyday tasks frustrating. Apps take forever to open, scrolling stutters, and the keyboard lags a beat behind your typing. The first time my own Pixel started crawling, I assumed it was finally wearing out after two years. It wasn’t. In almost every case I’ve troubleshot, a slow Android phone is fixable in minutes without losing data or visiting a repair shop.

These steps work on Samsung Galaxy, Google Pixel, OnePlus, Motorola, and virtually every other Android device. I’ve ordered them by impact, so start at the top and work down. Most people notice a clear improvement after the first two.

Quick Answer

Restart your phone, then clear the cache of your heaviest apps under Settings, Apps, the app name, Storage, Clear Cache. If lag persists, free up storage until at least 10 percent of your total capacity is available. These three steps resolve most Android slowdowns in under five minutes with no data loss.

Which fixes give the biggest speed boost?

When I diagnose a sluggish phone, I run through these six fixes in order. The first two solve the majority of cases on their own, so you may never need to reach the bottom of the list.

Fix Effort Time Best for
1. Restart the phone Very low 1 min Temporary slowdowns, RAM bloat
2. Clear app cache Low 3–5 min Specific laggy apps
3. Free up storage Medium 5–10 min Persistent system-wide lag
4. Limit background activity Low 2–3 min Constant RAM and CPU drain
5. Install system updates Low 5–15 min Post-update lag, missing patches
6. Reset app preferences Low 2 min Widespread app slowdowns

Work top to bottom and stop the moment your phone feels responsive again.

Does restarting your phone actually fix lag?

Yes, more often than you’d think. A restart clears RAM, ends runaway background processes, and flushes temporary files. When my phone has been on for several days straight, this single step usually restores snappy performance on its own.

  1. Hold the power button.
  2. Tap Restart, not Power Off.
  3. Wait 60 seconds before opening apps so the system finishes loading.

I now set a weekly restart reminder in my calendar. A regular reboot prevents gradual slowdowns from building up before I even notice them.

A clean reboot is the fastest, lowest-risk speed fix on Android.

How do I clear app cache to speed things up?

A bloated cache is the most common cause of a slow Android phone I run into. Clearing it removes stored temporary files without touching your personal data, and the app rebuilds its cache automatically on the next launch.

  1. Open Settings.
  2. Tap Apps, or Application Manager on older devices.
  3. Select the app that feels slowest. I usually start with the browser, camera, and social apps.
  4. Tap Storage & Cache, then Clear Cache.
  5. Repeat for your three to five heaviest apps.

The first time I did this on a friend’s Galaxy, clearing Instagram alone shaved the app’s launch time from roughly six seconds to under two. For broader cleanup, see my guide on clearing Android storage space.

Clearing cache is the safest cleanup on Android because it never deletes your settings or logins.

How much free storage does Android need to run smoothly?

Keep at least 10 percent of your total capacity free. When storage drops below that, Android slows noticeably because the system struggles to write temporary files and index data. On a 128 GB phone, that means keeping roughly 13 GB free at all times.

  1. Go to Settings, then Storage to see what is eating space.
  2. Open the Files app and delete anything in Downloads you no longer need.
  3. Back up photos to Google Photos, then remove the local copies.
  4. Uninstall apps you haven’t opened in three months or more.

Crossing back above the 10 percent line is what most reliably ends system-wide lag.

Should I limit background app activity?

Yes, for the worst offenders. Apps that silently refresh, like social feeds, email clients, and news readers, consume RAM and CPU even when you’re not using them. Restricting the biggest ones frees resources for whatever you’re actively doing.

  1. Open Settings, then Apps.
  2. Tap the app you want to restrict.
  3. Tap Battery, then Background usage, then Restricted. On Pixel devices, I leave Adaptive Battery on under Settings, Battery for a system-wide control.

One caution from experience: if a restricted app stops delivering notifications, return to its Battery settings and switch from Restricted to Optimized. That balances background limits with timely alerts. If the same apps are also draining your battery, my guide on stopping fast Android battery drain targets the most common culprits.

Restricting a few chatty apps frees real resources without breaking the ones you rely on.

Why do system updates make a slow phone faster?

Android updates frequently include memory management improvements and performance patches. Google publishes monthly security and performance bulletins, so skipping updates leaves documented fixes unapplied on your device.

  1. Go to Settings, then System, then System Update, or Software Update on Samsung devices.
  2. Tap Check for updates.
  3. If an update is available, download and install it. Keep the phone plugged in and allow 10–15 minutes.

Installing pending updates applies performance fixes you can’t replicate any other way.

What does resetting app preferences do?

It restores every app’s default settings without deleting a single app or any personal data. When my whole phone felt slow rather than one app, corrupted defaults or a disabled system service were usually dragging everything down, and this reset fixed it.

  1. Open Settings, then System, then Reset options.
  2. Tap Reset app preferences.
  3. Confirm by tapping Reset.

If apps keep crashing after this step, see my guide on why Android apps keep crashing for deeper troubleshooting.

Resetting preferences is the broadest safe fix when slowdowns span the whole phone.

Common Mistakes to Avoid

  • Using task killer apps. Manually killing background apps forces Android to reload them from scratch, burning more CPU and RAM than leaving them idle. The fix: trust Android’s own memory management and uninstall the killer.
  • Clearing data instead of cache. Clear Storage, sometimes labeled Clear Data, wipes your settings and logins. The fix: always choose Clear Cache, the safe option that touches nothing personal.
  • Waiting until storage is completely full. At zero percent free, the phone has been struggling for weeks. The fix: check storage monthly and clear space before you hit the 10 percent line.
  • Factory resetting as your first move. It erases everything and is rarely necessary. The fix: work through the six steps above first, since they target the same causes without data loss.
  • Trusting speed booster apps. They run their own background processes and tend to make a slow phone worse. The fix: remove them and rely on the built-in tools.

Frequently Asked Questions

Why did my Android suddenly slow down after a system update?

It’s usually temporary reindexing, not a broken update. Android can take 24 to 48 hours to fully optimize as it rebuilds app indexes in the background. After a recent update on my Pixel, it felt sluggish for a day, then snapped back on its own. If lag lasts past two days, clear your app cache and check for a follow-up patch under Settings, System Update.

Will a factory reset speed up my Android phone?

Yes, but it should be your last resort. A reset removes all accumulated clutter and returns the phone to its original state. The six steps above target those same causes without erasing anything, which is why I’ve only had to factory reset one phone in years, and only after the simpler fixes failed.

How often should I clear app cache?

Clear an app’s cache whenever it feels sluggish or right after a major update. As a routine, I clear my five heaviest apps once a month, and that alone keeps buildup from ever affecting overall speed.

Can I reduce lag without deleting any files?

Yes, several of these fixes touch nothing personal. The restart, background limits, system update, and reset app preferences steps leave every file and app intact. When a relative worried about losing photos, those four steps fixed her lag without removing a single image.

Do live wallpapers slow down Android?

They can, especially on older or budget devices, because animated wallpapers use GPU resources continuously. On an aging phone I tested, swapping a live wallpaper for a static one made scrolling visibly smoother. It’s a small but genuine gain when a phone is already struggling.

Conclusion

A slow Android phone is almost always fixable without a repair shop or a new device. Start with a restart and a cache clear, which resolve most slowdowns in under five minutes, then work down only if lag continues.

If you’ve tried all six and your phone still drags, leave a comment with your device model and Android version, and I’ll help you pinpoint exactly what’s left.

How to Clear Browser Cache and Cookies in Chrome, Firefox, Safari, and Edge

Clear browser cache and cookies in Chrome, Firefox, Safari, and Edge in under two minutes — fix blank pages, login loops, and glitches on any device today.

When a webpage loads blank, shows yesterday’s content, or freezes mid-scroll, a bloated cache is usually the first thing I check. Every browser quietly stores temporary files — images, scripts, and cookies — to make repeat visits faster, but over weeks those files pile up and start causing the very glitches they were meant to prevent. Clearing cache and cookies is the cheapest, fastest reset you can give a misbehaving browser.

The whole job takes under two minutes and fixes a long list of headaches: login loops, broken layouts, videos that won’t play, and general sluggishness. I’ll walk through Chrome, Firefox, Safari, and Edge on both desktop and mobile.

Quick Answer

Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) in Chrome, Firefox, or Edge to open the clear-data dialog. Choose All time, check Cached images and files plus Cookies, then click Clear data. In Safari on Mac, go to Safari > Clear History > All History. On iPhone, open Settings > Safari > Clear History and Website Data.

What Do Cache and Cookies Actually Do?

Your browser uses cache to store copies of pages you’ve visited so the next load is faster. Cookies are small text files websites use to remember your login session, shopping cart, or preferences. Both are helpful right up until they aren’t.

A cached version of a page can be weeks old, and an expired or corrupted cookie can lock you out of a site entirely. Clearing both forces the browser to start fresh with current data from the server. You don’t need a weekly cleaning schedule — I only clear cache when a site behaves oddly, looks outdated, or has just gone through a redesign.

Cache speeds up loading; cookies remember you — clearing them resets both to a clean slate.

How Do I Clear Cache and Cookies in Google Chrome?

  1. Open Chrome and press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac).
  2. Set the time range to All time.
  3. Check Cookies and other site data and Cached images and files. Leave browsing history unchecked if you want to keep it.
  4. Click Clear data.

Chrome clears the cache in seconds. The first time I did this I panicked when I got logged out of every site at once — that’s expected behavior, not an error, so just sign back in. On Android, tap the three-dot menu > Settings > Privacy and security > Clear browsing data, then follow the same steps. If Chrome still drags afterward, the problem is usually memory rather than cache; my guide on Chrome memory usage covers what to do next.

In Chrome, the keyboard shortcut plus an All time range clears everything in one pass.

How Do I Clear Cache and Cookies in Mozilla Firefox?

  1. Click the hamburger menu (three lines) > Settings > Privacy & Security.
  2. Scroll to Cookies and Site Data and click Clear Data.
  3. Check both Cookies and Site Data and Cached Web Content.
  4. Click Clear.

You can also press Ctrl+Shift+Delete for a quicker dialog with a time-range selector. If Firefox still misbehaves after a clear, I go to Help > More troubleshooting information > Refresh Firefox, which resets settings without deleting bookmarks or passwords. Mozilla’s official Firefox cache guide adds screenshots if you want them.

Firefox separates cache and cookies clearly, and Refresh Firefox is the next step when clearing alone falls short.

How Do I Clear Cache and Cookies in Safari on Mac and iPhone?

  1. On Mac, open Safari and click Safari in the menu bar > Clear History.
  2. Set the range to All History and click Clear History.

Safari wipes history and cookies in one step. When I want to clear cache only — without losing my history — I enable the Develop menu under Safari > Settings > Advanced > Show Develop menu, then choose Develop > Empty Caches. On iPhone, go to Settings > Safari > Clear History and Website Data. If you also want to know what stays private while browsing, see what Incognito mode actually hides.

Safari bundles cookies into Clear History, so use the Develop menu when you only want the cache gone.

How Do I Clear Cache and Cookies in Microsoft Edge?

  1. Press Ctrl+Shift+Delete or go to Settings > Privacy, search, and services > Choose what to clear.
  2. Set the time range to All time.
  3. Check Cookies and other site data and Cached images and files.
  4. Click Clear now.

Edge is built on Chromium, so the process is nearly identical to Chrome and the same keyboard shortcut works on both. That shared foundation is also why a clear in one rarely fixes a problem in the other — they keep separate caches.

Edge mirrors Chrome step for step, but its cache is stored separately from Chrome’s.

Which Browser Clears Cache Fastest?

Each browser exposes the same controls a little differently. This table shows the shortcut, whether you can target cookies on their own, and the mobile path for each one.

Browser Keyboard Shortcut Clears Cookies Separately Mobile Clear Path
Chrome Ctrl+Shift+Delete / Cmd+Shift+Delete Yes Menu > Settings > Privacy > Clear browsing data
Firefox Ctrl+Shift+Delete / Cmd+Shift+Delete Yes Menu > Settings > Data Management
Safari No shortcut (use Develop menu for cache only) Via Develop > Empty Caches Settings > Safari > Clear History
Edge Ctrl+Shift+Delete / Cmd+Shift+Delete Yes Menu > Settings > Privacy > Clear browsing data

Chromium browsers tie for the fastest one-shortcut clear; Safari trades speed for a dedicated cache-only option.

Common Mistakes to Avoid

  1. Choosing a short time range. Selecting “Last hour” or “Last 7 days” won’t remove a file cached weeks ago. Fix: pick All time before clicking Clear when troubleshooting a stubborn problem.
  2. Clearing cache but skipping cookies. Login loops come from corrupted or expired cookies, not cached page files. Fix: always check both boxes together.
  3. Expecting a dramatic speed boost. Clearing cache helps with stale data and glitchy pages, not sluggish RAM. Fix: audit your extensions and enable Memory Saver, as my Chrome memory guide explains.
  4. Not restarting the browser afterward. Some cached data doesn’t fully flush until every window closes. Fix: quit the browser completely and reopen it.
  5. Using a third-party “cache cleaner.” Every major browser has built-in tools. Fix: use the native dialog above and skip any app that promises to “speed up your browser.”

Frequently Asked Questions

Will clearing cache delete my saved passwords?
No. Passwords live in the browser’s built-in password manager, which is separate from cache and cookies. For example, after I cleared everything on All time in Chrome, my saved logins still autofilled — I just had to re-enter them once because the session cookie was gone. You can review them anytime in your browser’s saved passwords.

How often should I clear my browser cache?
There’s no fixed schedule for most people. I clear mine only when a site looks broken, shows outdated information, or has just gone through a major redesign — for instance, when a banking site kept showing an old layout until I cleared it.

Why do I get logged out after clearing cookies?
Cookies store your active login session, so deleting them tells the site it no longer recognizes you. The first time it happened to me across a dozen tabs it felt alarming, but logging back in simply creates a fresh cookie and restores access.

Does clearing cache speed up my browser?
Sometimes, if slowness comes from an oversized or corrupted cache. When my Chrome felt sluggish, though, the real culprit was a dozen open tabs eating RAM — managing extensions and memory moved the needle far more than clearing cache did.

Can I clear cache in Chrome and Firefox on iPhone?
Yes. In Chrome for iOS, tap the three-dot menu > Clear Browsing Data. In Firefox for iOS, tap the menu > Settings > Data Management > Clear Private Data. I keep both apps and clear them the same way on my own phone.

Does “Clear History” in Safari also delete cookies?
Yes. Safari’s Clear History removes browsing history, cookies, and cached data together in one action. When I wanted to keep my history but dump the cache, I used Develop > Empty Caches instead.

Conclusion

Clearing cache and cookies is the fastest first move I reach for whenever a site breaks — it costs nothing and takes under two minutes on any device. Use Ctrl+Shift+Delete on Chrome, Firefox, or Edge, work through the Safari menu on Mac or iPhone, and always clear cookies alongside cache to fix login loops rather than just stale pages. Bookmark this page so the right steps are always a tap away the next time a browser acts up.

Android Phone Keeps Restarting on Its Own: How to Stop It

Android phone keeps restarting on its own? I walk through force restart, Safe Mode, storage, and updates to find the cause and get your phone stable for good.

When an Android phone keeps restarting on its own, the hardest part is that nothing on screen tells you why. A reboot every few days is annoying; one every few hours makes the phone almost unusable. I have chased this exact problem on my own Pixel and on a friend’s Galaxy, and the reassuring pattern is the same both times: spontaneous reboots are almost always a software issue you can fix at home, not a dead motherboard.

I have ordered the fixes below from the fastest (a 10-second force restart) to the most involved (a factory reset). On my friend’s phone the culprit turned out to be a single weather widget, and Safe Mode exposed it in under an hour. Most people land on a fix within the first three steps.

Quick Answer

Force restart your Android by holding the Power button for 10 seconds, then install every pending app and OS update. If it still reboots, boot into Safe Mode (hold Power, long-press Power Off, tap Safe Mode). A phone that stays stable in Safe Mode means a third-party app is to blame, so uninstall recent apps one at a time.

What Is Actually Causing the Reboots?

Spontaneous reboots usually trace back to one of five root causes. When I match the symptom to the cause first, I skip straight to the fix that matters instead of working through all six blindly.

Symptom Most Likely Cause Start With
Reboots right after installing an app Incompatible or buggy app Safe Mode
Reboots when the phone gets hot Overheating Cool down
Reboots during gaming or video Overheating or low storage Cool down, then storage
Reboots randomly all day OS bug or corrupted system file Force restart, then updates
Reboots only while charging Faulty cable or battery Force restart, then reset

Pinning the symptom to a likely cause saves you from running every fix when only one applies.

How Do I Force Restart the Phone?

A force restart clears the phone’s memory without deleting any data. It takes 10 seconds and clears the one-time glitches that cause a sudden reboot. This is always the first thing I try because it costs nothing and often works.

Steps

  1. Hold the Power button (or Power + Volume Down on Samsung and some Pixel models) for 10 seconds until the screen goes dark and the phone vibrates.
  2. Release the buttons and let the device boot normally.
  3. Use the phone for 30 minutes. If no reboot occurs, the cause was a one-time glitch.

On Samsung Galaxy devices, Power + Volume Down forces a restart even when the screen is frozen and ignoring your taps — the trick that saved me when my friend’s Galaxy locked up mid-reboot.

A 10-second force restart costs nothing and fixes the most common one-off crashes.

Why Does My Phone Restart When It Gets Hot?

Android reboots itself when the processor hits a critical temperature, usually around 45 to 50 degrees Celsius. That is a protective shutdown, not a fault — but it confirms overheating is your trigger. The first time my Pixel did this, it was during a long navigation session in a hot car.

Steps

  1. Remove the case and set the phone on a flat, cool surface for 10 to 15 minutes.
  2. Close all apps and do not charge while it cools.
  3. Feel for heat concentrated in one spot (behind the camera or the center of the back). Localized heat can point to a hardware problem rather than normal load.

If reboots only strike during gaming or streaming, removing the case and not charging at the same time usually solves it. Reboots during plain calls or texting suggest something more serious worth a technician’s look. For prevention, my full guide on how to stop your Android phone from overheating covers the rogue apps and chargers behind most heat.

An overheating reboot is Android protecting itself, so let the phone cool fully before using it again.

How Do I Boot into Safe Mode to Find a Bad App?

Safe Mode starts Android with only built-in system apps running. If your phone stops rebooting in Safe Mode, a third-party app is the cause — and you can remove it without a full factory reset. This is the test that exposed the weather widget on my friend’s Galaxy.

Steps

  1. Hold the Power button until the power menu appears.
  2. Long-press Power Off (or Restart on some models) until a Safe Mode prompt appears.
  3. Tap OK to reboot into Safe Mode. The words “Safe Mode” show in the bottom-left corner.
  4. Use the phone normally for 30 to 60 minutes and watch for reboots.
  5. If it stays stable, reboot normally and uninstall the apps you added around the time the reboots began, one at a time, testing after each.

For the official walkthrough, see Google’s Android Safe Mode guide. If individual apps were already crashing before the reboots started, my guide on why your Android apps keep crashing handles that app-level diagnosis.

If the phone runs clean in Safe Mode, a recently installed app is your culprit.

How Much Free Storage Does Android Need?

Android needs roughly 500 MB to 1 GB of free internal storage to write temporary system files reliably. When that space runs out, the OS can crash the device mid-task. I have seen a phone at 200 MB free reboot several times a day until I cleared room.

Steps

  1. Open Settings > Storage and check the free space. If it is under 1 GB, keep going.
  2. Clear the cache for your biggest apps: Settings > Apps > [App Name] > Storage > Clear Cache.
  3. Back up photos and videos to Google Photos and delete the local copies — this recovers the most space the fastest.

For the full method, see my walkthrough on how to clear gigabytes of Android storage in under 10 minutes.

Keep at least 1 GB free so Android always has room for temporary system files.

Should I Install Every Pending Update?

Yes. Manufacturers ship patches that fix system instability and known reboot bugs, and running an outdated build is one of the most common reasons restarts drag on for weeks after other fixes. I always check for updates before considering a reset.

Steps

  1. Open Settings > System > Software Update. Samsung uses Settings > Software Update; Pixel uses Settings > System > System Update.
  2. Tap Check for Updates and install anything available.
  3. Update every app: open Google Play Store, tap your profile icon, then Manage Apps & Device > Update All.
  4. Restart the phone after the updates finish to apply them.

An up-to-date OS and app set removes the known bugs behind a surprising share of reboots.

When Is a Factory Reset the Right Call?

A factory reset wipes software corruption and returns Android to a clean state, resolving problems that survive every other fix. Treat it as a last resort and back up everything first, because it erases all local data, apps, and settings.

Steps

  1. Back up your data: Settings > Google > Backup > Back Up Now. Confirm photos are synced to Google Photos first.
  2. Go to Settings > System > Reset Options > Erase All Data (Factory Reset).
  3. Confirm and let it finish — usually 5 to 10 minutes.
  4. Set the phone up as new, restore only essential apps first, and watch for reboots over 24 hours before restoring the rest.

If the phone still reboots after a clean reset, the problem is hardware — a failing battery, damaged motherboard, or water intrusion — and a certified repair center is the right next step.

A factory reset clears any software corruption, so anything left afterward points to hardware.

Common Mistakes to Avoid

  • Skipping the Safe Mode test. Many people jump straight to a factory reset when Safe Mode would have exposed one bad app in under an hour. Always test Safe Mode before wiping the device.
  • Using the phone while it cools down. Running apps during an overheating episode keeps the temperature high and triggers more shutdowns. Set the phone aside completely for at least 10 minutes.
  • Restoring every app at once after a reset. Adding everything back in bulk reintroduces the problem app without isolating it. Restore in small batches and monitor between each one.
  • Wiping the system cache partition. Some older guides push this from recovery mode. On Android 10 and later it rarely fixes reboots and can introduce new OS errors, so skip it.
  • Replacing the battery first. A failing battery does cause reboots, but mostly on phones three to four years old or with visible swelling. Exhaust the software fixes before paying for a replacement.

Frequently Asked Questions

Why does my Android restart only at night?
Scheduled app and OS updates usually install between midnight and 6 AM, and many trigger an automatic reboot to finish. On my own phone the nightly restart stopped once I set Play Store auto-updates to Wi-Fi-only and checked the System Update schedule.

Can malware cause an Android to keep restarting?
Yes, though it is uncommon. Malicious apps can destabilize Android and trigger reboots. When I suspect this, I boot into Safe Mode to isolate it, then run a scan with Google Play Protect from the Play Store menu and uninstall anything I do not recognize.

My phone reboots only while charging. Is the charger the problem?
Often, yes. A counterfeit or damaged cable delivers inconsistent voltage and can trip a protective shutdown. I once traced this to a cheap car charger; swapping in the certified manufacturer cable and adapter fixed it instantly. If it persists, the port may need cleaning or repair.

How long does an Android factory reset take?
The reset itself takes 5 to 10 minutes. Setup and restoring your backup adds another 15 to 30 minutes. When I reset my Pixel, the full round trip back to a usable phone was about 40 minutes with a large photo library.

Is it normal for an Android to restart once in a while?
One spontaneous reboot every few weeks is generally harmless, usually a minor system hiccup. I only start working through these fixes when a phone reboots more than once a week, which is the point where it stops being a fluke.

Conclusion

In most cases a force restart, a Safe Mode test, or freeing up storage is enough to stop an Android phone from rebooting on its own. Start with the force restart and work down only as far as you need — most people never reach a factory reset.

If battery life is suffering too, my guide on Android battery draining fast covers the next settings worth checking.

Chrome Crashing on Windows or Mac: How to Stop Aw, Snap and Random Closes

Chrome crashing on Windows or Mac usually traces to one bad extension, a stale cache, or a GPU conflict. Walk through six ranked fixes and get stable again today.

Chrome crashing on Windows or Mac almost always traces back to a small set of culprits: a rogue extension, a corrupted cache, a GPU driver conflict, or simply an outdated build. The first time my own copy started throwing “Aw, Snap!” on every tab, I assumed the install was beyond saving — but the real cause was a single extension that had silently updated overnight.

I have rebuilt this troubleshooting routine across dozens of Windows and Mac machines, and the order below is ranked easiest-first. Each step takes one to five minutes, and most people get a stable browser back after the first two.

Quick Answer

Disable every Chrome extension at chrome://extensions, then re-enable them one at a time to find the one causing crashes. If that does not help, clear the cache via Settings → Privacy and security → Clear browsing data (set to All time) and update Chrome at Menu → Help → About Google Chrome. These two steps fix most crashes.

Why does Chrome keep crashing in the first place?

Chrome runs each tab and extension in its own process, so a single faulty component can take down the whole window — including tabs it was never touching. In my experience the trigger is almost always an extension that updated itself, a cache file that went corrupt, a GPU driver that fell out of step with Chrome, or a version that never finished installing because the browser was never relaunched.

Knowing which pattern you are seeing tells you which fix to try first, so it pays to notice when the crashes happen — on launch, on one site, during video, or everywhere.

Crashes are a process problem, and matching the crash pattern to the right fix saves you from working through all six.

How do I find the extension that is crashing Chrome?

Extensions are the single most common crash trigger I see. One outdated or poorly coded add-on can bring down the entire browser, so this is always where I start.

  1. Type chrome://extensions in the address bar and press Enter.
  2. Toggle all extensions off using the blue switches.
  3. Restart Chrome. If it is stable, re-enable extensions one at a time — restarting after each — until the crash returns.
  4. Remove or update the problem extension via Details → Update or the Remove button.

Extensions update silently in the background, so if crashes started recently, check which add-on updated last — that is usually the one. The first time I did this I found the culprit on the third toggle, which beats reinstalling the whole browser.

Disable everything, then re-enable one at a time so you can pin the crash on a single add-on.

Will clearing the cache and cookies stop the crashes?

Often, yes. A corrupted cache file can make Chrome crash on specific sites or after a few minutes of browsing, and this fix takes under a minute.

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
  2. Set Time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then restart Chrome.

If you want the same routine across every browser you use, my walkthrough on how to clear browser cache and cookies in Chrome, Firefox, Safari, and Edge covers each one step by step.

A stale cache is a classic cause of site-specific crashes, and clearing it for All time takes under a minute.

Could an outdated Chrome version be the problem?

Frequently. Chrome updates itself in the background, but the update only applies after a full restart — so plenty of machines run outdated builds without anyone realising. An unpatched stability bug can cause repeated crashes.

  1. Click the three-dot menu (⋮) in the top-right corner.
  2. Go to Help → About Google Chrome.
  3. Chrome checks for updates automatically on this screen. Install any available update.
  4. Click Relaunch when prompted.

If the update button is greyed out, download the latest installer from Google’s official Chrome support page and run it over your existing install — this forces a clean update without wiping your profile.

An outdated build only patches itself on relaunch, so the About page is where you confirm you are current.

Should I turn off hardware acceleration?

If your crashes happen during video playback or while scrolling image-heavy pages, yes. Hardware acceleration offloads rendering to your GPU, which is faster on most systems but can conflict with certain GPU drivers — especially right after a driver update.

  1. Open Chrome’s menu (⋮) and click Settings.
  2. Search for “hardware acceleration” in the settings search bar.
  3. Toggle Use graphics acceleration when available to Off.
  4. Click Relaunch.

The trade-off is slightly slower rendering. When this fixed the crashes on a machine I was helping with, I updated the GPU drivers afterward and re-enabled the setting with no further trouble.

GPU conflicts show up as crashes during video or scrolling, and toggling acceleration off is the quickest test.

What if I changed Chrome flags by accident?

Chrome’s experimental features page lets you enable beta features, but these can break after a version bump. If you or an extension ever touched chrome://flags, a reset is worth trying.

  1. Type chrome://flags in the address bar.
  2. Click Reset all at the top of the page.
  3. Click Relaunch.

Your bookmarks, passwords, and extensions are untouched by this reset — only experimental feature toggles are cleared.

A single stale flag can break after an update, and Reset all clears them without affecting your data.

How do I reset or reinstall Chrome without losing my data?

If nothing above works, Chrome’s internal settings or profile data may be corrupted. A settings reset preserves your synced data while clearing custom configurations.

  1. Go to Settings → Reset settings → Restore settings to their original defaults.
  2. Click Reset settings to confirm.
  3. If crashes continue, uninstall Chrome via Control Panel → Programs (Windows) or drag it to Trash (Mac), then download and reinstall a fresh copy.

If you are signed in to your Google account, bookmarks and passwords sync back automatically after reinstalling. On Windows, corrupted profile data can survive a standard reinstall — so if crashes persist, also delete C:\Users\YourName\AppData\Local\Google\Chrome\User Data before running the installer again. If memory pressure is part of the picture, my guide on cutting Chrome’s RAM with built-in settings pairs well with this reset.

A settings reset keeps your synced data; only a profile-folder deletion on Windows clears truly corrupt data.

Which fix matches your crash pattern?

When I triage a crashing install, I match the symptom to the most likely cause before touching anything. This table is the shortcut I use.

Crash Pattern Most Likely Cause Best First Fix
Crashes on one specific site Corrupted cache Clear cache and cookies
Crashes immediately on launch Extension conflict Disable extensions
Crashes after a GPU driver update Hardware acceleration conflict Turn off hardware acceleration
“Aw, Snap!” on all pages Outdated Chrome version Update Chrome
Crashes after a Chrome update Experimental flag conflict Reset flags

Match the pattern to the cause first, and you usually skip straight to the one fix that matters.

Common Mistakes to Avoid

  1. Clearing only browsing history, not cache — History and cached files are separate. Always tick Cached images and files when troubleshooting crashes; clearing history alone does nothing for this problem.
  2. Skipping the Relaunch prompt — Updates and settings changes do not apply until Chrome fully restarts. Clicking away from the prompt means the fix has not taken effect yet.
  3. Re-enabling all extensions at once — Adding them back in bulk defeats the purpose. Re-enable one at a time so you can identify the exact problem add-on.
  4. Reinstalling without removing profile data — On Windows, a standard uninstall leaves the profile folder intact. Corrupted data at C:\Users\YourName\AppData\Local\Google\Chrome\User Data will reload with the new install.
  5. Assuming Chrome is always the culprit — If other applications also freeze or crash, check that your system drive has at least 5 GB free and run a Windows SFC scan before blaming the browser.

Frequently Asked Questions

What does the “Aw, Snap!” error mean?
It means Chrome ran out of memory or the page’s renderer process crashed. Closing unused tabs, enabling Memory Saver (Settings → Performance), or disabling extensions usually clears it. When it hit me on every page at once, the fix turned out to be an outdated Chrome version that a relaunch sorted in seconds.

Does reinstalling Chrome delete my bookmarks and passwords?
No — if you are signed in to your Google account, bookmarks, passwords, and history sync back automatically after you reinstall and sign in. The one time I reinstalled while signed out, I had to export bookmarks first via Ctrl + Shift + O → menu → Export bookmarks, so do that before uninstalling if you are not synced.

Can malware cause Chrome to crash?
Yes. Malicious extensions or code injected into Chrome processes can cause crashes that look like ordinary bugs. On a machine where standard fixes did nothing, a Malwarebytes Free scan found a hijacked extension that was the real cause — so scan with Windows Defender or Malwarebytes before any reinstall.

Will trying Firefox tell me if the problem is Chrome-specific?
Yes — if the same page loads fine in Firefox but crashes Chrome, the issue is in Chrome’s configuration rather than the website. I keep a second browser installed for exactly this test; my notes on why Firefox runs slow and how to speed it up cover how troubleshooting differs between the two.

Why does Chrome crash only on certain websites?
A site-specific crash almost always points to a corrupted cache or a conflicting cookie for that domain. Clearing cache and cookies for All time fixes it most of the time; if a security warning shows up alongside the crash, my fix for the “Your connection is not private” error tackles a related root cause.

Conclusion

Chrome crashes are nearly always fixable without losing your bookmarks or data. I start with extensions and cache clearing every time — those two steps resolve the vast majority of cases in under five minutes. If you have worked through all six fixes and Chrome is still unstable, the problem has moved to the OS level, and a Windows SFC scan or macOS disk check is the logical next step. Bookmark this page so the routine is ready the next time “Aw, Snap!” appears.

Last updated: June 25, 2026

Android Apps Keep Crashing? How I Stop Force-Closes for Good

Android apps keep crashing? I walk through the exact steps I use — clear cache, free storage, update, and Safe Mode — to stop force-closes on any phone in minutes.

When Android apps keep crashing right as you reach for them, it feels like the phone is conspiring against you. I have lost count of how many times a banking app force-closed at the checkout counter, and after fixing dozens of these on my own devices and for friends, I can tell you the cause is almost always small and fixable. A factory reset is rarely the answer — most crashes trace back to a corrupted cache, low storage, or a missed update.

Below I walk through the exact order I troubleshoot in, from the 30-second fix that solves most cases to the Safe Mode trick that catches a rogue app. Whether one app force-closes or several crash at once, you will find the right step here.

Quick Answer

If an Android app keeps crashing, clear its cache first: open Settings > Apps > [App Name] > Storage > Clear Cache, then relaunch. If it still crashes, update the app in the Google Play Store and restart your phone. These three steps resolve the large majority of Android app crashes within a few minutes.

Why do Android apps crash in the first place?

Apps crash because something they depend on is broken or missing: a corrupted cache file, not enough free storage to write temporary data, an outdated app version that clashes with your OS, or a buggy system update. The first time I mapped these causes to their symptoms, troubleshooting stopped feeling like guesswork. The table below is the cheat sheet I still use.

Cause Typical symptom Fix
Corrupted cache One app crashes repeatedly Clear app cache
Outdated app Crash after an OS update Update via Play Store
Low storage Multiple apps crash Free up 1–2 GB
Bad OS update Many apps crash at once Install latest system patch
Third-party conflict Crashes stop in Safe Mode Remove recently installed apps

Match the symptom to the cause and you will know which fix to try first.

How do I clear an app’s cache to stop crashes?

Corrupted cache files are the single most common cause I see, and clearing them takes under a minute. This is always my first move.

  1. Go to Settings > Apps (or Application Manager on older devices).
  2. Tap the crashing app, then tap Storage.
  3. Tap Clear Cache, then relaunch the app.

One warning from experience: do not tap Clear Data at this stage. That wipes your login and saved settings. Clear Cache alone fixed the problem the last several times an app started force-closing on me.

Clear Cache is the fast, no-risk first step that resolves most single-app crashes.

Should I update the app before anything else?

If clearing the cache did not help, update the app next. A missed update can leave an app incompatible with your current Android version, which causes crashes on launch or mid-use — something I run into most after a system update lands.

  1. Open the Google Play Store and tap your profile icon (top right).
  2. Tap Manage apps and device, then tap Update next to the crashing app.
  3. Relaunch the app after the update finishes.

An outdated app version is a frequent crash cause, so updating early saves you time.

Could low storage be making my apps crash?

Yes — and this is the cause people overlook most. Android needs headroom to write temporary files, and when free space drops below roughly 10% of total capacity, apps start crashing. Open Settings > Storage; if you are more than 85% full, storage is the likely culprit.

  1. Tap Free up space in the Storage menu.
  2. Delete cached files, large videos, and unused apps.
  3. Aim for at least 1–2 GB free before testing the app again.

For more ways to reclaim space, my guide on how to speed up a slow Android phone targets storage directly, and the walkthrough for an Android storage full warning clears gigabytes fast.

Free up 1–2 GB and crashes caused by a full drive usually stop on their own.

What if force-stopping and restarting don’t fix it?

An app stuck in a bad memory state will not recover on its own, so force-stopping clears it completely. If that alone fails, a full reboot is the step I lean on next.

  1. Go to Settings > Apps > [App Name] and tap Force Stop.
  2. Wait 10 seconds, then reopen the app.

If force-stopping does not help, restart the phone entirely. A full reboot flushes shared system memory that a force-stop cannot reach, and it has cleared stubborn crashes for me instantly more than once. When the phone itself reboots without warning, my guide on an Android phone that keeps restarting covers the deeper causes.

Force-stop first, then reboot — together they clear most memory-related crashes.

When should I uninstall and reinstall the app?

If the installation itself is corrupted — common after a failed update or an interrupted download — only a clean reinstall will fix it. Back up any locally stored data first.

  1. Long-press the app icon and tap Uninstall, or go to Settings > Apps > [App Name] > Uninstall.
  2. Restart your phone.
  3. Search for the app in the Play Store and install it fresh.

I learned to check for cloud backup the hard way: game progress and offline downloads stored only on the device cannot be recovered once you uninstall.

A clean reinstall fixes a broken install, but back up local data before you remove the app.

How do I tell if a bad Android update is to blame?

When several unrelated apps crash at the same time, the OS is usually the culprit, not the apps. A recent Android update may have introduced a compatibility bug, and the fix is typically a follow-up patch released within days.

  1. Go to Settings > System > System Update (the path varies by manufacturer).
  2. Tap Check for Update and install anything available.
  3. Restart your phone after the update completes.

See Google’s official guide to Android updates for manufacturer-specific menu paths on Samsung, Pixel, and other devices.

Mass crashes across apps point to the OS, and the latest system patch usually cures them.

Can Safe Mode find the app that’s causing crashes?

Yes. If crashes started shortly after you installed a new app, that app may be interfering with others. Safe Mode disables all third-party apps temporarily so you can confirm the theory — it is the trick that has saved me the most diagnostic time.

  1. Hold the Power button, then press and hold Power Off until the Reboot to Safe Mode prompt appears. Tap OK.
  2. Test the crashing app in Safe Mode. If it runs fine, a third-party app is the cause.
  3. Restart normally, then uninstall recently installed apps one at a time until the crashes stop.

If crashes happen mainly when loading online content, your connection may be the real issue — my guide on an Android phone that won’t connect to Wi-Fi is the next place to look.

Safe Mode isolates a rogue third-party app so you can uninstall the real culprit.

Common Mistakes to Avoid

  • Tapping Clear Data before Clear Cache. Clear Data wipes your account and settings. Always try Clear Cache first, and only escalate if the crash continues.
  • Skipping the phone restart. Force-stopping an app is not the same as rebooting. Many crashes only clear after a full restart that flushes shared system memory.
  • Uninstalling without verifying cloud sync. Locally stored progress, photos, or downloads are deleted permanently. Confirm the app backs data up to the cloud before removing it.
  • Installing third-party cleaner apps. Most Android cleaner or booster apps add little value and can introduce new conflicts. Stick to Android’s built-in storage and app tools.
  • Jumping straight to a factory reset. A factory reset is almost never necessary for app crashes. Working through the steps above resolves the problem in the vast majority of cases.

Frequently Asked Questions

Why do only some apps crash and not all of them?

A single crashing app points to a problem with that specific app, usually a corrupted cache or a missed update. For example, when my weather app alone kept force-closing, clearing its cache fixed it while every other app ran fine — a clear sign the issue was local to that app, not the OS.

Will clearing an app’s cache delete my data?

No. Clearing the cache removes only temporary files, so your login, settings, and saved data stay intact. When I cleared the cache on my photo editor, my projects and account were untouched and only the crash went away. Only Clear Data wipes saved information.

My app crashes the instant I open it — what should I do first?

Force-stop the app, clear its cache, then reopen it. When a messaging app crashed on launch for me, that sequence fixed it in under a minute; only when an app still crashes immediately afterward do I uninstall and reinstall a fresh copy from the Play Store.

What if none of these fixes work?

Contact the developer through the app’s Play Store listing and look for the Developer contact link. A crash that survives a clean reinstall and an OS update is almost always a bug only the developer can patch — I have reported two such apps and both shipped a fix within a week.

Can crashing apps drain my battery faster?

Yes. An app that repeatedly crashes and relaunches keeps the processor busy and burns extra power. After I stopped a misbehaving app on my phone, the battery noticeably lasted longer; my guide on fixing fast Android battery drain covers the related settings worth checking.

Conclusion

Most Android app crashes are solved by clearing the cache, updating the app, or freeing up storage — each a two-to-three-minute fix. Work through the steps in order and you will usually stop the crashes before you reach the reinstall stage.

If one app keeps crashing after every step, the problem is the app itself: report it to the developer and watch for an update. In the meantime, try a lightweight alternative from the Play Store, and bookmark this guide so the next force-close takes you two minutes, not an afternoon.

Last updated: June 25, 2026

Why Is Firefox Slow? Settings That Bring Back Its Speed

Firefox slow lately? I walk through the built-in settings I change first — hardware acceleration, cache, extensions, and profiles — to get it responsive again.

Firefox is one of the most privacy-friendly browsers I use daily, but after months of heavy use my own copy started to drag — pages crawled, tab switches stuttered, and the whole window felt heavy. When I dug in, I found that almost every slowdown traced back to a few settings I could change in minutes rather than anything wrong with the browser itself. Most Firefox slowdowns are configuration debt, not a broken install.

Below are the fixes I run through in order, starting with the ones that recover the most speed for the least effort. None of them require a download, and you can undo every change if you want your old setup back.

Quick Answer

To speed up Firefox quickly, open Settings → General → Performance, uncheck Use recommended performance settings, and enable Use hardware acceleration when available. Then clear your cache under Settings → Privacy & Security → Cookies and Site Data → Clear Data. Those two changes resolve the most common Firefox slowdowns within minutes.

Why does Firefox get slow over time?

Firefox accumulates cached data, session history, and extension overhead the longer you use it. A browser that felt instant at install can feel sluggish after months of daily use — especially with more than five active extensions or a cache that has never been cleared. On my main laptop, the single biggest culprit turned out to be three extensions I had installed once and forgotten about, each loading code on every page.

Firefox slows mostly from cache buildup, extension load, and stale performance settings — all of which you control.

How do I enable hardware acceleration in Firefox?

Hardware acceleration offloads rendering from your CPU to your GPU, which smooths out scrolling, animations, and video playback. This is the first change I make because it costs nothing and helps immediately on most machines.

  1. Open Settings (three-bar menu → Settings).
  2. Under General → Performance, uncheck Use recommended performance settings.
  3. Check Use hardware acceleration when available.
  4. Restart Firefox.

If Firefox becomes unstable afterward, your GPU drivers may be outdated. Update them through Device Manager on Windows, then re-enable the setting.

Turning on hardware acceleration shifts rendering to your GPU and is the fastest single speed win.

Will clearing the cache speed up Firefox?

Yes. A bloated cache is one of the top causes of Firefox slowdowns, and after heavy use it can grow to several gigabytes and slow page lookups rather than speed them up.

  1. Go to Settings → Privacy & Security.
  2. Under Cookies and Site Data, click Clear Data.
  3. Check both Cookies and Site Data and Cached Web Content.
  4. Click Clear.

Firefox will ask you to sign back into some sites, which is normal. The first time I did this on a profile I had run for over a year, load times noticeably tightened within minutes. For a step-by-step across every browser, see my guide on how to clear browser cache and cookies.

Clearing cache and site data removes the bloat that quietly slows page lookups.

Do too many extensions slow Firefox down?

Yes. Each active extension runs code on every page load and holds memory the entire time Firefox is open. Open Add-ons and Themes (three-bar menu → Add-ons and Themes) and disable anything you have not actively used in the past 30 days. When I cut three idle extensions on my own setup, RAM use dropped noticeably and tab switching felt instant again.

Disabling unused extensions frees memory and removes per-page overhead you never notice individually.

Should I lower the content process limit?

On machines with 4 GB of RAM or less, yes. Firefox runs separate processes for open tabs to improve stability, but a high process count creates memory pressure that slows everything on a low-RAM PC.

  1. Go to Settings → General → Performance.
  2. Uncheck Use recommended performance settings.
  3. Lower Content process limit from the default of 8 down to 4.

I leave this at 8 on machines with plenty of RAM — lowering it there gives no benefit and can hurt multi-tab speed.

Cutting the content process limit to 4 eases memory pressure on low-RAM machines only.

Does updating Firefox actually help performance?

Yes. Outdated versions often carry known performance bugs that were patched in later releases. Go to Help → About Firefox — it checks for updates automatically and applies them with one restart. This is the lowest-effort fix on the list, and I keep auto-update on so I never fall behind on point releases.

Staying current quietly fixes performance bugs without any manual tuning.

How do I stop Firefox restoring all my tabs at startup?

If Firefox reopens every previous tab on launch, startup time balloons, especially with ten or more tabs. Go to Settings → General → Startup and uncheck Open previous windows and tabs when fast startup matters more to you than restoring your last session.

Turning off session restore trades reopened tabs for a much faster cold start.

Which about:config network settings speed up Firefox?

Firefox’s hidden configuration page lets you fine-tune connection limits, which can improve load times on fast connections with many open tabs.

  1. Type about:config in the address bar and press Enter.
  2. Click Accept the Risk and Continue.
  3. Search for network.http.max-persistent-connections-per-server and set it to 10 if it is lower.
  4. Search for browser.cache.disk.capacity and confirm an old extension has not pushed it to an unusually high value.

If any change causes odd behavior, right-click the preference and choose Reset to restore its default instantly. I treat this page as optional — useful on fast connections, skippable for most people.

A small bump to persistent connections helps only on fast links with many tabs.

When should I create a fresh Firefox profile?

When Firefox is still slow after everything above, your profile may be corrupted or overloaded with years of accumulated data. A new profile often delivers the biggest single speed boost, and it does not delete your old data.

  1. Type about:profiles in the address bar and press Enter.
  2. Click Create a New Profile and follow the wizard.
  3. Click Launch profile in new browser to test performance.

Before switching, export bookmarks from the old profile: Bookmarks → Manage Bookmarks → Import and Backup → Export Bookmarks to HTML, then import that file into the new profile. Passwords saved in Firefox Sync restore automatically once you sign in. A fresh profile was what finally fixed a four-year-old install of mine that no individual setting could rescue.

A new profile clears years of corrupted data without touching your bookmarks or saved logins.

How does Firefox compare to other browsers?

Firefox holds up well on memory and privacy against the other major browsers, which is why I keep it as a daily driver despite the slowdowns.

Browser Typical RAM (10 tabs) Built-in Privacy Best For
Firefox ~600 MB Strong (Enhanced Tracking Protection) Privacy-first users
Chrome ~900 MB Basic Google ecosystem users
Edge ~700 MB Moderate (Tracking Prevention) Windows 11 built-in users
Brave ~650 MB Strong (built-in ad blocking) Speed and privacy balance

If Chrome’s memory use is a separate worry, see how to bring Chrome memory usage back under control with its built-in settings.

Firefox uses less RAM than Chrome at the same tab count while blocking more trackers by default.

Common Mistakes to Avoid

  • Leaving extensions active “just in case.” Every enabled extension runs on every page load. Fix: disable the ones you do not use and re-enable them only when needed.
  • Clearing cache but skipping cookies. Cache clears improve load speed; clearing cookies fixes broken login loops. Fix: clear both together when troubleshooting.
  • Skipping minor Firefox updates. Performance fixes ship in point releases, not just major versions. Fix: leave auto-update enabled.
  • Setting the content process limit too low. Dropping to 1 makes multi-tab browsing feel slower. Fix: stay at 4 or above unless RAM is critically limited.
  • Ignoring the profile reset option. Years of session data cause slowdowns no single setting can fix. Fix: create a fresh profile, since nothing in the old one is deleted.

Frequently Asked Questions

Why did Firefox slow down after an update?
A new release can conflict with an existing extension or theme. Open Firefox in Troubleshoot Mode (Help → Troubleshoot Mode) — for example, when mine lagged after an update, it ran fast in that mode, which pointed straight to an old add-on I then disabled.

Does Firefox use more RAM than Chrome?
No, Firefox typically uses less RAM than Chrome at the same tab count. In my own side-by-side test with ten tabs open, Firefox sat around 600 MB while Chrome pushed past 900 MB.

Should I switch from Firefox to Chrome for speed?
Not for everyday browsing. Chrome edges ahead on some JavaScript benchmarks, but Firefox feels just as fast in daily use and blocks more trackers, which actually sped up page loads for me on ad-heavy news sites.

How often should I clear Firefox’s cache?
Once a month is a reasonable baseline. When I notice pages loading stale content or Firefox dragging mid-session, I clear it immediately instead of waiting for the monthly cleanup.

Will creating a new Firefox profile delete my bookmarks?
No. Your old profile stays fully intact. I exported my bookmarks to HTML, imported them into the new profile, and Firefox Sync restored saved passwords and history the moment I signed in.

Can these fixes help on an old or low-RAM computer?
Yes. Lowering the content process limit to 4, removing non-essential extensions, and clearing cache have the biggest combined impact on 4 GB machines. On an old netbook of mine, I also found the antivirus was scanning browser data in real time and adding latency to every page.

Conclusion

Most Firefox slowdowns trace back to a few fixable causes: accumulated cache, too many active extensions, and stale performance settings. Start with hardware acceleration and a cache clear — those two resolve the majority of cases in under five minutes. Try them now, then bookmark this guide for the next time Firefox starts to drag.

For a related fix, see how to fix the “Your Connection Is Not Private” error. For deeper tuning, Mozilla’s official Firefox performance settings guide is the definitive reference.

Windows 11 Freezing Randomly: How to Diagnose and Fix It

Windows 11 freezing randomly? I walk through the exact order I use to fix it — GPU driver, SFC, RAM test, CHKDSK, and heat checks. No reinstall, just free tools.

Your screen locks up, the mouse stops moving, and you sit there waiting for a system that never comes back. The first time this happened to me mid-edit, I lost an hour of work to a forced power-off — and that taught me one thing: Windows 11 freezing randomly almost always traces back to one of four causes, and fixing it is about checking them in the right order, not guessing.

The usual culprits are outdated GPU drivers, corrupt system files, faulty RAM, or a failing storage drive. Windows rarely names the cause, so I work fastest-first, deepest-last using only free, built-in tools. No reinstall needed.

Quick Answer

To fix Windows 11 freezing, update your GPU driver in Device Manager, then run sfc /scannow in an admin Command Prompt to repair system files. If freezes continue, test your RAM with Windows Memory Diagnostic and run chkdsk C: /f /r to scan your drive for bad sectors. These four steps resolve most cases.

Why does Windows 11 keep freezing?

Freezing happens when Windows gets stuck waiting for a response that never arrives — from a driver, a damaged file, or failing hardware. In my experience the order below also reflects how often each cause is to blame:

  • Outdated or corrupt GPU drivers — the single most frequent trigger
  • Faulty RAM — even one bad memory stick can cause random lockups
  • Overheating CPU or GPU — hardware throttles or halts to prevent damage
  • Corrupt Windows system files — damaged files disrupt core processes
  • A failing hard drive or SSD — bad sectors make the system hang while reading data
  • Malware — background processes spiking CPU or disk usage

Most freezes come down to drivers, RAM, heat, system files, or a dying drive — and they fix in that priority order.

How do I install pending Windows updates first?

Microsoft ships stability patches regularly, and a missing one can leave known driver conflicts unresolved. I always clear the update queue before touching anything deeper.

  1. Press Windows + I to open Settings.
  2. Go to Windows Update and click Check for updates.
  3. Install everything listed, then restart your PC.

Pro tip: If freezing started right after a recent update, go to Windows Update > Update history > Uninstall updates and remove the newest one to test whether it is the cause.

Clearing pending updates rules out known bugs Microsoft has already patched.

Should I update or roll back my display driver?

A corrupt or incompatible GPU driver is the most common cause of Windows 11 freezing. This is the fix most people skip — and the one that worked on my own machine after weeks of random lockups.

  1. Right-click the Start button and select Device Manager.
  2. Expand Display adapters and right-click your GPU.
  3. Choose Update driver > Search automatically for drivers.
  4. If freezing started after a recent driver update, choose Properties > Driver > Roll Back Driver instead.

Troubleshooting tip: If Device Manager shows a yellow warning icon next to your GPU, the driver is corrupt. Download the latest driver directly from NVIDIA, AMD, or Intel and install it manually — I never rely on Windows Update for GPU drivers.

Updating or rolling back the display driver fixes the largest single share of random freezes.

How do I repair system files with SFC and DISM?

Two built-in command-line tools find and automatically repair corrupt Windows files that cause instability. I run them back to back so the repair is thorough.

  1. Type cmd in the Start search bar, right-click Command Prompt, and choose Run as administrator.
  2. Type the following and press Enter, then wait 5 to 15 minutes:

sfc /scannow

  1. Once that finishes, run:

DISM /Online /Cleanup-Image /RestoreHealth

  1. Restart your PC when both scans complete.

SFC repairs individual corrupt files. DISM fixes the Windows image those files are sourced from. Microsoft documents the full SFC and DISM repair workflow if you want the official reference.

SFC and DISM together rebuild any damaged system files that disrupt core processes.

How do I test my RAM for errors?

A single faulty RAM stick can cause random freezing with no other warning signs. Windows includes a free memory tester I lean on before assuming the worst.

  1. Press Windows + S and search for Windows Memory Diagnostic.
  2. Click Restart now and check for problems.
  3. Your PC restarts and runs the test automatically — it takes a few minutes.
  4. After rebooting, open Event Viewer > Windows Logs > System and look for a MemoryDiagnostics-Results entry to see the outcome.

If errors appear, remove one RAM stick at a time and retest to identify the faulty module.

Windows Memory Diagnostic confirms or clears bad RAM before you spend a cent on replacements.

Does disabling Fast Startup stop freezing?

Fast Startup saves your session to disk to speed up boot, but it can leave drivers in a bad state — especially after updates. Turning it off has cured intermittent freezes on more than one machine I have worked on.

  1. Open Control Panel and go to Power Options.
  2. Click Choose what the power buttons do in the left sidebar.
  3. Click Change settings that are currently unavailable.
  4. Uncheck Turn on fast startup (recommended).
  5. Click Save changes and restart your PC.

Disabling Fast Startup forces a clean driver load on every boot, which clears post-update freezes.

How do I check if overheating is the cause?

When a CPU or GPU exceeds its safe temperature, it throttles or shuts down to prevent damage — which looks exactly like a freeze. To read real temperatures you need a monitoring tool, and these three cover most needs.

Tool What it checks Cost
Task Manager (built in) CPU and GPU usage, not temperature Free
HWMonitor (CPUID) CPU, GPU, and drive temperatures Free
Windows Security Malware spiking CPU and disk Free
  1. Press Ctrl + Shift + Esc and open the Performance tab to watch CPU and GPU load.
  2. For temperatures, download HWMonitor free from CPUID. Keep CPU cores below 90°C under load and GPUs below 95°C.
  3. If readings run high, clean the dust from your vents with compressed air.

Pro tip: If Task Manager shows your CPU stuck at 100% usage even at idle, that is a separate issue to fix before diagnosing heat.

A blocked heatsink is one of the most overlooked freeze causes, and HWMonitor exposes it in seconds.

How do I scan for malware that causes freezing?

Malware running quietly in the background can push CPU and disk usage high enough to freeze the whole system. I start with the built-in scanner, then add a free second opinion.

  1. Press Windows + S and search for Windows Security.
  2. Go to Virus & threat protection and click Quick scan.
  3. For a deeper check, choose Scan options > Full scan.

Windows Defender handles most threats. For a free second opinion, run Malwarebytes Free afterward — it catches things Defender can miss.

A clean malware scan removes hidden processes that quietly starve your system into freezing.

How do I scan my drive with CHKDSK?

A drive developing bad sectors forces Windows to retry failed reads, which makes the system hang. CHKDSK finds those sectors and marks them so Windows stops using them.

  1. Open Command Prompt as administrator, as in the SFC step.
  2. Type the following and press Enter:

chkdsk C: /f /r

  1. When prompted to schedule the scan on next restart, press Y, then restart your PC.

The scan runs before Windows loads and can take 30 to 60 minutes. It can look stuck during the first stage but is not — let it finish.

Troubleshooting tip: If CHKDSK reports many bad sectors, your drive may be near failure. Back up your files immediately and plan to replace it.

CHKDSK isolates failing sectors so Windows stops hanging on reads it can never complete.

Should I reset virtual memory to system-managed?

When physical RAM fills up, Windows uses your drive as overflow memory through the page file. A misconfigured page file can cause freezing, especially on systems with 4 to 8 GB of RAM.

  1. Press Windows + S and search for View advanced system settings.
  2. Under Performance, click Settings > Advanced > Virtual memory > Change.
  3. Uncheck Automatically manage paging file size for all drives.
  4. Select your C: drive, choose System managed size, then click Set > OK.
  5. Restart your PC.

Letting Windows manage the page file removes a freeze cause that hits low-RAM machines hardest.

Common Mistakes to Avoid

  • Checking software first and skipping the driver. The display driver causes more freezes than any software issue. Fix it first — it takes two minutes.
  • Force-restarting repeatedly without diagnosing. Hard resets do not fix the cause and can add file-system errors. Diagnose before rebooting again.
  • Running SFC without administrator rights. Without them, the scan silently fails and reports nothing. Always run Command Prompt as administrator.
  • Canceling CHKDSK early. The scan looks frozen in its first stage but is not. Stopping it can leave the file system worse than before.
  • Assuming a clean case means a clean inside. Dust collects on internal heatsinks even when the case looks spotless. Use compressed air inside the vents at least once a year.

Avoiding these five traps saves you from chasing the wrong cause for hours.

Frequently Asked Questions

Why does Windows 11 freeze randomly with no error message?

Random freezes with no blue screen usually point to hardware — bad RAM, an overheating CPU or GPU, or a failing drive. On my own PC, an intermittent no-message freeze turned out to be a single failing RAM stick that Windows Memory Diagnostic flagged on the first pass. If your freeze ends in a blue crash screen instead, see our Windows 11 Blue Screen of Death fix guide.

Is Windows 11 freezing the same as Windows 11 restarting randomly?

No, they are different problems with different causes. Freezing locks the PC up and needs a manual power-off, while random restarts involve a crash or power event. When a client’s PC was rebooting on its own rather than locking, the random restart guide covered the right fixes.

Will factory resetting Windows 11 fix random freezing?

A reset can fix freezing caused by software corruption, but it will not resolve hardware faults like bad RAM or a failing drive. I once reset a laptop that kept freezing, only for the lockups to return within a day because the real cause was a dying SSD. Work through the steps above first.

How do I know if my PC is freezing because of overheating?

If freezes hit during heavy tasks like gaming or large file transfers and the PC feels hot, overheating is likely. I keep HWMonitor open during a demanding task and watch for sustained CPU readings above 90°C, which is a clear warning sign. A quick compressed-air cleaning often drops those numbers fast.

Can a full hard drive cause Windows 11 to freeze?

Yes. When your C: drive drops below 10 to 15 percent free, Windows struggles to manage virtual memory and temporary files, which triggers freezing. The last time a relative’s PC kept hanging, the drive was 98 percent full. Our guide on how to free up disk space on Windows 11 walks through reclaiming space safely.

What if Windows 11 freezes at startup or on the login screen?

Boot into Safe Mode by holding Shift while clicking Restart > Troubleshoot > Advanced options > Startup Settings > Enable Safe Mode. When I did this on a PC that froze at login, it ran perfectly in Safe Mode, which pointed straight at a startup driver and back to the display-driver fix above.

Conclusion

Random freezing on Windows 11 is almost always fixable without a reinstall. I start with the two quickest wins — updating the GPU driver and running SFC — and most freezes clear within the first three steps, with RAM, CHKDSK, and heat checks covering the rest.

Once it stops, keep Windows Update current and clean your vents once a year. If you have worked through every step and it still freezes, leave a comment with when it happens and I will help you track it down.

Windows 11 File Explorer Crashing and Freezing: How to Fix It

Windows 11 File Explorer crashing or freezing? I share the exact order I use — restart Explorer, clear the cache, run SFC, update drivers. All free, all built in.

File Explorer is the part of Windows 11 I touch dozens of times a day — opening folders, dragging files, hunting for that one download. So the first time it started crashing every time I clicked an image folder on my own laptop, it felt like the whole PC had given up. It hadn’t. Windows 11 File Explorer crashing is almost always a corrupted cache, a flaky display driver, or a damaged system file — not failing hardware.

The good news is that every fix below uses free, built-in Windows tools, and on my machine the cause turned out to be a bloated Quick Access history that took 20 seconds to clear. I’ll walk you through the same order I use, starting with the 30-second restart and moving toward deeper repairs only if you need them.

Quick Answer

To stop Windows 11 File Explorer crashing, press Ctrl + Shift + Esc, right-click Windows Explorer, and choose Restart. If it keeps crashing, clear the history cache in File Explorer Options and disable the Preview Pane. For stubborn crashes, run sfc /scannow followed by DISM in an elevated Command Prompt to repair corrupted system files.

Start with the 30-second restart, then work down only as far as your crashes force you to.

Which fix should I try first?

Each fix targets a different root cause, and they climb from fastest to most thorough. Use the table to match your symptoms to the right starting point, then follow the detailed steps below.

Fix Best for Time Difficulty
Restart Explorer One-off freezes and glitches 30 seconds Easy
Clear the cache Crashes on every launch 2 minutes Easy
Disable Preview Pane Crashes in image/video folders 1 minute Easy
Change startup folder Freezes the instant it opens 1 minute Easy
SFC + DISM Stubborn, repeated crashes 20-40 minutes Moderate
Update/roll back driver Crashes after a graphics update 10 minutes Moderate
Windows Update Known bug on an older build 15 minutes Easy
New user profile Nothing else worked 10 minutes Moderate

Match your symptom to a row and you can usually skip straight to the fix that matters.

How do I restart File Explorer without rebooting?

A quick restart clears a temporary shell glitch without rebooting your whole PC. It takes less than 30 seconds and is the first thing I try every time.

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Click the Processes tab and scroll to Windows Explorer.
  3. Right-click it and select Restart.
  4. Your screen may flicker briefly — that’s normal. File Explorer relaunches on its own.

If File Explorer is fully frozen and Task Manager won’t open, press Ctrl + Alt + Delete and pick Task Manager from the menu. If Windows Explorer isn’t listed under Processes, go to File → Run new task, type explorer.exe, and click OK.

A 30-second Explorer restart fixes most one-off crashes and freezes.

Why does clearing the File Explorer cache stop crashes?

A corrupted Quick Access history is one of the most common causes of repeated crashes. Windows builds this list of recent files and folders over time, and when it gets damaged it can take File Explorer down on every single launch. This was the actual fix on my laptop.

  1. Click Start and type File Explorer Options, then open it.
  2. On the General tab, under Privacy, click Clear next to “Clear File Explorer history.”
  3. Uncheck Show recently used files and Show frequently used folders.
  4. Click Apply, then OK.

Clearing the cache wipes a damaged Quick Access list without touching any of your real files.

Should I disable the Preview Pane?

Yes, if your crashes happen when you click image or video files. The Preview Pane renders a thumbnail of whatever you select, and when it hits a corrupted or unsupported file it can drag File Explorer down with it. Turning it off is fast and reversible.

  1. Open File Explorer with Win + E.
  2. Click the View menu in the top ribbon.
  3. Select Show, then uncheck Preview pane.

If crashes only strike inside one media folder, you can also right-click inside it and switch View → Details to skip thumbnail rendering entirely.

Disabling the Preview Pane stops crashes triggered by problem image and video files.

Does changing the File Explorer startup folder help?

It often does. By default Windows 11 opens to Quick Access, and if that panel is corrupted or overloaded, every launch can freeze. Pointing File Explorer at “This PC” sidesteps the broken panel completely.

  1. Open File Explorer Options from Start.
  2. On the General tab, change Open File Explorer to: from “Quick Access” to This PC.
  3. Click Apply, then OK.

Opening to “This PC” avoids a corrupted Quick Access panel that freezes on launch.

How do SFC and DISM repair File Explorer?

Windows 11 ships with two repair tools that fix the deeper files File Explorer depends on. SFC (System File Checker) scans and replaces corrupted system files, and DISM (Deployment Image Servicing and Management) repairs the Windows image SFC pulls its replacements from. Run them as a pair for a thorough fix.

  1. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Type this and press Enter: 
    sfc /scannow
  3. Wait for the scan to finish (10–20 minutes) and don’t close the window.
  4. When it’s done, run: 
    DISM /Online /Cleanup-Image /RestoreHealth
  5. Restart your PC when DISM finishes.

If SFC reports “found corrupt files but was unable to fix some,” run DISM first to repair the source, then run SFC a second time. Microsoft documents this exact sequence in its System File Checker guide.

SFC and DISM repair the corrupted system files behind the most stubborn crashes.

Could my display driver be causing the crashes?

Very possibly. Graphics drivers power the Windows shell that File Explorer runs inside, so an outdated or buggy driver can crash it without warning. Updating usually helps; rolling back is smarter if the crashes started right after a driver update.

  1. Press Win + X and select Device Manager.
  2. Expand Display adapters.
  3. Right-click your graphics card and choose Update driver → Search automatically for drivers.
  4. Restart your PC after any update installs.

If crashes began after an update, choose Roll Back Driver instead. If your display also flickers outside File Explorer, my guide on Windows 11 screen flickering covers the same driver-level fixes in more depth.

Updating or rolling back your display driver clears crashes rooted in the Windows shell.

Will a Windows update fix File Explorer?

It might already contain the fix. Microsoft patches shell and Explorer bugs through cumulative updates, so if you’re on an older build the cure may simply be waiting to install.

  1. Press Win + I to open Settings.
  2. Go to Windows Update.
  3. Click Check for updates and install everything available.
  4. Restart your PC when prompted.

If updates themselves are stuck, my guide on Windows Update not working gets them installing again first.

A pending cumulative update often carries Microsoft’s own fix for Explorer bugs.

What if a corrupted user profile is to blame?

If every fix above fails, your Windows profile may be damaged, which quietly breaks how File Explorer loads its settings and shell extensions. Creating a fresh account is the fastest way to confirm it.

  1. Open Settings → Accounts → Other users.
  2. Click Add account.
  3. Select I don’t have this person’s sign-in information → Add a user without a Microsoft account.
  4. Create a username and password, then sign out of your current account.
  5. Log into the new account and open File Explorer.

If File Explorer runs perfectly there, your original profile is the culprit. Copy your files from C:\Users\[OldUsername] into the new account and use it going forward. For broader instability, my guide on Windows 11 freezing randomly covers overlapping root causes.

A new user account confirms whether a corrupted profile is crashing Explorer.

Common Mistakes to Avoid

  • Skipping the cache fix. Most people jump straight to advanced steps. A corrupted Quick Access history is behind the majority of crashes — clear it first.
  • Running SFC without admin rights. In a normal Command Prompt, sfc /scannow can’t repair anything. Always right-click and choose Run as administrator.
  • Grabbing drivers from random sites. Update only through Device Manager or the official maker (Intel, NVIDIA, AMD). Third-party driver sites often bundle adware or mismatched drivers.
  • Dismissing Windows Update. Microsoft quietly patches Explorer bugs in cumulative updates; the fix you need may already be queued.
  • Not restarting after a fix. Driver, system-file, and account changes don’t fully apply until you reboot. Restart before deciding a fix failed.

Avoiding these five missteps saves you from chasing fixes that were never going to stick.

Frequently Asked Questions

Why does File Explorer keep crashing on Windows 11?

Usually a corrupted Quick Access cache, the Preview Pane choking on a bad file, damaged system files, or an outdated display driver. On my own laptop it was the cache — clearing the File Explorer history stopped the crashes immediately.

Will clearing File Explorer history delete my files?

No. It only removes the list of recent files and pinned shortcuts in Quick Access. After I cleared mine, every document and photo was still exactly where I left it; only the recents list reset.

Is File Explorer crashing a sign of a virus?

Not usually — a corrupted cache or system files is far more common. But when a client’s Explorer crashed alongside random pop-ups and unknown programs, a full Windows Defender scan found the malware behind it. Scan if you see those extra symptoms.

Is it safe to run SFC?

Yes. SFC is a free, built-in tool that replaces corrupted system files with healthy copies and is recommended by Microsoft. I’ve run it on dozens of PCs without it ever breaking anything; the worst case is that it simply finds nothing to repair.

Can a corrupted user profile cause File Explorer to crash?

Yes. A damaged profile breaks how Explorer loads settings and shell extensions, crashing it on launch. When I created a fresh account on a stubborn machine and Explorer worked instantly, that confirmed the old profile was the problem.

How long does DISM take to run?

Typically 10–30 minutes, since it may download replacement files from Windows Update. On my laptop it sat at 20% for several minutes, then jumped to done — so let it finish without interrupting it.

Conclusion

Windows 11 File Explorer crashing is frustrating but rarely serious. Start with the quick wins — restart Explorer, clear the cache, disable the Preview Pane — then run SFC and DISM if it persists. Try them in this order and tell me in the comments which step finally stopped your crashes.