Computer Crashes after Chrome Freezes

Question

Hey There,
Macbook Aluminium Unibody 2008, running latest mavericks and SSD in place of disk drive.
Chrome crashes to 'Aw, Snap' page, randomly and doesnt occur every time or on the same page. May go a week without crashing or do it multiple times per day.
OSX returns this error:
Process:         Google Chrome [595]
Path:            /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:      com.google.Chrome
Version:         35.0.1916.153 (1916.153)
Code Type:       X86 (Native)
Parent Process:  launchd [199]
Responsible:     Google Chrome [595]
User ID:         501
Date/Time:       2014-07-09 13:23:42.155 +1000
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version:  11
Anonymous UUID:  A0CA37D3-2F8B-58FC-3FD3-71C6A803F1DA
But also returns Google Chrome [380] on some occasions.
If reopen chrome (including not reopening tabs) immediately returns 'Aw, Snap' page and crashes without doing anything, returning the same errors.
Once chrome has crashed then Finder doesn't work properly, can't bring any dialogue box such as 'shut down' or 'restart' up. There are other issues but i think they are Finder related and not consistent.
When restarted, even if i close all other apps after the chrome crash, they will be open on restart. So I think that finder has sort of frozen their status of being open.
Have disabled any plugins I didn't know and updated chrome to latest version, still happening.
Any ideas? Help would be much appreciated!

Answer 1

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.