The cause of this error, in most cases, has to do with a conflict among multiple Flash installations on your computer. This is an often seen situation that can occur when you have multiple browsers, each with their own instance of Adobe's Flash player. Fortunately this can be verified and remedied in a few simple steps:
Type the following text into Chrome's address bar (also known as the omnibox) and hit Enter:chrome://plugins. You should now see a list of all installed plug-ins. In the upper right hand corner of this page is a Details link, accompanied by a plus icon and circled in the example above. Click on this link to expand the respective plug-in sections, displaying in-depth information about each.
Each plug-in section should now be expanded, displaying all details. Locate the Adobe Flash Player plug-in section, highlighted in the example above. If multiple files are associated with this plug-in, this will be noted directly to the right of its name. In this example you will notice that there are two files shown, one located within a subfolder belonging to Google Chrome and the other in a Windows system folder.
Your individual configuration may differ from the one depicted in this screen shot. If you do have two files associated with Adobe Flash Player, first determine which file is internal to Google Chrome. This can be discerned by locating the words Google and Chrome within theLocation path. In newer versions of Chrome, this file will be called pepflashplayer.dll. Once found, click on the accompanying Disable link. Chrome will now be forced to utilize the standalone version of Adobe Flash when needed and your problem should be solved. If you have followed these directions and are still experiencing this crash, continue reading below.
If you only have one plug-in file associated with Adobe Flash Player, continue to read below for further suggestions.
If you have two files associated with Adobe Flash Player and successfully disabled the internal option, your Plug-ins page should now appear similar to the screen shot above.
If you only have one file associated with Flash, then there is most likely another cause for the crashes that you have been experiencing. One possibility is that an installed extension is the culprit. The best way to narrow this down is to disable your extensions one at a time, checking to see if the crashes cease in each instance. If an extension is to blame, using this process of elimination should point you in the right direction.
Another virtual villain here could be a plug-in other than Flash. Following the same logic that you did with extensions, disabling your plugins one by one can rule out a potential problem.
If you are still seeing The following plugin has crashed: Shockwave Flash error in your browser. In rare cases, a conflict between some of the other modules loaded into Google Chrome could be the issue. Thankfully, Chrome does a decent job of detecting these potential disturbances.
Type the following text into Chrome's address bar and hit Enter: chrome://conflicts. You should now see a detailed list of all modules loaded into your browser. If any conflicts are found, they will be presented here. As you can see in the example above, no conflicts were detected.
Finally, if you've exhausted these steps and are still experiencing Flash errors then you may want to completely uninstall and reinstall your Chrome browser.