How to Fix Chrome Crashes in Windows 10 – Tips and Tricks
Some Windows 10 users are reporting Chrome crashing issue after updating to the latest build. If you too are having troubles with Chrome on Windows 10, here is how to try fixing this issue.
Fix Windows 10 Chrome crashes:
Microsoft released Windows 10 build 10525 yesterday, initiating a new wave of Windows 10 updates bringing more features to the operating system. However, after this update some users are reporting a Chrome crash problem. In a typical Chrome-like fashion, websites stop loading and all the plugins and extensions crash with the annoying “Aw, Snap! Something went wrong while displaying this webpage. Closing the apps and tabs that you don’t need may help by making more memory available” message.
Here are two Windows 10 tips to help you get rid of this Chrome crash problem on your new operating system.
- Reinstall Chrome 32-bit version which is reported to fix the issue.
- Alternatively, right-click on the Chrome shortcut in Start menu. In the end of the target path, type —no-sandbox. This will help you keep the 64-bit version of the browser.
The second method may affect the stability of the app but you will find the crashing issue sorted. We expect Google to fix this problem soon and would update this post with any more possible and official fixes as they come.
Remember, Gabriel Aul had mentioned in the blog to be aware of some of the issues present in the first post-launch Preview build 10525. However, the 64-bit Chrome issue wasn’t included in the known errors’ list. Microsoft initiated a new wave of Windows 10 updates helping insiders get the flavor of new features and improvements that might be introduced in the operating system in future. Let us know what you think of the new feature changes introduced in the OS.
So, Google has “confirmed” the issue but seems annoyed with everyone commenting on report page with “me to” messages. Woot folks, star the issue, stop annoying Google.
We have the problem confirmed and someone is working on it, so additional "me to" comments are a distraction at this point. Please just star the issue if you want to convey that you are affected, and if we have any questions or need additional feedback we'll post a comment. Also, please remember that this kind of temporary breakage is expected for users on the Windows 10 fast ring. So, we definitely appreciate your assistance in tracking down these problems, but if you're not comfortable dealing with disruptions and workarounds, then the fast ring might not be for you.