What should I do when Chrome crashes on Windows 10?
Microsoft released quite a few Windows 10 post-RTM build for insiders over the years, but they are still far from bug-free.
Why is Chrome crashing all the time?
According to various reports, the 64-bit version of Google Chrome doesn’t work in particular Windows 10 build versions. On the other hand, the 32-bit version works just fine.
You can try it yourself, just run the 64-bit version of Google Chrome, and you’ll probably get a crash report and a bunch of error messages.
So, why does this happen? Google Chrome uses a special technology called “sandbox,” which isolates the browser‘s processes in order to reduce the vulnerability of the browser, and reduce a chance for malicious software to get to your computer.
“Cutting through the noise, it looks like the sandbox is breaking in the Win10 10525 previews for 64-bit Chrome,” said Justin Schuh, a Google software engineer, in one of his messages on the Chromium bug tracker.
How can I fix my Google Chrome from crashing?
Step 1: Disable sandbox
Apparently, some aspects of the latest Windows 10 build conflict with the sandbox technology, which prevents Google Chrome from working on certain builds of Windows 10 for Insiders.
So, if you want Google Chrome to work, you’ll need to disable the sandbox feature.
To disable the sandbox technology in your Google Chrome browser, do the following:
- Right-click on your Desktop shortcut of the Chrome browser and go to Properties
- Go to Shortcut tab and click on the Target: field
- Type space at the end of the path in Target: filed and enter the following: –no-sandbox
- Click OK, and use that shortcut to launch Google Chrome
This should restore the functionality of Google Chrome in Windows 10, but it takes some risks with it.
Namely, when you disable the sandbox feature of your Chrome browser, it will become more vulnerable, and potentially malicious content will find an easier way to enter your computer through the Google Chrome browser.
But, if you don’t want to mess with your security in the Chrome browser, you can switch to the 32-bit version, or maybe try another browser, until Microsoft comes up with the solution.
And, since this issue is now widely reported, I’m sure that Microsoft’s developers will start working on the solution, along with the fixes for other bugs.
If you’re still having issues on your PC or you simply want to avoid them for the future, we recommend you to download this tool (100% safe and tested by us) to fix various PC problems, such as file loss, malware, and hardware failure.
If you have any other Windows 10-related issues you can check for the solution in our Windows 10 Fix section.
Step 2: Additional solutions
In some cases, the “-no sandbox” method is still popular, but remember, it can cause a lot of vulnerability to your browser. If none of the solutions written above didn’t work out for you, try some of the steps listed below.
We strongly recommend installing the x32 version of Google Chrome because it’s more stable. Don’t forget to often check for an updated version of the browser.
- Check if you have an internet connection available
- Clear your browser cache
- Uninstall extensions that you don’t use anymore
- Free up memory by closing other applications in use
- Restart your browser
- Run a full system antivirus scan
- Clean boot your computer
- Reinstall Chrome is the crashes persist.
RELATED STORIES TO CHECK OUT:
- Is it possible to auto-hide Address Bar in Chrome?
- Full Fix: Google Chrome could not move extension directory into profile
- Chrome 68 reduces browser RAM utilization for faster performance
Editor’s Note: This post was originally published on August 2015 and has been since updated for freshness, and accuracy.
A lot of people still love to use Windows Media Player as their go-to player, but many users reported Windows Media Player cannot play the […]
Windows users often experience high CPU usage. This issue causes PC performance to slow down, consuming huge chunks of memory. It is critical to take […]
So you’re on your machine and plug-in your TV, the devices seem to recognize each other and appear to be connected, but suddenly you get […]