Shockwave Flash has crashed in Google Chrome

Shockwave Flash Chrome Error

Chrome surpassed its competitors and was in first place in the browsers ranking. But some problems remain unchanged.

A rather annoying problem happens at the most inopportune moment. If many tabs open, there is not the slightest desire to restart the browser. But, we have found a few solutions that may suit you.

Google Chrome is a user-friendly, and attractive browser. It received real-world popularity after it offered its users a built-in flash player. The other browsers do not have it at that time. But now, the situation is getting complicated. Google Chrome connects all plugins at startup at once: its own and those installed by the system. In this case, an error appears: “Shockwave Flash has crashed Google Chrome,” and a warning message pops up.

How to fix Shockwave Flash Chrome crashing in two clicks?

This problem can be easily corrected manually. It’s not difficult at all. We will disable the extra Shockwave Flash modules, leaving only one. To do this, we need to go to the plugin settings. This can be done through the menu or paste the text into the browser’s address bar: chrome://plugins.

To get there through the menu, you need to go to “Settings > Show advanced settings > Content settings > Disable individual modules ….”.

We reveal the plus sign “Details” on the right of the Flash block. Disable unnecessary Flash modules. There may be two or more used Shockwave Flash modules of different versions. One of them will be built into Google Chrome, and the rest will be system ones. It is easy to determine this: if the path of the module files starts with “C:\Windows\.…,” then this is a plugin installed separately in the system, and if “C:\Users\.…,” then it is built into Chrome. Often they have different versions. The built-in module is updated only with the program, while the external one is updated independently and frequently.

We need to disable all unnecessary modules and leave only one. To do this, click “Disable” on each extra module. I recommend starting by trying to disable external modules, restart Chrome, and observe the browser’s behavior. If it was impossible to fix the failure, try to do the opposite: enable the external module of the latest version and disable the internal one.

Note. After updating to version 42, some old extensions, including the external player, were no longer supported. Therefore, you must enable the built-in module or follow the instructions for everything to work. Namely: enter in the address bar: chrome://flags/#enable-npapi and click “Enable” for NPAPI extensions.

Uninstall and reinstall Adobe Flash Player

If the previous method does not solve the problem, then try to remove the plugin Adobe Flash Player. Close all browsers, go to “Control Panel > Uninstall Programs” in Windows 7/10, and remove the Adobe Flash Player Plugin.

If you need it for other browsers, then after deleting it, install it again to the latest version from the Adobe website Then try alternately using different modules.

How to disable Flash Player hardware acceleration?

Another possible problem that makes Flash Player buggy is the hardware acceleration of the flash, which is enabled by default. In this case, the video can be played with artifacts, and the plugin will hang. In some cases, disabling hardware acceleration solves this problem.

First way. To do this, open any site with Flash, right-click on any flash element, and select “Settings”: disable hardware acceleration Flash Player.

Next, click the first tab and uncheck “Enable hardware acceleration.”

The second way. It consists of launching Chrome with hardware acceleration already disabled. To do this, you need to add a parameter to the program launch: click on the Google Chrome shortcut and select “Properties,” and on the “Shortcut” tab, go to the end of the line and add the text: -disable-accelerated-video.

What else can you try?

Try uninstalling and reinstalling Chrome. Don’t lose your bookmarks when reinstalling.

The failure of Shockwave Flash may be due to the “sandbox” of plugin execution. The sandbox is something like a testing ground for a programmer. But this safe environment tends to get cluttered. If all else fails, try adding the -disable-flash-sandbox option to the Chrome launch line.

For example, if you add both parameters mentioned, then the launch line will turn out something like this:


I hope this information helped you fix Shockwave Flash Chrome crashing. Share your experience in the comments.