Plug-in Failure (Flash not working in Safari but working in Chrome)

Question

Hi There,
I realise there have been threads on this subject but I seem to have tried everything besides re-installing ML at this stage.
When loading any flash content on any website within Safari - I receive a 'Plug-in Failure' message where the content should appear.
I feel the problem has been occurring since downloading the newest update
I was hoping someone could point out if I had missed out on something
Here are the steps I have taken to attempt to resolve this...
1. Uninstalled and reinstalled the latest version of Flash. (This actually did work once for about a half an hour, i've tried it about half a dozen times)
1a. Turning my computer off and on again
1b. Attempted downgrading my Flash version but the flash installer kept failing.
2. Logged into a guest account (Flash didn't work in safari)
3. Booted up in Safe Mode (Flash worked but very slowly)
4. Reset Safari (Flash didn't work)
5. Disabled Extensions (Flash didn't work)
6. Enabled Plug-ins & Java within Safari (Flash didn't work)
7. Removed plug ins that I believed may be effecting it (Flip4Mac) (Flash didn't work)
8. Deleted all data in the pref pane for Flash (Flash didn't work)
9. Removed all website data within Safari (Flash didn't work)
10. Tested Firefox and flash is also not working in firefox.
The console is showing the following Pluginprocess crash:
Process:         PluginProcess [2331]
Path:            /System/Library/PrivateFrameworks/WebKit2.framework/PluginProcess.app/Contents/ MacOS/PluginProcess
Identifier:      com.apple.WebKit.PluginProcess
Version:         8536 (8536.30.1)
Build Info:      WebKit2-7536030001000000~9
Code Type:       X86-64 (Native)
Parent Process:  Safari [2257]
User ID:         501
PlugIn Path:       /Library/Internet Plug-Ins/Flash Player.plugin/Contents/PlugIns/FlashPlayer-10.6.plugin/Contents/MacOS/FlashPlay er-10.6
PlugIn Identifier: com.macromedia.FlashPlayer-10.6.plugin
PlugIn Version:    11.8.800.94 (11.8.800.94)
Date/Time:       2013-09-01 01:45:37.808 +0100
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version:  10
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 - this line looks quite suspect to me...
VM Regions Near 0:
-->
    __TEXT                 00000001072e8000-00000001072e9000 [    4K] r-x/rwx SM=COW  /System/Library/PrivateFrameworks/WebKit2.framework/PluginProcess.app/Contents/ MacOS/PluginProcess
The above crash log is repeated several times. (there's more to the log but i thought i'd just paste in the above)
Desparate to resolve this - chrome is so ugly and buggy! (Not to mention so Google)
Thanks in advance!

Answer 1

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac. 
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing. 
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands. 
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
Launch the Terminal application in any of the following ways: 
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
Step 1 
Triple-click the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -ef 
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2 
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo; sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; } 2> /dev/null | open -ef 
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. 
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
Step 3
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; echo; crontab -l 2> /dev/null; } | open -ef 
Step 4
ls -A /e*/{cr,la,mach}* {,/}Lib*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -ef  
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
Step 5
osascript -e 'tell application "System Events" to get name of login items' | open -ef 
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output. 
You can then quit Terminal.