While browsing websites in Microsoft Edge, a tab may suddenly crash and display a sad-folder icon accompanied by the error message: ‘Error code: RESULT_CODE_KILLED_BAD_MESSAGE’. This Chromium-level crash occurs unexpectedly across social media feeds, streaming portals, and administrative web apps. Unlike standard HTTP errors (such as 404 Not Found or 500 Internal Server Error) which originate from external web servers, RESULT_CODE_KILLED_BAD_MESSAGE is a client-side browser process termination. The browser’s master process deliberately kills a child renderer process because it received an invalid, malformed, or out-of-order Inter-Process Communication (IPC) message.
Why Microsoft Edge Kills Renderer Processes with Bad Message
Chromium architecture isolates individual browser tabs into sandboxed child processes. When an IPC communication channel encounters protocol corruption, it triggers this protective crash:
- Corrupted Local Browser Cache and Cookie Desynchronisation: Stale web session tokens, corrupted service worker caches, or damaged IndexedDB data sending unexpected payload structures.
- Rogue or Outdated Browser Extensions: Third-party extensions injecting modified JavaScript headers or communicating via outdated Chromium API message channels.
- Chromium Multi-Process Memory Leaks: System RAM corruption or memory pressure causing IPC buffers to deliver truncated byte streams between processes.
- Antivirus Web Shield Packet Inspection: Network security software altering web socket payloads in transit, resulting in malformed packets that violate browser protocol checks.
Step 1: Clear Cached Web Content and Site Cookies
Flushing damaged local cookies and cached web assets eliminates malformed session payloads.
- Open Microsoft Edge.
- Press Ctrl + Shift + Delete to open the Clear browsing data dialogue.
- Set the Time range dropdown to All time.
- Check the boxes for:
- Browsing history
- Cookies and other site data
- Cached images and files
- Click Clear now.
- Close and restart Microsoft Edge, then navigate back to the problematic website.
Step 2: Test in an InPrivate Browsing Window
InPrivate windows launch without active extension hooks or third-party cookies, instantly isolating software conflicts.
- Press Ctrl + Shift + N to launch an InPrivate window.
- Load the website that previously crashed with
RESULT_CODE_KILLED_BAD_MESSAGE. - If the page renders smoothly without crashing, a third-party extension or stale local site profile is the root cause.
- Navigate to
edge://extensionsin your regular window, toggle off all extensions, and re-enable them one by one to identify the faulty plug-in.
Step 3: Reset Microsoft Edge Settings to Factory Defaults
If core Chromium configuration flags or search provider hooks are desynchronised, resetting settings restores pristine operational state without deleting your saved passwords or favourites.
- Click the three dots (…) in the top-right corner of Edge and select Settings.
- In the left sidebar, click Reset settings.
- Click Restore settings to their default values.
- Review the prompt and click Reset to confirm.
- Restart Microsoft Edge.
Step 4: Repair the Microsoft Edge Application in Windows
If browser binaries or system DLL integrations are corrupted, repairing the installation files replaces damaged components.
- Close all open Edge windows.
- Open Windows Settings (Win + I) and select Apps > Installed apps.
- Search for Microsoft Edge.
- Click the three dots (…) next to Microsoft Edge and choose Modify.
- Click Repair. Windows will verify and reinstall the latest stable release of Microsoft Edge automatically.