How to Troubleshoot Microsoft Edge Crashes & Errors
Why This Is Happening
I've seen this exact situation hundreds of times: you're mid-project, halfway through filling out a form or streaming a meeting, and Edge just dies. Maybe it crashes silently. Maybe it throws up a grey STATUS_BREAKPOINT or RESULT_CODE_HUNG screen and refuses to move. Maybe it's been getting slower for weeks and today it finally stopped loading pages entirely. Whatever the symptom, I know how disruptive this is , especially when your whole workflow lives in browser tabs.
Microsoft Edge (Chromium-based, first released January 2020) is a solid browser, but it inherits many of the same failure modes as Chrome because it's built on the same engine. That means the same categories of problems show up: corrupted user profiles, rogue extensions hogging memory, outdated GPU drivers triggering renderer crashes, and Windows Update quietly breaking something in the background.
Here are the most common root causes I see when people come to me with Edge problems:
- Corrupted profile data. Edge stores your profile , bookmarks, passwords, settings, cached tokens, in
%LOCALAPPDATA%\Microsoft\Edge\User Data\Default. If that folder gets corrupted (often from an unclean shutdown or a failed sync), Edge either refuses to open or throws a "Your profile couldn't be opened correctly" banner on every launch. - Extension conflicts. A poorly coded third-party extension, especially ad blockers or screen-capture tools, can cause the renderer process to terminate unexpectedly. You'll often see Aw, Snap! errors (error code
RESULT_CODE_KILLED) tied to specific tabs. - Stale or bloated cache. Edge's disk cache can grow to several gigabytes. When the cache index gets mismatched, common after an abrupt crash, Edge starts hanging on page loads or returning stale content.
- Outdated or incompatible GPU drivers. Edge offloads rendering to your GPU via hardware acceleration. If your display driver is outdated (or if you recently updated to a driver with a known bug), you'll see crashes specifically when loading pages with heavy graphics, video, or WebGL content. Event Viewer will log these as Edge GPU process crashes under Event ID 1000.
- Windows Update side effects. Patch Tuesday updates occasionally break Edge's integration with Windows Security or update the underlying WebView2 runtime in a way that conflicts with the installed Edge version.
- Enterprise policy conflicts. If your machine is domain-joined, Group Policy objects pushed from IT can force Edge into a configuration that conflicts with its defaults. I've seen GPOs that disable the GPU process entirely, and then IT wonders why Edge is crawling.
The frustrating part is that Microsoft's built-in error messages almost never tell you which of these is actually happening. "Aw, Snap!" tells you nothing. "STATUS_BREAKPOINT" sounds alarming but is usually just a renderer crash. This guide cuts through that and gives you a clear path from symptom to fix. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you touch anything else, run this sequence. It resolves the majority of Microsoft Edge not opening, freezing, or crashing on startup issues in under five minutes.
Step 1: Close every Edge window. Don't just close tabs, right-click the Edge icon in your taskbar and click Close all windows. Then open Task Manager (Ctrl+Shift+Esc), go to the Processes tab, and look for any lingering Microsoft Edge processes. Right-click each one and select End task. Edge sometimes leaves orphaned processes running, and they block a clean relaunch.
Step 2: Open Edge, click the three-dot menu (top right), go to Settings > Privacy, search, and services, then scroll down to Clear browsing data and click Choose what to clear. Set the time range to All time. Check Cached images and files and Cookies and other site data. Leave passwords unchecked unless you want to re-login everywhere. Click Clear now.
Step 3: After the clear finishes, type edge://restart directly into the address bar and press Enter. This forces a clean restart of the browser process, cleaner than just closing and reopening.
If Edge won't open at all, do this from PowerShell instead:
Stop-Process -Name "msedge" -Force -ErrorAction SilentlyContinue
Start-Process "shell:AppsFolder\Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App"This kills any stuck process and launches Edge fresh. If the problem is gone after this, great. If it comes back within a session or the next day, keep reading. The issue is deeper, and the steps below will find it.
Extensions are the single most common cause of Microsoft Edge crashing or freezing mid-session. I always check these before touching anything in the OS. The approach is surgical: launch Edge in InPrivate mode first. Press Ctrl+Shift+N to open an InPrivate window. Extensions are disabled by default in InPrivate unless you've specifically allowed them.
If Edge runs fine in InPrivate, pages load, nothing crashes, an extension is your problem. Now go to edge://extensions in a regular window. You'll see all your installed extensions with on/off toggles. Disable every single one by clicking the blue toggle next to each until it goes grey.
Relaunch Edge normally. If it's stable, start re-enabling extensions one at a time, relaunching after each one. The one that breaks stability is your culprit. Common offenders I've seen repeatedly: Honey, older versions of Grammarly, any screen-recording extension that hooks into the browser's media APIs, and cryptocurrency wallet extensions. Remove the bad extension by clicking Remove on its card.
If you need to keep the problematic extension, check the developer's website for an updated version, many extension crashes on Edge are fixed in newer builds that the automatic updater hasn't fetched yet. You can force an extension update by clicking Update at the top of edge://extensions (you may need to enable Developer mode first using the toggle in the bottom-left corner).
What success looks like: Edge launches without crashing and pages load normally after you've re-enabled all extensions except the bad one.
When Edge throws "Your profile couldn't be opened correctly" or if it silently loses your settings and bookmarks every restart, the Default profile folder is damaged. This is one of the trickier Microsoft Edge troubleshooting scenarios because people are scared to touch it, they think they'll lose everything. Here's the reality: your synced data (bookmarks, passwords, history) is safely stored in your Microsoft account. Renaming the local folder just forces Edge to rebuild it fresh from that sync.
Close Edge completely (kill all processes in Task Manager as described above). Then open File Explorer and navigate to:
%LOCALAPPDATA%\Microsoft\Edge\User Data\You'll see a folder named Default. Don't delete it, rename it to Default.bak. This preserves it as a fallback while Edge regenerates a clean copy.
Also look for any folders named Default (1), Default (2), etc. These are leftover duplicates from failed profile repairs and can cause their own conflicts. Rename those to .bak versions too.
Relaunch Edge. It will create a new Default folder and ask you to sign into your Microsoft account. Once signed in, your sync data will repopulate, bookmarks, passwords, and history should all come back within 60–90 seconds. Extensions will re-install automatically from the cloud.
What success looks like: Edge opens to a fresh start screen, you sign in, and your bookmarks/history sync back. If it still crashes, the issue isn't the profile, move to Step 3.
Hardware acceleration is Edge's way of offloading visual rendering to your GPU instead of your CPU. Usually this is a good thing, it makes scrolling smoother and video playback more efficient. But when your GPU driver is outdated, corrupted, or has a specific bug (and this is distressingly common on both Intel integrated graphics and NVIDIA cards after a Windows Update), hardware acceleration becomes the source of crashes, flickering, black screens, and "Aw, Snap!" errors on media-heavy pages.
To disable it, go to edge://settings/system. Look for the toggle labelled Use hardware acceleration when available. Turn it off. Edge will prompt you to relaunch, do it.
If your crashes stop after this, your GPU driver is the real problem. Open Device Manager (Win+X, then select Device Manager), expand Display adapters, right-click your GPU, and select Update driver. Choose Search automatically for drivers. If Windows says you're up to date but you're still having problems, go directly to the GPU manufacturer's website (Intel Download Center, NVIDIA Driver Downloads, or AMD Support) and grab the latest driver manually.
Once you've updated the driver, go back to edge://settings/system and re-enable hardware acceleration. Test it. If crashes return, stay without hardware acceleration until the manufacturer releases a fixed driver.
You can also check Edge's internal GPU diagnostics at edge://gpu, this page shows exactly what features are hardware-accelerated and flags any that have been disabled due to known driver issues.
What success looks like: Pages with video, animations, and maps load without crashing or showing a blank GPU process error screen.
If the above steps haven't resolved your Microsoft Edge not loading pages or persistent crashing issue, it's time to use Windows' built-in repair function. This is different from uninstalling Edge, the Repair option specifically rebuilds Edge's core files without touching your profile data.
Open Windows Settings (Win+I), go to Apps > Installed apps (on Windows 11) or Apps & features (on Windows 10). Search for Microsoft Edge in the search box. Click the three-dot menu next to it and select Modify.
A small repair dialog will open. Click Repair. Windows will verify and rebuild Edge's binary files. This takes about 60–90 seconds. After it finishes, relaunch Edge and test.
If Repair doesn't appear as an option (this happens on some Windows 11 configurations where Edge is protected), you can trigger the same process from an elevated PowerShell window:
Get-AppxPackage -Name "Microsoft.MicrosoftEdge.Stable" | Reset-AppxPackageIf Repair didn't fix it, go back to the same Modify dialog and this time click Reset. Reset is more aggressive, it wipes your local profile data (local-only data, not synced data) and returns Edge to a factory state. Your synced bookmarks and passwords from your Microsoft account are safe and will repopulate on next sign-in.
After a Reset, Edge will launch as if it's brand new, no extensions, no customizations. Sign in to your Microsoft account and let everything sync back. This resolves Edge high CPU usage and corrupt installation issues in most cases.
What success looks like: Edge launches cleanly with a fresh interface. Sign-in triggers sync and your data returns within a couple of minutes.
A surprising number of "Edge is broken" situations I've diagnosed are actually caused by a mismatch between the Edge version and the WebView2 Runtime. WebView2 is a shared component that lets Windows apps embed web content. Edge and WebView2 ship on the same cadence, but they can get out of sync, especially if Edge updates silently while WebView2 doesn't, or vice versa.
First, update Edge itself. Go to edge://settings/help. Edge will automatically check for and download any available update. Let it install. Relaunch when prompted.
Then fix WebView2. Open Apps > Installed apps in Settings and search for Microsoft Edge WebView2 Runtime. If it's listed, click the three-dot menu and select Modify. Choose Repair.
If you want to do this from the command line (useful on managed/enterprise machines where the Settings UI is locked down):
# Check current WebView2 version
Get-ItemProperty "HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}" | Select-Object pv
# Force WebView2 update via Edge Updater
"C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" /update /sessionid {00000000-0000-0000-0000-000000000000}While you're in here, also check your Edge update channel. Navigate to edge://settings/help and look at the channel name. If you're on the Beta or Dev channel and experiencing instability, switching to the Stable channel might solve your problem entirely. You can download the Stable channel installer from Microsoft's official Edge site and install over the top of your current channel.
What success looks like: edge://settings/help shows "Microsoft Edge is up to date" and no WebView2 mismatch errors appear in Event Viewer.
Advanced Troubleshooting
Reading Event Viewer for Edge Crash Data
When Edge crashes without an obvious error message, Event Viewer is where the real story lives. Press Win+R, type eventvwr.msc, and press Enter. Expand Windows Logs > Application. Filter the log (Action > Filter Current Log) for Event ID 1000 (application crash) and Event ID 1001 (Windows Error Reporting). Set the source to Application Error.
Look at the Faulting module name field in the crash entry. Common patterns I've seen:
msedge.dll, Core Edge process crash, usually profile or update-related.d3d11.dllornvwgf2umx.dll, GPU/Direct3D crash, confirms the hardware acceleration fix in Step 3.chakra.dllorv8.dll, JavaScript engine crash, often caused by a specific webpage or extension.
The Exception code field is also useful. 0xc0000005 is an access violation (memory corruption), 0x80000003 is a breakpoint (usually a driver conflict), and 0xc000001d is an illegal instruction (typically a CPU compatibility issue or a very outdated driver).
Group Policy and Registry Fixes for Enterprise Machines
If your machine is domain-joined and you're experiencing Edge issues that don't respond to any of the above steps, Group Policy is often the culprit. IT teams sometimes push policies that conflict with Edge's defaults without realizing it.
Open a command prompt and run:
gpresult /h C:\gpresult.html /f
start C:\gpresult.htmlThis generates a full Group Policy report. Open it and search for "Edge", look for any applied policies under Computer Configuration > Administrative Templates > Microsoft Edge. Policies like HardwareAccelerationModeEnabled set to Disabled, or ExtensionInstallBlocklist with wildcard entries, can silently break features without any error message to the user.
For non-domain machines, you can check Edge's active policies directly at edge://policy. Any policy shown there is actively constraining Edge's behavior. Compare against what you'd expect and identify anything anomalous.
A specific registry fix that resolves the "Edge crashes on Windows startup" issue on some Windows 11 machines, where Edge was set to open at boot and corrupted a startup entry:
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Run" /v "MicrosoftEdgeAutoLaunch_*" /fThis clears Edge's auto-launch registry entry. Edge will still work normally, it just won't attempt to launch at Windows startup, which removes the race condition that caused the crash.
Reinstalling Edge as a Last Resort
Full reinstall is rarely necessary, but if nothing else has worked, here's how to do it cleanly. Edge is a system component on Windows 11, so you can't uninstall it the normal way. Instead, download the offline installer from Microsoft's Edge Enterprise page, run it, and it will overlay-install the latest version over your current broken installation. This fixes binary-level corruption that the Repair option sometimes misses.
If you've completed every step in this guide and Edge is still crashing or not loading pages, the issue may be at the OS or hardware level, beyond what browser-level fixes can address. Specifically, escalate to Microsoft Support if: Event Viewer shows recurring Event ID 1000 with faulting module ntdll.dll (points to an OS-level memory issue), if Edge crashes exclusively on one user account even after a full profile reset (points to a corrupted Windows user profile), or if you're on a managed device and suspect a policy conflict your IT team needs to investigate. Have your Event Viewer crash logs ready, they'll ask for them immediately.
Prevention & Best Practices
The best way to troubleshoot Microsoft Edge is to not need to troubleshoot it at all. After fixing hundreds of these issues, I've noticed that the machines that rarely have Edge problems share a few habits.
Keep Edge updated automatically. Go to edge://settings/help and make sure the update channel shows as Stable and that automatic updates are not blocked. Edge ships security patches and stability fixes every four weeks on the Stable channel. Letting updates fall behind by more than one or two cycles dramatically increases your crash risk, especially on sites that push new web APIs aggressively.
Audit your extensions quarterly. Every three months, open edge://extensions and delete any extension you haven't actively used in the past 30 days. Extensions that are no longer maintained by their developers don't get security updates, and their code gradually becomes incompatible with newer Edge builds. An extension that worked fine six months ago can become an Edge high CPU usage or crashing issue today without any warning.
Don't ignore the WebView2 Runtime update prompts. When Windows prompts you to update WebView2, do it. I've seen people dismiss that notification for months and then be mystified when Edge and every other Electron-based app on their machine starts behaving strangely. It's a small, quick update with a big stability payoff.
Set a cache size limit. Edge doesn't cap its disk cache by default. You can set a limit via a command-line flag, but the simpler approach is to schedule a monthly cache clear. Go to edge://settings/clearBrowserData and add it to your calendar to run the cached images/files clear once a month. This prevents the gradual cache index corruption that causes Edge not loading pages issues over time.
Use separate profiles for work and personal browsing. If you use Edge for both personal and work accounts (especially if work involves Microsoft 365 and Azure AD), create separate Edge profiles for each identity. Profile corruption is far more likely when one profile is juggling multiple Microsoft account tokens with conflicting sync states. Click your profile avatar in the top right of Edge and select Add profile to set up a second one.
- Enable Efficiency mode at
edge://settings/system, it throttles inactive tabs and dramatically reduces Edge high CPU usage on older hardware. - Keep fewer than 20 tabs open simultaneously; beyond that, Edge's memory manager starts making aggressive decisions that can destabilize the session.
- If you use Edge on multiple devices, check
edge://sync-internalsoccasionally, sync conflicts can silently cause profile data corruption that only shows up weeks later. - Run
sfc /scannowin an elevated command prompt after any major Windows Update, it catches OS file corruption that can affect Edge's runtime components before you ever see a symptom.
Frequently Asked Questions
Why does Microsoft Edge keep crashing on startup every time I open it?
This almost always comes back to a corrupted user profile or a conflicting startup extension. The fastest diagnostic: open Edge with the --disable-extensions flag by running msedge.exe --disable-extensions from a Run dialog (Win+R). If it opens fine, an extension is crashing on startup. If it still crashes, the profile is the problem, follow Step 2 above to rename the Default folder and let Edge rebuild. Check Event Viewer (Event ID 1000) for the faulting module name if neither fix works; that'll point you at the actual failing component.
Microsoft Edge is running slow and using 100% CPU, how do I fix it?
Open Edge's built-in task manager: press Shift+Esc while inside Edge. This shows you exactly which tab or extension is consuming the most CPU. Sort by CPU descending. Usually it's a tab with heavy JavaScript (crypto mining, badly coded dashboards, or an ad-heavy news site) or an extension like a password manager with a sync loop. Kill the high-CPU process from Edge's task manager first, then address the root cause, either close that tab permanently or remove the misbehaving extension. If overall Edge CPU is high even with no tabs open, disable hardware acceleration at edge://settings/system as your GPU driver may be thrashing.
Edge says "Your profile couldn't be opened correctly" every single time I launch it, even after I click OK it seems fine. Should I be worried?
Yes, this banner is a warning sign you shouldn't dismiss. It means Edge detected inconsistency in your profile data on launch and auto-corrected it, but it doesn't always correct it cleanly, and repeated occurrences lead to bookmark loss or password sync failures down the road. Rename your Default folder to Default.bak as described in Step 2 to get a fresh profile. Since your data syncs from your Microsoft account, you lose nothing. Once you've done that, the banner disappears permanently in the vast majority of cases.
Edge stopped working after a Windows Update, pages won't load and I get ERR_NETWORK_CHANGED errors constantly. What happened?
This is a classic Windows Update side effect. The update likely changed a network adapter setting, reset your DNS configuration, or modified the Windows Filtering Platform in a way that Edge's network stack disagrees with. Start by flushing your DNS and resetting the network stack: open an elevated command prompt and run netsh int ip reset, then netsh winsock reset, then ipconfig /flushdns, then reboot. If ERR_NETWORK_CHANGED persists specifically in Edge but not in other browsers, go to edge://settings/privacy and under Security, try toggling Use secure DNS off. Some Windows Update DNS policy changes conflict with Edge's built-in DoH (DNS-over-HTTPS) resolver.
How do I fix the "Aw, Snap!" error that only shows on certain websites?
Site-specific "Aw, Snap!" errors (which correspond to error code RESULT_CODE_KILLED or STATUS_ACCESS_VIOLATION) are almost always caused by either a conflicting extension that reacts to content on that specific page, or by a site using a web API (like WebAssembly, WebGL, or SharedArrayBuffer) that Edge's current settings block or handle incorrectly. Test the site in InPrivate mode first to rule out extensions. If it works in InPrivate, disable extensions one by one in a normal window. If it fails in InPrivate too, navigate to edge://flags and search for the specific API the site uses, try resetting flags to default. Also check if the site uses WebGL by opening edge://gpu and looking for any disabled graphics features.
Can I reinstall Microsoft Edge on Windows 11 if it's completely broken?
You can't uninstall Edge from Windows 11 through normal means, it's a protected system component. But you can reinstall over the top of it without uninstalling. Download the Microsoft Edge Enterprise Stable offline installer (MSI) from Microsoft's Edge for Business page. Run the installer while Edge is closed, it will detect your existing installation and perform an overlay repair, replacing any corrupted binary files. This is more thorough than the Repair option in Apps settings and fixes cases where the core Edge executable itself has been corrupted. After the reinstall completes, sign back into your Microsoft account and let your profile sync.