How to Fix ‘RESULT_CODE_KILLED_BAD_MESSAGE’ in Google Chrome

Browsing your favourite websites or completing an online form only for the active tab to abruptly crash into the iconic dead-tab screen declaring “Aw, Snap! Something went wrong while displaying this webpage. Error code: RESULT_CODE_KILLED_BAD_MESSAGE” brings productivity to an immediate halt. In the Chromium browser architecture, Google Chrome isolates individual tabs, renderer processes, and extensions into separate sandbox environments communicating via Inter-Process Communication (IPC) message channels. When a tab’s renderer process sends an invalid, structurally malformed, or out-of-order IPC payload to Chrome’s main browser process, the security supervisor immediately terminates the offending renderer to prevent memory corruption or potential sandbox escape exploits. While this security fail-safe protects your device, the error is frequently triggered by corrupted local web cache files, conflicting browser extensions, outdated graphics drivers, or third-party antivirus web filters. This guide outlines step-by-step methods to resolve the bad message error and restore browsing stability in Google Chrome.

Primary Causes Behind RESULT_CODE_KILLED_BAD_MESSAGE Crashes

Pinpointing what caused the browser process to abort the IPC channel directs you toward the fastest resolution without unnecessarily resetting your entire user profile. Review the common triggers below.

Failure Point Technical Explanation Recommended Action
Corrupted Local Browser Cache / Cookies Stale service worker tokens or malformed HTTP headers trigger IPC deserialisation faults. Clear browsing history, cookies, and cached web data across all time.
Conflicting Browser Extensions Ad blockers, script managers, or download tools inject malformed content scripts into DOM frames. Launch Chrome in Incognito mode and selectively disable third-party extensions.
Hardware Acceleration Desynchronisation The GPU compositing process drops frames during IPC pipe transfers, causing message deadlocks. Disable hardware graphics acceleration in Chrome Settings.
Antivirus Network Shield Interception Third-party security software alters internal IPC packets while filtering web requests. Add Chrome binary exclusions or temporarily pause third-party web shields.
Corrupted User Profile Directory The local “Default” user folder contains corrupted SQLite databases or Preferences files. Rename and regenerate a pristine Chrome user data directory.

Step 1: Test in Incognito Mode and Clear Browsing Cache

Because extensions and cached cookies are the leading triggers for malformed renderer messages, testing in a clean session isolates the underlying cause immediately.

  1. Open Google Chrome, click the three-dot menu icon in the upper-right corner, and select New Incognito window (or press Ctrl + Shift + N).
  2. Navigate to the website that triggered the error. If the page loads cleanly without crashing, a corrupted cookie, cached script, or extension is responsible.
  3. Return to your standard Chrome window and press Ctrl + Shift + Delete.
  4. Set the time range to All time.
  5. Check the boxes for Browsing history, Cookies and other site data, and Cached images and files.
  6. Click Clear data, close all Chrome windows completely, and relaunch the browser.

Step 2: Disable Conflicting Browser Extensions

Extensions that hook directly into page network requests or modify DOM structures (such as automated translation plugins, privacy shields, or cookie consent banners) often dispatch asynchronous messages that fail Chrome’s strict IPC schema validation.

  1. In Chrome’s address bar, type chrome://extensions/ and press Enter.
  2. Toggle off all active extensions to disable them simultaneously.
  3. Refresh the problematic webpage. If it loads smoothly, re-enable extensions one at a time while refreshing the page to pinpoint the exact culprit.
  4. Once identified, click Remove on the problematic extension to eliminate recurring crashes.

Step 3: Disable Hardware Graphics Acceleration

On systems running multi-monitor setups or integrated Intel/AMD graphics, hardware graphics rasterization threads can desynchronise from Chrome’s browser process, dropping frame buffers and resulting in killed IPC pipelines.

  1. Click the three-dot menu in Chrome and select Settings.
  2. In the left-hand navigation pane, click on System.
  3. Locate the option labelled Use graphics acceleration when available.
  4. Toggle the switch to the Off position.
  5. Click the Relaunch button directly next to the toggle to apply the changes.

Step 4: Rename and Rebuild the Chrome User Profile Folder

If the error code persists across multiple websites, the internal SQLite database files inside your Chrome user profile directory (such as Web Data or Network Action Predictor) have suffered structural corruption.

  1. Ensure Google Chrome is completely closed. Press Ctrl + Shift + Esc to launch Task Manager and confirm that zero instances of chrome.exe remain active.
  2. Press Windows Key + R to open the Run dialogue box.
  3. Paste the following path and press Enter:
    %localappdata%\Google\Chrome\User Data
  4. Locate the folder named Default.
  5. Right-click the Default folder and rename it to Default.old.
  6. Relaunch Google Chrome. The browser will automatically compile a clean, pristine profile directory. Sign back into your Google Account to synchronize your bookmarks and passwords cleanly without the corrupted cache data.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.