MacBook – Cloned and changed HDD; now almost every program crashes on startup

bootcampcrashmacbook pro

As the title suggests I cloned my mac hdd using CCC and bootcamped and restored win 7 on the bootcamp partition.

It would seem that everything worked out as planned but the first thing I noticed was that chrome wouldn't launch. It would crash instantly. So I re-installed it which did nothing. I then proceeded to remove the application support folder for Chrome and then re-installed. Nope.

I then noticed that NONE of my applications that aren't from Apple (apart from Unity3d which actually runs) will start. They all "quit unexpectedly". I have tried to repair dependencies and I have controlled the integrity of my drive. It repaired a bunch of dependencies but couldn't find anything wrong with the disk. I have a hunch it has something to do with when I restored the windows 7 installation but I can't be sure of that.

Anyone have the slightest idea what's going on? How would I fix this without having to wipe the mac installation?

Thanks for reading!

Edit
After having a look in system.log I can see something that might indicate that something is bad with the partitioning. Every crash looks like this:

Jun 28 14:47:53 MacBook-Pro ReportCrash[3461]: [CrashReport _extractBinaryImageInfoUsingSymbolicator] caught exception: Called memoryAtAddress: 0xa0a5b794, which is in an unmappable portion of [0x0 -> 0xffffffffffffffff] in PID# 3457. (0x1005cb796 0x100b750f3 0x1007b4ec6 0x10000494c 0x100004fc3 0x10085c362 0x100848b7a 0x100004ac0 0x100005956 0x1008477fd 0x10000541c 0x100007fb4 0x100008aa0 0x10000ad72 0x10000ab4f 0x10095f9dc 0x10000a256 0x1009534f6 0x1009533a9)
Jun 28 14:47:53 MacBook-Pro com.apple.launchd.peruser.501[295] ([0x0-0x9e09e].dk.Otee.Unity_Unitron[3457]): Job appears to have crashed: Bus error
Jun 28 14:47:53 MacBook-Pro ReportCrash[3461]: Saved crash report for Unitron[3457] version ??? (???) to /Users/phil/Library/Logs/DiagnosticReports/Unitron_2011-06-28-144753_MacBook-Pro.crash

Best Answer

Restoring any data to another partition won't affect your mac partition unless you have a serious hardware error and no amount of software steps will address that. Let's set aside errors with HD or RAM or MLB for a moment and make sure things are working.

Run a safe boot, then reboot back to OS X and dig a bit at the crashes.

Specifically, the three lines in each crash report will let you know why the system crashed each third party app.

Exception Type: EXC_BAD_ACCESS (SIGSEGV) 
Exception Codes: 0x000000000000000d, 0x0000000000000000 
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Once you get a feel for whether it's the same exception type, you can dig deeper. Like I commented - you could try repairing permissions or re-installing the latest OS X update you are comfortable (10.6.8 is the latest) but whatever you had before should rebuild any shared library code and try again with the 3PP apps.

Good luck - you will certainly learn something about how OS X apps load in this ordeal.